WhatsAppOur software development process: six stages, zero surprises
-
1. DiscoveryWeek 1–2
Workshops to understand goals, users, features, integrations and risks. You receive a scope document, a roadmap and a fixed estimate or team plan.
-
2. UX & UI designWeek 2–4
User flows, wireframes and a clickable prototype tested with real users before any code is written.
-
3. Agile development2-week sprints
Working software every sprint, live demos, code reviews and automated tests. A staging site is always available.
-
4. Quality assuranceContinuous
Manual and automated testing, plus performance and security checks before every release.
-
5. Launch1 week
Production setup, data migration, monitoring and a zero-downtime release.
-
6. Support & growthOngoing
Maintenance, monitoring and new features on a predictable monthly plan.
What happens in discovery
Discovery is the most valuable two weeks of any project. It replaces guesswork with a plan both sides trust:
- Goals and success metrics — what the software must achieve for the business.
- Users and journeys — who will use it, and the key tasks they need to complete.
- Feature list and priorities — must-haves for launch versus later releases.
- Integrations and data — the systems involved and how data moves between them.
- Technical approach — architecture, technology choices and hosting.
- Risks and assumptions — written down, with a plan for each.
The output is yours to keep, even if you decide not to continue with us.
A typical sprint
| When | What happens | Your involvement |
|---|---|---|
| Day 1 | Sprint planning: agree the goals and tasks for the next two weeks | 30–60 minutes |
| Days 2–9 | Design, development, code review and testing | Answer questions in a shared channel |
| Weekly | Written progress update: done, next, budget, risks | 5 minutes to read |
| Day 10 | Sprint demo on staging, feedback and acceptance | 45 minutes |
| Day 10 | Retrospective: what to improve in the next sprint | Optional |
What you can expect from us
- An NDA signed before you share your idea
- A written scope and estimate before any commitment
- Access to the task board, repositories and staging environment
- Weekly progress reports covering work done, budget and risks
- A demo at the end of every sprint
- Full handover: code, documentation and accounts
The stages follow the software development life cycle and work with any of our engagement models. First releases are often an MVP; every release goes through QA and testing, and after launch a maintenance and support plan keeps the software healthy. Browse the kinds of projects we deliver.
Engagement models
| Model | Best for | How billing works |
|---|---|---|
| Fixed-scope project | MVPs, websites and well-defined builds | Fixed price, paid by milestone |
| Dedicated product team | Ongoing roadmaps and products | Monthly per team |
| Staff augmentation | Adding senior engineers to your team | Monthly per engineer |
Not sure which fits? Tell us about your project and we will recommend one.