The problem

A drop-off is rarely a button problem.

People arrive with something specific they are trying to do. They leave at the point the journey stops matching that, and the cause is usually further back. Fixing one screen sometimes works, but usually the journey has to change.

The difference

Is this just CRO?

CRO needs three things: enough traffic for a test to prove anything, a page that already exists, and permission to change what is on it. If you have all three, a good CRO team is the right call.

Most of what we get called in for is missing at least one. A platform your users work in all day has the same people in it every day, so a test has nobody new to learn from. A journey not built yet offers nothing to optimise. And what moves the number is often a decision already made before anyone reaches that page.

This is where Performance Design comes in. Instead of running slow experimentation on live sites, we agree on the number first, validate a working prototype with your users, then tell you what moved and what did not before the build.

The trade-off

Every gain takes something from the other side.

Take the fields out of a form and more users finish it, but your sales team gets worse leads. Push the upsell harder and revenue per customer climbs, but retention drops a quarter later.

Something the user wants gets given up for something the business wants. The cost of not looking at the experience end-to-end is real.

So we make that choice before we design, and we say which side is losing out. Getting the balance right is most of the job.

What changed

Every page now has two readers.

The person deciding, and the AI summarising the page before that person ever arrives. Search is collapsing into answers, so a page has to work for both.

Being easy to follow has always been the work. Now a model has to follow it too. Most redesigns still miss that, so the site looks new but the number does not move.

We agree on the number before anyone builds.

A number without a starting point is an opinion.

Before

The baseline is agreed with you, in your own analytics, before we touch a page. Nothing ships until you sign it off.

During

We test on a working prototype with your users while the design is still cheap to change. What we find gets fixed before anything is built.

After

We measure once against the number you agreed on and report the changes that missed the mark. The tracking stays yours, so the measurement outlives us.

One team

Split the work and the outcome belongs to nobody.

We run design, content and search as one team against one outcome. Split them and design hands off to copy, copy hands off to search. All three can show you they have done their job, yet the number has not moved.

Internal teams fall into the same trap: Marketing owns the traffic, product owns the flow, digital owns the build, and the drop-off happens in the gaps between them.

We work inside your internal review process, with design, content and search all in the same room, so a decision does not have to survive three handovers.

Accountability

What we own.

Everything after someone arrives: the page, the journey, the words and the way it is all put together, which decides whether a person or an AI can make sense of it.

Your media team brings users in. We own what happens once they are here.

We do the search work too, so users arrive without a media budget behind them. That keeps working even after we leave.