How to map a buying committee

Seats, not titles

Every deal of size is decided by a group — the committee exists whether or not you’ve met it. The only question is whether you find it before it votes.

The mapping mistake that wastes the most effort is starting from the org chart: exporting titles and calling the tallest one the decision maker. Committees aren’t org charts. They’re five seats defined by the decision itself, and the same title sits in different seats on different deals:

• Owns the problem — the person whose year is defined by the thing you fix.
• Decides — the person whose yes actually converts to a purchase order.
• Pays — the budget owner, who may care nothing for your feature and everything for a defensible number.
• Can veto — security, legal, procurement, the platform team: seats that can’t say yes but can say no.
• Lives with it — the people who use the thing daily and quietly kill deals in pilots.

Map the seats first and the names become hypotheses to test — which is the entire method.

---

Step 1 — List the seats the decision requires

Which roles must agree for this purchase to happen?

Start from the purchase, not the people: for a deal like this one, at this account, who has to say yes — and who merely has to not say no? The five seats above cover most B2B decisions; a specific deal may split one (two problem owners across functions) or add one (a compliance seat in regulated industries).

Write the seats down before hunting names. This is what makes the map falsifiable: an empty seat is visible, whereas a list of contacts always looks full.

Step 2 — Put candidate names in each seat

Who probably sits where?

Now fill seats from what’s knowable outside the building: the account’s own materials, the research you already ran, what titles suggest. A VP whose earnings-call quote announced the initiative is a strong candidate for owns the problem. The CFO is a default candidate for pays until evidence says otherwise.

Hold every name as a hypothesis. Titles lie constantly — the SVP may be a bystander while a director runs the decision — and the map’s job is to get corrected, not to be right on day one.

Step 3 — Mark engagement honestly

Which seats have you actually reached?

Three states per seat, and the middle one is where self-deception lives: unknown (no name), identified (a name, no conversation), engaged (a two-way conversation about the initiative — theirs, not yours). A name in the CRM, an accepted invite, an opened email: all identified, none engaged.

This honesty is what connects the map to money. A deal’s forecast number is only as real as its committee coverage, and your best accounts drift single-threaded precisely when engagement pools on the friendliest seat while the map says “covered.”

Step 4 — Validate with your first real conversation

How does this decision actually get made?

The first person who engages is your map’s editor, whatever seat they hold. Ask directly: how does a purchase like this happen here? Who else does it touch? Who killed the last one? Their answers move names between seats, expose seats you never listed, and tell you — by how willingly they share — whether you’re talking to a future champion or a friendly bystander.

Every subsequent conversation re-edits the map. A map that hasn’t changed in a month isn’t stable; it’s stale.

Step 5 — Date every claim and re-verify as the deal ages

When was each seat last verified?

People change jobs mid-deal. Veto-holders materialize at contract time. The problem owner gets reorganized away. So every seat carries a last-verified date, and the map gets re-walked at every stage change — which takes minutes once the seats exist, and catches the silent committee changes that otherwise surface as “the deal slipped.”

The rule that makes this operational: an unknown or unverified seat is not a to-do. It’s deal risk with a date on it, and it belongs in the forecast conversation by name.

The template

The seat map

One deal's committee, one row per seat. Copy the structure; the values show one illustrative deal.

Owns the problem

• Director of OperationsEngaged — two conversations about the initiative · verified Sep 24

Decides

• VP OperationsIdentified — intro requested via Director · verified Sep 24

Pays

• CFOIdentified, never met — risk, dated Sep 10 · what wins the seat: a defensible number

Can veto

• Security leadIdentified · review not yet requested — surface early, not at contract

Lives with it

• Two team leadsUnknown names — ask the Director; pilot risk until filled

Keep it alive without making it a job

One deal’s map is an afternoon. The practice — every qualified deal mapped, every seat dated, every stage change re-walked — is where teams quit, because maintaining maps by hand across a pipeline is exactly the unpaid record-keeping that never survives the quarter.

Systematize the map’s upkeep, keep its judgments human. Narrative AI builds and maintains the buying-group map per account — seats, candidates, engagement, freshness — so re-walking a committee costs minutes at each stage gate; the seller still decides who matters and what wins each seat, every message stays rep-initiated, and every AI-suggested CRM change waits for the rep’s approval.

Five seats, dated claims, one weekly re-walk. The committee was always going to vote — map it while your deal can still shape the ballot.