How a project actually runs.
From first conversation to a system somebody else could maintain. Seven phases, no handoff theatre.
How we deliver
Four stages. One team. No handoffs between them.
In detail
What happens in each phase.
01
Discovery
- Initial consultation and problem framing
- Business requirements and constraints
- User research with the people who will use it
- Feasibility assessment and technical spike
- Scope definition — including what we are not building
02
Planning
- Requirements document and prioritised backlog
- Architecture and integration plan
- Cycle-by-cycle timeline
- Cost per cycle and total ceiling
- Risk register with mitigations
03
Design
- User flows and information architecture
- Wireframes, then interface design
- Design system and tokens
- Interactive prototype
- Accessibility decided at design time
04
Development
- Two-week cycles with a working deployment at the end of each
- Front end, back end and database in step
- Integrations built against contract tests
- Code review on every change
- Continuous deployment to staging
05
Testing
- Automated unit, integration and end-to-end coverage in CI
- Security review against the OWASP Top 10
- Performance and load testing
- Device, browser and assistive-technology testing
- User acceptance with your team
06
Deployment
- Production infrastructure as code
- Domain, certificates and monitoring
- Data migration with a rehearsed rollback
- Staged rollout behind feature flags
- Documentation and staff training
07
Maintenance
- Agreed response and resolution targets
- Dependency and security patching
- Performance monitoring and capacity review
- Verified backup restores
- Steady iteration, or clean handover
Start with discovery
One or two weeks, fixed price, and it ends with a scope and a cost per cycle — not a commitment to build.
Start a project