How we work
Discover, design, build, run.
A clear, four-week standard for a well-scoped project — one team throughout, progress you can see every week, and support after launch on terms we agree together.
Standard project timeline
01Week 01
Discover
Understand the business, clarify objectives, identify users and agree on scope.
You receiveA written scope and plan, agreed together.
02Week 02
Design
Shape the experience and settle what will be built before development begins.
You receiveDesigns you can click through, and the technical plan.
03Weeks 03–04
Build
Develop, test, refine and prepare the solution for launch.
You receiveTested software, live on accounts in your name.
04Ongoing
Run
Agreed maintenance, support and improvements after launch.
You receiveUpdates and improvements, or a documented handover.
Four weeks is our standard for a well-scoped project, agreed together in week one — not a promise for every project. Larger work is planned in phases, and ongoing support follows the engagement we agree.
Week 01 — Discover
We learn how your business works and what the project must change. We meet the people who will use it, look at the tools and data you already have, and agree on a scope that fits the time.
What you do: give us time with the people who know the work, and access to the existing tools and data.
What you receive: a written scope and plan, and the main risks with how we’ll handle them.
Week 02 — Design
We shape the experience and settle what will be built before development starts. You see real screens on real devices — not a slide deck — and decide with us.
What you do: review the designs and make the decisions only you can make.
What you receive: designs you can click through, and the technical plan behind them.
Weeks 03–04 — Build
We develop, test and refine, then prepare everything for launch: content, accounts, analytics, documentation. You can try the work in progress throughout.
What you do: try each build and tell us what’s wrong while it’s still easy to change.
What you receive: tested software, live on accounts in your name.
Ongoing — Run
After launch we keep the software healthy and improve it from what people actually do — under maintenance and support terms we agree together. Or we hand it over cleanly to your team.
What you do: decide what comes next, based on what your users need.
What you receive: updates and improvements, or a documented handover.
About the four weeks
Four weeks is our standard for a project scoped to fit it, agreed together in week one. It is not a promise for every project: larger work is planned in phases, each with its own release, and we say so before anything starts.
What we commit to
- A written update every week, in plain words.
- Set up in your name: the repository, the accounts and the domains are in your name from the start, and you own the code as set out in your contract.
- Your data is handled with care: access only where needed, secrets kept out of code, and a security review based on the OWASP Top 10 before launch.
- A clean handover whenever you want it: documentation, architecture notes and a handover walkthrough (recorded on request).
Quality, shown
The technical standard
What every project includes, whichever service you choose.
| Commitment | Standard |
|---|---|
| Code review | Code review on every change before it’s merged |
| Automated tests | Unit and end-to-end tests, with a DevSecOps pipeline, scope agreed per project |
| Accessibility | Designed and tested against WCAG 2.2 AA |
| Performance | Performance budgets targeting “good” Core Web Vitals, tested on mid-range Android |
| Security | Security review based on the OWASP Top 10 before launch |
| Updates | A written update every week |
| Ownership | Repository and accounts set up in your name; you own the code as set out in your contract |
| Handover | Documentation, architecture notes and a handover walkthrough (recorded on request) |