Every engagement follows a defined process: four phases, in a specific order. The sequence exists to reduce uncertainty before each major decision is made. Discovery before strategy. Strategy before design. Design before delivery.
The diagnostic phase is organised around three questions. Who is the right client for this business — specifically, not generally? What does that person need to understand before they decide to reach out? And what is the business currently communicating that helps or works against that?
Who is the right client for this business — specifically, not generally?
What does that person need to understand before they decide to reach out?
What is the business currently communicating that helps or works against that?
Until those questions are answered, design decisions are premature. Colour, layout, typography, content structure — these choices should follow from a clear communication objective, not precede one. We postpone them deliberately.
The diagnostic work also tests assumptions. Most businesses have a working theory of why people choose them. That theory is frequently incomplete — and sometimes wrong. Uncovering the gap between how a business describes itself and how it is actually perceived is what this phase is for. Finding that gap before design begins is what prevents expensive rebuilds later.
They determine what we will and won’t do at each stage of the process. They’re why the work unfolds in the sequence it does.
Every project begins with a structured discovery process. We need to understand what the problem actually is — not assume it is what it first appears to be.
When we believe a direction is wrong, we say so. Agreement that doesn't serve the business isn't professionalism — it's self-protection.
A website is not the solution. It is the expression of a solution. The positioning, the narrative, the content architecture — these come before anything visual.
The work is successful when the right people encounter our clients and understand — quickly, clearly — whether this business is right for them. Beautiful is secondary to clear.
The four phases that follow are sequenced deliberately. Each one closes a question before the next opens. Discover establishes what the problem actually is. Define translates that into a strategy. Design expresses the strategy visually. Deliver makes the work usable and transferable.
No phase begins until the previous one is complete.
We begin by listening — not to your brief, but to the business underneath it. Structured conversations, competitor analysis, audience mapping. We’re building a picture of the gap: what you currently communicate versus what your intended clients need to understand to choose you.
What we need from you at this stage is honest access. Time for the conversations that need to happen, and willingness to engage with questions that go beyond what a brief typically covers. The most useful input here is rarely in the written document — it’s in what you say when asked why certain clients don’t work out, or why your best clients stay.
Before design begins, we define what design needs to accomplish. Positioning, message architecture, content hierarchy. This is the strategic document every subsequent decision will be tested against.
Your engagement here matters. If the positioning isn’t right, the time to say so is during Define — not during Design, when changing direction is more expensive. We present the strategy document and work through it with you before anything moves forward.
Design does not begin until this phase is signed off.
Every visual decision is made against the strategy. Typography, colour, layout, content structure — each choice is justified by what the business needs to communicate, and to whom. Nothing here is aesthetic preference without a strategic reason behind it.
Your feedback is most useful when it connects to that standard. “This doesn’t help someone understand X” is more actionable than “I’m not sure about this.” We make the same kind of feedback in return when something doesn’t meet the standard.
We hand over a system, not just files. Documentation, usage guidance, and a handoff designed to give you confidence — to use what we built and to build on it.
The goal of this phase is to leave you confident using what we’ve built long after the project is complete.
We work with founders who are prepared to question their assumptions, engage with the discovery process honestly, and trust that strategy precedes every surface decision.
Start a conversation