The committee behind the person who answered

The first call could not have gone better. The director loved it, asked for pricing, promised to champion it internally. Then four weeks of silence, and eventually a two-line email: "The team decided to hold off for now." The team. Four people you never met just decided the deal, and the enthusiastic director turned out to be one vote.

This is the normal shape of a B2B loss. The typical purchase involves a group: the person who feels the problem, the person who owns the budget, the person who has to implement, and at least one person whose entire role is asking what happens if they do nothing. Roughly one in two held meetings advances, and a large share of the other half dies not in the meeting but in a room after it, where your whole case was represented by whoever you happened to reach, performing your pitch from memory, without you.

Multi-threading starts on call one

Most teams start multi-threading after the stall, which is like buying insurance after the flood. The committee exists from the first conversation, and the first conversation is where the mapping starts.

• Ask about the process, not the org chart. "Walk me through how the last purchase like this got decided" gets a story, and the story names the committee: who signed, who resisted, who had to be brought around. People describe process far more freely than hierarchy.
• Write everything to be forwarded. Assume every note you send will be read aloud in the meeting you are not in, because the good ones are. The same-day recap is the workhorse here: the prospect's problem in the prospect's own words is a document a champion can forward without translating it first.
• Arm the champion instead of just thanking them. An enthusiastic contact is not a strategy. An equipped one is. The one-line answer to the finance objection, the benchmark for the skeptic, the implementation answer for the person who has to live with it. The committee's default is the status quo, the gravity we covered in the status quo post, and a champion without material loses to it politely.

What the SDR layer contributes

Committee mapping usually gets filed under closing, but the earliest names surface at the top of the funnel, on the cold call and in early discovery, when nobody is guarding them. "I'd have to run it by our ops lead" is a committee member being announced. A rep trained to hear those sentences, capture the names, and pass them forward hands the AE a map instead of a contact, the context transfer we described in the handoff post. Our reps log every name mentioned on every call for exactly this reason, because a deal that arrives with its committee sketched advances at a visibly better rate than one that arrives as a single enthusiastic phone number.

The director who loved your product was real. The committee behind the director was more real. If your pipeline is full of great first meetings that go quiet in week four, book a strategy call and bring two of the stalled ones. The missing names are usually visible in the first-call notes, and we will show you where to look.