A founder pulled me into a Slack DM last month, panicking. A deal he had worked since January, an eight-figure ACV target, had just slipped to next quarter. Again. He had run six demos, three pricing calls, and a security review with his champion. The champion told him the buyer was a "lock". Then a name nobody had heard of showed up on a late email asking about data residency in Frankfurt, and the deal froze.
I asked him one question. "Who else in the account did you talk to besides your champion?" He looked at his CRM. The contact count on the account was one. His champion. After ten months in pipeline.
This is the most common reason B2B deals die, and it has nothing to do with product, pricing, or competition. The buying committee did the work without the seller in the room, and the seller never knew it existed. So let me walk through how to map a buying committee properly, where most teams get it wrong, and the operating system I use with my clients to keep deals from going dark.
Why one champion is not a strategy
Gartner has been saying the same thing in slightly different ways since 2017. The typical B2B buying group has 6 to 10 decision makers, and each one drags 4 to 5 pieces of information they collected independently into the room. By 2026, every CRO I have spoken with says the number is closer to 8 in their deals, with at least two of those buyers being someone in finance or procurement that the seller never spoke to.
If you are working a deal with one contact, you are not actually working a deal. You are working a champion. The deal is happening somewhere else, in Slack threads and forwarded PDFs and a Notion doc your champion built to convince their boss. You have zero signal into any of it.
This is why a deal can look like a 90% commit on Monday and a "lost to competition" on Friday. Nothing happened with your champion. Something happened with the four people you never met.
If your CRM shows one contact on a five-figure-plus deal, that deal is not real.
You are not selling to a person. You are selling to a group, and the group has been meeting without you. Map the group before the next call, or stop forecasting the deal.
The five roles every buying committee has, even if nobody admits it
Forget the old MEDDIC and BANT labels for a minute. Those tell you what questions to ask. They do not tell you who is in the room. In every B2B deal above 25K ACV, I find these five roles, and you need a name in your CRM for each one before you forecast the deal.
The economic buyer. The person who signs the budget. Often the CFO for finance tools, the VP of sales for revenue tools, the CTO for dev tools. Usually not your champion.
The user buyer. The person whose team will actually use the product day to day. Often the manager one level below the economic buyer. They care about workflow, not strategy.
The technical buyer. Security, IT, data, or the person who has to integrate your tool. Their default answer is no. Their power is veto only, but veto is enough to kill the deal in week 11.
The coach or champion. The person who wants you to win and will tell you what is happening. They are not always senior. Often the most useful coach is a sharp manager three levels deep.
The blocker. The person who already has a vendor they like, or a project they are protecting, or a budget line they are guarding. Every deal has at least one. If you do not know who it is, it is you.
What buying committee mapping actually looks like
The mistake I see most often is treating the committee map as a one-time exercise the AE does once at the qualification stage, then forgets. The committee is a living thing. People rotate, get promoted, leave. Someone you never met joins the eval in week eight because a peer mentioned your name in a meeting.
Mapping is a discipline, not a deliverable. Here is the operating cadence I install with my clients.
At the start of every deal above your minimum threshold, the AE has to fill in a stakeholder grid. Real names, real titles, real LinkedIn URLs, real email addresses. Not placeholders. If they cannot fill it in, they have not done discovery. The deal stage does not move forward.
Every two weeks, the AE has to update the grid in their pipeline review. Who did you add? Who did you talk to? Who went dark? Who came in late? This is not paperwork. It is the only thing that catches a deal going sideways before it shows up in the forecast as a slip.
At the close call or last-mile review, the grid has to show at least four engaged stakeholders for any deal above the average ACV. Engaged means a real conversation in the last 30 days. Not "we sent them a deck". Engaged.
The single-threaded versus multi-threaded comparison
The funny thing here is that the single-threaded AE almost always forecasts higher confidence than the multi-threaded one. They feel like they are winning. The champion is texting them. The user demo went great. Of course it is a 90% commit.
The multi-threaded AE has seen the IT team push back on the SSO requirement. They have heard the CFO ask about a competitor. They are forecasting 70 because they actually know what is happening. And they close 65% of the time, while the single-threaded AE closes 15%.
This is why pipeline reviews that go off the rep's gut are dangerous. The reps with the worst signal feel the most confident. The reps with the best signal sound worried. If you only listen to the confident voice in the room, you build a forecast on the deals that are least likely to land.
How to actually find the missing stakeholders
The AE who says "my champion is the only person I can get to" is almost always wrong. They have not tried hard enough. Here is what works.
Start with a LinkedIn map of the account. Pull the org chart for the function that is buying. If you are selling sales tech, find every director and above in revenue. If you are selling security, find every director and above in IT and security. Drop those names into your CRM as contacts before the next call.
Ask the champion directly. "Who else should be in our next conversation?" If they hedge, name names. "I noticed you have a director of operations. Should they be part of this?" Naming a real person makes it easier to say yes or no than the abstract "who else".
Use the tools you already pay for. Most CRMs and engagement platforms can show you who has opened your emails, visited your pricing page, or watched your demo recording. If three new people from the account have opened the proposal you sent your champion last week, those three people are now part of the deal. Get their names in the CRM and reach out.
Send the executive summary directly. After every key call, send a short summary email to the champion and ask them to forward it to "anyone else evaluating". Most champions will copy two or three people. Now you have email threads with those people, which means you can reach out one on one.
How to set this up in your CRM
In HubSpot, this means three things. First, you need a custom property on the contact object called "buying role" with a dropdown of the five roles. Second, you need a custom property on the deal object that shows a stakeholder count, calculated from how many contacts on the associated company have a buying role filled in. Third, you need a workflow that flags any deal above your ACV threshold with fewer than three filled roles when it hits proposal stage. I have built this in about four hours for clients who already had HubSpot Sales Hub Pro. The blockers are usually political, not technical.
In Salesforce, the same pattern works with contact roles on the opportunity, which has existed forever and almost nobody uses correctly. Most Salesforce admins set up the contact roles object on day one, then never touch it again. Make filling it in a required field at the proposal stage. Run a report weekly that shows opportunities with fewer than four contact roles. Those are the deals that will slip.
In Attio, you can build this natively with the relationship model since contacts and companies and deals are all first-class objects. Add a "buying role" attribute on the people object, filter views by role, and build a dashboard that surfaces understaffed deals.
The tool does not really matter. What matters is that the data exists, the reps are required to keep it current, and the pipeline review uses it as the first filter before the forecast number gets discussed.
Where AI changes the workflow in 2026
A year ago, building a buying committee map was 30 to 60 minutes of manual work per account. LinkedIn searches, email guessing, title verification. The AE who did it well closed more, but the cost was real, so most reps skipped it.
In 2026, this is mostly automated. Tools like Clay can pull the org chart, identify likely buying-committee members based on title and reporting line, and enrich contact data in under five minutes per account. I have built workflows for clients that fire a Clay table the moment a deal hits qualification stage. The output drops 8 to 12 enriched contacts into HubSpot with buying roles pre-tagged based on title. The AE reviews and edits, but the heavy lifting is done.
n8n sits on top of this. When a contact at an account opens a pricing page, n8n updates the deal with that signal and pings the AE in Slack with "someone you have not met just looked at pricing". The deal moves from a static record to a live system that surfaces stakeholder changes in real time. I wrote more about n8n workflows for B2B revenue teams if you want the technical setup.
The cost has dropped from "AE does it manually if they remember" to "the system does it automatically and the AE just acts on what surfaces". This is where I think most teams should invest their RevOps budget in 2026, more than another lead scoring rebuild or another attribution tool. The accounts you already have in pipeline have the highest ROI, and the way to get more from them is to know who is in the room.
What this looks like for a client we built it for
A Series B company I work with was running 14 active deals in a typical quarter. Single-threaded. Average four contacts per closed deal, but only one or two per lost deal. We installed the stakeholder grid, made it required, and added the Clay enrichment workflow.
Three quarters in, the numbers had moved. Average contact count on closed deals went from four to seven. Win rate on proposal-stage deals went from 31% to 48%. The biggest change was not the win rate, it was the slip rate. Deals that used to push two quarters because someone unexpected showed up at the end now pushed maybe half a quarter because the someone was already in the CRM in month two.
The CRO told me the most valuable thing was not the higher win rate. It was that the forecast finally matched reality. He could tell his board what was going to close, and it actually closed. That is what a real buying committee process buys you. Not magic, just signal.
Want to install this in your pipeline?
I have built this exact stakeholder mapping system in HubSpot, Salesforce, and Attio for B2B teams from seed stage to Series C. Book a free 30 minute audit and I will show you the three changes I would make first in your CRM.
Book an audit →FAQ
What is buying committee mapping?
Buying committee mapping is the practice of identifying every person involved in a B2B purchase decision, recording them as contacts in your CRM with their buying role tagged, and keeping that map current throughout the deal cycle. It replaces the older model of selling to a single champion and hoping they sell internally on your behalf.
How many stakeholders should be on a typical B2B deal?
For deals above 25K ACV, you should have at least four engaged stakeholders in your CRM by the proposal stage, with at minimum one champion, one economic buyer contact, one user manager, and one technical or security contact. Below that count, the deal is at high risk of stalling when someone you have not met enters the eval late.
What is the difference between single threading and multi threading in sales?
Single threading means selling to one person at an account, usually the champion. Multi threading means actively building relationships with multiple stakeholders across roles and seniority levels. Multi threaded deals close roughly three times more often than single threaded deals at the same ACV level, because the seller has real signal on what is actually happening in the buying group.
How do I get my reps to actually fill in the stakeholder grid?
Make it a required field in the CRM that gates deal stage progression. If the grid is not filled in, the deal cannot move to proposal stage. Reinforce it in pipeline reviews by asking only about named stakeholders, not deal feelings. After three or four cycles, the reps either fill it in or the deals fall out of the forecast and the pattern becomes visible to leadership.
What tools help with buying committee mapping in 2026?
Clay is the best enrichment tool I have used for pulling org charts and identifying likely buying-committee members from a single account name. HubSpot, Salesforce, and Attio all support the stakeholder grid pattern natively if you configure them correctly. n8n is useful as the glue layer that fires enrichment and surfaces stakeholder changes back to the AE. The combination of those four covers most B2B teams up to Series C.