Why One Generic Deck Can't Win an 11-Person Buying Committee
A generic deck sent to one contact cannot answer what the economic buyer, the technical evaluator, and the end user each need to know, so it satisfies none of them fully. The fix is building one trackable prospect page with distinct sections for each role, then watching which sections each stakeholder actually opens to see who still needs convincing.
How many people actually decide a B2B purchase today?
More than you are probably building for. Forrester's 2024 State of Business Buying Report found that 41% of B2B buyers already have a preferred vendor before formal evaluation even begins, and that same research puts the typical buying group at thirteen people spanning multiple departments. Gartner's figures run a little lower, closer to six to ten stakeholders for complex purchases, but every major research firm agrees on the direction: committees have gotten bigger, not smaller, and the median enterprise buying group includes 11 stakeholders for technology and SaaS purchases above $100,000 annual contract value.
The gap between that number and how most reps actually sell is the real problem. You get one meeting, usually with one or two people in the room, and you send one follow-up asset built for whoever happened to show up. The other nine or ten people who will weigh in before a signature happens never see anything built with them in mind.
Why does sending everyone the same material hurt your chances?
Because the CFO, the department head, and the person who will use the product every day are not evaluating the same thing. Multi-threading research breaks this down cleanly: technical buyers care about integration and implementation, economic buyers care about ROI and strategic impact, and end-users care about workflow changes and ease of use. A deck optimized for one of those concerns reads as irrelevant to the other two.
This is not a minor inefficiency. Research on buying committee outcomes found a win rate with 6+ stakeholders mapped of 34% versus 11% when fewer than three are mapped, and separate analysis of closed deals found that engaging five or more contacts within a buying committee increased win rates by 82%, with each new engaged contact improving win rates by approximately 12%. The stakeholders you never speak to are not neutral bystanders. They are votes, and a generic asset does nothing to earn them.
The usual response is building more collateral: a technical one-pager here, an ROI calculator there, a slightly different deck for each persona. That solves the relevance problem and creates a new one, because now you are tracking five disconnected files with no shared record of who opened what. You end up guessing which version landed and which one sat unread in an inbox.
What does a prospect page built for a whole committee look like?
It looks like one link with distinct sections instead of five separate files. Rather than mailing a technical buyer a spec sheet and an economic buyer a business case under different cover emails, you build a single page where the cost and ROI argument sits in one section, the integration and security detail sits in another, and a short walkthrough video addresses the end user's day-to-day concern. ActiDesk lets you assemble that kind of page in minutes ahead of a meeting, combining video, a business-card-style introduction, and a document section on one branded desk scene, so each stakeholder finds their own entry point without wading through material meant for someone else.
This matters most in deals where the buying group spans departments with genuinely different stakes. A home services contractor bidding on a multi-site commercial maintenance contract is a good example. The facilities manager wants to see the crew and the equipment. The finance contact wants the pricing structure and the contract terms. The property owner wants a sense of who they are actually hiring. A resource built for home services and contractor teams shows how that kind of segmented page gets built around a single opportunity instead of three separate pitches that never reference each other.
How do you know who on the committee is actually paying attention?
You look at what they open, not what they say. A link sent to one contact and then forwarded internally used to be invisible, but engagement tracking on a shared page now surfaces that movement directly. Content engagement research describes this as one of the clearest buying signals available: when two or three people from the same account read the same asset within a short window, it is a reliable indicator that someone has shared it internally.
The detail that matters even more than who opened the page is what they spent time on once inside it. Document engagement platforms built for complex sales track exactly this, noting that forwarding and multi-stakeholder detection reveal when a document was passed internally, and see how each additional stakeholder engaged with it. If your economic buyer section gets three times the time-on-page that your technical section gets, that tells you the deal is stalling on budget, not on fit, and you can call the right person with the right answer instead of guessing.
That kind of visibility changes what a follow-up call sounds like. Instead of opening with "did you get a chance to look at what I sent," you open already knowing which section someone spent four minutes on and which one they skipped. Sales teams using this kind of first-party engagement data describe it as a more accurate signal than general intent data because when a buyer reads your content inside your ecosystem, you see exactly which topics they engaged with, how deeply they read, and what they came back to, which is a much closer read on actual buying behavior than a form fill or a website visit ever was.
Building the page without losing the thread
A segmented page only works if it still reads as one coherent pitch rather than three unrelated arguments stapled together. The table below is a rough guide to what belongs in front of which stakeholder, used as a starting point rather than a rigid template.
| Stakeholder | Primary concern | What to put in front of them | |---|---|---| | Economic buyer | Cost, ROI, timeline | Business case, pricing structure, payback estimate | | Technical evaluator | Integration, security, fit | Implementation detail, technical specs, architecture notes | | End user | Daily workflow, ease of adoption | Short demo video, walkthrough, day-in-the-life example | | Executive sponsor | Strategic alignment | One-paragraph summary tying the deal to a larger goal |
None of this replaces the conversation you have with your champion about who else is involved and what they each care about. Multi-threading guidance is consistent on this point: ask directly who needs to sign off and who controls budget before you build anything, rather than guessing at the org chart. What a shared, trackable page adds is a record of what happened after you asked, so the next six weeks of follow-up are built on evidence instead of assumption.
Reps who still send one static PDF to one contact are betting that a single champion will carry their case accurately through eight or nine more conversations they will never hear. Some champions do that well. Most compress a forty-minute pitch into two sentences in a Slack message, and the people reading that message never see your ROI numbers, your security answer, or your demo. Building a page that speaks to the whole committee, and watching which parts of it actually get read, is how you stop depending on a secondhand retelling of your own pitch. If you want to see what that looks like for your next meeting, you can start building a prospect page through ActiDesk's signup before the committee starts talking without you in the room.