The Buying Committee Map Every AE Should Draw in the First Two Meetings
Every enterprise B2B deal has a committee behind it.
Gartner puts the average size at 6 to 10 people. Not one buyer. Not two. Six or more.
Most AEs map two of them. The champion. The person who does the demo. That is why deals stall in the middle.
Who is on the committee
Every enterprise deal has these roles inside the buyer's company.
The economic buyer. Signs the contract. Owns the budget. Often invisible until stage 3.
The technical evaluator. Runs the POC. Tests the demo. Writes the review that lands on the executive's desk.
The end user. Will live with the tool. Their complaint kills a deal faster than any exec's.
The champion. Sells the deal internally. The person the AE talks to most.
The executive sponsor. Carries political weight. Rarely on the calls. Signs the vendor selection memo.
The procurement gate. Negotiates the discount. Adds 30 days to every deal cycle.
The security review. For deals over $250K. IT and Info Sec. Silent until day 60.
That is seven names on average.
Why most AEs only see two
Two reasons.
First, the champion introduces the AE to the demo person and stops there. That is not a stakeholder map. It is a courtesy tour.
Second, most AEs feel awkward asking "who else needs to be involved in this decision?" It feels pushy. It is not. It is the question that saves every deal.
Ask it in meeting one. Ask it again in meeting two. Ask it a third time before the demo.
The 2-meeting mapping method
Meeting one goal: get names.
Not titles. Not org charts. Names. Real people. Real relationships to the champion.
The question that works: "Who is the person you would need to convince if you decided to move forward with this?"
That surfaces the economic buyer.
Then: "Who would need to sign off from a technical side?"
That surfaces the evaluator.
Then: "Who lives with this every day?"
That surfaces the end user.
Meeting two goal: get access.
Bring one or two of those names into a call with the champion. Not all four at once. That looks like a pitch.
What each name is worth
A mapped economic buyer means the champion has ammunition to sell up.
A mapped technical evaluator means the POC does not surprise the AE.
A mapped end user means the objection does not appear in month six.
Every unmapped stakeholder is a possible veto the AE cannot see.
The one-line rule
If you have mapped fewer than four people by the end of meeting two, the deal is single-threaded.
Multi-threading is not "we CCed procurement on the proposal." It is knowing the name, the title, the priority, and the objection of at least four humans inside the buyer's org.
The AE who does this has coverage. The AE who does not has hope.
Related reading
- Why multi-threaded enterprise deals win 34% more often
- Why enterprise deals go silent after the demo
- 4 stakeholders to reach before stage 4 in enterprise sales
- State of B2B Sales 2026
Try scoring one of your live deals against a real stakeholder map: saleskriya.com/deal-scorer. No login. Two minutes.
See whether the model fits your team
We embed a senior Sales Leader and an AI System of Action to build, enforce, and run your playbook across 6 to 12 months. Start with a revenue diagnostic.
Get a revenue diagnosticDiscussing this on LinkedIn.
We open every blog up for discussion on the Sales Kriya LinkedIn page. Share your take there, or send us a private reaction below.
Or send us a private reaction.
We read every one. If something here rang true (or not) for your team, tell us. No newsletter, no sequence.
More from Sales Kriya
Sales Kriya is an embedded sales coaching partnership plus an AI System of Action for enterprise B2B teams. The full model is on how we work, and the four-condition fit check is on the alignment matrix. If a stalled deal of your own came to mind while you were reading, the three free tools. Score a deal, Score a call, Pick a play. Are the closest thing to seeing the model run on your data.