Home/Playbooks
Playbooks
A method, not a template.
A template gives you column headings. A playbook gives you the eighty-eight things that have to happen, in the order they have to happen, with the sign-offs that stop a bad go-live and the trackers already populated to catch what goes wrong.
Available now
One playbook, and it is a real one.
We would rather ship one method that has actually been used than five that were generated to fill a page.
In development
Two more, honestly labelled.
These are being written. They are not in the product today and we are not going to put invented task counts on them to make the page look fuller.
Client onboarding
Kickoff through first invoice. Contracting, access provisioning, discovery, systems setup and the 30-day check-in — the engagement shape that sits in front of every delivery project and never gets a plan of its own.
System selection & RFP
Requirements gathering, vendor long list, scripted demonstrations, a scoring matrix that survives contact with a steering committee, and the recommendation pack at the end.
Want one of these sooner, or a different one entirely? Tell us what you run — the order they get built in is driven by what firms actually ask for.
Bring your own
Your method, loaded once, reused forever.
Most firms that have been delivering for a decade already have a method. It lives in a spreadsheet somebody maintains, gets copied at the start of each engagement, and drifts into nine slightly different versions.
Because every tracker imports from CSV, yours becomes the thing you start from instead.
Export your current plan
From a spreadsheet, a scheduler, whatever you keep it in now. You need task names, phases, hours and roles.
Map it to the WBS template
Sixteen columns, of which only two are required. Fill the ones you have and mark your gate rows with the gate flag.
Import and check the preview
Nothing is written until you approve what it says it will do.
Export the whole project as JSON
That file is now your firm's starting point. Every new engagement begins from it.
What transfers between platforms
The phase structure, the gate positions, the readiness dimensions and the migration reconciliation model are not industry-specific. What changes between one engagement and the next is the wording of individual tasks and which workstreams exist.
That is a find-and-replace on a CSV, not a rebuild.