Home/Solutions
Solutions
Built for firms who deliver, not firms who coordinate.
The common thread is not company size or platform. It is whether your work has phases, a sign-off at the end of each one, and a moment where somebody has to decide it is safe to switch on.
By firm
Three shapes this fits.
Solo consultants
One person, several clients, and no project manager to delegate the plan to. The seeded method matters most here because there is nobody else to build it.
- Estimator sized before you quote
- A status report you did not spend Friday on
- Handover tracking so old clients stop calling
- Single-user is not a limitation for you
Solo · $149/mo
Boutique practices
Three to ten people with two or three go-lives running at once. The pressure is knowing which project is actually in trouble, early enough to move somebody.
- Same dashboard shape on every engagement
- Unstaffed hours surfaced on each project
- One method rather than per-consultant habits
- Readiness scored the same way every time
Practice · $499/mo for 5 seats
Delivery firms
Twenty or more people and a methodology that exists on paper. The problem is not writing it down — it is that nobody runs projects out of the document, and nobody can see across the book of work.
- Load your method once, start every project from it
- Portfolio dashboards across every live engagement
- Cloud projects and shared editing for teams on one plan
- Readiness compared like for like across go-lives
- A REST API into your PSA or BI stack
- Extra seats cheaper than on the tier below
Firm · $1,199/mo for 20 seats
Examples
The method is about the shape of the work.
Discovery, design, build, test, train, cut over, stabilise. That sequence and its sign-offs hold whatever sits at the end of it — a system, a facility, a programme, a regulated change. What differs is the wording of individual tasks.
System implementations
The seeded task list is written as a system implementation, so this shape starts closest to ready. Firms run it on ERP, finance, warehouse and CRM rollouts including NetSuite, Dynamics, Acumatica, Intacct and SAP.
Transformations and migrations
The phase structure, the gate positions, the readiness dimensions and the migration reconciliation model carry over with task wording edited — a pass over a CSV rather than a rebuild. A data migration with counts to reconcile and a cutover to rehearse behaves the same whatever is being migrated.
Programmes and regulated change
Any phased engagement with a cutover and a sign-off: a compliance programme, a site or facility opening, a regulated change, an operational transformation. The further from a system implementation, the more of the 88 tasks you replace — at some point you are using the trackers rather than the seeded method, which is still a reasonable trade.
By role
What each person opens it for.
The delivery lead
Opens the dashboard daily. Wants four numbers before a client call: how complete, how many gates open, how many risks live, how many P1s. Spends Friday afternoon on the status report and would like that back.
The practice principal
Cares about margin and staffing across everything, not one engagement. Uses the estimator before a proposal, the margin calculator when a discount is requested, and the portfolio dashboard to find out which engagement is quietly under-resourced before it becomes obvious.
The person accountable for the go-live
Needs the readiness score, the migration reconciliation state and the open P1 count in one place, because those three are what the go/no-go conversation is actually about and they are usually in three different documents.
The one who has to leave cleanly
Post go-live, wants every ongoing responsibility named, assigned to a real successor and verified once before the engagement closes. Wants no calls in April about a portal renewal.
Not sure it fits your work?
Describe the engagement you run. If the answer is that a spreadsheet is doing fine, we will say so.