Process
How a project runs
Four phases with a written goal each, working software every Friday, and nothing built that was not agreed and priced first. Here is what happens in each phase and what you hold at the end of it.
Phase by phase
What happens, and what you hold at the end
Durations are typical ranges. Discovery fixes them for your project, in writing, before design starts.
Phase 1 of 4 · Discover
Estimate your timeline →Discover 1 to 2 weeks
We start with five to ten interviews across the people who will buy, use and maintain the product. Each one is recorded and summarised the same day.
If code already exists, two engineers spend a week in it. The audit covers architecture, test coverage, security basics and the cost of running it.
The output is a one-document roadmap: what we would build first, what we would leave out, and two or three priced options. It is written so that you can take it elsewhere.
- Interview summaries
- Technical audit
- Scoped roadmap
- Fixed-price options
- Risk register
Design 2 to 4 weeks
Flows come first, as boxes and arrows you can argue with. Wireframes follow only once the flow is agreed.
The prototype is tested with real users recruited from your customers or a panel. We watch, we do not lead, and we change the design before engineering sees it.
The design system is expressed as tokens and components in code from the start, so there is no gap between the Figma file and what ships.
- User flows
- Wireframes
- High-fidelity UI
- Clickable prototype
- Test recordings and findings
- Design tokens
Build 6 to 12 weeks
Sprints are two weeks with a written goal. Friday's demo shows working software on staging, never slides.
Every pull request runs tests, type checks and a preview deployment. Nothing merges red.
A security review in the final sprint covers authentication, authorisation, secrets, dependencies and data handling, with findings fixed before launch.
- Sprint goals and demos
- Repository with CI
- Staging and production environments
- Test suite
- Security review
- Runbook
Launch and grow Ongoing
Launch follows a checklist we have used before: DNS, monitoring, error tracking, analytics, backups, rollback plan, and a named person on call.
Thirty days of support are included in every build. Issues are triaged within one business day.
After that, you choose: a monthly retainer with the same team, or a handover sprint that leaves your engineers confident in the codebase.
- Launch checklist
- Dashboards
- 30-day support
- Retainer or handover plan
Fixed price per phase
Discovery is a fixed fee. Design and build are priced after discovery as fixed-scope sprints with a written goal each. Changes are quoted on one page before anyone starts.
Friday demos
Every Friday from the first sprint you see working software on staging. If there is nothing to show, we say so and explain why.
Your accounts, your code
Repositories, cloud, domains and app-store accounts are created in your name on day one. We are members, never owners.
One team, start to finish
The people in discovery are the people who design, build and support. Nobody is swapped out after the sale.
Thirty days of support
Included with every build. After that, a retainer or a documented handover, whichever you prefer.
Start with discovery
Two weeks, a fixed fee, and a roadmap you can take anywhere.