
Understand the problem
Review your audience, existing customer journey and business priorities. Identify where people struggle and which assumptions need checking.
Turn an early idea or a disconnected digital presence into a focused brief before investing in development or marketing.
For a new business idea, a website that no longer fits, or a team deciding what to build next.

Review your audience, existing customer journey and business priorities. Identify where people struggle and which assumptions need checking.

Map the essential pages or user tasks. Connect the message, brand and technical requirements around the action that matters.

Prioritise the first website release or marketing activity, then plan later improvements. Agree what success means and what needs to be measured.
A shared brief, a prioritised scope and a clear next decision. The exact deliverables are agreed around your project.
Explore design & developmentThe discovery framework
Discovery is the part of a project people struggle to picture, so here is the whole of it. Each step says what we need from you and what exists at the end of it that did not exist before.
01
We start with the people who carry the business — whoever founded it, whoever sells it, whoever answers the same customer question for the fifth time this week. Their accounts rarely agree, and the disagreements are usually the most useful thing in the room.
02
Then we look outward: who your audience already compares you against, what they search for on the way to a decision, and which positions in your market are occupied before you say a word.
03
A working session, not a presentation. Options go up on the wall and get scored against the business goal rather than against the loudest voice, and the ones that survive keep their trade-offs attached.
04
The chosen direction becomes a sequenced plan: what gets built first, what waits, what is measured, and what the next quote is actually for. This is the document the build runs on.
What discovery produces
The objection to a discovery phase is always the same: it sounds like conversation you pay for. It is not. It is structured material — maps, profiles and boards that the next decision gets argued over. These are fragments of the real thing.
Every stage a buyer passes through, the touchpoints they meet in each, and where satisfaction drops. The dip is the deliverable — it names the stage your website, your sales process or your ad spend is quietly losing people at.
The cautious buyer
Operations lead · mid-sized team
Not a demographic. The person who signs, what they are trying to achieve, what is currently stopping them and what they judge a supplier on — written so that a copywriter and a developer can both act on it.
Everything raised in the interviews, clustered until the themes show themselves. Options get grouped, argued with and cut here — on a board, cheaply — rather than later in a build where each one has a price.
Inside a session
Nobody disappears for weeks and returns with a document. The thinking happens with you in the room, on a wall you can see, which is also the fastest way for us to be corrected early rather than expensively.
Deliverables
A discovery phase ends on a date with named documents attached, not with a feeling that things are clearer. These four are the standard set, and they belong to you whether the build that follows is ours or somebody else's.
01
The sequence: what gets built first, what deliberately waits, and which decisions block which work. Phased so that something useful ships before the whole thing is finished.
You receivePhased plan with dependencies and decision points
02
The key screens and the paths between them, clickable before a line of production code exists. Argue with the structure of a page while changing it still costs an afternoon.
You receiveClickable prototype of the primary journeys
03
Where you stand against the alternatives your buyer is also reading, and the language that holds up when they compare. One statement, with the messaging that follows from it.
You receivePositioning statement and messaging framework
04
Functional requirements, integrations, content model and constraints, written so a development team can price the work without a second discovery of their own.
You receiveWritten requirements an external team could build from
Research findings, a measurement plan and a content inventory are added where a project needs them. The exact set is agreed before the phase starts, so nothing on this list is a surprise at the end of it.
The economics
Discovery looks like a cost added to a project. It is better understood as the cost of changing a decision, bought at the only point in a project where that cost is still small.
A feature nobody needed
Specified, built, tested, documented, and then quietly switched off not long after launch. It was paid for at the build rate. The conversation that would have cut it takes a few questions in an interview.
A structure rebuilt after the words are written
Reorganising how a site is arranged costs an afternoon on a board. It costs considerably more once the content is written against it, the URLs are live and the search rankings are attached to them.
Media spend aimed at the wrong page
Advertising is the one cost that leaves daily while the actual problem sits upstream of the page receiving the traffic. Campaigns pointed at an unclear offer do not fail quietly; they fail at budget.
A discovery phase is bounded: fixed scope, a known end date, agreed before the expensive part of the project starts. Its most valuable output is not the document — it is that the next quote you are handed is based on something, and holds.
Share your goals, what you have today and the decisions you need help making. We can discuss the right starting point and scope.
Tell us about your project