Skip to content

The method, in full, before you buy any of it

The full method: the timelines, what we need from you, the named risks, and what happens when the test fails.

SIX PHASES QUOTED, NOT PRICED ENGLISH AND SPANISH

  1. 01 SCOPE30 MIN
  2. 02 AUDIT2 TO 3 WKS
  3. 03 PROOF30 DAYS
  4. 04 BUILD4 TO 10 WKS
  5. 05 HANDOVER30 DAYS
  6. 06 RUNNINGMONTHLY

Why this is published

The research keeps landing in the same place. MIT research, the NANDA project, put the share of AI pilots producing no measurable return at roughly 95%. RAND's interviews found the failures organisational rather than technical: the thing got built and nobody changed how they worked.

So the method is built around one thing: the system getting used. Training is a deliverable, not an upsell. The test is signed before the build is paid for. Every paid step has an exit, described here instead of discovered later. And it is published so you can read it without talking to us.

Industrial infrastructure receding into shadow, hard edges against a pale sky
Systems that keep running

The six phases

01 SCOPE CALL 30 MINUTES NO FEE

  1. 01 SCOPE 30 MIN
  2. 02 AUDIT 2 TO 3 WKS
  3. 03 PROOF 30 DAYS
  4. 04 BUILD 4 TO 10 WKS
  5. 05 HANDOVER 30 DAYS
  6. 06 RUNNING MONTHLY

  1. Scope call

    What the process is, who runs it, how often, in which language. You ask whatever you want. Thirty minutes, with the people who would do the work, and you leave with a straight answer either way: worth doing or not, and which of the six groups it sits in.

    02 AI AUDIT TWO TO THREE WEEKS PAID

  2. AI Audit

    Optional, and most people should take it. Skip it if you already know exactly what you want built.

    • Where you stand in AI answers and in search, and the gap against three rivals.
    • A check of your operations for the most valuable automations.
    • The three best opportunities scoped for any supplier, a 90 day plan, a recorded walkthrough.

    The fee, and how it credits toward later work, are set out on the Audit page.

    03 PROOF STEP TWO ROUTES

  3. The proof step

    Monthly growth systems open with a first month that proves them. The output agreed in writing, the test signed before it starts.

    Builds open with a paid pilot on one process. Two to four weeks, the test signed before the build is paid for.

    04 BUILD FOUR TO TEN WEEKS

  4. Build

    • Mapping with the people who do the work, where the real problem surfaces.
    • Build and integration with the tools you already run.
    • Fixed scope, fixed fee. If scope changes, we requote before we build.

    05 HANDOVER AND TRAINING 30 DAYS OF SUPPORT

  5. Handover and training

    • Training in their language, on their own work.
    • A written handover at go live, by default.
    • Thirty days of help while it becomes routine. The research says this phase decides whether the previous four mattered.

    06 RUNNING IT MONTHLY

  6. Running it

    A monthly report in plain language: what ran, what it produced, what changed, what we would change next, every line tracing to something you can open. Builds carry optional monthly upkeep. You can stop, and everything from 05 stays yours.

What we need from you

The half of the method most process pages leave out, and the half that decides the timeline.

  1. One named decision maker who can say yes.
  2. The people who do the work, in the mapping. Without them we map what management believes happens.
  3. The material we work from: content and voice for growth, logins and a walkthrough for a build.
  4. A named reviewer who reads what we send, in the language it ships in.
  5. What you have already tried, straight. It saves weeks.

If access slips, the timeline slips, and we say so in the weekly note.

READ

The risks, named now rather than later

  • Nobody uses it

    The most likely failure by a distance. Training and after-launch help sit inside the scope, and the map is built with the people who will use the system.

  • The process is the problem, not the software

    Sometimes the answer is to reorganise the work and automate less. We say it even when it is the smaller invoice.

  • The data is messier than anyone thinks

    A system inherits the mess you point it at. We look for it in the audit and again in the pilot.

  • Two languages doubles the review, not the production

    Producing bilingual output is cheap. Checking it is not, and that cost sits inside the scope rather than surfacing in month two.

  • The calendar

    Your diary is half of the timeline.

If the test fails

A first month that misses its test: the term does not start, you owe nothing more, and you keep what was made. A pilot that fails: no build follows, and the fee stands, because the pilot bought the answer and the answer arrived. A build that goes live and gets ignored: that is on us, and phase 05 exists to prevent it.

A TEST AGREED IN ADVANCE NOT A GUARANTEE

What we sign is a test on the part we control: what gets delivered, by when, in which languages, checked by whom. Never a percentage of your revenue or your leads, because your market holds no honest baseline for one.

Three things we do, every time

  1. We put our name to the work, the compliance and the signed test: the part we control.
  2. We scope, then we price. A band you have to guess your way into is not information; every figure is a real figure for your business.
  3. We publish only what we can show the source of: one case study in full, counts and all.

Where this starts

Tell us the process and who runs it. We take it from there.

Book a call

Read next