The standard first paid engagement

Make one meaningful improvement real — and learn where to go next.

Understand where the company is most exposed or advantaged by the next generation of working, identify the highest-value place to begin, and make one meaningful improvement real.

Why not an AI audit

A list of use cases is not progress.

The standard offer in this market is an assessment: interviews, a maturity score, a ranked list of use cases, a roadmap. It ends exactly where the difficulty starts. Nobody has yet discovered whether the information those use cases depend on is actually reachable, whether the process survives contact with the change, or whether anyone will use the result.

This engagement is not that, and it is not simply a proof of concept either. A POC proves a technology works. This proves that a way of working can change and hold — because it is designed, built, adopted into the real operation and then measured against the business driver leadership named at the start.

The planning that follows is built on what that actually proved, rather than on what a workshop predicted.

How the engagement works

Eight phases, one First Win.

The engagement is gated on proof and outcomes rather than a calendar, so we do not put a fixed duration on it. Scope is agreed before it starts.

Phase 1

Align

Agree the business driver with leadership, and what a meaningful improvement against it would actually look like. Everything downstream is judged against this.

Phase 2

Understand

Targeted discovery of one strategically important operating area: how the work really happens, where the information lives, who decides what, and where it breaks.

Phase 3

Prioritise

Exposure and opportunity analysis, and an AI-first positioning baseline where it is useful. Then one First Win is selected — deliberately one.

Phase 4

Design

Design the better way of working, not just the technology. What changes for the people doing the work is usually the harder half.

Phase 5

Build

We carry the build. Where software is the answer we build it; where the answer is a changed practice, a data fix or an automation, we do that instead.

Phase 6

Adopt

Integrate it into how the business actually operates. An improvement nobody uses is not an improvement, and this is where most AI pilots quietly die.

Phase 7

Measure

Outcome evidence against the driver agreed at the start — including the honest result if it underperformed, and what that taught us.

Phase 8

Readout

The Executive Readout: what we learned, what changed, what happened, what the work exposed, and the 90-day and 12-month direction that follows from it.

What leadership provides

An executive sponsor who owns the business driver and can make decisions about how work changes. Access to the people who actually do the work in the operating area we look at — not just their managers. Access to the relevant systems and information. And a willingness to let something genuinely change.

The time commitment is real but bounded, and concentrated in the understand and adopt phases. We will be specific about it before the engagement starts rather than discovering it together later.

How the First Win is chosen

  • It matters to the business driver leadership actually named — not the easiest thing to automate
  • It is bounded enough to finish and prove, rather than becoming a programme
  • The evidence of whether it worked will be visible to leadership, not only to the team doing the work
  • It teaches us something about the operating area that makes the next decision better
  • The capability it builds is one the company keeps

What you receive.

The First Win itself — implemented and in use, not specified and handed over
The better way of working designed around it, documented so it survives staff changes
Outcome evidence against the business driver
The Executive Readout, including 90-day and 12-month direction
A clear view of what the work exposed — capability, information, workflow and architecture opportunities we found along the way
Ownership of whatever was built

The bridge to the next decision

The Executive Readout.

A bounded engagement is only worth doing if it makes the next decision better. The readout is how that happens: it turns what the work actually produced into a planning view leadership can act on.

What we learned

The business driver, the operating reality and the constraints as they actually are.

What changed

The better way of working, or First Win, that was implemented.

What happened

Outcome evidence, and what the work taught us — including where it fell short.

What the work exposed

Further capability, information, workflow or architecture opportunities the engagement surfaced.

90-day direction

The next small number of actions or investments leadership should make, with owners.

12-month direction

The broader capability trajectory and the sequencing logic behind it.

Recommended operating model

Run it internally, commission another bounded project, or establish an ongoing mandate.

An honest note on the 90-day and 12-month direction. It is a planning view built from this engagement and whatever discovery was actually performed — not a claim that your entire company has been mapped. Anyone offering you a complete enterprise architecture off the back of one bounded project is selling you a document, not a plan.

What can happen afterward.

Four outcomes, all legitimate. Three of them do not involve us continuing, and the engagement is designed so that any of the four is a fair reading of the evidence.

Run it internally

You have the improvement, the working practice and the direction. Plenty of companies should take it from here themselves, and we would rather say so than manufacture a reason to stay.

Another bounded project

The readout usually surfaces more than one opportunity worth acting on. Taking the next one as its own bounded engagement keeps every decision evidence-gated.

Defer

Sometimes the right answer is to consolidate what changed before changing anything else. We will tell you when we think that is the case.

A Fractional AI Officer mandate

Where the work has exposed a continuing portfolio worth executive accountability, an ongoing mandate becomes appropriate. It is earned at this point, not assumed at the start.

We carry the build. You keep the capability.

Whatever gets built is yours. So is the working practice designed around it, and so is the understanding of how your own operation runs that the engagement produced. We are not trying to become load-bearing — the point is that your company can keep improving how work gets done whether or not we are still involved.

It starts with a conversation about the business.

We do not scope a First-Win engagement off a web form. The Competitive Advantage Review establishes whether there is a real driver here and whether this is the right next step.