Fixed price • 90 minutes • £750

Find where your AI rollout will stall.
Before you spend.

A structured 90-minute pre-mortem on the rollout you're about to run. You leave with the three places it is most likely to stall — verification, workflow joins, decision rights — and what to design differently now. From someone who diagnoses the failures for a living.

£750, credited in full against a PoC Sprint or workshop cohort within 60 days.

Where rollouts stall

I spend most of my time diagnosing AI 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:

Verification

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.

Workflow joins

The AI does step three brilliantly while steps two and four still assume a human. Pilots die at the joins, not in the model.

Decision rights

When the output is wrong, whose name is on it? If nobody can answer before launch, the rollout stalls at the first mistake.

The pre-mortem is the stall diagnosis run early — the same questions, asked when changing course costs a conversation instead of a write-off. The cheapest stall to fix is the one that never happens.

What you get

Your three most likely stall points, named

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.

What to design differently, now

The changes that cost a conversation today and a write-off in twelve months: the verification step, the workflow join, the accountability line.

A next step only if it earns itself

The £750 is credited in full against a PoC Sprint or a workshop cohort within 60 days. If the session is all you need, that was the engagement.

How every engagement runs

1

Diagnose

Find where the constraint actually sits. Not where the org chart says it should be.

2

PoC

Build the thing that proves the pathway exists. Working software, not a slide.

3

Teach

Transfer the capability to your people while it is being built, not after.

4

Leave

Every engagement has a defined end. Extension is your choice, never my pitch.

I leave. The capability stays. If you want a consultant who embeds for eighteen months, I am the wrong person.

Questions you are probably asking

How is this different from the Stall Review?

Same 90-minute structured session, same diagnostic muscle, run at the opposite end of the timeline. The Stall Review works out why a rollout stopped. The pre-mortem finds where yours would stop, while changing course still costs a conversation.

We haven’t committed budget yet. Is this premature?

This is exactly when it pays. The three stall points — verification, workflow joins, decision rights — are cheapest to design for before tooling is chosen and pilots are promised. After that, every fix has an audience.

What do you need from us?

One conversation with the person who owns the rollout, and whatever plan exists — a deck, a budget line, or a strong intention all work. The session is structured; you do not need to prepare materials for it.

What happens afterwards?

You own the write-up and can act on it without me. If you want the capability built with your team, the credit applies to a workshop cohort or a PoC Sprint within 60 days. Extension is your choice, never my pitch.

Ninety minutes now, or a post-mortem later.

£750 fixed, credited against the work that follows. Your three stall points named, before they cost anything.