How we work
Eight steps, in order, every time.
The order matters. We do not design before we understand, and we do not build before we design. Each step has an output you can hold, and each step's output is the next step's input.
Phase 1
Understand
Step 1: Understand the business
What it sells, how it makes money, what is slow.
A few working sessions, not a workshop. We learn how the business earns, where the friction is, and what a good outcome looks like in its own terms.
You get: A one-page brief in your words, agreed by both sides.
Step 2: Understand the problem
The specific thing that is broken or missing.
We write the problem down in one paragraph everyone agrees on. If we cannot, we are not ready to design, and we say so.
You get: A written problem statement and success criteria.
Step 3: Understand the users
Who touches the product, how often, under what pressure.
Interviews and observation with the people who will use the product: their devices, their context, and the moments where a product earns or loses trust.
You get: User profiles, key journeys, and the constraints that follow.
Phase 2
Make
Step 4: Design the solution
Flows, then screens, then a design system.
Structure comes first, visual design second. Every screen is designed in both themes and at three breakpoints, with loading, empty, and error states considered.
You get: Reviewed flows, interface designs, and a design system in code.
Step 5: Build the technology
Working software from the first week.
Short cycles with a demo at the end of each. Every change is reviewed by a second engineer, tested, and measured against the performance budget before it merges.
You get: Reviewed, tested software you can use from week one.
Phase 3
Grow
Step 6: Launch
Staged rollout, monitoring, and a rollback plan.
Nothing goes to everyone at once. Releases roll out in stages with monitoring in place, and a rehearsed way back if something is wrong.
You get: A live product, monitoring dashboards, and a runbook.
Step 7: Improve
Real usage beats assumptions.
We look at what people actually do, remove what is in their way, and fix what breaks. The first weeks after launch are the most valuable data a product ever gets.
You get: A prioritised list of changes, and the changes themselves.
Step 8: Scale
More users, more markets, more integrations.
Growth on foundations built for it: more traffic, new regions, new integrations, and the next product, without a rewrite.
You get: A roadmap grounded in real usage, and the capacity to deliver it.
Underneath every step
Four habits, in every step.
Write it down
Decisions, scope, and trade-offs are recorded so nobody relies on memory.
Show, do not tell
Progress is a working thing you can click, not a status report.
Review everything
Design and code are reviewed by someone who did not make them.
Measure what matters
Performance, accessibility, and usage are numbers, not opinions.
Have something in mind?
See the process on your project.
See the process on your project.Tell us what you are building and we will map it against these eight steps before any quote.