How we work
You'll know exactlywhere your projectstands. Every week.
Two-week sprints, a working demo every sprint, and a shared board you can open at any time.
The phases
Six phases, each with a deliverable.
Every phase ends with something you can hold — a document, a prototype, a working system. A phase that produces only progress isn't finished.
Discovery
1–2 weeksScope document, risk list and a fixed estimateDesign & architecture
2–3 weeksClickable prototype and system designBuild
6–16 weeksA working demo at the end of every sprintTest & harden
ContinuousAutomated test suite, UAT sign-off, security reviewLaunch
1 weekProduction deployment, monitoring and full handoverSupport
90 days includedSLA-backed fixes and a roadmap for what's nextEvery week
What you get, without asking for it.
The fear with any development partner is the black box — money going in and nothing visible until a deadline slips. This is how we remove it.
A shared board
Your Jira, Linear or our board — whichever you prefer. Open it whenever you like; nothing is hidden until a milestone.
A written update
Every Friday: what shipped, what's next, what's blocked and anything that changed our estimate.
A working demo
At the end of every two-week sprint, on the real system with real data. Not slides.
Direct access
A shared channel with the engineers. No ticket queue, no account manager relaying questions.
What we need from you
It only works if you show up too.
Most projects that go wrong go wrong on the client side, and nobody says so upfront. These four things matter more than anything in our contract.
- 01
One decision-maker
Someone who can settle a question within a day. Design by committee is the single most common cause of overrun.
- 02
Two hours a week
Sprint demo and a short planning call. Less than that and we start guessing at your priorities.
- 03
Access to real users
Even two or three. Building for an imagined user is how products miss.
- 04
Honest constraints
Budget ceilings, immovable deadlines and political realities. We'd rather design around them than discover them late.
Engagement models
Pick the risk model.
Fixed scope
The brief is clear and finite. We quote a firm price after discovery and carry the delivery risk.
Best when requirements are genuinely settled.
Dedicated team
You set priorities each sprint and scale the team monthly. We provide capacity and expertise.
Best when the product will evolve as you learn.
Retainer
Agreed monthly hours for ongoing work, with guaranteed response times.
Best after launch, for improvement and support.
Discovery. We watch how your team actually works, map the process, identify risks and produce a written scope with a fixed estimate. You own that document whether or not you continue with us — it's useful even if you take it to another firm.
On a dedicated-team engagement you simply re-prioritise the next sprint; that's the model working as intended. On fixed scope we quote changes separately so the original budget stays predictable. Requirements changing isn't a failure — pretending they won't is.
You'll hear about it in that Friday's update rather than at the end. We'd rather tell you a sprint underdelivered and explain why than absorb it quietly and compress a later one.
The engineers building your system, in a shared channel. There's no account manager layer — that's usually where information gets lost and decisions get slow.
After discovery, never before. An estimate given before we understand the scope is a number designed to be revised. If you need a rough band earlier, we'll give a wide one and label it as such.
Full handover — repository, infrastructure, documentation and a walkthrough with whoever takes it on. Ninety days of support are included. We build so you can leave; that's the point.
Start with discovery.
One to two weeks, a written scope and a fixed estimate — which is yours to keep whether or not you continue with us.
Average response under 4 business hours