The two-week diagnostic

Two weeks to find where AI pays first, and what it is worth

A paid, fixed-price working engagement with your team. It ends in a build decision you can defend to a board, and a plan worth keeping, whoever you choose to build with.

Who it is for

Built and priced for organisations of 50 to 1,000 people in the Gulf, Ireland and the UK.

It fits if

  • You know AI matters and cannot get a straight answer on where it pays.
  • You have run a pilot that never reached production.
  • One process carries real volume, and someone senior owns its numbers.
  • You can give us two weeks of access to the people who do the work.

It does not fit if

  • You need a migration, a security review or a support contract. Those start with a scoping conversation.
  • You want a strategy document with no build attached. We do not sell those.
  • You want extra hands on a team. We do not sell staffing.
More than 1,000 people, or regulated

The diagnostic runs the same way, scoped to one division. See your sector.

The two weeks, day by day

Ten working days. You know on day five which processes are in the running, and on day ten what the first build costs.

  1. Day 1

    Kick-off with your sponsor and the people who run the work. We agree the scope, the access and the measures that matter.

    You get: Interviews in the diary
  2. Days 2 to 4

    Process walkthroughs, team by team. We sit with the people doing the work and record how each workflow runs: volumes, handoffs, exceptions.

  3. Day 5

    Systems and data review: what is ready, what is not, where the data lives and which rules govern it.

    You get: A shortlist of scored processes
  4. Day 6

    With your sponsor, we choose one process. Baseline measurement starts: cycle time, cost and error rate, in your numbers.

    You get: The chosen process
  5. Days 7 to 8

    The business case and the architecture: models, guardrails, approval gates, where data lives, what a regulator or auditor will ask. Where feasible, a proof of concept on your anonymised data.

  6. Day 9

    Your sponsor reads the draft readout before anyone else does.

    You get: The draft, a day early
  7. Day 10

    Readout to your leadership team.

    You get: The five deliverables

Five deliverables, the same every time

Also included: a call 30 days after the readout, to see what moved and what stuck.

  1. A process and opportunity map. Your workflows scored on value, feasibility and data readiness.
  2. One quantified business case. The single highest-leverage process, with projected cycle time, cost and error impact in your numbers.
  3. An architecture and governance sketch. Which models, what guardrails, where data lives, and what your regulator or auditor will ask.
  4. A fixed-price, fixed-scope proposal for the ninety-day build, with the run phase priced in the same document.
  5. A working proof of concept on your real, anonymised data, where feasible.

One fixed price

USD 3,000Two weeks · Five deliverables
  • No day rates and no add-ons. The price is agreed before we start and does not change. Excludes VAT where it applies.
  • The USD 3,000 is credited in full against a ninety-day build signed within 60 days of the readout.
  • The ninety-day build: fixed price, quoted in the diagnostic.

Three ways it can end

You build with us

The proposal in your hands is fixed price and fixed scope. The ninety days start the day you sign. Until then the clock is paused, and the fee credit holds for 60 days from the readout.

See how the build runs

You build it yourselves, or with someone else

The map, the business case and the architecture are yours. That is what a plan worth keeping means.

You wait

If no process clears the bar, the readout says so, and says what would have to change.

Common questions

Is the 30-minute call the diagnostic?

No. The call is free and decides whether the diagnostic is worth your money. The diagnostic is a paid, two-week engagement with five written deliverables.

When do the ninety days start?

The day the build is signed. The diagnostic's two weeks come before that, and nothing counts against you while you decide.

What do you need from us?

A sponsor who owns the decision, about an hour from each person we interview, and read access to the systems involved. We agree the list on day one.

What happens to our data?

The proof of concept runs on anonymised data.

What if nothing is worth building?

Then the readout says that. You still leave with the scored map and the reasons.

Do we have to build with you?

No. The plan is yours to keep, whoever you choose to build with.

What does the build cost?

A fixed price, quoted in the diagnostic. The proposal is one of the five deliverables, and the run phase is priced in the same document.

Can we skip the diagnostic?

If you already have one process chosen, a baseline measured and the data in order, tell us on the call and we will scope the build directly. Most organisations do not.

Do you work on site?

Often. The engineer works where the work happens: your office, your stand-ups, your systems, in your time zone.

Begin here

Start with a 30-minute call

Free. We ask what you run and what you want to change, and tell you whether the two-week diagnostic is worth your money. If it is, you leave it with a plan worth keeping, whoever you choose to build with.

Not ready to talk? See where AI would pay off first: twelve questions, three minutes.