Buying Committee Navigation & Champion Development

⬅️ Back to Day 4: Convert

For any deal larger than ~$25K ACV, you don't sell to a person — you sell to a buying committee. Five to fifteen people are involved. Most of them you'll never meet. Only some are aligned with your champion. Some are skeptical. Some don't care. Procurement and legal will appear at the end with veto power. The deal closes when the committee reaches enough consensus to authorize purchase, not when your single contact says "yes."

This is the playbook for navigating that committee — mapping who's involved, identifying and developing the champion who'll sell internally for you, getting in front of the economic buyer, neutralizing detractors, building the business case the executive sponsor needs to approve, and avoiding the silent committee killers (legal, security, finance) that derail deals weeks before close.

What Done Looks Like

A documented map of the buying committee for every deal over $25K ACV: roles, names, level of support
A formally identified champion for each deal — someone willing to advocate internally when you're not in the room
The economic buyer (the person who controls the budget) explicitly identified and either met or planned to be met
Decision criteria captured from the customer's own words — what makes them say yes vs. no
Decision process mapped — what's the formal path from "we want this" to "P.O. issued"
Detractors identified by name + objection — with a plan for each
Procurement, legal, security, finance pre-engaged before late-stage surprises
A business case the executive sponsor can present upward — owned by you, validated by the champion
Multi-thread engagement — meetings with 3+ committee members before close
A champion development conversation explicitly happens early ("here's what I need from you to make this happen")

1. Why "the One Decision-Maker" Is a Lie

Twenty-year-old sales training says "find the decision-maker." It's wrong for modern B2B SaaS. According to research consistently across the last decade (Gartner, Challenger, Forrester):

Average B2B buying committee in 2026: 6-11 stakeholders for $50K+ deals
84% of B2B deals require multiple stakeholder consensus
70%+ of deals lost to "no decision" — meaning the committee couldn't agree, not that a competitor won

The single-decision-maker mental model causes reps to:

Over-rely on one champion and miss detractors
Skip multi-threading (engaging multiple people on the buyer's side)
Get blindsided by procurement / legal / security at the end
Mis-forecast deals because "they said yes" doesn't mean the org said yes

2. Mapping the Committee

For every deal over $25K, build a stakeholder map. This is not optional.

The Roles

Different frameworks (MEDDIC, MEDDPICC, Challenger) use slightly different vocabulary, but the roles are the same:

Economic Buyer — the person who controls the budget. Has the authority to approve or veto. Often a VP or C-level. May be invisible until late-stage. Without their explicit yes, the deal doesn't close.

Champion — internal advocate. Wants you to win. Will sell for you when you're not in the room. Has political capital they're willing to spend.

User Buyer / End User — the people who'll actually use the product. They evaluate from a "will this make my work better?" lens.

Technical Buyer — IT, security, engineering. Evaluates "will this fit our infrastructure / security posture?" Can veto for technical reasons.

Procurement / Purchasing — vendor management. Negotiates price, contract terms, vendor onboarding paperwork. Doesn't decide what to buy; gates how to buy.

Legal — reviews contract, terms of service, MSA, privacy / data terms. Common veto source on indemnification or liability clauses.

Finance — budget approver below the EB. Sometimes the same person as the EB, sometimes a separate gate.

Coach — supportive but not the champion. Provides information; doesn't actively sell internally. Useful for intel, not for closing.

Detractor / Anti-Sponsor — actively opposed. Has a different vendor in mind, prefers status quo, or has political reasons. Critical to identify and either neutralize or work around.

The Map

For each deal, document:

Role	Name	Title	Sentiment (Champion / Coach / Neutral / Detractor)	Last Contact	Next Action
Economic Buyer	[name]	[title]	[sentiment]	[date]	[planned action]
Champion	[name]	[title]	Champion	[date]	[planned action]
User Buyer	[name]	[title]	[sentiment]	[date]	[planned action]
...

Do this in your CRM. Salesforce, HubSpot, etc. all support contact roles on opps. Some opps need a Notion page or shared doc with the committee map for richer context.

What "Identified" Means

Two definitions you'll see:

Inferred: champion mentioned them; you haven't met
Confirmed: you've had at least one direct interaction (call, email reply)

For the EB, confirmed is required to forecast the deal as committed. A deal where you've never spoken to the EB is structurally less certain than one where you have.

3. Champion Development

Your champion is the most important asset in any deal. They're the person who answers the email at 8pm, brings up your product in internal meetings, and walks the proposal up to the EB. Without one, you're outbound-emailing into a deal nobody owns.

Identifying Real Champions

Not everyone enthusiastic is a champion. The signs of a real champion:

Willing to spend political capital — will go to bat for you, even when uncomfortable
Has access to the EB — knows them, can get on their calendar
Clear "why me?" — articulates personal upside ("this will make my team's work better; my boss will see it as a win")
Pre-shares info — tells you what's happening internally without being asked
Asks for help selling — "what would you say to my CFO about ROI?"
Returns calls quickly — engagement is consistent, not just when you push

The signs of a false champion (looks like a champion, isn't):

Engages but doesn't take action
Forwards your emails up the chain without context
Asks you to "send something I can share" rather than collaborating on the message
Never schedules the next meeting
Goes dark for weeks, then re-engages with no internal context

Developing the Champion

Champions aren't found; they're developed. Practical mechanics:

Make the champion look smart. Their internal credibility is on the line every time they advocate for you. Give them:

A clear, sharp value proposition they can quote
ROI math specific to their org, not generic
Differentiation language vs. competitors they'll be asked about
Risk-mitigation talking points (security, change management)
Customer references and case studies relevant to their use case

Ask explicitly about the deal. "What does success look like for you personally if we get this implemented?" If they can't answer, they're not a champion yet.

Discuss the buying process. "How do deals like this typically get approved here?" Their answer reveals what they know — and what they don't. Gaps mean coaching.

Coach them on internal selling. "When you bring this to your CFO, here's the question they'll ask: 'why now?' Here's how I'd answer..." You're literally arming them.

Find their personal motivator. Career advancement, team success, hated-existing-vendor relief. Personal motivation > organizational motivation as a closing force.

Test commitment. Ask for things: "Can you set up a meeting with our security team and yours this Friday?" If they make it happen, real champion. If not, develop more or find someone else.

When You Don't Have a Champion

If after 2-3 meetings nobody is taking ownership of the deal internally, you don't have a champion. Options:

Multi-thread: meet other people in the org; one of them might emerge as a champion
Re-qualify: maybe this deal doesn't have organizational pull. Pause; come back when there's a trigger event
Champion-elsewhere: sometimes the champion is in a different department than your contact

Selling without a champion to a $50K+ B2B deal almost always loses. Be honest with yourself — and your forecast.

4. Reaching the Economic Buyer

The EB controls the budget. If you've never spoken to them, the deal is at risk.

Why You Must Meet the EB

Champion's interpretation of EB priorities is sometimes wrong
EB may have unstated requirements (board presentation, year-end budget pressure, vendor consolidation initiative)
Direct conversation reveals true urgency
Champion-only deals are easier to kill at EB level than EB-engaged deals
Without EB engagement, you're forecasting hope

How to Get the Meeting

Ask the champion directly: "Given the timeline and budget, I want to make sure [EB] has the information they need to approve this. Can we schedule 30 minutes with the three of us?"

Frame the value to the EB: "I'd love to share the ROI model and the implementation plan with [EB] so the decision is informed by both technical and financial context."

Earn it through value: deliver something to the EB indirectly first (a benchmark report, an industry insight) so when you ask for the meeting, you're not cold.

Use executive sponsor on your side: have your VP / CEO offer to meet their VP / CEO. Peer-level access often unlocks meetings champions can't broker.

What to Cover with the EB

Don't waste the meeting on a product demo. The EB wants:

Strategic alignment: how does this fit your stated priorities?
Financial outcome: what does this make / save you?
Risk: what could go wrong and how do you mitigate?
Proof: who else like you has done this and what happened?
Ask: what specifically do you need from me to move forward?

A 30-minute EB meeting that produces a clear "yes, proceed to procurement" is worth 10 demo calls.

5. Multi-Threading

Deals where you've engaged 3+ stakeholders close at 2-3x the rate of single-thread deals. Concrete tactic: always have at least 3 contacts on the buyer side at MEDDIC stage 4+.

How to Multi-Thread

Ask your champion: "Who else internally would benefit from being part of this conversation?"
Send a thoughtful "intro" email to the broader committee at appropriate moments
Find LinkedIn connections — peer in another department; ask champion for warm intro
Use small executive-sponsor moments (founder's email to their VP) at key transitions
Tag people on follow-ups so they're aware of progress

Don't over-thread (10 emails to 10 different people without coordination = chaos). 3-5 active threads, with clear lanes per person, is healthy.

6. Detractors and How to Handle Them

Every committee has at least one detractor. Identify and strategize.

Why Detractors Matter

A detractor doesn't have to win to make you lose. They can:

Raise objections in internal meetings you never see
Slow-walk security review
Insist on a competitor in evaluation
Question the business case at the wrong moment

Identifying Them Early

Signs:

Quiet during meetings; doesn't engage
Asks technical / process questions that imply they prefer a different path ("can it integrate with our existing X?" — where X is the competitor's tool)
Pushes back on timeline ("we should consider more options")
Comments to the champion that get back to you ("Sarah said maybe we should wait")

Tactics

Meet them directly. A detractor who's met you may shift to neutral. A detractor you've never met stays a detractor.

Address their objection on its terms. If they're pro-competitor, don't trash the competitor — show why your approach fits this specific situation better.

Find their underlying concern. Often "we should wait" means "I'm worried about the migration disrupting my team." Address that, not the surface objection.

Bring in a peer. Sometimes a detractor responds to a customer reference at their level / role.

Acknowledge — don't dismiss. "I hear that you're concerned about [X]. Let me address that directly..."

If they can't be neutralized, work around them: ensure their concern doesn't dominate the EB's decision. Sometimes detractors lose; they don't always need to win.

7. Pre-Engaging Procurement, Legal, Security

The deal-killers that emerge in week 11 of a 12-week process. Pre-engage them.

Procurement

Don't wait for "send your standard MSA" at the end. Ask the champion:

Is there a vendor onboarding process? How long?
Is there a procurement contact you can introduce me to early?
What documentation do you typically need? (Insurance certificates, compliance attestations, vendor questionnaires)

If you can pre-stage all of this in week 4, you save 2-3 weeks at the end.

Legal

Send your standard MSA early. Get redlines back early. Don't wait for "let's send it to legal for review" the day before quarter-end.

Common legal issues to expect:

Indemnification limits / caps
Data processing addendum (DPA) — required for GDPR
Service level agreement (SLA) terms
Auto-renewal language
Termination for convenience clauses

If you have a battle-tested MSA, your sales cycle on legal is days, not weeks. Invest in template strength.

Security / IT

For B2B SaaS, security review is increasingly the longest pole. Pre-engage:

Send SOC 2 report, security questionnaire, GDPR/CCPA documentation early
Offer a call between your security team and theirs
If they have a vendor risk management (VRM) tool (Whistic, OneTrust, SafeBase), make sure your data is current

A trust center / security page (with downloadable evidence) shortens this dramatically.

Finance

Sometimes finance is the EB; sometimes a separate gate. For larger deals (>$100K), engage finance directly:

ROI / business case validation
Payment terms negotiation
Multi-year structure or expansion plans

8. Building the Business Case

Your champion needs to walk a written business case to the EB. You write it; they validate; they present.

Structure

A 2-3 page business case for $50K+ deals:

Executive summary — what's the proposal in 3 sentences
Current state — what they're doing today; what's broken
Proposed solution — what you'd implement
Financial impact — ROI / payback math, with assumptions
Risk and mitigation — what could go wrong; how you'd handle it
Implementation plan — timeline, resources, who does what
Comparison — vs. alternatives (including doing nothing)
Recommendation — what they should do; what's needed to proceed

Make it editable. Champions who can't tweak feel disempowered. Send a Google Doc or Word doc, not a PDF.

ROI Math

Specific to their numbers, not generic. If their team has 20 people and current process takes 5 hrs/week per person, the math is:

20 people × 5 hrs/week × 50 weeks = 5,000 hours/year
At fully-loaded $80/hour = $400K/year cost
Your tool reduces this by 50% → $200K/year savings
Vs. your $50K cost → 4x payback in year 1

Champion-validated assumptions are stronger than generic ones. Sit with the champion to derive the numbers; they'll defend math they helped build.

9. The Forecast Conversation

If you've done the work, your forecast for a deal looks like:

Committee mapped (yes/no)
Champion confirmed (yes/no)
EB met (yes/no)
Decision criteria documented (yes/no)
Decision process mapped (yes/no)
Procurement / legal / security pre-engaged (yes/no)
Business case sent (yes/no)
Verbal commitment from EB (yes/no)
Paper out for signature (yes/no)

Number of yeses correlates with close probability. A deal at "champion confirmed, EB met, business case sent" should be 60-70% to close. Without EB met, it should be 30-40% regardless of champion's optimism.

10. Common Failure Modes

Single-threading. Champion goes dark; deal evaporates. Always have 3+ contacts engaged.

Skipping the EB. "Champion told me she'll handle her boss." Champion's interpretation is often wrong; you need direct EB engagement.

Confusing coach with champion. A coach gives info but doesn't sell internally. Test for advocacy explicitly.

Procurement at the end. "Send your MSA" is the start of a 6-week process you didn't plan. Pre-engage.

No business case. Champion has nothing to walk upstairs. The conversation dies in their absence.

Generic ROI. "Save 30%!" without numbers specific to their environment. EBs see through it.

Detractor unaddressed. "I'll just work around them." Sometimes works; often doesn't. Engage directly.

Champion overload. Asking the champion for 12 things. They can do 2-3 high-leverage actions; pick wisely.

Late security engagement. SOC 2 questionnaire arrives Tuesday for a Friday close. Doesn't happen. Pre-engage.

Single-threading on YOUR side. You're the only one engaged from your company. Bring in your CSM, your AE manager, your CTO for technical questions. Multi-thread internally too.

Ignoring committee dynamics. "I don't know who else is involved." Find out. Ask your champion. Ask procurement. The committee exists whether you know it or not.

Discount as champion currency. Cutting price to "make it easier for my champion to sell." Sometimes warranted; often a tell that the value case isn't strong. Build the value case first.

Committee map decay. Built it in week 2, never updated. Update it weekly through the deal cycle as you learn more.

No formal "next steps" at end of every meeting. Each meeting should end with: who does what by when. Without this, momentum dies.

Trying to skip MEDDIC steps. "We don't need to identify all the criteria; just push to close." This is how deals slip from Q4 to Q1 and then never close.

Forgetting the post-sale handoff. Deal closes; champion is forgotten; CSM shows up cold. Champion was the relationship; preserve it through handoff.

Engaging the wrong champion. Sometimes the loudest internal supporter has no political capital. Find the person with influence even if they're quieter.

Champion turnover mid-deal. Champion leaves the company; deal dies. Have at least 2 internal advocates.

Talking past procurement. Procurement isn't "in the way"; they're a stakeholder with their own goals (cost reduction, vendor consolidation, terms standardization). Engage them on their terms.

What Done Looks Like (Recap)

You've shipped buying committee discipline when:

Every deal >$25K ACV has a documented committee map
Champion is identified, developed, and explicitly committed
EB is met, not just inferred
Detractors are named and have a plan
Procurement, legal, security pre-engaged early
Multi-thread engagement (3+ contacts) standard practice
Business case written, validated, and walked upstairs
Decision criteria + decision process documented in the rep's MEDDIC fields
Forecast accuracy improves because deals are diagnosed honestly

Mistakes to Avoid

Single-threading the deal through one champion
Skipping the EB on the assumption "champion will handle it"
Confusing coach with champion — no advocacy, no real sell
Pre-procurement / pre-legal / pre-security work skipped until end
Generic ROI not tied to their numbers
Detractor identified but not engaged
Champion overloaded with 12 asks instead of 2-3 high-leverage ones
No written business case for the EB to read
Committee map drawn once, never updated
Skipping MEDDIC fields on the rationale "we'll figure it out at close"
Treating procurement as obstacle instead of stakeholder
Forecasting EB-not-met deals as committed
No internal multi-thread on your side (just you, all the way through)
Discounting as a substitute for value case