How I work

Diagnose. Prove. Embed. Leave.

The whole operating model fits in four words, and the fourth one is the differentiator. I am a drop-in operator: I find what is stuck, prove the fix is real, embed it in live use, and go. It holds without me.

How every engagement runs

Diagnose

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

Prove

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

Embed

Get it into live use with your people, on real cases, until it is load-bearing without me in the room.

Leave

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.

What I do

  • Diagnose where the constraint actually sits, with evidence you can defend upwards.
  • Build the proof of concept that shows the pathway exists, with your people in the build.
  • Embed it in live use, on real cases, until it holds without me — that is what makes leaving safe.
  • Leave on the date we agreed, with everything handed over.

What I don't do

  • Open-ended delivery. I do not become your dev lead, your interim head of anything, or a permanent body on the org chart. Embedding the capability is the job; embedding myself is not.
  • Open-ended retainers. Every engagement has a defined end written into it from day one.
  • Frameworks as products. You will not get a branded methodology with a workbook. You will get a diagnosis.
  • Implementation armies. If the work needs twenty consultants, I am the wrong shape and I will say so.

The honest reason: my strength is the diagnosis, the proof, and getting it adopted — then leaving. What I am not is a twenty-body implementation army for an eighteen-month build; if the work needs that, I will say so and point you elsewhere. The engagement is built to end when the thing is load-bearing, not to run indefinitely. That defined end is a feature for you.

Fixed prices, published

Every standard engagement has a public fixed price, from the free 3-minute survey to the £22–30k Embed Sprint. You can see the whole ladder, qualify me in or out without a sales call, and forward the page to whoever signs it off.

See services & pricing

Common questions

What kind of organisations do you work with?

Organisations where progress has slowed, not because people aren’t capable, but because the system has reached its limits. That ranges from Series A scale-ups whose AI adoption has plateaued, to large regulated organisations whose transformation isn’t landing, to funds and accelerators with stuck portfolio companies.

How is this different from a management consultancy?

I don’t sell frameworks or methodology. I diagnose what’s structurally stuck, name it clearly, and help you redesign how work, decisions, and learning actually flow. And unlike most consultants in this space, I actually build AI products, so the advice comes from practice, not theory.

What does it cost?

Every offer has a public fixed price: the Maturity Review is £750, the AI Maturity Diagnosis £4,500, the Pattern Diagnostic £8–12k, the PoC Sprint £15–25k, and the Embed Sprint £22–30k. The full ladder, including the free 3-minute survey, is on the services page. Bespoke work happens, but it starts from these shapes.

Do I need to have started an AI initiative already?

No. Some clients come to me because their AI adoption isn’t landing. Others come because their transformation ran out of road long before AI entered the picture. I work at the intersection. The operating model problems are often the same regardless of whether AI is involved yet.

What does a typical engagement look like?

Diagnose, Prove, Embed, Leave. It starts with a conversation, then usually a fixed-price diagnostic. If the diagnosis points to something worth building, that is a separately scoped sprint — and getting it adopted is its own separately scoped sprint that closes on an adoption checkpoint, not an open-ended tail. The decision to continue is always yours. I work fixed-price by default, day-rate by exception.

Why don’t you publish client names or case studies?

Because the work is confidential and I take that literally. Even anonymised case studies leak. The evidence I offer instead is public and checkable: the products I’ve shipped, the book, the SETsquared role, and several years of published thinking you can read before we ever speak.

Remote or on-site?

Remote by default, on-site when the work needs it. I’m based in Wiltshire, UK, and work UK-first.

What if you can’t help?

I’ll say so, usually in the first conversation. A worthwhile chunk of my referrals come from people I told "this isn’t my problem to solve", so the incentive to be honest is real.

Sound like the right shape?

A short conversation is usually enough to know whether I can help.

Start a conversation