Home/Pricing
Pricing
Priced per firm, not per person.
A delivery team changes shape between projects. You add a tester for six weeks, borrow a data person for the cutover, bring a partner in for the go/no-go. None of that should require a purchasing decision.
Solo
- Everything in the product
- Unlimited projects
- The method, seeded in every project
- All nine CSV templates
- Desktop and hosted builds
- Full JSON export, always
Practice
- Everything in Solo
- 5 seats included
- Extra seats at $60
- Priority support
Firm
- Everything in Practice
- 20 seats included
- Extra seats at $45 — cheaper than Practice
- Cloud projects
- Shared editing, live
- Portfolio management & dashboards
- REST API
- Mobile app
- Automations
- Onboarding session
Enterprise
- Everything in Firm
- Data residency options
- Invoiced billing
- Security review support
- Named contact
- Volume seat pricing
These lists are short on purpose. Moving up a plan buys you seats and support, not features — the estimator, the playbook, the gates, readiness scoring and full export are on Solo exactly as they are on Firm. If a pricing page has to list the same capability three times to make the expensive column look worth it, something has been held back from the cheap one.
Every plan
Every plan gets the whole method.
The playbook, the gates, readiness scoring, migration reconciliation, handover tracking and full export are on every tier, including the cheapest. There is no plan that gets a lesser version of the method.
What Firm adds is not a better version of the same thing — it is where projects live and how many people can be in one. Cloud projects, shared editing, portfolio management, the mobile app, automations and the API are the connected layer, and all of them need a server.
| Included on every plan | Solo | Practice | Firm |
|---|---|---|---|
| Seats | 1 | 5 | 20 |
| Extra Seat | — | $60 | $45 |
| All thirteen tabs | Yes | Yes | Yes |
| Unlimited projects | Yes | Yes | Yes |
| The seeded method | Yes | Yes | Yes |
| Gates & readiness scoring | Yes | Yes | Yes |
| Migration reconciliation | Yes | Yes | Yes |
| Handover tracking | Yes | Yes | Yes |
| Status report export | Yes | Yes | Yes |
| Nine CSV templates | Yes | Yes | Yes |
| Full JSON export | Yes | Yes | Yes |
| Desktop and hosted builds | Yes | Yes | Yes |
| Cloud Projects | — | — | Yes |
| Shared Editing | — | — | Yes |
| Portfolio Management | — | — | Yes |
| Portfolio Dashboards | — | — | Yes |
| REST API | — | — | Yes |
| Mobile App | — | — | Yes |
| Automations | — | — | Yes |
Questions people actually ask
Can more than one person work on a project at the same time?
Yes, on a cloud project. Several people edit the same plan with presence and live updates, so a delivery lead and two consultants can work a cutover plan together rather than passing a file around.
Cloud projects and shared editing are on Firm and Enterprise. Solo and Practice run local file projects, which are edited by one person at a time and work with no connection.
Switching a project to the cloud is a per-project choice, not a condition of using the product, and a cloud project exports to the same JSON file whenever you want it back.
What happens to my work if I stop paying?
You keep it. Projects live in a file you own — on your disk in the desktop build, exportable at any time from either build. Losing access means losing the application, not the data. That holds if you later switch on cloud storage too: one click exports a project as readable JSON regardless of subscription state.
Can I get my data out?
One click exports a whole project as JSON, including note threads, and one click reads it back. Every individual tracker also exports as CSV that opens in any spreadsheet. Leaving is deliberately easy, which is the only credible answer when you are asking a firm to put client delivery plans into a young product.
Does it work offline?
A local file project does. It links to a file on your disk and keeps working with no connection, which is what you want on a client site with poor wifi.
A cloud project needs a connection, because several people are editing the same plan. That is the trade, and it is per project rather than per plan — a Firm customer can run some engagements local and some in the cloud.
Is there an API?
Yes, on Firm and Enterprise. A documented REST API reads and writes project data, so a PSA, a BI tool or a client's own system can connect to it directly.
On every plan, data also moves in and out as CSV and JSON, which remains the right answer for spreadsheet workflows.
My projects are nothing like a system implementation. Is this useful?
Probably, if the work is phased and somebody has to sign it off. The seeded task list is written as a system implementation, but the phases, gates, readiness model and migration reconciliation are not industry-specific — they are what structured delivery work has in common.
The test is the shape, not the sector. If your engagements have a discovery, a build, a moment where something goes live and a handover at the end, this fits. If they have none of those, it does not, and we would rather say so.
How does the trial work?
Get in touch and we will set you up with the full product. Bring a live engagement rather than a toy project — the thing worth testing is whether the seeded method survives contact with a client you actually have.
Try it against a real engagement.
Not a demo project. Bring something live and see whether the plan holds up.