Development process
Seven phases, each with a deliverable you can hold us to
No phase closes on a slide. Every one ends with artefacts your team keeps — documents, environments, tests and code in your repositories.
Timeline
Pick a phase to see what happens inside it
Durations are real ranges from delivered engagements, not best-case marketing numbers.
Phase detail
Discovery
1–3 weeks
Understand the operating constraint, the systems already in place and the number that has to move.
Activities
- Stakeholder and process-owner interviews
- Current-state system and data mapping
- Baseline metric capture and target agreement
- Risk, compliance and integration audit
Deliverables
- Discovery report
- Baseline & target metrics
- Risk register
- Indicative budget range
Principles
Four rules that do not bend
These are the reasons our engagements stay predictable when the scope gets uncomfortable.
No unpaid discovery
Free discovery produces optimistic scopes. Ours is paid, time-boxed and credited against the build.
Reversible by default
Feature flags, expand-contract migrations and rollback rehearsals mean a bad release is an inconvenience, not an incident.
Documentation is a deliverable
If it is not written down, it did not happen. ADRs, runbooks and diagrams ship with the code.
One number that matters
Every phase reports against the baseline metric agreed in discovery, not against story points.
FAQ
How the process works in practice
Discovery
Begin with a baseline, not a proposal
Paid, time-boxed discovery credited against the build. You end with an architecture, a phased scope and a number your finance team can approve.