Process
You always know what stage we’re in and what you’ll get next.
Illustrative shape, not a fixed schedule. Your plan after discovery has real dates.
Understand
We interview the people who will use and pay for the software, read what exists, and agree what problem we are solving first.
You receive
- A written scope with priorities: must-have, next, later
- A technical approach and the reasons behind it
- Milestone plan and estimate
- A list of risks and open questions
You decide
- Which problem to solve first
- What is out of scope for version one
- Who on your side signs off each stage
Design
We turn the scope into flows and screens you can click through, test them with your team, and refine until they fit the real work.
You receive
- Clickable prototype of key journeys
- UI system: components, type, colour, states
- Updated estimate if scope moved
You decide
- Approve the flows before build starts
- Content and data you need to provide
- Accessibility and brand requirements
Build
We build in short cycles. At the end of each, you get a working build to open — a URL, a TestFlight invite or an installer — not a status report.
You receive
- Working builds at each milestone
- Automated tests for critical paths
- Release notes in plain language
You decide
- Accept or adjust each milestone
- Prioritise change requests (see below)
- Test with real users and data
Launch & evolve
We deploy, migrate data, submit to app stores where relevant and hand over. Then we measure how it is used and plan the next release with you.
You receive
- Production deployment and monitoring
- Data migration with reconciliation
- Admin and user documentation
- Support options for after launch
You decide
- Go-live date and rollback plan
- Who owns accounts, domains and stores
- What to build next
When things change (they will)
1. Write it down. Any change request goes into the shared backlog with who asked and why.
2. We size it. You see the effect on time and cost before anything is built.
3. You choose. Swap it for something of similar size, add it to the plan, or park it for later.
4. The plan updates. Nothing changes silently. The current scope is always one document.
Handover means you can carry on without us
Code & repositories with setup instructions a new developer can follow.
Infrastructure documented, with accounts in your organisation’s name.
Admin guides for the people who run the system day to day.
A known-issues list and the backlog of what we’d do next.
Contract terms — ownership, warranty and support — are agreed in writing per project.
Start with step one.
Send a brief and we’ll suggest how discovery would look for your project.
Start a project