HOW WE WORK
SIX STAGES.
Planning, wireframing, design, code, testing and deployment. Two-week sprints with dedicated QA, and a project manager who owns the relationship and has authority to act.
- SPRINT LENGTH
- Two weeks
- CADENCE
- Daily written · weekly demo
- NOTICE PERIOD
- Two weeks, either side
- MINIMUM DURATION
- None
02 / THE METHOD
NO STATUSTHEATRE.
Clients sit inside the repository, the design file and the tracker. There is a written update every working day and a demo of working software every week. Progress is something you can look at rather than something we report.
We estimate in ranges rather than points, because a range communicates uncertainty honestly and a point estimate pretends it away. The range narrows as discovery removes unknowns.
Two-week notice on either side, and no minimum duration. If the engagement stops working for you, leaving should be straightforward.
03 / The six stages
PLANNING TO DEPLOYMENT.
Planning
Scope, constraints and success criteria written down. Architecture decided and the estimate range produced.
Wireframing
Structure and flow resolved before any visual decision, so that layout arguments do not become colour arguments.
Design
Interface design against a system rather than a set of screens, with states and edge cases drawn.
Code
Two-week sprints, continuous deployment, feature flags. Working software at the end of each sprint.
Testing
Dedicated QA throughout, not a phase at the end. Automated coverage where the cost of being wrong is highest.
Deployment
Staged rollout, monitoring, rollback tested before it is needed, and a handover that does not require archaeology.
04 / Operating rhythm
THE WEEK.
- DAILY
- A written update in the client channel every working day: what moved, what is blocked, what is next.
- WEEKLY
- A demo of working software. Not slides, not a status document — the thing itself, running.
- SPRINT
- Two weeks. Planning at the start, review and retrospective at the end, both open to the client.
- ACCESS
- Client sits in the repository, the design file and the tracker with read access from day one.
- QA
- Dedicated, throughout, and independent of the engineer who wrote the feature.
- ESCALATION
- A project manager owns the relationship. One person to call, and they have the authority to act.
05 / What we ask of you
THREE THINGS.
One decision-maker
Someone who can settle a scope question in a day rather than a fortnight. Committees are the most common cause of slippage.
Access to the real users
Discovery that talks to actual users produces different answers from discovery that talks to their managers.
Tolerance for being told no
A meaningful part of our value is identifying scope that should not be built. That only works if it can be heard.
Close
Engagements begin with a conversation about the constraint, not the specification.