Map the Buying Committee Before You Send the Proposal [2026]
Champion ≠ committee
Champions sell internally when you are not there — but they rarely control budget, security approval, and legal redlines alone. Mapping the committee is how you learn what your champion cannot say yes to. Skip the map and proposals become PDFs that sit in someone’s inbox while the real decision happens elsewhere.
Six roles — fill or flag unknown
| Role | Power | Question to answer |
|---|---|---|
| Champion | Drives process | Will they spend political capital? |
| Economic buyer | Signs or allocates budget | Have they been in a meeting? |
| Technical validator | IT, security, ops | What must pass before sign? |
| User lead | Daily adoption | Will they resist change? |
| Blocker | Quiet veto | Why do they prefer status quo? |
| Coach | Information only | What are they telling you about timing? |
Unknown is acceptable early. Unknown at proposal is negligence. Log each role on the opportunity in Momentum with last activity date.
Discovery questions that surface the map
- “Besides you, who cares if this works in Q3?”
- “Whose budget line does this hit?”
- “Who got burned last time you switched tools?”
- “Does IT need to bless integrations before you can sign?”
- “What does legal usually redline on SaaS contracts?”
Listen for titles and names. Ask permission to include them on a follow-up — multi-threading is not cc-bombing; it is giving each role a relevant thread.
Map template — copy to CRM note
- Champion: [Name] — engaged / neutral / cooling
- Economic buyer: [Name or UNKNOWN] — met? Y/N
- Technical: [Name or UNKNOWN] — questionnaire sent?
- Users: [Team] — pilot participants named?
- Blocker: [Name or none identified] — concern
- Procurement: [When they enter] — target date
Review the map in weekly pipeline — pipeline review playbook. If economic buyer is still UNKNOWN at stage three, the deal is miscategorized.
Reaching roles without alienating the champion
Champions fear you end-run them. Frame multi-threading as help:
- “Can we brief your CFO on total stack savings — you stay on the invite?”
- “IT usually has ten security questions — want us to send answers proactively?”
- “Who from ops should see migration timing so week one is smooth?”
Reaching the economic buyer without burning the champion is a skill — map first, ask second, cc always.
Committee gaps that kill proposals
- Finance never saw ROI frame — send champion kit executive page
- IT discovered SSO requirement late — technical validation earlier
- End users not in pilot — adoption revolt after signature
- Incumbent admin still owns renewal calendar — displacement timeline
Each gap has a playbook. Random gaps have random losses.
Proposal gate — do not send until
- Economic buyer identified or executive meeting scheduled
- Technical path clear — questionnaire started or waived in writing
- Champion kit forwarded internally (not just to you)
- Mutual timeline agreed — MAP optional but ideal
- Map updated in CRM within last 7 days
Founders who waive the gate for quarter-end pressure learn which roles actually sign.
After legal enters — map becomes action plan
Legal names are not surprises if procurement was on the map. Assign owners: who answers security, who handles redlines, who escalates term disputes. Log on the opportunity so handoffs do not reset context — CS handoff starts with the same record sales used to close.
Sentiment tracking — beyond names on a list
A name without sentiment is trivia. Update weekly during active deals:
- Green — attended meeting, asked constructive questions, forwarded materials
- Yellow — silent, delegated to junior, or asked for competitor comparison
- Red — explicit preference for status quo, blocked calendar, or hostile in thread
Yellow roles get a targeted touch — security summary for IT, ROI one-pager for finance, pilot invite for users. Red roles need a strategy conversation with your champion: convert, neutralize, or qualify out. Deals with two red roles and no economic buyer meeting are pipeline fiction.
Coach vs champion — do not confuse them
Coaches give intel; champions spend capital. A coach who shares procurement timing is valuable. A coach who cannot get you in front of the signer is not a champion — update the map honestly. Founders who mislabel coaches inflate win rates and wonder why proposals die in committee.