/runbook · 4 steps
How an engagement runs.
Every build follows these four steps. Each one ends with something in your hands, so you can stop after any of them and keep what you have.
01
Diagnose
We sit with the people who do the work and watch how it gets done: the inbox, the spreadsheets, the handoffs. You get a short list of what's costing you the most, with numbers.
typical · one call plus two days
you getA one-page findings note with the costs ranked
we needTwo hours with the person who does the work today
02
Design
One page per system: what it does, what it won't do, what it costs, and how you'll know it's working. Nothing gets built until you've approved that page.
typical · two to five days
you getA spec with a price on it
we needOne decision-maker who can say no
03
Build
You see it handle last month's work before it touches this month's. We demo weekly and keep a decision log you can read. Every system ships with checks that confirm it did the work correctly.
typical · two to eight weeks
you getA running system with its checks and runbook
we needReal historical cases, including the messy ones
04
Run
Your business changes and the system has to change with it. Either we keep it running and watch the checks, or we hand it to your team with the documentation. You can switch later.
typical · ongoing, or one handover week
you getA system we monitor, or a documented handover
we needA named owner on your side
who owns the system at the end? straight answers →
advisory runs differently one to three sessions and a written plan →
Step one is a call.