Fixed price • 2 days • £4,500
Two days on the rollout you're about to run. You leave with one document: where the constraint will move when it ships, and the three things to change before it does. From someone who runs the post-mortems for a living.
£4,500 fixed, one invoice. The £750 Maturity Review is credited in full against it within 30 days.
I spend most of my time diagnosing rollouts after they stall, and the post-mortems rhyme. Pilots rarely die in the model. They die in three places, none of which appear in a demo:
Who checks the output, and is that cheaper than doing the work? Most rollouts never ask, and the answer arrives later as senior-management overload.
The new thing does step three brilliantly while steps two and four still assume the old way. Pilots die at the joins, not in the model.
When the output is wrong, whose name is on it? If nobody can answer before launch, the rollout stalls at the first mistake.
The mechanism has a name, constraint migration: speed up one part of the work without redesigning the rest and the limit does not disappear, it moves. The pre-mortem finds where it will move before you have paid to find out.
AI is the most common reason the meeting happens. It is not what moves the constraint. Anything that makes one part of the system faster or different without redesigning the rest does the same thing, so the same two days apply to:
Sometimes the honest answer is that more technology would make it worse. The document says so when it is true.
Before anything
One conversation with the person who owns the rollout, and whatever plan exists. A deck, a budget line, or a strong intention all work. Nothing to prepare.
Day 1 to 2
Four to six conversations with the people closest to the handoffs the change will touch. Not a workshop, not a survey. The point is to find the next constraint, not audit the last one.
Within a week
One document: where the constraint will move when this ships, and the three things to change before it does. If a partner introduced me, they get the same paper you do.
Then I leave
You own the document and can act on it without me. If you want the changes run rather than recommended, that is a separate rung and your decision.
Not a generic checklist. The specific places your rollout, in your organisation, is most likely to stop, mapped against the patterns I diagnose for a living.
The changes that cost a conversation today and a write-off in twelve months: the verification step, the workflow join, the accountability line.
Two days, one paper, no implementation tail. Generous enough that a capable team could act on it alone, and most do.
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.
Same two days, same diagnostic muscle, run in opposite directions. The Diagnosis measures how far an adoption has actually got and what stopped it moving. The pre-mortem finds where the next one would stop, while changing course still costs a conversation.
This is exactly when it pays. The three stall points are cheapest to design for before tooling is chosen and pilots are promised. After that, every fix has an audience.
Access to four to six people across the handoffs the change will touch, and whatever documentation already exists. Remote by default; on-site by arrangement.
You own the write-up and can act on it without me. If the document points at something worth building, a PoC Sprint or a workshop cohort is the next shape, each with its own fixed price. Extension is your choice, never my pitch.
Putting this at the front of your own proposal to a client? The partners page describes exactly what happens when you introduce me.
£4,500 fixed. Where the constraint will move, and the three things to change, before any of it costs anything.