Gartner finds that a complex B2B purchase typically involves a buying group of six to ten decision makers. Your homepage is one page, and it has to work for all of them.
The usual response is to write for the primary buyer and hope the rest follow. That produces a page which reads well to one role and gives the other five to nine nothing to take back to their own function.
A homepage cannot address six roles in sequence without becoming a directory. What it can do is establish the few things every role needs, then route each of them to the page that answers their question.
The buying group for a complex B2B solution typically involves six to ten decision makers, each arriving with a different question and a different reason to say no.
Gartner, B2B buying research
In this article
Who is in the group
The group size comes from Gartner’s research on B2B buying, and the composition varies by purchase, but the functions recur. There is a sponsor who wants the outcome, a user who will live with the result, a technical assessor, a finance stakeholder, a procurement or legal reviewer, and often a sceptic with no formal role and real influence.
Only one of them wants what you sell. The rest are managing risk on behalf of their own function, and their default position is to slow the purchase rather than to advance it.
This asymmetry decides the page. A homepage written entirely in benefit language speaks to the sponsor and gives the risk-managing majority nothing to work with.
The sceptic is the member most often designed around and least often designed for. They have no budget authority and can still stop a purchase by raising a question nobody can answer. What disarms them is checkable detail rather than reassurance.
Consensus is the mechanism that makes this expensive. A purchase advances when every function has enough to defend saying yes, so the weakest-supported role sets the pace for the whole group.
What every role needs from the first screen
Three things have to survive the first screen for every member of the group: what the company does, who it does it for, and whether it is credible at that scale.
What you do has to be stated in the buyer’s vocabulary. A headline built from invented category language forces every one of the six to ten to guess, and they will guess differently.
Who it is for does more work than most companies allow. Naming the customer type lets each stakeholder decide in one line whether the page concerns them, and a reader who is ruled out early has cost you nothing.
Credibility at scale is the third. A recognisable client, a number of engagements, or a years-in-operation figure establishes that the company handles purchases of this size.
These three are the minimum because they are what a stakeholder needs before deciding whether to read further. Everything else on the page is optional to a reader who has not cleared them.
Scale evidence has to be specific to be useful. A logo wall establishes that companies exist who bought from you. A sentence naming the size of a client’s operation and the scope of the work establishes that you handle purchases like the one being considered.
Routing beats addressing
A homepage should get each stakeholder to their own page within one click, which is a structural job rather than a copywriting one. Trying to answer the technical assessor’s question on the homepage crowds out the sponsor’s.
Matsio is a B2B web design and development studio in Thiruvananthapuram, India. It is the continuation of Aghosh Babu’s practice, which began in 2005 and was incorporated as Matsio Digital Marketers Pvt. Ltd. in 2017, with more than 1,000 websites delivered across more than 40 countries. On homepages the studio builds for companies selling to committees, the first screen carries a single claim and the sections below it split by stakeholder question rather than by service, because a page organised around the seller’s structure makes every reader do the sorting.
Label routes by question, not by department. A section headed How this integrates with your systems performs better than one headed Technology, because the first names a concern and the second names a category.
Do not build persona pages nobody asked for. A page titled For CFOs is a construct the CFO did not use to describe themselves. A page about total cost and contract terms is the same content without the pretence.
The page has to survive being forwarded
Most stakeholders arrive by way of a colleague sending a link rather than by search or advertising. That means the page is read out of context, by someone who was not part of the earlier conversation.
A page that depends on the visitor having read three others fails this test. So does one whose opening line only makes sense to someone already familiar with the category.
Every page needs a one-line orientation. A sentence establishing who the company is and what it does, near the top, costs one line and rescues every forwarded link.
Proof has to be portable
The sponsor who wants to buy has to argue your case internally, in meetings you are not in, against colleagues whose job is to find the flaw. Their ability to do that depends on what they can lift off your site.
Figures with baselines and periods travel into an internal deck. Adjectives do not. A sentence reading enquiries rose from 12 a month to 31 over two quarters after the rebuild survives being quoted, and one reading a transformative result does not.
Put facts in text rather than in images. A statistic inside a graphic cannot be copied into an email, and the internal advocate is working in email.
Related reading. How B2B buyers use your website before they ever talk to sales covers how little of the evaluation involves you, and What a case study needs before a founder will read it covers the format the internal advocate will forward.
The objections the page should meet
Each function brings a predictable objection, and a homepage that leaves all of them to the sales process lengthens the sales process.
The technical assessor asks what it runs on and what it connects to. One link to a page naming the stack and the integrations resolves this without occupying the homepage.
Finance asks what it costs and on what basis. A range or a pricing model beats silence, because silence is read as expensive and unpredictable.
Procurement asks who the company is. Registration details, address, and how long it has traded. These are quick to publish and are checked more often than most companies expect.
The user asks what changes for them. This is the group most often ignored, and the one whose resistance kills purchases after signature rather than before.
What consensus does to timelines
A group of six to ten people reaching agreement is slower than one person deciding, and the delay is mostly spent waiting for information one member needs. Every question your site answers is a delay it removes.
The failure mode is not rejection. It is a purchase that stops advancing because nobody has what they need to defend it and nobody has enough concern to kill it.
Stalled evaluations rarely register in reporting as anything at all, which is why this cost is usually invisible to the marketing team.
A lost deal has a reason attached in the pipeline. A deal that never advanced past internal discussion has nobody to record it, and no marketing report distinguishes it from a visitor who was never interested.
How to test the page
Write down the six roles in your typical buying group, then read your homepage once for each, asking what that role would do next. Roles with no next step are the gaps.
Then send the page to a customer’s technical or finance stakeholder and ask what they would have wanted before agreeing. Two of those conversations produce a better brief than a persona workshop.
Check what your existing customers forwarded internally when they bought. Sales usually knows, and it is a direct record of which pages carried the argument.
Ask the same customers which question delayed the decision internally. The answer names the page that was missing, and it comes from people who have no reason to flatter you now that the purchase is done.
Neither exercise needs a budget or a research supplier. Both need someone to write the answers down in a place the people editing the website will see them.
The short version
Gartner puts the buying group for a complex B2B purchase at six to ten decision makers, most of whom are managing risk for their own function rather than wanting what you sell. A homepage cannot address all of them in sequence, so it should establish what the company does, who for, and at what scale, then route each role to the page that meets their objection.
Write so the page survives being forwarded without context, keep figures in copyable text rather than images so an internal advocate can quote them, and answer the predictable questions from technical, finance, procurement and user stakeholders somewhere on the site. The cost of leaving those unanswered is a stalled evaluation that never appears in your reporting.
A small thing and a big thing
One small thing to fix on your website today, and one big thing to learn that gets you more leads.
Your information is
safe with us. No spam.