Stakeholder maps: champion, economic buyer, blockers

A deal is a committee, not a person — and if every thread runs through one person, that person is your .

The idea

Enterprise deals are decided by a buying committee: a champion who wants it, an economic buyer who pays for it, users who’ll live in it, a blocker who can stall it, and procurement who owns the paperwork. Your job is to map who’s who from what they say on calls, then test whether your champion can actually reach power inside the account. The trap is comfort: routing everything through one friendly contact. When that person changes jobs, so does your deal.

Direct threads

Routes through champion

yes

Survives their exit

Right now you only know Dana, your champion. She relays everything — which feels efficient, but every path into the account runs through one person. Add direct relationships, then simulate her leaving.

Danachampion — “Send me the deck — I’ll push this through and get us time with finance.”
Rajeconomic buyer — “Anything over $50k comes to me. Show me the payback.”
Miauser — “My team would live in this daily — but I don’t hold the budget.”
Tomblocker — “I’m not sold on data residency. I can stall this.”
Priyaprocurement — “Nothing gets a PO without my paper and a signed MSA.”

How it works

Multi-threading is a habit, applied in four moves:

1  Map the committee
   Tag each voice on the call: champion, economic
   buyer, user, blocker, procurement.

2  Test the champion
   Ask for a direct intro to the economic buyer.
   A champion spends capital to get you in the room.
   Someone who only forwards emails is a coach.

3  Multi-thread
   Build a direct line to the economic buyer and at
   least one user — with the champion’s blessing.

4  Stress-test the map
   Remove any one node. If the deal dies, you are
   single-threaded. Add threads until it survives.

When to use it

Fits	Trade-off
Any deal with more than one decision-maker; enterprise and committee sales.	Multi-threading takes time and can read as “going around” your champion if done clumsily — thread with their blessing, framed as covering more ground for them.

Watch out for

A friendly user mistaken for the buyer. Enthusiasm is not signature authority. Confirm who actually approves the spend.
A “champion” who can’t get you a meeting. That’s a coach, not a champion. Test it by asking for the introduction — if it never comes, keep threading.
Single-threading because it’s comfortable. One senior contact who relays everything feels productive right up until they leave.
Ignoring the blocker until late. An unaddressed detractor (security, legal) surfaces at the worst possible moment — the week before signature.
Treating procurement as a rubber stamp. They can add weeks and re-open price. Bring them in early.

Worked example

The interviewer asks, “Walk me through how you’d de-risk this deal.” Your champion Dana, a VP of Engineering, is enthusiastic and forwards everything to the CFO on your behalf. It feels great — until Dana takes a new job. Because every thread ran through her, the account goes cold overnight. Had you asked Dana for a direct introduction to Raj (the economic buyer) and looped in Mia (a user) and Tom (security) early, her exit would sting but the deal would still have a pulse. That’s the whole point of the map: it tells you which relationships you can afford to lose.

Check yourself

Your main contact loves the product and forwards your emails to the buyer — but won’t introduce you directly. What are they?

Which single relationship most reduces your single-thread risk?