Digital & AI
Copilots, models and the data underneath them, built with your team and deployed into the systems you already run: production is the deliverable, not the demo.
£160–240k, fixed · quoted before we start
Work that production.
A demo takes a fortnight. A system your staff rely on at nine on a Monday takes twelve weeks, because it needs evaluation thresholds, a rollback, an owner and a runbook. We build the second thing, in your environment, with your engineers in the room, and we spend the first eight weeks on the data, because that is where every model we have ever seen fail actually failed.
What it is not
A system earns its place when the numbers beside it are checkable. These are, and the workings are sent on request.
Stage 03 of the method, 12 weeks of the 28.
The stages run in order, and each is bought on its own: the roadmap from stage 01 prices the rest, so nothing after it is bought blind.
Four parts, and what each is for.

Ownership, definitions, quality gates and lineage, the eight weeks nobody puts in the press release.
Scoped to one job each, with the evidence for every suggestion shown to the person acting on it.
Chosen against your data, not against a leaderboard; thresholds agreed before launch.
Into the systems you already run, behind your access controls, with a rollback.
4 steps, in this order, every time.
The data, first
One definition per field, one owner, quality gates in the pipeline, lineage from source to decision.
The thin slice
One job, end to end, in your environment and behind your access controls.
The evaluation
Thresholds agreed before launch, measured after, published either way.
The rollout
Sequenced so the worst-served users go first, not the easiest ones.
What you are holding at the end.
You leave with
Buy this when
If none of these is true yet, the audit is the cheaper place to start.

