Map the Buying Committee Before Legal Surprises You [2026]
Core roles (define every deal)
| Role | Question they answer | Engagement |
|---|---|---|
| Champion | Will they sell internally? | Weekly; owns internal momentum |
| Economic buyer | Will they sign the check? | Before pricing finalization |
| Technical validator | Does it work in our stack? | Before pilot success sign-off |
| Procurement / legal | Can we buy it? | Before commit stage |
| Blocker / skeptic | What kills the deal? | Identify early; do not avoid |
Map template (log on the account)
For each person: name, title, role, stance (support / neutral / against), last touch, next action.
- Support — actively helping
- Neutral — unknown or passive
- Against — prefers incumbent or competitor — needs a plan
Store in Momentum on the account and opportunity — not a slide that dies in Google Drive. Link to mail threads and meeting notes in Workspace.
Discovery questions that surface the map
- Who else cares about this problem besides you?
- Who owns budget for tools like this?
- Who has killed vendors like us before — and why?
- What does your security or legal review look like for new SaaS?
- Who needs to say yes for this to ship in production?
Use the discovery framework — these questions belong in call two, not call five.
Engagement plan by deal stage
- Stage 1–2 — champion + light technical; confirm EB name
- Pilot — technical validator active; EB briefed on success criteria
- Proposal — EB on pricing call; procurement loop started
- Commit — legal/security tickets open; no new faces
If a new stakeholder appears at commit, pause — you are not multi-threading, you are late. See multi-threading playbook.
EB access without awkwardness
Frame as alignment, not escalation: “Before we finalize scope, we want thirty minutes with [EB] to confirm success metrics match budget — can you help schedule?” Offer a one-page business case they can forward. If they hesitate, ask what the EB cares about most — price, risk, or speed — and tailor the ask.
Security and procurement early
Ask for their questionnaire template in discovery. Send your security packet when pilot starts — not when legal is already blocking signature.
When the map changes mid-deal
Reorgs, champion promotions, and new CFO reviews reset the committee. Re-run the five discovery questions when:
- Deal slips a quarter without explanation
- A new name appears on email threads
- Procurement returns redlines you have never seen
Update stance fields the same day — stale maps are as dangerous as stale pipeline. Tie executive engagement to EB access plays before you discount to save a deal you never fully qualified.
Blocker playbook
When stance is against, document why — incumbent preference, failed prior vendor, political turf. Options: narrow scope to champion’s team, executive sponsor on your side, proof from same industry, or walk early. Do not outlast a blocker with discounts; run a competitive war room if the blocker names a rival, then decide invest vs disqualify.
Single-threaded risk score
Flag deals with only one contact engaged as high risk in pipeline review. Require a second thread — technical lead, finance, or operations — before proposal. Champions who refuse introductions may be coaches, not champions. Pair mapping with multi-threading once roles are named: map first, then open threads with intent.
For global teams selling across regions, note time zones and local approvers on the map — worldwide access does not remove local procurement rules.
Review the map in every pipeline review for deals past stage 2 — empty blocker rows are how surprises show up in week ten. Update the map when anyone new joins the thread.
Stakeholder map checklist
- Champion, EB, technical, and blocker fields filled by stage 2
- Stance updated after every meeting
- EB engaged before final pricing
- Procurement/security path documented before commit
- Map lives on CRM account — not orphaned docs