Budgeting it to zero
The single most common Amplify failure is budgeting Phase 4 at 10% of Phase 3. A good Amplify is 25–40% the cost of Build. If the budget assumes Amplify is free, it will be skipped.
III.Flame
04 · Flame · Two to four weeks
Amplify
The phase most consulting firms skip.
Amplify is adoption. Two to four weeks of internal training, SOP documentation, launch communications, and explicit decommissioning of the old workflows. It is the single most-skipped phase in the consulting industry and the single biggest reason transformations quietly die in year two.
What it is
A dedicated phase focused entirely on making sure the system Build produced is actually used. We train your team, write the SOPs, name the owners of each workflow, run launch comms internally, and sit with your operators during their first real week of live use. A system nobody uses is worse than no system at all.
What it is not
Amplify is specifically not:
- Not external marketing launch comms. That's a different kind of amplify, and we do it in Creative Alliance if it's needed.
- Not a one-hour lunch-and-learn. Real adoption takes days of hands-on co-work, not a slide deck.
- Not optional. Budget for Amplify or budget for a dead system in twelve months.
You leave with
Adopted systems, documented workflows, named owners
Team training completed. Written SOPs for every new workflow, in plain English, versioned and stored where your team will actually find them. A named owner on your team for each new system. Explicit decommissioning of the legacy workflows — nothing runs in parallel after Amplify closes.
Why Amplify exists
Across the consulting industry, the pattern is identical: a firm ships a beautiful system in Phase 3, holds a champagne-style go-live meeting, collects final payment, and vanishes. Ninety days later, half the team has reverted to the old spreadsheet and the new systems has stale data. The system didn't fail — the adoption did.
Amplify is the correction. It is a <em>phase of the engagement</em>, not an afterthought. It has its own timeline, its own deliverables, and its own success criteria.
The three Amplify workstreams
Adoption has three parts that happen in parallel:
- Training — hands-on co-work with the operators who will use the system, in the context of real work, not a sandbox.
- SOPs — plain-English written standard operating procedures for every new workflow, versioned in a place the team will actually find.
- Decommissioning — explicitly turning off the old workflows. If the old spreadsheet still opens, the team will default to it.
The named-owner rule
Every new workflow needs a named owner on your team — not a title, a person. That person's job is not to run the workflow (the system runs the workflow); it's to notice when something drifts and raise a flag. Without named owners, systems decay silently.
Where it fails
Running it without the operators
Amplify without the daily operators in the room is just training the managers. The people who actually use the system have to be in every hour of it.
Not decommissioning the legacy system
If the old spreadsheet, systems, or workflow still technically works, the team will default back to it under pressure. Decommissioning is mandatory, not cosmetic.
Phase 4 Amplify — FAQ
Why is Amplify a separate phase and not part of Build?
Because adoption requires different work, different timelines, and different people than construction. Collapsing it into Build is the single biggest reason transformations fail after handoff. It needs its own budget line.
How long does Amplify take?
Two to four weeks. Fewer than two and you haven't sat with the team long enough; more than four and you're creating dependency instead of adoption.
Can we do Amplify ourselves without you?
Yes, if you have a strong internal operations lead with time to dedicate and a history of running change management. For most SMBs, the answer is no — the operations lead is already the bottleneck, which is why you hired a consultant.
System built but nobody's using it?
We engage on Amplify as a standalone rescue for transformations that shipped in Phase 3 but never adopted. Two to four weeks. Fixed price. Your team running the system by the end.
Get your time back.
Nicholas runs this studio on it. Mobile speed went from 49 to 92. We run on it too.