Identify the Buying Committee in B2B Sales

Most deals fail not because your product is bad, but because you're talking to the wrong people.

You build a relationship with the VP Demand Gen. You have a great first conversation. You send a proposal. Silence.

Six weeks later, you find out the IT Director rejected it on security grounds. The CFO wanted a different pricing model. The VP's boss had already decided on a competitor.

You were never talking to the real buyers.

This is the buying committee problem. B2B deals involve multiple people. Unless you map all of them, you're flying blind.

Who's on the Buying Committee?

In a typical B2B deal, there are 4-6 key stakeholders:

1. Economic buyer (who controls the budget) - Usually C-level (CMO, CRO, VP Finance) or their direct report - Cares about: ROI, budget justification, strategic impact - Approval needed: Yes (can't move forward without them) - Blocking power: Highest

2. User buyer (who uses the product day-to-day) - Usually director-level (VP Demand Gen, demand gen manager, marketing manager) - Cares about: Ease of use, integration with tools they use, workflow efficiency - Approval needed: Yes (won't use a tool they hate) - Blocking power: High

3. Technical buyer (who validates against requirements) - Usually IT director, security lead, or infrastructure team - Cares about: Security, compliance, data residency, integrations - Approval needed: Maybe (depends on company policy) - Blocking power: Can be absolute in regulated industries

4. Influencer (who influences but doesn't buy) - Usually individual contributor or peer of the user buyer - Cares about: Day-to-day usability, whether peers are using it - Approval needed: No (nice to have) - Blocking power: Low-medium (can persuade others)

5. Champion (your advocate inside the account) - Could be anyone on the team who loves your product - Cares about: Success of the deal (they bet on you) - Approval needed: No, but helps - Blocking power: Zero, but can amplify your message

6. Blocker (who can kill the deal) - Usually someone with veto power (head of security, CFO, head of legal) - Cares about: Risk mitigation - Approval needed: Yes (deal dies without them) - Blocking power: Absolute

Mapping the Committee: Interview Your Sales Team

Your AEs know this. Ask them.

Schedule a 30-minute session with your top 3-5 AEs. Ask:

1. "In your best deals, who are the 4-6 people in the buying committee?"
2. Get titles, not names

3. Ask for typical names (CMO, VP Sales Ops, etc.)

4. "How do they interact?"

5. Does the CMO recommend to the CFO? Or does the CFO pull in the CMO?

6. Who has final say?

7. "What can each person block?"

8. Can IT Director block the deal on their own?

9. Can CFO kill it on price? On security?

10. "Who usually comes to the conversation first?"

11. Is it a top-down buy (CFO identifies need, pulls in VP Demand Gen)?

12. Or bottom-up (VP Demand Gen pitches, then brings in CFO)?

13. "What's the typical decision timeline?"

14. How long between first conversation and final approval?
15. Who moves fastest? Who drags their feet?

Document answers. Create a committee map:

Research the Committee: Tools to Find Names

Once you know the roles, find the names.

Tools: - LinkedIn (search company, look at org chart on company page) - Apollo or Hunter (API search for emails by company and title) - ZoomInfo (database of B2B contacts, reverse lookup by company) - Company website (leadership page, team page) - Crunchbase (investor updates often list team)

Start with the user buyer (easiest to find, most visible on LinkedIn). Then find the economic buyer (CEO or CMO usually visible). Then technical (might be titled "VP Security" or "IT Director").

For blockers and influencers, ask your sales team. They know from past conversations.

Build Outreach Around the Committee

Once mapped, tailor outreach to each stakeholder.

Don't send the same email to everyone. Different people care about different things.

To the economic buyer (CMO): - Subject: "How [Company] improves campaign ROI" - Body: Focus on business impact, time saved, revenue impact - Timing: Start here if it's a top-down buy

To the user buyer (VP Demand Gen): - Subject: "Simplify your campaign coordination" - Body: Focus on workflow, ease of use, time saved day-to-day - Timing: Always include early; they're your advocate

To the technical buyer (IT Director): - Subject: "Enterprise security and compliance for marketing" - Body: Focus on SOC 2, GDPR, integrations, data handling - Timing: Include before proposal if you know security is important

To the influencer (demand gen manager): - Subject: "How demand gen teams cut setup time" - Body: Focus on templates, shortcuts, team collaboration - Timing: Bring in after user buyer warms up

The Buying Committee Playbook: Orchestrate the Sequence

Don't try to close all 4-6 people at once. Sequence:

Week 1-2: User buyer - Your champion. Get them excited. - Email + call. Show product demo.

Week 2-3: Economic buyer - Introduce via user buyer if possible - Email framing business impact - Call with user buyer + economic buyer together

Week 3-4: Technical buyer - Introduce if user buyer or economic buyer gives greenlight - Email about security/compliance - Call with technical buyer + AE

Week 4-5: Final alignment - Get all 4 people (if needed) in a call - Address remaining objections - Move to proposal

This way, each person feels heard. By the time you're at proposal, there are no surprises.

Validate Your Map Continuously

As you move through a deal, refine your committee map.

If you hit an unexpected blocker late in the deal, ask: "Who else should have been in the conversation earlier?"

If a stakeholder moves faster than expected, note that for future deals.

Your map evolves. After 10 deals, you'll have a very accurate committee structure. After 20 deals, you can predict exactly who needs to be involved and when.

Common Mistakes

1. Assuming the first person who responds is the decision maker - Usually, they're the champion or user buyer. The economic buyer comes later.

2. Ignoring the technical buyer until late - If IT can block, bring them in at proposal stage and they'll block on security. Bring them in at discovery and they'll shape requirements.

3. Only talking to one person - If that person leaves or changes their mind, the deal dies. You need multiple relationships.

4. Not validating who has budget - You can have everyone's buy-in, but if the CFO didn't approve budget, the deal stalls.

The Real Advantage

Sales teams that map the buying committee win deals faster. They know who to talk to, what they care about, and when to involve them.

They don't waste time pitching the wrong person.

They don't get surprised by a late-stage blocker.

They close.

Map your buying committees systematically

Abmatic helps you identify and track the buying committee for every account, orchestrate personalized messaging to each role, and measure engagement across the committee.