How it runs · Stage 03 · Build
Working software every two weeks, in your accounts
Companies with a blueprint, or a clear problem, that want it built in weeks and handed over with documentation.
- Price
- From $1,000 one-time; internal tools from $3,000
- Time
- 2 to 8 weeks
- For
- Companies with a blueprint, or a clear problem, that want it built in weeks and handed over with documentation.
- You own
- Code, in your repository
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, set after the audit: from $1,000 for workflow automation, $3,000 for internal tools, $5,000 for multi-module systems and $10,000 for micro-SaaS. Sixty days of hypercare are included.
How a build runs
Two-week sprints in your accounts, each ending in working software.
-
Sprints that end in working software
One measurable outcome every two weeks.
-
Built in your accounts
Every workflow, database and key is yours from day one.
-
Monitoring on every automation
Retries and an alert to a named person when something fails.
-
Fixed price by type of build
From $1,000 for workflows to $10,000 for micro-SaaS.
-
Sixty days of hypercare
Included, and extended free until adoption is met.
Step by step
- Week 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.
- Week 2
Sprint 1 review with your owner, using the working software on screen. Their feedback goes into sprint 2.
- Weeks 3 to 6
Further sprints follow, each with one outcome. We write documentation as we go and train your team on each piece as it lands.
- Go-live
The new system runs alongside the old spreadsheet or tool, which is retired once the new one has handled real work. Hypercare begins.
Measured in production
“We show working software every second Friday. If you cannot see it running, it does not count as done.”
What you get
- The internal tools, agents and integrations in the blueprint, in production
- Monitoring, alerts and retries on each 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, 2025What 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. The acceptance criteria are written down, so both sides know what done means.
Do you bill by the hour?
Not for builds. Scope and price are agreed in writing before work starts. The time-based offers are Extend, a named specialist in prepaid blocks that roll over, and forward deployed engineers, a monthly engagement.
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
Audit
Teams of 1 to 1,000 people that know something is manual and expensive but not which fix to make first.
Blueprint
Teams that want to see the whole design, the cost and what they will own before committing to a build.
Run
Builds we have delivered, and systems built by others that need a team on call.
Every project starts with an audit
We spend one to two weeks with the people who do the work and give you a costed blueprint, ordered by 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 $1,000 one-time; internal tools from $3,000.
- Run60 days of hypercare, then monthly. Hypercare included; care plans from $50/month.















