How to Design One Page for Two Different Buyers

How do you design one page for two different buyers?

Order the page by what both buyers need to decide, and branch only at the point where their questions genuinely diverge. Do not split the page into two halves and ask the visitor to pick a side before you have earned anything. Shared context first, divergence second, and only where it is real.

This comes up constantly in B2B. You sell to the person who will use the thing and to the person who will pay for it, and they want different reassurances. Or you sell to agencies and to in-house teams. Or to a five person company and a five hundred person one.

The instinct is to give each of them their own path immediately. I think that instinct is wrong almost every time, and the reason is that it asks for a commitment before the visitor knows enough to make it.

Why does splitting the page into two tabs usually fail?

Because a toggle at the top of a page is a question, and the visitor arrived with questions of their own. You have opened by asking them to classify themselves, which is work, and the reward for doing that work is invisible until after they have done it.

There is a second cost that matters more than people think. Half your page is now hidden at any given moment, so a skim reader scrolling fast sees one version and never learns the other exists. Whichever variant is the default becomes the page, and the other one becomes a thing almost nobody reads.

The third cost is maintenance, and it is the one that kills these designs slowly. Two variants drift. One gets updated, the other does not, and eighteen months later you have a page that contradicts itself depending on which tab you clicked. Compare that to the discipline in designing for the skim reader, where the whole point is that everything important survives a fast scroll.

What do your two buyers actually share?

More than you think, and identifying it is the real work. Both need to understand what the thing is, whether it applies to their situation, whether it has worked for anyone like them, and what happens if they say yes. Those four are almost always shared.

What differs is usually narrower than the segmentation implies. A technical evaluator and a budget holder do not disagree about what your product does. They disagree about which risk they are trying to retire, and that is one section of the page, not the whole page.

So run the exercise honestly. Write down every question each buyer has, put them in two columns, and look at the overlap. In my experience the overlap is the majority, and the genuinely divergent questions fit in a handful of paragraphs.

Where should the page actually branch?

At the objection, not at the introduction. The visitor has read what you do, seen that it plausibly applies to them, and now wants to know the specific thing that would stop them. That is the moment where two buyers need different answers, and it is usually two thirds of the way down.

Structuring it this way has a pleasant side effect, which is that both branches are on the page at once. Nobody has to choose. The person who cares about implementation effort reads that part and skims the procurement part, and the person who cares about procurement does the reverse, and neither is blocked.

Label the branches plainly so people can find their own. A heading that says "If you are evaluating this for a team that already has a solution" does more work than any tab ever will, because it tells the reader what is in the section before they commit attention to it.

How do you let someone self-identify without making them choose twice?

Use the language of the situation rather than the label of the role. People recognise their circumstances faster than they recognise their job title, and a surprising number of visitors do not think of themselves the way your segmentation does.

"If you are the only person doing marketing" lands better than "For solo marketers", because the first describes a Tuesday and the second describes a category. The visitor does not have to agree with your taxonomy to recognise themselves in a description of their own week.

This matters more now that a lot of visitors arrive already partly briefed, having asked Google or ChatGPT or Perplexity about the category before they ever reached your site. They come with a specific question, not a persona, and a page organised around situations answers specific questions better than one organised around audience segments.

What does this do to your headline?

It forces it to be about the problem rather than the buyer. A headline that tries to name both audiences becomes a list, and a headline that names one alienates the other. A headline about the shared problem does neither.

This is where most two-audience pages fall apart before the fold. Somebody writes "For agencies and in-house teams" and thinks they have solved it, when what they have actually done is spend their most valuable line of copy on administration. Nobody needed that line to know whether the page was for them.

The test I use is whether the headline would still be true if you deleted every audience noun. If it would, keep the version without them. Getting this right is most of the job, which is why I keep returning to designing a hero section that actually says what you do.

What happens to proof and testimonials?

They get labelled rather than separated. A testimonial from a fifty person company and one from a five person company both belong on the page, and the context line under each does the segmentation work without hiding anything from anyone.

What does not work is a proof section that only speaks to one buyer, because the other one reads it and quietly concludes this is not for them. That conclusion is almost never stated and almost never recovered from, and it happens in about two seconds.

The most useful thing you can do is make the diversity of your customers visible. If the page shows a small team and a large one, a technical buyer and a commercial one, the visitor stops asking whether they qualify and starts asking whether it works. That is a much better question for them to be asking.

When should you build two pages instead?

When the two buyers arrive from genuinely different searches, when the price or the product is materially different, or when the shared section would have to hedge so much that it stops saying anything. Those are real reasons and they do exist.

The search reason is the most concrete. If one audience searches for something the other would never type, two pages let each rank for its own language, and forcing them together produces a page that matches neither query well. That is a legitimate case for separation.

What is not a good reason is that two internal teams each want their own page. That is an organisational problem wearing a design costume, and building the second page usually ratifies the confusion rather than resolving it. Across more than seventy projects, the pages that worked hardest were almost always the ones where somebody had been forced to decide what the page was actually about.

How do you test whether it worked?

Scroll depth by traffic source, not overall conversion. Google Analytics will give you the first part and Search Console will tell you which queries brought people in, and if the page is working for both buyers, visitors arriving from two different query types should both reach the branch point. If one group consistently stops before it, your shared section is written for the other one.

Session recordings are unusually useful here, because the failure mode is visible rather than statistical. Whether you use Microsoft Clarity, Hotjar, or anything else, you will see people scroll to the branch, read one label, and leave. That tells you the labels are wrong in a way no conversion number ever will.

Give it real traffic before judging. A two-audience page splits an already small sample in half, so the numbers move slowly, and reading them early leads to changes that make things worse. This is the same patience problem as deciding how many CTAs a page should carry.

What should you do next?

Take your current two-audience page and write out every question each buyer brings, in two columns. Then delete the columns and keep the order: shared understanding first, shared qualification second, divergent objections third, shared next step last.

If you are currently using a toggle, try the single scrolling version before you optimise the toggle. In Webflow that is often a matter of unwrapping the tabs component and letting the sections stack, so it is usually less work than you expect. You already wrote both halves, and this removes a decision from the visitor rather than adding one.

If you have a page that has to serve two buyers and it is currently serving neither, let's chat. It is usually a structure problem rather than a copy problem, and structure is much faster to fix than most people assume.