Five ways to work with us.
And what each one is actually good for. We do not publish a rate card, because a number without a scope is meaningless.
| Model | Best for | Billing | Commitment | What you get |
|---|---|---|---|---|
| Discovery engagement | Starting from an idea, or an unclear problem | Fixed price, 1–2 weeks | None beyond the two weeks | Requirements, scope, architecture outline and a cost per cycle. Sometimes the finding is that you do not need us. |
| Cycle-based delivery | Most build projects | Fixed price per two-week cycle | Stop at any cycle boundary | Working software at the end of every cycle, deployed and clickable. |
| Dedicated team | Sustained roadmaps over several months | Monthly, per named person | Rolling, one month's notice | A ring-fenced team working only on your product, embedded in your rituals. |
| Maintenance retainer | Live systems that need an owner | Monthly, by response target | Rolling, one month's notice | Patching, monitoring, fixes and small improvements against agreed targets. |
| Audit | Inheriting or acquiring a system | Fixed price | One-off | An honest assessment of code, infrastructure and risk, with a keep, fix or replace recommendation. |
On pricing
We give you a cost per cycle after discovery, before you commit to a build. Every advertised fixed quote we have seen gets renegotiated once reality arrives — we would rather skip that step.
What we need from you
- One decision-maker who can approve scope changes
- Access to the people who will use the software
- Feedback at the end of each cycle
- Credentials for systems we must integrate with
Not sure which fits?
Describe the problem and we will tell you which of these we would recommend — including when the answer is none of them.
Send a brief