Build ยท Build Sprint
One decision line, built start to finish, on tools you already own.
Four to eight weeks, fixed fee, on one line. Build does not start until both sides have signed what done looks like.
What it is
Built to the line, and nothing past it
We build one decision line, test it against acceptance criteria both sides signed before build started, and hand it over running on tools you already own. The spec goes in your own drive in plain language, so the line survives any vendor shutting down.
The note written at the line during Line Mapping, what the decider needs in front of them, is the build specification. Everything the system produces exists to satisfy that note and nothing more. The judgment call stays with the person accountable for the outcome, only now it arrives with the evidence already assembled and a citation on every fact.
- Price
- $15,000 to $35,000
- Terms
- Fixed fee, receives credits
- How long
- 4 to 8 weeks
What you get back
- The system in production, stopping at the line
- A plain language spec in your own drive
- Before and after measurement
- 30 days of defect correction
How it runs
Six milestones, and one of them is a signature
Payments run 40% at signature, 40% at readiness and 20% at acceptance.
Kickoff
Confirm the decision line, the delivery track and access. Draft the acceptance criteria.
Criteria signed
Build does not start until both sides sign.
Build and test
Built in staging and tested against the criteria, with a weekly 30 minute check in.
Promoted to production
You enter your own credentials. We never request, receive or store them.
Observation
You use it on live work before anyone signs anything off.
Handover
Then 30 days of defect correction and a before and after measurement.
Deliverables
What arrives at handover
- The working system in production, preparing the decision and stopping at the line
- Operating documentation, including how to pause it and how to rotate credentials
- A plain language spec of the line, stored in your own drive, so it can be rebuilt on any platform
- A before and after measurement report
- A handover session and 30 days of defect correction after acceptance
Ownership
Nothing turns off when we leave
These are properties of how we build, not promises about how we behave. Hold us to each one.
- Live systems run on software your company already owns and pays for.
- We never request, receive or store production credentials. Our staging uses sandbox credentials only.
- You can pause or turn off any line without calling us, and that switch is tested at handover.
- Failure alerts go to an inbox you own, not ours.
- Every line ships with a plain language spec in your own drive, so it survives any vendor shutting down.
What we build on
The tools your company already pays for, and the AI your people already use
We start with what is already on the shelf. The work runs on your office suite, and the AI steps run on the assistant your team already knows. Custom agents only when the numbers say the off the shelf version can't do the job.
- Microsoft 365
- Power Automate with Copilot Studio or AI Builder, inside your own Microsoft tenant.
- Power Automate
- Copilot Studio
- AI Builder
- Google Workspace
- Workspace Studio for lines that live in Gmail, Sheets and Docs.
- Workspace Studio
- Gemini in Workspace
- The AI your people already use
- If your team already works in ChatGPT, Claude, Gemini or Grok, we build the AI steps there, on your company plan, so the prompts, files and history stay with you.
- ChatGPT
- Claude
- Gemini
- Grok
- Outside systems
- Zapier, when the line reaches past the suite into your CRM, ERP or job tracking.
- Zapier
You pay the software bills directly. Nothing is resold through us, and nothing stops working when we leave.
Questions
Before you ask
Where does the automation run?
On tools your company already owns and pays for, the ones that match the suite you already run. We never request, receive or store your production credentials, our staging uses sandbox credentials only, failure alerts go to an inbox you own, and you can pause or turn off any line without calling us. That switch is tested at handover.
Why is the price fixed per decision line?
Because the line has already been measured, so we are not guessing at scope. One decision line, start to finish, for a number agreed before the work starts. Acceptance criteria are signed by both sides at the end of week one and build does not start until they are.
What stops this from becoming a vendor lock in?
Every line ships with a plain language spec stored in your own drive, so it can be rebuilt on any platform, by anyone, if we or the platform disappear. The workflows live on your own software and the operating documentation covers how to switch the line off and how to rotate credentials.
What happens after we accept it?
A handover session, then 30 days of defect correction, and a before and after measurement that times the same steps again and compares them to the map. Plenty of teams take it from there themselves, which is a fine outcome.
Talk to us
Tell us which decision line you would build first.
If you already know the line and roughly what it costs to prepare, a sprint can start from that. If you do not, Line Mapping is the cheaper way to find out which one is worth the weeks, and its full fee comes off the sprint.