Agree what working means.
You receive: a written scope and a measured baseline.
THE HANDOFF METHOD
Systems that
don't leave
when people do.
The Handoff Method is how I deliver every workflow I build, from the first scope to the results memo. It is the method inside Operate, and the first 90 days of Operate are the first Handoff.
Seven steps for every workflow, ending with a handoff test.
WHERE IT SITS
Architecture first. Then the workflows, in order.
Every engagement starts with Architecture: the areas of your business named in writing, the workflows in each ranked, and a named owner on every one. Operate works through that list in order.
An area is one function of the business: one team or process family with one owner, such as quoting, scheduling, billing or marketing. Marketing is an area; newsletters, social captions and review replies are workflows inside it. Each workflow goes through the same seven steps.
What you provide.
- One defined area.
- Someone who can set priorities.
- A named person to run each workflow.
No named owner, no workflow.
HOW A WORKFLOW MOVES
Scope, build,
then hand it over.
Test it against what breaks it.
You receive: the working system and a one-page AI use policy.
Prove someone else can run it.
You receive: the runbook, the results memo and every account in your name.
THE SEVEN STEPS
What happens to every workflow.
- STEP 01
The scope.
What starts it, what goes in, what comes out, where a person reviews it, the measured baseline, and a written definition of what working means.
- STEP 02
The build.
Tested against normal cases, missing information and the exceptions that break it, and checked by the people who will run it.
- STEP 03
The governance minimum.
A one-page AI use policy, a register of where AI is used, and a named checkpoint for the system.
- STEP 04
The handoff.
Training for your named owner, and a runbook covering what it does, how to tell it is broken, who owns it and how to switch it off. Every account is in your name.
- STEP 05
The handoff test.
Your named owner runs it while I watch and say nothing, then breaks it on purpose and restores it from the runbook alone. The date goes in the results memo.
- STEP 06
The warranty.
A pass rate agreed in writing before the build, held for 90 days.
- STEP 07
The results memo.
Measured against the baseline we agreed in week one.
WHAT YOU KEEP
Four things stay in your name.
How the system works.
The written instructions each workflow runs on, kept in your account.
What the system knows.
The reference material each workflow draws on, in your account and yours to update.
What the system is asked.
Every prompt the workflows use, documented so your named owner can maintain them.
The keys.
Every account is in your name, from the first day.
YOUR PART
Your judgment makes
the system fit.
You and the people who run each area explain how the work runs and agree on the standard. Your named owner is trained on the workflow and runs it from the handoff test on.
I build inside the systems you already run. If a tool needs replacing, Architecture says so in writing first. Your IT provider stays: they run the network and devices, and I take work off your desk.
Where AI fits
AI is how the work gets built. Every workflow still gets a written scope, a named owner and a runbook your people understand.
AFTER THE HANDOFF TEST
The warranty.
Then the next workflow.
Before each build, I agree with you in writing on a set of sample cases and the pass rate the workflow must hold. For 90 days after the handoff test, if the workflow falls below that pass rate on those cases, I fix it at no charge. The warranty ends if anyone else changes the workflow, its instructions or its connected tools. On Operate, upkeep is part of the fee anyway; the warranty is what you keep if you leave.
Then the next workflow in the queue starts at step one.
The first workflow is running in shadow mode within 30 days of readiness. Two are handed over within 90 days of readiness. Readiness means a named owner, system access and baseline data. The schedule pauses whenever any of those is missing.
See pricingYOUR NEXT STEP
Find the workflow worth handing over first.
In a 30-minute discovery call, I’ll look at what is stuck on your desk and whether Architecture is the right place to start.
The proof is the handoff.