Three shapes,scoped then priced.
There is no minimum engagement and no ceiling. One use case is a project; a multi-region rollout is the same team on a longer timeline. We do not publish a number, and we would be suspicious of anyone who does — a figure quoted before anyone has examined your systems is either padded to cover the unknown or about to be revised. What we commit to is the shape below, and a real number within a week of the first call.
Starter
Fixed scope, one use case
3–6 weeks
A single use case, resolved end to end. A booking or follow-up agent, a working product for the thing you are raising against, or a first CRM implemented properly. A complete engagement in its own right, not a trial run.
Discuss thisGrowth
Phased, multi-workstream
8–16 weeks
A validated need, ready to be built properly. Multi-step automation, full CRM plus AI, or an application with real users. Frequently what a Starter becomes once the first piece has paid for itself.
Discuss thisOngoing
Retained capacity
Rolling, 30 days notice
Systems that must keep running and keep improving. Monitoring cadence, vulnerability triage, multi-agent architectures, enterprise integration work, and a named engineer who holds the codebase.
Discuss thisWhat is included
| Included | Starter | Growth | Ongoing |
|---|---|---|---|
| Discovery call and written scope | Included | Included | Included |
| Architecture documentation | Included | Included | Included |
| Interactive prototype | Key screens | Included | Included |
| Deployed staging from week one | Included | Included | Included |
| Sprint demos | End of build | Fortnightly | Fortnightly |
| AI / automation layer | Not included | Included | Included |
| Third-party integrations | 1 | Up to 5 | Unbounded |
| Monitoring and alerting | Not included | Included | Included |
| Named engineer on call | Not included | Not included | Included |
| Post-launch iteration | Not included | 30 days | Ongoing |
| You own the code | Included | Included | Included |
Every row above is a starting point. Scope moves during Discover, and we confirm the final shape in writing before anything is signed. Rows move down a tier as often as up — we would rather sell Starter twice than Growth once.
How it is billed
Milestones you have already seen working.
- How is it billed?
- By milestone, on the sprint cadence. Each milestone is a demo you have already seen working, so you are never paying against a status report. Ongoing engagements bill monthly with thirty days notice either way.
- When do we get a number?
- In writing within a week of the first call, once Discover has established what the build touches. Never a padded range beforehand — a figure quoted before scope is either guesswork or insurance, and both cost you.
- What moves a project from Starter to Growth?
- Two things, usually. More than one system needs integrating, or the automation layer needs a sprint of its own rather than riding along with the build. Neither is a surprise — it surfaces in Discover, before anything is signed.
- Can a project move back down?
- Often, and we will say so. If Discover shows the bottleneck is one workflow rather than five, that is a Starter. We would rather sell Starter twice than Growth once.
Each tier maps onto the same five stages — see what happens at each one.
Get a number