Buyers with power: mapping the committee before you pitch

The deal with one name in it

You know this deal. It’s in your pipeline right now, sitting at 60%, with a close date you’ve already pushed once. There is exactly one person on it: a VP of Operations who takes every call, asks sharp questions, volunteers that the incumbent vendor is a mess, and says he’ll get this in front of the team. Week seven, he stops replying. You send two follow-ups. You mark it closed-lost in the next pipeline review and say the timing wasn’t right.

The post-mortem, if anyone ran one, would land somewhere more specific than timing. He never controlled the money. Anything over $50K in his org routes through a shared-services committee he doesn’t sit on, and the person who does sit on it had already committed that line to a platform migration. He liked you. He was never able to buy from you. Everything he told you was true, and none of it was decisive.

That isn’t a discovery failure — you asked good questions. It’s a coverage failure. The deal had a committee, you had a contact, and you found out the difference after it was over.

The committee is five jobs, not five titles

A committee isn’t an org chart slice. It’s a set of jobs that have to get done for money to move, and the same person occasionally does two of them:

The economic buyer owns the budget line the purchase comes out of. They are the only person who can convert intent into a signature, and in most mid-market and enterprise deals you will speak to them twice: once briefly, once at the end.

The champion spends their own credibility arguing for you in rooms you’re not in. You don’t recruit a champion by being likeable. You recruit one by making their existing project succeed faster.

The technical evaluator owns the questionnaire — security review, integration architecture, data residency, SSO. They rarely get to say yes. They almost always get to say not yet.

The end user is whoever’s Tuesday changes if this gets bought. Their opinion barely affects the signature and completely determines the renewal.

The blocker is anyone whose position gets worse if you win: the admin who owns the tool you’d replace and would have to run the migration, the procurement analyst enforcing a three-bid rule, the manager who proposed a competing internal build last quarter.

Here’s the part that breaks one-size messaging. These five want different things, and two of them want opposite things. The economic buyer wants payback inside the fiscal year. The technical evaluator wants no new attack surface, which means fewer integrations, which is the opposite of the value story you sold upstairs. The end user wants their workflow not to get worse and has heard three vendors promise that. A single message written for “the buyer” reads as generic to all five, because it was written for an average of people who don’t average.

Seniority is not power

This is where most committee maps go wrong: they get built by title, so they inherit the org chart’s logic instead of the deal’s. The SVP two levels up looks like the most important name on the page. Often they are a spectator with a strong opinion.

Power in a deal is two separate things, and you need both mapped:

Who can say yes. Not who is senior — who has sign-off authority on this purchase, at this dollar amount. That’s a threshold question, and it has a factual answer you can just ask for: “When you brought in the tool you’re replacing, who signed the order form?” and “Is there a number above which this stops being your decision?” Two questions, asked in a discovery call, and you have the economic buyer by name instead of by inference. Nobody finds them strange questions. Everybody knows the answer.

Who can say no. Veto power is distributed far more widely than signing power, and it lives lower in the org than you’d guess. A security reviewer with an unanswered questionnaire is not senior and can hold a deal for a quarter. So can a procurement analyst who needs a second quote. The count of people who can stop your deal is almost always larger than the count who can approve it, and it’s the number reps track least.

Two field tests that separate power from seniority in about a minute. First: watch who moves dates. Someone who can pull a decision forward or push it back has real authority; someone who has to go check does not. Second: watch who’s optional. The people whose absence cancels a meeting are the deal. The people who are cc’d are weather.

The map is a coverage tool, not a diagram exercise

Drawing the committee is not the point. Reps have made pretty stakeholder diagrams in Figma for a decade and lost single-threaded deals anyway, because the diagram was a picture of what you knew, and the thing that kills deals is what you don’t.

A working map answers one question every week: where is this deal thin? Every name carries a status — reached, not reached, who owns the relationship, when they were last touched, what they’ve actually said versus what you’re assuming they think. Read that way, single-threading stops being a post-mortem finding and becomes a visible fact in week two, when you can still fix it. Six names, one of them touched, five untouched, and the untouched one holds the budget. That’s not a diagnosis you need a forecast call to reach.

This is the job Narrative does first in the closing motion: it builds the committee on one canvas from your CRM and live research, then you confirm the role tags yourself — champion, decision maker, executive sponsor, blocker, user — because the tag is a judgment call and judgment is yours. Nothing about it runs on autopilot. Every message that goes to a name on that canvas lands on your task list for you to edit and send, and every CRM update comes back as a suggestion you approve before anything writes.

Mapping is how multi-threading actually happens

Multi-threading gets talked about as a discipline — reach more people, be less dependent on one relationship. Framed that way it’s just an instruction to work harder, and reps respond by cc’ing two extra names on the same email.

It’s not a separate activity. It’s the output of the map. Once the committee is real, the next two steps have obvious inputs. You can research each buyer’s existing motivation, because you now know which five people to research and what each of them is measured on. You can build and validate champions, because you can see which of them will spend credibility on you and which are just being pleasant — the ones who make introductions, take a meeting to their leadership, forward your material internally. The people who never move tell you something equally useful: that part of the deal isn’t real yet.

A ramping AE at a PE-backed digital manufacturer worked this way from his first month, and sourced and closed $40K MRR inside 60 days — $480K ACV, six times the annual cost of his entire sales stack. He wasn’t outworking anyone. He was prioritizing the buyers with power on accounts where he’d mapped who those were before he pitched.

The deal you lose to a champion who goes quiet was never lost in week seven. It was lost in week one, when you decided one enthusiastic contact was a committee. Map it first. Then you’ll know which conversation actually matters, and you’ll still have the quarter left to have it.