The average B2B SaaS deal above $25K ACV involves 4 to 7 stakeholders in the decision process. Yet in call recording reviews, the pattern is almost always the same: the AE is running every call with a single point of contact — usually the person who responded to the outbound sequence or attended the inbound demo — and treating that person as the de facto decision-maker and champion until the deal either closes or goes dark.
When it goes dark, the post-mortem reveals some version of the same story: "We were talking to the right person technically, but they didn't have budget authority," or "Security needed to sign off and we hadn't spoken to them," or "The CFO killed it at the final stage and we'd never met them." Single-threading is one of the most reliably predictable causes of late-stage deal loss in B2B SaaS, and it's almost always visible in the discovery call if you know what to look for.
Why reps default to single-threading
Before coaching the behavior, it's worth understanding why it happens. Reps single-thread for three reasons, none of which are laziness:
Access anxiety: Asking your contact to introduce you to their colleagues or manager feels presumptuous before the value is established. Reps hold back because they're afraid the request will signal distrust of the current contact — or worse, that the contact will feel bypassed.
Complexity aversion: Managing a multi-threaded deal requires coordinating calendars, tailoring messaging to different personas, and tracking multiple relationship states simultaneously. For reps early in their career or still ramping on the product, adding that complexity feels like risk.
False confidence: When the current contact is enthusiastic and responsive, reps interpret engagement as a proxy for authority. A champion who replies to emails within an hour and says "yes, this looks interesting" is a pleasant contact to work with — and that pleasantness creates a cognitive bias toward treating them as more powerful in the decision process than they actually are.
Understanding these dynamics matters because the coaching intervention needs to address the underlying concern, not just add a checklist item. A rep who is told "you need to multi-thread more" without a framework for how to do it without damaging their current relationship will half-execute the behavior and then stop when it creates friction.
MEDDIC's economic buyer criterion in practice
In the MEDDIC framework, the "E" stands for Economic Buyer — the person with budget authority and the ability to say yes without further approval. Most reps know the criterion exists. Far fewer have a reliable behavioral pattern for identifying the economic buyer in the first or second call, before the deal has enough momentum to make asking feel natural.
The probing sequence that works in discovery: after the prospect has described the problem and its consequences, ask "if your team decided to prioritize solving this in the next 90 days, who would need to approve the investment?" This question is deliberately future-conditional rather than direct ("who has budget?"), which reduces social friction. It produces one of three useful responses: a name, a process description, or an acknowledgment that the current contact isn't sure — which tells you the problem hasn't been internally prioritized yet.
A second probe that consistently surfaces additional stakeholders: "Who else on your team would be most directly affected if this problem persists?" This identifies potential champions or influencers who aren't yet in the conversation — people with skin in the game but who don't know a potential solution is in play. Getting those names in the discovery call is the foundation of multi-threading.
Champion identification vs. stakeholder mapping
These are related but distinct behaviors. Champion identification is about finding the specific person who will advocate for your solution internally — someone with access to the economic buyer, personal credibility on this problem, and a stake in the outcome. Stakeholder mapping is broader: understanding the full cast of decision participants, their roles, their interests, and their likely objections.
Most reps who ask the stakeholder question at all do a surface version: "Who else is involved?" gets them a list of names and titles. Genuine stakeholder mapping means understanding what each person cares about. The head of IT security has different success criteria than the VP of Sales than the CFO. A rep who knows all three names but not their individual concerns is mapped on paper but not in practice.
The behavioral coaching target for discovery calls is not comprehensive stakeholder mapping — that requires multiple conversations and a deal with enough momentum to justify the time. The target for discovery is: identified at least one stakeholder beyond the current contact, established their role in the decision, and created a path to a conversation with them before the proposal stage.
The champion test
A useful coaching framework: the "empty room test." If your current contact left the company tomorrow, could this deal survive? A true champion is someone who cares about the outcome enough that the deal would survive their departure — because they've brought others into the conversation, established the business case internally, and created institutional buy-in beyond their personal enthusiasm.
Most single-threaded deals fail this test. If the current contact goes on leave, gets promoted, or becomes distracted by an internal initiative, the deal typically goes dark because there's no one else who knows enough or cares enough to keep it moving. The champion test is a useful 1:1 conversation opener: "If [contact name] left the company tomorrow, who else in their organization would still want to solve this problem? Have you met them?"
Coaching the multi-threading behavior
The most effective coaching intervention for single-threading is not adding a multi-threading checklist to discovery prep — it's identifying the specific moment in a call where the rep could have asked about other stakeholders and didn't. Find that moment in the recording. Ask the rep what stopped them. Almost always the answer is some version of "it felt too early" or "I didn't want to seem like I was going around them."
Then work through the specific language that makes the ask feel collaborative rather than threatening: "To make sure we're thinking about this holistically — who else on your side tends to have strong opinions about projects like this?" positions the ask as thoroughness, not distrust. "I want to make sure we're not missing anyone who'd have useful context" positions it as diligence on the rep's part.
The goal is to get the rep to a place where multi-threading feels like a service to the prospect — making sure the right people are involved, preventing a late-stage surprise — rather than a sales tactic. Reps who internalize that framing execute the behavior naturally and maintain it even under the social pressure of a warm, responsive single contact who seems to be making good progress.