How Do You Design a Page That Helps a Champion Sell Internally?

How Do You Design a Page That Helps a Champion Sell Internally?

Build a page for the people your champion has to convince, not for your champion. They already believe you. Their problem is a finance lead, a security reviewer and a sceptical peer who will never visit your site. The page's job is to be forwardable, skimmable and defensible without you in the room.

Most B2B sites have no page for this. They have feature pages for the user, a pricing page for the buyer, and nothing at all for the moment a champion opens a message and types "thoughts on this?"

That moment decides deals, and it is a design problem as much as a sales one.

Who Is Actually Reading This Page?

More people than you think, and most of them are not your user. 6sense's research, published in November 2025 and drawing on nearly 10,000 B2B buyers over three years of global study, puts the typical buying group at around ten members.

The composition matters more than the headcount. The same research found roughly 40 percent of buying group members come from departments outside the intended end-user department. Finance, security, legal, procurement, and a neighbouring team who will have to integrate with you.

Those people have no context, no enthusiasm, and a professional obligation to find the problem. Designing for them is uncomfortable, because everything that works on an excited user reads as marketing noise to a sceptical reviewer.

Why Does the Buying Group Change the Design Problem?

Because the decision is mostly made before anyone talks to you. The 6sense research found that in 80 percent of buying journeys the major decisions about requirements and vendor selection happen before sellers engage, and that 83 percent of buying groups keep their initial requirements with minimal adjustment.

The shortlist is similarly settled. Four of the five vendors on a shortlist are there on day one, and 95 percent of the time the eventual purchase comes from those initial four. On top of that, 77 percent of buying groups buy from the vendor they ranked first before making contact.

Read together, those numbers say something specific about your website. It is not supporting the sales conversation. It is often the whole conversation, happening among people you never meet, using whatever your champion can forward them.

What Does a Champion Need That a Feature Page Does Not Give Them?

Ammunition for objections they will not be in the room to hear. A feature page answers "what does it do". A champion needs answers to "why now", "why this one", "what does it cost in total" and "what happens if it goes wrong".

They also need it in a form they can paste. A champion is not going to transcribe your site into a slide. If the argument is not already assembled somewhere they can link to, they will assemble a weaker version of it themselves, from memory, at eleven at night.

The reframe we find most useful is to stop designing for a visitor and start designing an artefact. This page is a document your champion sends to someone else. Everything follows from that.

What Belongs on a Business Case Page?

Six blocks, in roughly this order. The problem stated in the buyer's language rather than your category's. What changes operationally when it is solved, which is the part finance actually evaluates. The cost structure, honestly, including what drives it up.

Then the risk section, which is the one most companies skip and the one reviewers open first: security posture, data handling, what happens to the data if they leave, contract length, and what support looks like. Then evidence, meaning named customers and specific outcomes rather than adjectives. Then the alternatives, including doing nothing, treated fairly.

That last block does more work than the rest combined. A page that honestly compares itself to doing nothing reads as written by someone confident, and it hands your champion the exact argument they need for the person asking why this is a priority this quarter. Our approach to that kind of page is in designing a comparison page.

Should It Be Gated?

No. Gating this page defeats its only purpose. The value of the page is that a champion can forward it to seven people, and a form in front of it means six of them bounce and your champion looks like they are recruiting for you.

If your marketing team needs a capture point, put it after the content rather than before it, and make it an offer worth the exchange, such as a tailored version with their numbers in it. That converts the person who is genuinely running the process rather than taxing everyone your champion sends.

The counter-argument is always attribution. It is a real cost, and it is smaller than the deals you lose when a security reviewer hits a form and gives up.

How Do You Make It Easy to Forward?

Design for the paste. That means a title that makes sense out of context, a first paragraph that works as a link preview, a URL a person can read, and an open graph image that does not look like a banner ad.

Structurally, it means the page has to survive being skimmed in ninety seconds by someone on a phone between meetings. Clear section headings that state conclusions rather than tease them. Numbers in the text where they can be quoted. No content that only appears after a scroll-triggered animation.

And keep it one page. The instant a champion has to forward three links, they forward none and write a summary instead, and now your argument is being made by someone with less information than your website has.

What Should the Numbers Look Like?

Defensible rather than impressive. A reviewer's job is to find the assumption that breaks, and an implausible number invalidates the whole page in one line.

So show the workings. If you claim time saved, say per what, based on what, over what period. If you offer a calculator, let the inputs be edited rather than pre-filled with flattering defaults. If a number came from one customer, say which and in what circumstances rather than generalising it into an average.

Our rule internally is that every number on a page like this should survive being read aloud in a meeting by someone who wants it to be wrong. If it needs context that is not on the page, it fails. That is the same standard we apply to case study pages.

Where Should the Page Live?

On your main site, at a stable, readable URL, linked from pricing and from your demo flow. Not in a resources library where it is one card among forty, and not as a PDF.

The PDF instinct is strong and worth resisting. A PDF cannot be updated after it has been forwarded, is awkward on a phone, and is invisible to search and to answer engines. A page can be improved the week after you learn what objection you keep losing to.

Linking it from your pricing page matters specifically, because pricing is where an evaluator lands when they are trying to work out whether this is worth a conversation. We covered that page's job in designing a pricing page.

How Do You Know It Worked?

Not through conversion rate, because this page rarely converts anyone directly. Look instead at whether it appears in deals, and ask your sales team the only question that matters: did anyone send this to someone else?

Two practical signals. Direct traffic to the page's URL with no referrer, which is what a forwarded link looks like. And multiple visits from the same organisation within a short window, which is what a buying group reading it looks like.

Then treat the page as living. Every time a deal stalls on an objection, check whether the page answers it. If it does not, that is next week's edit. This page improves through contact with lost deals more than through design reviews.

If you want help building one, or an honest read on whether your current site gives a champion anything to work with, we are glad to talk it through. Find us at phoenix.studio.