How a project runs, start to finish.
The same six stages for a two-week sprint or a six-month build. What changes is how long each one takes.
Six stages. You see working software from week four.
Every stage ends with something you can review and sign off, so there are no surprises at the end.
- 01
Discover
Understand the business problem and the people who have it.
Interviews with your team and, wherever possible, your users. We look at the numbers you already have and the workarounds people use today.
You get: A one-page problem statement both sides sign off
- 02
Define
Agree requirements, scope and how success will be measured.
We turn the problem into a scoped first release, name what is out of scope, and agree the two or three numbers that will tell us it worked.
You get: Scope, architecture sketch and a fixed proposal
- 03
Design
Map the journeys and prototype them until the questions are answered.
Flows first, then interface. Prototypes are tested with real users before engineering starts, so we build decisions, not guesses.
You get: Clickable prototype and design system
- 04
Engineer
Build secure, tested, maintainable software in short cycles.
Two-week cycles, each ending with a working demo on a staging link you can click through. Code lives in your repository from the first commit.
You get: A staging link that updates every week
- 05
Launch
Deploy, measure and fix what real usage reveals.
Release behind feature flags, with monitoring, alerts and a rollback plan in place. Analytics track the success measures agreed in Define.
You get: Production release and launch report
- 06
Evolve
Improve the product from what users actually do.
A monthly cycle of review, prioritise and ship. Or a clean handover to your own team, with documentation and pairing sessions.
You get: Roadmap driven by usage data, or a full handover
Working together
How involved do we need to be?
About an hour a week for a demo and decisions, plus quick answers on a shared channel. More during discovery, when we need time with you and your users.
What if the scope changes halfway through?
It usually does a little. Changes are written up with their cost and effect on the timeline, and nothing changes until you agree. Smaller swaps of equal size happen without paperwork.
How do you price projects?
Discovery sprints and builds are fixed price against a written scope. Ongoing product work is a monthly fee for an agreed team. We don't bill by the hour.
What happens after launch?
A short stabilisation period is included. After that you can continue with us monthly or take the product in-house; either way you get documentation and handover sessions.
Do you sign NDAs?
Yes, happily, before you share anything sensitive.
Have an ambitious idea? Let's engineer it.
Tell us what you're trying to do. A senior engineer reads every message and replies personally.