How it runs · Stage 03 · Build
Working software every two weeks, in your accounts
Companies with a blueprint, or a clear problem, that want a system built fast and handed over complete.
- Price
- From $2,500 one-time; most builds $5,000 to $15,000
- Time
- 2 to 8 weeks
- For
- Companies with a blueprint, or a clear problem, that want a system built fast and handed over complete.
- You own
- Code, in your repository
In short
Build is where the blueprint becomes a running system. We work in two-week sprints with a named owner on your side, in your accounts, on the tools you already run. Each sprint ends with working software and one measurable outcome. Builds run from two to eight weeks at a fixed, one-time price, from $2,500; most land between $5,000 and $15,000. Sixty days of hypercare are included.
How it runs
Step by step.
- 1Week 1
Sprint 1 kick-off. Accounts, access and environments set up in your name. The first workflow is built end to end, with test data.
- 2Week 2
Sprint 1 review with your owner. Working software on screen, not slides. Feedback goes straight into sprint 2.
- 3Weeks 3 to 6
Further sprints, each with one outcome. Documentation written as we go. Your team trained on each piece as it lands.
- 4Go-live
Side-by-side rollout. The old spreadsheet or tool is retired only when the new system has run for real. Hypercare begins.
What you get
- The internal tools, agents and integrations in the blueprint, in production
- Monitoring, alerts and automatic retries on every automation
- Documentation: runbooks, architecture, recorded walkthroughs
- Training for the people who will run it
- Sixty days of hypercare, extended free until adoption is met
How we know it is done
- Each sprint’s acceptance criteria, from the blueprint, are met and signed off
- The system runs on real data for an agreed period before the old way is retired
- Your team can operate it from the documentation alone
What you own
- Code, in your repository
- Workflows and agents, in your accounts
- Databases and integrations, in your tenancy
- Documentation and training recordings
success rate of buying from a specialised vendor versus building in-house (about 67% against 33%)
Source: MIT NANDA, 2025Proof
Customer stories.
“We show working software every second Friday. If you cannot see it running, it does not count as done.”
How it starts
Every project starts with an audit.
One to two weeks with the people who do the work. A costed blueprint in order of payback. The $500 is credited in full to the build.
- Audit1 to 2 weeks. $500, credited to your build.
- BlueprintIncluded in the audit’s second week. Included with the Audit; quoted separately for multi-phase programmes.
- Build2 to 8 weeks. From $2,500 one-time; most builds $5,000 to $15,000.
- Run60 days of hypercare, then monthly. Hypercare included; care plans from $1,000/month.
Questions
What people ask about the build.
What stack do you build on?
Whatever fits your problem and what you already run: Zapier, Make and n8n for workflows; Airtable, SmartSuite, Retool and Bubble for tools and portals; Claude and OpenAI through their APIs for agents; custom code where it earns its place. Every choice is in the blueprint with its reason.
How involved does our team need to be?
One named owner for about two hours a week: a sprint review every second week and quick answers in between. The people who will use the system join training as each piece lands.
What if a sprint does not meet its acceptance criteria?
We fix it at our cost before the next sprint starts. Acceptance is written, so there is no argument about what done means.
Do you bill by the hour?
Not for builds. Scope and price are agreed in writing before work starts. The only hourly-shaped offer is Extend, where you book a named specialist in prepaid blocks that roll over.
What happens if the scope changes mid-project?
We agree the change in writing before doing the work, with its price and its effect on the timeline. You decide whether it is worth it. We do not absorb scope quietly and present a larger invoice at the end.
The other stages
- How it runs
Audit
Teams of 1 to 1,000 people that know something is manual and expensive but not which fix to make first.
- How it runs
Blueprint
Teams that want to see the whole design, the cost and what they will own before committing to a build.
- How it runs
Run
Every build we deliver, and systems built by others that need a team on call.
Stage 03 · Build
Talk to the people who would build it.
Thirty minutes. Bring the work your team still does by hand. You leave with a yes or no on fit and the first thing we would build.
Book the call