Fixed price • 2–4 weeks • £15–25k

Build the thing that proves
the pathway exists.

A diagnosis tells you where the constraint sits. The PoC Sprint proves the fix is real: working software in your context, built with your team, handed off cleanly.

Start a conversation

What the sprint includes

  • A working proof of concept in your context, on your data, against your real constraint. Not a demo on synthetic data.
  • Your people in the build. The sprint is a teaching vehicle as much as a delivery one; the capability transfers while the thing is being made.
  • An honest verdict. If the pathway does not survive contact with reality, you find out in weeks for £15–25k, not in eighteen months for a hundred times that.
  • A clean handoff. Code, documentation, and the decisions behind them. Yours, with no dependency on me.

I have shipped seven production AI products of my own. The sprint is the same muscle applied to your constraint: fast, honest, and designed from day one to be handed over, not to make me indispensable.

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.

Where it usually starts

Most PoC Sprints follow a diagnosis: the AI Rollout Stall Diagnosis or the Pattern Diagnostic. That is deliberate. Building before diagnosing is how pilots end up in the graveyard. If you already know exactly what needs proving, we can start with a conversation instead.

Start a conversation