Home/Product
Product overview
Fifteen tabs. One project file.
Two of them belong to the sale. Thirteen belong to the delivery. All of them read and write the same file, so a number typed once is a number everywhere.
The map
Where everything lives.
The sidebar has two groups. Sales and scoping is shared across every project you run. The rest belongs to whichever project is open.
Sales & scoping
Shared across all projects. This is where an engagement gets sized before it is sold.
- Estimator — a module list becomes hours, price, duration and gross margin.
- Margin Calculator — test a rate, an hour count, a discount and an acquisition cost against your cost basis.
Per project
Thirteen tabs, in this order.
- Dashboard — weighted percent complete, open gates, open risks, open P1 defects, phase progress and the readiness donut.
- WBS & Phases — the plan. Four editable columns, everything else derived.
- Timeline — the Gantt, laid out from the phase plan and task hours.
- RAID Log — risks, assumptions, issues and dependencies, scored 1 to 9.
- Issues & Decisions — the dated, numbered record you will want in month nine.
- UAT Tracker — scenarios, pass or fail, severity, tester, retest.
- Data Migration — object by object, source against loaded, variance and reconciliation.
- Budget — planned against actual by phase, with contingency carried separately.
- Workforce & RACI — rates, capacity, allocation, utilisation and the RACI matrix.
- Readiness — the weighted go/no-go scorecard.
- Handover — ongoing responsibilities and who takes them.
- Status Report — the client-facing document, built from everything above.
- Import / Export — CSV in and out, and the full project as JSON.
| Task | Base | Scope× | Planned | % |
|---|---|---|---|---|
| 3.4 Revenue recognition plan design | 40 | 1.5 | 60 | 70 |
| 3.5 Three-way match process design | 24 | 1.0 | 24 | 100 |
| GATE — Design Sign-Off | 4 | 1.0 | 4 | 100 |
| 4.1 UAT: GL, AP, AR and period close | 60 | 1.5 | 90 | 46 |
| 4.2 Defect triage and rework | 32 | 1.5 | 48 | 20 |
Engagement mode
Advisory or delivery, from one plan.
The same engagement costs different amounts depending on whether you are building it or watching someone else build it. Rather than maintaining two task lists, tasks carry a mode and the whole plan re-prices on a toggle.
- Delivery multiplies module hours by 1.0. You are doing the implementation.
- Advisory multiplies by 0.7. The client builds, you direct and assure.
- Tasks tagged Both always count. The rest filter by the mode you are in.
Switching the toggle changes which tasks appear, what the estimator returns, what the budget plans for and what the resource demand looks like — in one move, at the top right.
What the toggle moves
| Number | Advisory | Delivery |
|---|---|---|
| Tasks in scope | Filtered | All |
| Module hour multiplier | ×0.7 | ×1.0 |
| Planned hours | Recalculated | Recalculated |
| Budget & margin | Recalculated | Recalculated |
| Resource demand | Recalculated | Recalculated |
Notes
A note that survives the re-upload.
Every row on every tracker takes a note thread. The thing that makes them useful is where they are anchored.
Keyed to the item
A note attaches to a business key such as wbs::1.4, not to a row position. Sort the grid, delete rows above it, re-import the whole file from CSV — the note is still on task 1.4.
Stamped
Date and author on every entry, so the reason a date moved in March is still readable in September, in the words of the person who moved it.
Travel with the project
Notes come along on a full project export and can be exported on their own. They do not ride in a per-tracker CSV, which keeps client-facing exports clean of internal commentary.
Two builds, one source
Desktop or browser.
The same application, built two ways from one codebase. Which one suits you is mostly a question of whether you want a file on disk.
Desktop
Links to a .json file on your own disk and autosaves about a second after you stop typing. A coloured dot in the sidebar tells you the truth about the connection at all times: green saved, amber reconnect needed, grey with red text when a write actually failed.
- Works with no connection once it is open
- No account to lapse mid-project
- File lives wherever you put it, including a synced drive
- Needs the File System Access API — Chrome or Edge
Hosted
Runs in any modern browser with nothing to install. Work is held in browser storage and comes out as a downloaded export whenever you want a copy, which makes it the right choice on a locked-down client laptop.
- Nothing to install or approve
- Any modern browser
- Export downloads the project file
- Keeps working once loaded, but is not an offline app
See it against your own engagement.
Bring a live project. We will load your phases, your tasks and your migration objects and you can decide from there.