Execution Blueprint™ · Start here

Know exactly what to automate.
In ten business days.

A fixed-price diagnosis of where your team's hours actually go. Every workflow mapped, every manual task scored by what it costs you, and a costed roadmap you own — whether you build it with us or not.

$1,099Fixed price · no variation
10Business days, start to handover
4–6 hrsOf your time. One person.
The real problem

You don't have an AI problem.
You have a where do we start problem.

Almost nobody who calls us is short of ideas about AI. They are short of a way to rank them. Some version of this is usually true:

  • Someone sent round a list of AI tools. Nobody could say which one solves what.
  • A pilot ran, demoed well, and quietly stopped being used.
  • You know the team loses hours to re-typing, but not how many, or which hours.
  • Two vendors quoted. Neither had seen a single one of your workflows.
  • The budget exists. What it should be spent on first does not.

None of that is a technology problem. It is a measurement problem. Nobody has counted what the manual work costs, so nobody can say which fix is worth doing first. The Blueprint counts it, in ten days, for $1,099.

What actually happens

One plan in ten days.
Not a single slide deck.

Most of the work is ours. You are needed on three of the ten days, for four to six hours in total. The ten days start after the free 30-minute discovery call, not during it.

  1. Days 1–2Your time

    We watch the work happen

    Day one is a 90-minute kickoff — the engagement proper, not the free discovery call — where you walk us through how work actually moves rather than how the org chart says it does. Then we sit with the people doing it and time it, with a stopwatch, at their desk.

    OutcomeA timed baseline

    Real durations for the work you are about to automate. Everything downstream is measured against these, which is why they are timed rather than estimated.

  2. Days 3–4

    We read your systems

    Read-only access to what you already run. No migrations, no installs, no new licences, and nothing switched on. We are looking at where data stops and a person starts.

    OutcomeSystem inventory

    Every tool in the path of the work, what it holds, and which handoffs between them are being done by hand.

  3. Days 5–6

    We draw how work really moves

    Every workflow documented end to end, including the ones nobody wrote down: the workarounds, the shadow spreadsheet, the step that only one person knows.

    OutcomeOperations Map

    Clients routinely tell us this document alone was worth the fee, because it is the first time the whole operation has been on one page.

  4. Days 7–8

    We score it and cost it

    Each manual task ranked by hours lost, cost of error, and effort to fix. Then what each automation costs to build and what it returns, with the arithmetic shown rather than asserted.

    OutcomeOpportunity Scorecard

    Not our opinion of what is interesting. A score with its inputs visible, which means it is a score you can argue with.

  5. Days 9–10Your time

    You challenge it, then you keep it

    A 60-minute draft review where you attack the numbers before they are final. On day ten, a walkthrough with your leadership where we defend the math live.

    OutcomeThe Execution Blueprint

    Everything above, assembled into one plan: what to build first, what it costs, what it returns, in what order. Board-ready. Yours to keep and yours to execute — with us, with another team, or with nobody.

One deliverable, not five. The operations map, the scorecard and the costed roadmap are the parts of the Blueprint, not separate reports to chase — they arrive together on day ten, as one plan you can hand to a board or to another team.

So there is no confusion

This isn't a consulting engagement.
It's a diagnostic.

The difference is whether the document is allowed to tell you no.

It has told clients not to build

In writing, on day ten. That is the entire reason to pay for a diagnosis instead of accepting a free one from somebody who only gets paid if the answer is yes.

No strategy deck

No maturity models, no "AI readiness" score, no framework diagram with your logo in the corner. One plan you can act on, or hand to somebody else to act on.

Fixed price, fixed scope

$1,099, agreed before day one. If the work takes us longer than we judged, that is our cost and not your invoice.

Every number survives a room

The walkthrough on day ten is with your leadership, not with the person who briefed us. Anything that cannot survive that conversation does not go in the document.

You own all of it

Roadmap, operations map and scorecard. Execute with us or without us — we would rather be worth keeping than hard to leave.

How it starts

From call to plan in three steps.

01

Discovery call

30 minutes · free

We ask what the work looks like and you ask what this is. Nothing is charged and nothing is committed. If the answer is that automation is not your problem, we say so here — before you have paid anything.

02

The Blueprint

10 business days · $1,099

The diagnosis. It opens with a 90-minute kickoff on day one — a different meeting from the discovery call above. Four to six hours of one person’s time in total, and the finished plan on day ten.

03

Build, or do not

Your call

If the roadmap says build, it is already scoped and sequenced, and a build runs $4,500–$9,500. If it says do not, you have the document that says why.

The arithmetic

The cost of not knowing.

One workflow. 10 manual hours a week, at a $45 loaded hourly rate. This is what it costs while it goes uncounted.

$450Per week
$1,950Per month
$23,400Per year
$1,099To find out, once

Your real baseline gets measured during the Blueprint, not estimated in a sales conversation. This is the shape of the arithmetic, not a quote — and it is one workflow out of the twelve we look at.

Before you book

Is this for you?

We are not the right answer for every business, and the cheapest place to find that out is this list rather than day ten.

The Blueprint works when

  • A workflow runs many times a week, not many times a year
  • The steps are repetitive and the rules can be written down
  • The inputs arrive as documents, emails, forms or records
  • Somebody could tell you roughly how long it takes today
  • The work matters enough that fixing it would be noticed
  • You have 10 to 500 people and an operations function that is stretched

Call someone else when

  • The work mainly needs judgment, relationships or genuine creativity
  • The process changes fundamentally every time it runs
  • You want a strategy document for a board rather than a build plan
  • You need a decision this week — the diagnosis takes ten business days
  • You are looking for the cheapest quote rather than the right first build

If the work mainly needs judgment, hire a person. We will tell you that on the discovery call rather than on day ten, and we will not take the fee to say it.

Step one

Book your discovery call.

Thirty minutes, no obligation, no pitch deck. Bring the process that annoys you most. If the Blueprint is not the right answer for you, we say so on this call rather than after you have paid for one.

Would rather write it down? Send us the details instead →

Before you decide

The questions we get asked.

What does the Execution Blueprint cost?

$1,099, fixed, agreed before we start. There is no variation, no hourly overage and no change order. We price it at cost recovery rather than margin, because it exists so that neither of us commits to a build on a guess.

How long does it take?

Ten business days from kickoff to handover. You are needed on three of them — a 90-minute kickoff on day one, a shadowing session, and a 60-minute draft review on day nine — for four to six hours in total, from one person. The free 30-minute discovery call happens before any of that and is not part of the ten days.

Who needs to be involved from our side?

One coordinator who can open doors, plus access to the people who actually do the work. We do not need your IT team, a committee, or a steering group. We do need the person who knows where the spreadsheet is.

Do we need our data or processes cleaned up first?

No, and that request is usually how automation projects die before they start. We work with the operation as it exists, including the inconsistent naming and the workbook with four tabs nobody understands. Documenting how work actually flows is part of the Blueprint, not a prerequisite for it.

What if the answer is that we should not automate?

Then that is what the document says, and you keep it. The Blueprint has told clients not to build, in writing. If we can see it on the discovery call we will tell you there instead, and not take the fee.

What happens after day ten?

Nothing, unless you decide otherwise. The Blueprint is yours to keep and yours to execute, with us or with any competent team. If you do build with us, the roadmap inside it is already scoped and sequenced, and builds run $4,500–$9,500.

Is this just a sales process for the build?

It is a paid diagnosis that a competitor could execute. That is the test we hold it to: if the roadmap is only useful to us, it is not a roadmap, it is a proposal with a fee attached.

Ten days from now, you could have a plan.

$1,099 fixed. Four to six hours of one person's time. Yours to keep either way.