PILOT BUILD · WHEN YOU HAVE THE MAP
You did the discovery. Now get something built.
Pilot Build is for companies that have already done Phase 0, on their own or with someone else, and are done being assessed. Bring your findings. In the first week we validate them against your data and systems. Over the next two to four weeks we build one automation, run it against real work, and hand it over live in your tenant with your team trained to run it.
$20,000 – $40,000 · 3–6 weeks · fee credits toward Phase 0 · Assess
Who this is for
The COO with an audit on the shelf. The CFO whose team already agrees which report eats every Friday. The PE operating partner whose portco produced a roadmap at the last offsite. The head of function who has run three pilots and knows which one deserved to live. You do not need us to tell you where it hurts. You need someone to build the thing, inside your systems, without a six-week detour through another assessment.
What counts as having the map
Phase 0 is a stage every AI program passes through, not a BuildClub invention. If your team has produced the five things below, you have done it, and you should not pay us to do it again.
- Interviews with the people who do the work, not only the people who manage it.
- A map of the workflows tied to revenue, delivery and risk, traced end to end, including the handoffs.
- An inventory of your data: where it lives, what shape it is in, and who can access it.
- A ranked list of friction points with a time or cost estimate against each one.
- A sequenced view of what to do first, and the reasoning.
Three of five is enough to start. The validation week is where we close the gaps, and we tell you in writing which ones we closed.
How Pilot Build runs
Week 1 · Validate. We read everything you have: the audit, the roadmap, the pilot post-mortems, the offsite notes. Two or three working sessions with your technical lead and the process owner, on their screens. We check the plan against the data and systems it depends on, and we pick the first automation together. Output: a written validation note stating what holds, what does not, and the evidence for each call.
Weeks 2 to 4 · Build. One automation, scoped tight, built inside your tenant on your identity and access. It runs in shadow mode against real work while a human reviews every action. We tune until quality meets the bar you set.
Weeks 4 to 6 · Hand over. The automation goes live. Your team is trained to run it on their own work. You receive a runbook, the monitoring view, and a short written read on what should come next and whether it belongs in Amplify or Workforce.
What you walk away with
- The validation note: what holds, what does not, and the evidence for each call.
- One production automation you own, running in your environment.
- A runbook and the monitoring view.
- A trained operator inside your team.
- A one-page recommendation for the next step, with the option to stop there.
What Pilot Build is not
It is not a substitute for discovery when there is no map. If the validation week shows the findings do not hold, we say so, show the evidence, and the Pilot Build fee credits in full toward Phase 0 · Assess. It is not Phase 2. The automation runs with a human in the loop; autonomous digital employees come later, once a workflow has earned it.
If validation shows you need the full map after all, every dollar of the Pilot Build fee credits toward Phase 0 · Assess. You are never paying twice to find out where you stand.
Pricing
$20,000 – $40,000 · 3–6 weeks
Fixed fee, scoped in the first conversation to the automation's complexity and integration depth. Preparation and the written validation note are included. If validation shows you need the full map after all, every dollar credits toward Phase 0 · Assess.
Bring the list.
We will tell you in the first conversation whether Pilot Build fits, and which automation we would build first.
Book a Pilot Build conversation →