the method: hear, challenge, build, optimise
agree the build. make it work. measure the result.
Bring a clear brief or an idea that needs shaping. We work out what to build, connect it to the business and agree how to judge the result.
why the same four steps every time.
A website, a booking journey and a bespoke application each need a clear brief, practical testing and a way to measure the result. These steps keep the work focused.
Discovery is sized to the questions the project needs answered. If you already know what you want built, we start there and check the assumptions together.
how long it takes.
- The first conversation
- An hour. Free.
- You leave with our first read on where to look, and a straight answer on whether we are the right people.
- Agreeing the build
- Matched to your brief.
- HEAR and CHALLENGE. We agree how much discovery is needed, the deliverables and the hours before paid work starts.
- Building and measuring
- Depends on what we find.
- BUILD and OPTIMISE. The shape and the hours are agreed in writing before this starts, never after.
01
HEAR.
Understand what you want to build and what it needs to achieve.
Bring a clear brief or a problem to work through. We look at the website, customer journey and systems involved, and speak to the people who will use the result.
What you end up with: A shared brief, the existing systems involved and the result we will measure.
Discovery should answer the questions needed for the build. Its depth depends on the project.
02
CHALLENGE.
Check the proposed build against the way your business works.
We test the assumptions that matter: what customers need, what your current software can do and where a connection or bespoke application is justified. A clear brief is welcome. We refine it with you before agreeing the work.
What you end up with: Agreed deliverables, boundaries, hours and measures, with decisions about what to build or connect.
Use existing software where it fits. Build something bespoke where the business needs it.
03
BUILD.
Build and test the website, application or connected workflow.
We create the agreed website, browser application or booking workflow and connect the systems it depends on. We test the customer journey and the everyday tasks your team will use, with measurement built in. AI is included where it has a useful role, with human checks appropriate to that role.
What you end up with: The agreed build, tested journeys and the information your team needs to use it.
Using AI to write code does not make a website AI-powered. The customer should understand what AI actually does.
04
OPTIMISE.
Measure the result against where you started.
We compare the agreed measures with the starting point, review how people use the build and explain what to change next. Further development and ongoing improvement are agreed pieces of work.
What you end up with: A before-and-after report where the data supports it, an honest handover and recommendations for the next step.
Separate completed work from measured business outcomes. Do not claim a result the evidence cannot support.
the growth pressure map.
When the brief needs more investigation, these areas help us connect the build to the business outcome.
- Demand
- Whether enough of the right people know you exist and care.
- Conversion
- What happens between someone being interested and someone buying.
- Margin
- What is left after the sale, and where it leaks.
- Operations
- What the business spends effort on that it should not.
- Experience
- What people remember, as opposed to what you deliver.
- Scale
- What breaks first at twice the size.
It's not a scorecard with a total at the bottom. A score invites a league table and false precision. The map is built around how your business actually works and is there to focus the next move, not to grade you.
what we agree before anything is built.
- The problem we are solving, in one sentence we both recognise.
- Why it matters now.
- The numbers we are starting from, or the honest admission that there are none yet.
- What success looks like, as a number where possible.
- What is in scope and what is not.
- Who can make the decisions, and who owns implementation.
- What data and access we need.
- How we will review progress.
- What would make us stop, change direction or expand.
Every one of those is agreed in writing before the first day of build. It's not paperwork: it's the list of things that, left unsaid, turn into the argument at the end.
what this avoids.
- Building before the brief, users and intended result are understood.
- Treating every problem as a marketing problem.
- Using AI where it adds nothing.
- Handing over a strategy the business cannot actually implement.
- Measuring activity instead of impact.
- Carrying on after the useful outcome has already been reached.
- Letting everyone avoid the decision the business actually needs to make.
it starts with an hour, free.
Tell us what you want to build or improve and what it needs to achieve.