How to Build a Buying Committee Map for Your Top 20 Target Accounts
Most early-stage outbound runs single-threaded into a buying group of 6–10 people. Forrester's 2026 data puts that group at 13 internal stakeholders and 9 external influencers. Here's how to map a buying committee — and why deals you single-thread mostly stall.
The single most common pattern we see in early-stage outbound is also one of the most expensive: a Seed-stage team identifies a great target account, finds the one obvious buyer (usually the VP or the Head of), and runs the entire outreach motion at that single person. When the person doesn’t reply, the account is marked “no interest” and quietly dropped.
The data on what’s actually happening inside those accounts is unambiguous and worth absorbing. Modern B2B purchase decisions are committee decisions, and the committee has been getting larger, not smaller. Mapping the committee — even loosely — is one of the highest-leverage moves a small outbound team can make.
How big is the committee, really
The most-cited baseline is Gartner’s research showing the typical B2B buying group includes 6 to 10 stakeholders, each bringing 4 to 5 independent pieces of research. That number used to feel high. It’s now low.
Forrester’s 2026 State of Business Buying report puts the average at 13 internal stakeholders plus 9 external influencers, with AI-related purchases doubling the group size again. Procurement alone is now a decision-maker in 53% of B2B buying cycles, up sharply over the last three years.
The consequence for outbound is direct: if you’re sending one email to one person inside a target account, you’re talking to roughly 5–10% of the committee. The other 90% don’t know you exist.
The cost of running single-threaded
The conversion math on single-threading is brutal. Forrester data, cited via ZoomInfo’s pipeline analysis, shows that 74% of single-threaded deals stall or lose, versus 28% of multi-threaded deals. UserGems’ analysis of sales multithreading finds that engaging three or more contacts per deal lifts close rates by 2.4x — and by 3.1x in enterprise. And one of the quietest failure modes: 40% of stalled deals die simply because the single point of contact left, changed roles, or was reassigned. The deal didn’t lose. It just lost its only thread.
For a Seed-stage team, the implication is sharper than it sounds. You don’t have enough at-bats to waste accounts. Each target account that should have been a real conversation but didn’t get one because you single-threaded is a multi-quarter setback.
What a buying committee map looks like
For your top 20 target accounts — and yes, 20 is the right number, not 200 — the goal is a one-page committee view per account. The structure we use:
The Owner. The person whose function owns the problem. Almost always the first name founders identify. Often (but not always) the budget holder. Example: Head of Platform Engineering.
The Champion candidate. The person who would carry the project internally if it lands. Usually one or two rungs below the Owner. Example: Staff Platform Engineer who runs deployment infrastructure.
The Economic Buyer. Whoever signs off on the spend. Often above the Owner, often only loosely engaged early. Example: VP Engineering or CTO.
The Influencers. Anyone whose objection can stall the deal even if they aren’t the buyer. In enterprise this is Security, Procurement, Legal, sometimes Finance. In mid-market it’s often “the person who already evaluated something like this last year.”
The Detractor risk. The person most likely to push back, either because they own the incumbent solution, just got hired, or has scar tissue from a prior bad implementation.
You don’t need every name on day one. You need the roles identified, and at least two of the five names sourced before the first outreach goes out.
“When we run discovery on an account where the founder swears ‘we tried, they didn’t respond,’ the first thing we look at is how many people were contacted. The answer is almost always one. The fix isn’t a better sequence — it’s a different threading model. Two more stakeholders in the same account is more leverage than two hundred more accounts at the same depth.” — Kelly Arnstein, Head of Outbound at Outbound Panda
How to source the committee without burning a week
A few practical moves that compress the work:
- LinkedIn Sales Navigator for org topology. Filter to the company, the relevant department, and seniority band. The right buying committee shape usually becomes visible in 10 minutes per account.
- Hiring signals as a tell. If a company has hired three roles reporting to the Owner in the last quarter, the Owner is building a team and is likely actively making tooling decisions. That maps to urgency.
- Pull tooling/tech-stack from BuiltWith or similar. What they’re running tells you who else is in the conversation. A Snowflake stack implies a Data Platform leader. An Auth0 stack implies a Security stakeholder.
- Look for “owner of the problem” in job posts. A current job listing often names the person it reports to and the team it joins, which is committee-mapping in plain text.
- Cap it at five named people per account. More than that and you’re doing research, not outbound.
How to thread the outreach without spamming
Mapping the committee doesn’t mean sending five identical emails to five people in the same account on the same day. That’s how you get flagged as “sales spam” by everyone at once. The pattern that works:
- Sequence the Owner first, with the sharpest, most-personalised message.
- Two weeks later, lightly approach the Champion candidate with a different angle — usually more tactical, more operator-toned.
- Surface the Economic Buyer through the Champion, not directly. Once you have a real conversation with the Champion, ask who else should be in the room. Direct outreach to the Economic Buyer in cold state usually under-delivers.
- Address the Detractor risk early in discovery, not in outreach. If you can ask the question “who internally would resist this?” in the first call, you’ve collapsed two weeks of stall later.
What this means in practice
Single-threading is the most common form of unforced outbound failure at Seed stage. Mapping the committee isn’t enterprise-style account-based selling — it’s basic respect for the data on how decisions actually get made. Twenty accounts, mapped to five roles each, with two real names per role identified before launch, will outperform 200 single-contact accounts in every metric you can measure.
The number of contacts per account is one of the few outbound levers where the right answer is “more, not fewer.” Use it.
