Buying-Committee Mapping: Finding Everyone Who Has to Say Yes

Turning a target account into a named list of the people who decide, block, and champion is a repeated judgement call, and most reps do it badly by reading titles instead of authority. This guide is for founders selling their own product, account executives, SDR leads, and partnerships teams who need to map a buying committee before first touch. It gives you a scoring framework, a procedure you can run in under an hour per account, and the failure modes that turn a clean-looking map into a stalled deal.

Buying-committee mapping is not a research chore you do once at proposal stage. It is a state you hold until the contract is signed, because the thing that kills B2B deals is not a competitor - it is indecision inside a group that never reached consensus.

Why map the committee at all

Committee mapping produces a named stakeholder map per target account, with each person tagged by role, influence weight, and current engagement status. It exists because a single champion is necessary but insufficient: modern B2B decisions are consensus-driven, with veto power distributed across finance, IT, security, procurement, and the line-of-business owner.

The size of the problem has grown. HBR's 2017 "New Sales Imperative" put the average buying group at 6.8 stakeholders. Forrester's 2024 State of Business Buying Report, surveying more than 16,000 global buyers, found the average purchase now involves 13 stakeholders, with 89% of decisions crossing multiple departments. Gartner's most-cited working figure is 6 to 10 decision-makers for a complex solution, each arriving with four or five independently gathered pieces of research, and its May 2025 survey framed the range at 5 to 16 people across up to four functions.

The cost of not mapping is measured in stalls, not losses. Forrester found that 86% of B2B purchases stall during the buying process, and 81% of buyers end up dissatisfied with the provider they choose. The mechanism is internal conflict: Gartner reports that 74% of B2B buyer teams demonstrate unhealthy conflict during the decision process, and conflict defaults to inaction.

The most valuable reframe here: your enemy is "no decision", which Dixon and McKenna (HBR, 2022) put at 40 to 60% of qualified pipeline loss, exceeding losses to any single competitor. A map that only helps you win a bake-off is solving the wrong problem. A map that gets every function engaged before formal evaluation attacks the actual failure.

The six roles you are looking for

Every committee resolves to a small set of functions, and your first job is to name them. The classic Decision Making Unit model, still taught in Bill Aulet's Disciplined Entrepreneurship worksheet at MIT, names six recurring roles: initiator, user, influencer, gatekeeper, decider, and buyer. The go-to-market version reorganises the same functions around what they can do to your deal.

Sources label these differently but converge on the same functions. Note that roles collapse into individuals in smaller firms: in a consumer-scale sale one person may carry several, while in enterprise B2B the same roles split across three or more people. Reconcile role count against headcount before you declare a gap, or you will go hunting for a procurement lead who does not exist because the CFO does that job.

The scoring framework: two axes, four moves

Score each mapped person on two axes and you get a judgement you can act on: authority (can they move budget?) and disposition (are they with you?). Read profile language rather than titles. Deciders describe themselves with ownership words like "overseeing", "managing budget", and "responsible for vendor selection"; champions use "supporting", "coordinating", and "helping evaluate". The words tell you which axis a person sits on far more reliably than the title above their name.

The top-right quadrant is where deals close and the bottom-right is where they die quietly. Most reps spend their energy on the top-left, the enthusiastic champion with no budget, because that person answers emails. The framework's discipline is to force attention to the bottom-right blocker who never replies.

One counterintuitive rule about how you message these people. Content built for individual-level relevance can create conflict inside the buying group, with a measured 59% negative impact on group consensus. Hyper-personalising to each ego hardens private positions. Message the group's shared problem, not each person's private view.

The procedure: from account to named map

Run this in order for any deal above $100K ACV or with a cycle longer than 90 days. Sources agree on the sequence; they disagree only on when procurement and legal enter - early in enterprise, late in mid-market - so slot those steps to your deal size.

The heaviest step is the second, pulling the raw org structure. Manually mapping the org chart for a high-value account, pulling every Director-and-above name and noting who reports to whom, gives you a clear picture of where budget authority sits. It takes 10 to 15 minutes per company by hand. This is exactly the friction a good sourcing query removes: instead of clicking through profiles one by one, you describe the committee you want and get the named people back.

Named tools reps use for the same job include LinkedIn Sales Navigator's Relationship Map, which auto-flags when a mapped contact changes role or leaves, and enrichment tools for contact data. Whatever the tool, the sequence is the same: get the org structure, get verified contact data, then sequence outreach per role. Refolk collapses the first two of those into one plain-English query so you spend your time on the judgement, not the clicking.

The evidence that mapping works

Multithreading a mapped committee raises win rates, and it is one of the better-evidenced patterns in B2B sales, though the magnitude varies wildly by study. The direction is consistent; the exact multipliers are not, and every study below is a vendor analysis rather than peer-reviewed research, so treat them as indicative.

Read past the headline numbers to the mechanism. The win-rate lift comes from redundancy, not persuasion. Roughly 40% of stalled deals die because the primary contact changed roles, left, or got reassigned. The jump from 5% to 30% is really about surviving that turnover, which means the map's value is defensive. More engaged relationships mean no single departure kills the deal.

There is a gap between belief and behaviour here that the framework exists to close. Around 90% of BDRs say they multithread, yet roughly 70% of opportunities still have a single point of contact, and an older LinkedIn CRM analysis found 78% of deals single-threaded with only 7% connected to six or more people. The map's real job is to convert a self-reported behaviour into an auditable coverage number.

Where the supply is scarce

Procurement and security roles are far scarcer than the buyer pool, which makes them the structural bottleneck in your committee. In Refolk's index of professional profiles, the senior-buyer pool dwarfs the negotiator pool, and that ratio predicts which stakeholder will be overloaded and slow to respond.

The procurement negotiator pool is roughly half the CISO base and a fraction of the senior-buyer pool. These figures come from single-country US queries in Refolk's index. The practical read: there are fewer procurement and security people, each covering more deals, so they are the members most likely to be over-loaded and to sit on your deal for weeks. Map them first and engage them early, because they gate throughput regardless of how enthusiastic your champion is.

One caveat on geography. When I ran a VP Sales query across the US and UK together, the sample came back US-dominated at 8,969 people, so treat that as a US figure rather than a clean cross-market split. If you sell into another market, re-run the count against that market before you assume the same supply exists.

How this goes wrong

The framework fails in predictable ways, and the failure modes are more valuable than the procedure because a confident, wrong map is worse than no map. Each one below has a false positive - a reason the map looks fine when it is not - and a check that catches it.

• Title-based role assignment. The senior title is often a rubber stamp. A VP with the biggest title may not control this budget. Check profile ownership language and direct-report count, not the title alone.
• "Multithreaded" that is really one silo. Adding the champion's direct report and a same-function peer looks like coverage but is threading deeper into one silo. Check that IT, finance, procurement, and the business unit are each represented.
• Champion mistaken for decider. A strong champion is necessary but insufficient because veto power is distributed. Check whether the person can actually allocate budget or only advocate.
• Ignoring the gatekeeper until late. Security and procurement quietly kill deals; a security officer may need to approve any new software before it reaches anyone else, and conversations die there without the seller ever knowing. Check that a security or compliance stakeholder is on the map before formal evaluation.
• Stale map. The deal looks covered but the contact left; 40% of stalled deals die from exactly this. Check turnover flags on every mapped contact and re-verify at each stage.
• Mapping the org but not scoring readiness. A fully qualified committee can still refuse to decide, because qualification measures whether the deal conditions exist, not whether the buyer can act. Check for evidence of active pain and a decision deadline.
• Assuming one person equals one role. Roles collapse into individuals in smaller firms. Reconcile role count against headcount before declaring a gap.
• Over-tailoring to individuals. Hyper-personalised messaging can fragment the group, with a measured 59% negative impact on consensus. Check whether messaging helps members understand each other's perspective or only reinforces their own.

The funnel above is directional, built from the dossier's loss rates rather than a single tracked cohort, so read the shape rather than the exact counts. The shape is the point: the biggest leak is internal consensus, which happens before any competitor enters.

What "done" looks like before first touch

A committee map is ready when it survives the checks below, not when it has the most names. Run this before you send the first message and again at every pipeline review, because the map decays as people move.

Name | Title | Function (buyer/champion/tech/procurement/legal/sponsor/user) | Authority (high/med/low) | Disposition (with/neutral/against) | Verified? (Y/N + date) | Engaged? (Y/N) | Next move

Keeping the map current

A committee map is a living document, so build re-verification into your pipeline cadence rather than treating mapping as a one-time proposal-stage task. Multithreading is a state you hold until the contract is signed, not an event.

Set two recurring checks. First, at every pipeline review with your manager, confirm more than one engaged contact per deal; a deal with a single thread is a deal one departure away from stalling. Second, watch for movement - a mapped contact changing role or leaving is the single largest cause of stalls, so tools that auto-flag role changes earn their place here. When a champion moves, that is not only a risk to the current deal but a signal for the next: a previous champion who arrives at another target account is one of the warmest openings you get.

Re-run the coverage question, not just the contact list, each time the deal advances a stage. New stages surface new functions - security at evaluation, procurement at proposal, legal at contract - and a map that was complete for discovery is thin for redlines. The discipline that separates a mapped committee from a lucky one is treating coverage as a number you audit, converting the 90% of reps who believe they multithread into the minority who can prove it.