Buying-Committee Mapping: Naming Who Decides, Blocks, and Champions

A target account is not one buyer. It is a group of people who each hold a piece of the decision, and the deal advances only when you know who they are by name. This guide is for founders selling their own product, account executives, SDR leads, and partnerships teams. It gives you a framework to turn a target account into a named list of the people who decide, block, and champion, scored so you know where to spend your next call.

Why one name is not an account

A complex B2B buying committee runs six to ten decision-makers per Gartner, so treating a target account as a single buyer is a structural error, not a shortcut. Each of those people arrives with their own four or five independently gathered facts, which means you are not persuading one mind but reconciling several.

The numbers have drifted upward for a decade, and the direction is the point. Larger benchmarks push higher: Gartner's 2022 median is 11 stakeholders for enterprise software above $100K ACV, Forrester's 2024 work puts the average B2B purchase at 13, and deals above $1 million reach 14 to 23 per Forrester's 2023 study. Gartner also reports that 77% of B2B buyers describe their last purchase as complex or difficult. The load-bearing figure to plan around is Gartner's 6 to 10; the rest tell you which way the risk points.

The cost of an unmapped member is measurable. Each additional stakeholder cuts the probability of purchase by roughly 10 percentage points, which reframes mapping from admin into a defence of your own forecast. A stakeholder you have not named is not a rounding error; they are a ten-point drain sitting outside your view.

The five roles every committee has

Before you name anyone, name the seats. A five-role core recurs across practitioner frameworks: champion, economic buyer, technical evaluator, user or operator, and procurement or compliance. Everyone else is secondary. Writing these as blanks first stops you from cataloguing whoever is easy to find and calling the map complete.

The five roles are:

• Champion: the internal advocate who sells on your behalf when you are not in the room.
• Economic buyer: the person who controls the budget and can say yes to spend.
• Technical evaluator: the person who judges architecture fit and integration.
• User or operator: the person who will live with the product day to day.
• Procurement or compliance: the person who clears risk, security, and terms.

MEDDIC formalises two of these directly. The framework - Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion - was created at PTC in 1996 by Dick Dunkel and Jack Napoli, and is credited with taking PTC's sales from $300M to $1B in four years. If your team already runs MEDDIC, the economic buyer and champion seats are shared vocabulary; this framework adds the three you are most likely to leave blank.

Where the roster is easy to find and where it lies

Supply shapes attention, and attention skips the scarce role. The economic buyer is abundant and findable; the blockers who hold veto power are rare, which is exactly why they surprise you late. Refolk's index makes the gap concrete.

In Refolk's index there are 103,875 US profiles holding CFO, VP of Finance, or Head of Finance titles, against 886 US procurement leaders. That 117x gap is why teams over-index on the economic buyer and under-map the specialist who can quietly kill the deal. You will always find "a" CFO fast. That does not mean you found the person who signs.

Geography changes the shape of the committee. UK procurement is denser than US supply, a signal worth reading before you map an overseas deal.

The UK shows 1,674 procurement leaders to the US's 886, a 1.89x ratio despite a smaller economy, because UK and EU procurement is a more formalised, titled function. The practical read: on UK deals, expect a named procurement gate earlier and map that seat before you think you need it.

Finding names by role pattern used to mean stitching together LinkedIn searches and org-chart guesses. Refolk lets you ask for the seat you need in plain English - the economic buyer, the security lead, the head of the using department - and get named people back across LinkedIn and the open web, so the map starts filled instead of blank.

Score each member on influence, stance, and access

Once every seat has a name, score each person on three dimensions so you know where your next hour goes. Stance says which way they lean, influence says how much their lean matters, and access says whether you can actually reach them. A name without a score is a contact, not a map.

• Stance: decide, block, or champion. Who can approve, who can veto, who will sell for you.
• Influence: how much weight their stance carries in the room, high or low.
• Access: whether you have a live thread to them, direct or via the champion.

The two variables that most often mislead a forecast are stance and influence, so it helps to see them as a grid. A high-influence blocker is your priority; a low-influence champion feels good and moves nothing.

Public scoring rubrics exist but are illustrative, not standardised. One worked example weights technical capabilities at 40%, integration ease at 25%, scalability at 20%, and vendor support quality at 15%. Treat that as a template for scoring the decision, not the people. A robust cross-industry weighting for scoring committee members is not established publicly, so keep your influence weights simple and defensible: high or low, tied to a reason you could say out loud to your manager.

Name | Role slot | Stance (decide/block/champion) | Influence (H/L) | Access (direct/via champion/none) | Last touch
J. Okafor | Economic buyer | Decide | H | Via champion | Discovery call
R. Mensah | Security | Block | H | None | Not yet engaged
S. Patel | User lead | Champion | L | Direct | Weekly

The procedure

Run these seven steps in order. The first two happen before you name anyone; the rest are where the map gets built, scored, and kept alive. In smaller companies the initiator might also be the user and the decision maker, so the profile you set in step one governs how hard you thread the rest.

On step six, sequence matters. Some teams confirm before scoring; MEDDIC-driven teams score continuously through discovery rather than as a discrete step. Either way, do not interrogate. Identify likely stakeholders by role pattern first, then confirm with two or three targeted questions. Your champion should be validating a draft, not building the map for you.

Multi-threading is the whole point

The reason you map is to engage more than one person, because coverage of the committee, not persuasion of one person, is the lever that moves win rates. A single-threaded opportunity has about a 5% chance of winning; taking that to five people jumps it to 30%, a 6X improvement in UserGems' analysis of 500 opportunities. Gong separately reports multi-threading boosts win rates by an average of 130% in deals over $50K.

This is not a theoretical curve. In the Pedowitz case, engaged roles per opportunity rose from 2.1 to 5.4 after the team standardised buying-committee maps - almost exactly the five-person threshold UserGems ties to the 6X jump. The mechanism is coverage: the deal did not get more persuasive, it got more mapped.

Sequence the threads. Build a champion first, then expand around the third touchpoint; leading with executives too early drops win rates. Consensus is built inside rooms you never enter, so the champion has to be armed with your facts before the committee convenes. Multi-threading is not spraying the org with emails on day one. It is arming one advocate, then widening deliberately.

Coverage of the committee, not persuasion of one person, is the lever that moves win rates.

How this goes wrong

Most bad maps fail in one of six predictable ways. Each has a tell and a fast check. Read this section as the core of the framework: a map that survives these is a map you can forecast on.

Title-matching the economic buyer

With 103,875 US CFO-type profiles in Refolk's index, you will find "a" CFO in seconds. But the real budget holder for a $60K tool is often a VP or director, not the C-suite. The false positive is a named C-level who never touches the deal and inflates your map's credibility. Ask your champion who signs the purchase order at this dollar amount.

Missing the silent blocker

Compliance, security, and procurement kill more late-stage B2B deals than any other role, and they rarely signal early. Their supply is thin - 886 US procurement leaders and 4,572 CISOs in Refolk's index - so they are structurally easy to overlook. Name a security and a procurement contact during discovery, not when the contract hits legal and stalls.

Coach mistaken for champion

A coach likes you and shares information; a champion actively sells on your behalf, navigates politics, and puts their reputation on the line. The false positive is a friendly contact who takes your calls but never introduces you upward. The tell is behavioural: real champions respond within about 24 hours, volunteer process information, and name other stakeholders without being asked. If your contact does none of these, you have a coach, and the champion seat is still empty.

Single-threaded confidence

A deal built on one loved contact forecasts as strong and wins about 5%. Confidence is not coverage. Count the engaged roles on the map; fewer than three named, live threads is a structural risk regardless of how warm the one relationship feels.

Stale map and mis-sized committees

A relationship map flags when a lead leaves, but only if you keep it current. A mapped champion who changed jobs is a dead thread that still shows green. Re-survey after every stage change. And do not borrow enterprise committee sizes for SMB deals: the 11-to-23 figures are enterprise, and over-threading a three-person shop wastes cycles and annoys buyers. Size to the profile first.

Keep the map alive

A buying-committee map decays the moment you stop touching it, so treat it as a living record, not a one-time artifact. Update maps at key moments: when a new stakeholder appears, after major meetings, when the deal advances a stage, and after a win or loss. The re-survey after a win or loss is the one teams skip and the one that compounds, because it teaches you which seats you keep missing.

Run this checklist before you call any account mapped and ready for first contact.

The framework does not end at a full roster. It ends when every seat is named, scored, and touched recently enough to trust. A map that names the abundant economic buyer and skips the scarce procurement gate is the map that loses in legal review. Build for the roles supply makes you forget, keep three threads live, and re-survey on every stage change. That is the difference between a contact list and a committee you can close.