Fixed price • 3–6 weeks • £22–30k
A PoC proves the pathway exists. This is the mile after — getting it into daily use with your people, on real cases, until removing it would be noticed. Then I leave, because it holds without me.
Most AI projects have zero users six months after the demo. Not because the tech failed — because the last mile never got walked. This rung walks it.
The checkpoint cuts both ways: it needs your people on real cases from week one. That is a commitment you make going in — the sprint cannot close on usage nobody has time to give it.
How every engagement runs
Find where the constraint actually sits. Not where the org chart says it should be.
Build the thing that proves the pathway exists. Working software, not a slide.
Get it into live use with your people, on real cases, until it is load-bearing without me in the room.
Every engagement has a defined end. Extension is your choice, never my pitch.
I leave, and it keeps running. If you want a consultant who moves in for eighteen months, I am the wrong person — the whole point is that you don't need me.
The Embed Sprint follows a PoC Sprint — you don't embed something you haven't yet proven. If the proof already exists (yours or someone else's) and it is gathering dust, we can start from there.
How it differs from its neighbours: the Operating Model Redesign Sprint changes how your organisation decides and learns; the Embed Sprint gets a proven build into daily use. And if what you want is the truth on call while you run the adoption yourself, that is Advisor on Call — this sprint is for when you want the last mile walked with you, to a checkpoint.
To be clear about the word: embedding the capability is the job; embedding myself is not. A consultant who moves in for eighteen months is the opposite of this. The sprint ends when the usage bar is met — and then I go.