Process
How we work.
Five phases that describe how we think. The shape flexes with the project; the order of thinking does not.
-
Phase 01: Discover
Understand goals, users and challenges.
We start by learning the business, the people who use what you make, and the constraints that are real rather than assumed. Most projects change shape here, and that is the cheapest place for it to happen.
Deliverables
- Stakeholder and user interviews
- Review of existing product, data and support history
- Constraints and risk register
- Findings summary with recommendations
-
Phase 02: Define
Turn insights into a clear direction.
Research becomes a decision. We agree what the project is for, what success looks like, and — just as importantly — what is out of scope, so nobody is surprised in month three.
Deliverables
- Scope and success measures
- Information architecture
- Prioritised feature set
- Technical approach and estimate
-
Phase 03: Design
Create intuitive, purposeful experiences.
We design with real content at real sizes, in light and dark, across the widths people actually use. Prototypes go in front of users before anything is built.
Deliverables
- Wireframes and user flows
- Interactive prototype
- High-fidelity interface design
- Design system and documentation
-
Phase 04: Build
Develop, test and refine every detail.
Engineering runs in short cycles with something working at the end of each one. You see progress in a browser, not in a status report. Refinement happens inside that loop rather than after it — real devices, a performance budget and an accessibility audit as the work goes, so the small things that separate a build that works from one that feels finished are never left to the last week.
Deliverables
- Production codebase
- Component library
- Automated tests and CI pipeline
- Cross-browser, device and accessibility testing
- Staging environment for review
-
Phase 05: Launch
Release confidently and continue improving.
Launch is a planned event with a rollback path, not a leap. Afterwards we hand over properly — documentation, a walkthrough, and a clear view of what is worth doing next.
Deliverables
- Deployment and monitoring setup
- Analytics and measurement
- Handover documentation and training
- Post-launch review and roadmap
Working together
What we need from you
A project runs on both sides holding up their end. Here is ours, stated plainly, and yours.
What we commit to
- A named contact who is actually doing the work
- A weekly update, whether or not the news is good
- Estimates with the assumptions written next to them
- Everything handed over in editable, unlocked formats
What we ask of you
- One person empowered to make decisions
- Feedback within a few working days at review points
- Access to the people who understand the current system
- Honesty about budget and deadline from the start
FAQ
Common questions
Do we have to follow all five phases?
No. The phases describe how we think, not a fixed invoice. A focused piece of work might compress Discover and Define into a week; a complex product might loop through Design and Build several times.
How involved does our team need to be?
Most in Discover and at each review point. We work in the open with a shared channel and a regular check-in, so there are no long silences followed by a big reveal.
What if the scope changes mid-project?
It usually does. We handle change explicitly: what it affects, what it costs, and what we would drop to make room. What we do not do is absorb it quietly and let the deadline slip.
Who owns the work?
You do — code, design files and assets, in editable formats. There is no dependency on us to keep using what we made together.
What happens after launch?
That is your decision. We can hand over completely, stay on for a defined improvement period, or work to an ongoing arrangement. All three are normal.
Ready to start at phase one?
Discover is where every project begins. Tell us what you are trying to do and we will take it from there.