B2B sales
Warm Introductions for Account Executives: The In-Deal Multi-Thread Playbook
An SDR uses warm introductions to get in the door. An account executive uses them to build relationships across the full buying group while the deal is already in motion. The in-deal multi-thread playbook: how to use your champion as an introduction source, when to ask at each deal stage, and how to turn closed-lost contacts into re-open paths.
Warm introductions are how most people think about getting into a new account: someone in your network knows the right person and makes an introduction that opens the first meeting. But for account executives managing active deals, the introduction play starts over once you are inside.
Enterprise deals rarely close on the basis of one relationship. Gartner research finds an average of eleven stakeholders involved in a B2B purchase decision, with each additional unaligned stakeholder reducing the probability of a clean decision by ten percentage points. An AE who only has a relationship with the champion is one person’s internal advocacy away from losing the deal for reasons they never saw coming.
Multi-threading (building direct relationships with multiple buying-group stakeholders) is how AEs manage this risk. Warm introductions, sourced from the champion, are how they do it without appearing to go around the person who let them in.
Why AEs need a different introduction strategy than SDRs
The mechanics of a warm introduction are the same in every context: a connector with a genuine relationship transfers trust and credibility to a new contact. But the source, timing, and stakes are different when the deal is already in motion.
SDRs work the network before the first conversation
An SDR’s warm introduction play is a pre-contact motion: identify a warm path to the right person at a target account, request an introduction to get the first meeting, and use the referral halo to secure a higher opening conversion rate than cold outreach would deliver. The SDR’s job ends when the qualified meeting is booked. At that point, the warm introduction has done its work.
AEs work the network inside an active deal
An account executive faces a different problem. Once in a deal, the AE has a champion (the person who opened the door) and a buying group that the champion may or may not have full access to. Gartner research on enterprise deals finds an average of eleven stakeholders involved in a B2B purchase decision, and that each additional unaligned stakeholder reduces the probability of a clean decision by ten percentage points. An AE who relies on the champion to carry the message to the full buying group is betting the deal on the champion’s internal authority, political capital, and willingness to advocate without support. Multi-threading is the practice of building direct relationships with multiple stakeholders. Warm introductions are how AEs get multi-threading done without looking like they are going around the champion.
The trust mechanism is the same, the timing and source are different
A warm introduction works the same way whether it precedes the first meeting or occurs mid-deal: a connector with an existing relationship transfers trust and credibility to a new contact. For an SDR, the connector is typically someone in the AE’s broader network. For an AE, the connector is the champion inside the account: someone who is already bought in, already has the relationships, and can make an internal introduction that arrives with full credibility rather than the friction of an external outreach finding its way to a new inbox.
Mapping the buying group through your champion
Before an AE can request introductions to the right stakeholders, they need to know who those stakeholders are and how accessible they are via the champion. The mapping conversation is not a separate step but part of a thorough discovery process.
1. Ask the champion who else will weigh in on the decision
Early in discovery, when the champion is still in information-sharing mode, ask directly: "Who else in the organisation would need to be comfortable with this before a decision could move forward?" and "Who owns the budget line for something like this?" and "Is there an IT or security review that would happen as part of the evaluation?" The answers map the buying group without requiring the AE to independently research the org chart. Champions who trust the AE share this information readily, because they need the AE to understand the internal dynamics if the deal is going to progress.
2. Rate each stakeholder by the champion’s relationship depth
Not every stakeholder is equally accessible via the champion. Some are colleagues the champion works with daily; others are senior executives the champion may have limited access to; others are functional owners in departments the champion does not interact with. For each stakeholder, estimate the champion’s relationship depth: close (the champion works directly with this person and they have genuine trust), moderate (the champion knows them professionally but does not have a strong relationship), or loose (the champion knows the name but would need a reason to approach them). The depth rating drives the sequencing of introduction requests.
3. Map the likely objection source, not just the authority source
The most important stakeholder to reach is not always the one with formal authority. In many enterprise deals, the decision is technically made by a VP or Director, but the evaluation is killed or delayed by a functional objector: legal, finance, IT security, or a departmental owner who sees the solution as a threat to their team’s remit. Identifying likely objectors before they surface their objections, and requesting introductions to them proactively, converts potential blockers into engaged evaluators. A stakeholder who has a direct conversation with the AE early in the process is substantially less likely to introduce a late-stage objection than one who encounters the solution for the first time in the review meeting.
Deal-stage timing: when to ask for each introduction
Multi-thread introduction requests land differently depending on where the deal is. The same ask that feels like helpful due diligence in discovery can feel like political overreach at the proposal stage if the champion senses the AE is trying to build relationships that cut them out of the decision.
Discovery: map the buying group and request the first multi-thread intro
During discovery, the champion is still building trust with the AE and the deal has not yet reached the political sensitivity of the proposal or procurement stages. This is the easiest moment to ask for a multi-thread introduction, because the framing is natural: "To understand whether this is the right solution for your organisation, I would love to speak with the person who owns [budget / technical evaluation / compliance review]. Would you be comfortable making an introduction?" The ask is presented as due diligence that helps the champion build a stronger internal case, not as a threat to the champion’s control of the deal.
Proposal: introduce the economic buyer before the number lands
The worst moment for the economic buyer to first encounter the AE is alongside the proposal document. A stakeholder who sees a price for the first time without any prior relationship context evaluates it as a transaction, not as an investment in a solution they have been part of building. If the AE can secure a brief introduction to the economic buyer before the proposal is delivered, framed as a courtesy call to ensure the proposal addresses the right priorities, the economic buyer arrives at the proposal with a relational context rather than pure price sensitivity. Schmitt, Skiera and Van den Bulte found a 16 to 25 percent lifetime value premium for referred customers; the same trust-transfer mechanism that drives that premium operates inside the evaluation itself.
Pilot or proof of concept: bring in the technical evaluators
During a pilot or proof of concept, the champion’s network typically does not extend to the technical team running the evaluation. Technical evaluators form their own opinions based on hands-on experience, and those opinions are disproportionately influential on the final decision. They are the ones who write the evaluation report that the buyer group reads. An introduction from the champion to the technical lead gives the AE the opportunity to provide context, understand the evaluation criteria directly, and address concerns before they calcify into objections. A technical evaluator who has spoken with the AE is a different kind of influence on the final recommendation than one who has only interacted with the product.
The four-step in-deal introduction protocol
Requesting an internal introduction is a specific skill. AEs who do it well make the champion feel like a valued collaborator; AEs who do it badly make the champion feel like a door-opener. The difference is in how the ask is structured and how the introduction is followed through.
1. Identify the specific stakeholder and the champion’s relationship to them
Be specific about who you are asking for an introduction to and why. "I would love an introduction to Sarah in procurement" is less effective than "I know Sarah is going to be involved in the contract review. Would you be comfortable introducing me before that stage? I want to make sure I understand her standard requirements so we are not going through document revisions under deadline pressure." The specificity shows the AE has thought through the deal dynamics, gives the champion a clear reason to say yes, and frames the introduction as serving the deal rather than threatening the champion’s position.
2. Give the champion the language for the introduction
Most champions agree to make introductions and then delay, because writing an introduction note to a senior colleague requires effort they have not budgeted. Remove that friction by providing a short draft: "Feel free to adapt this. The main thing I want them to understand is why we are talking and that it’s worth a brief call before the formal evaluation starts." The draft should be three sentences: who the AE is in the context of what the champion is evaluating, what the AE wants to discuss with the new contact, and a direct ask for a call or meeting. The champion edits and sends; the AE did the work.
3. Confirm the introduction arrived and respond within 24 hours
Once the champion sends the introduction, the AE should know about it within hours, either because the champion forwards the sent note or because the new contact replies. Responding to an internal introduction within 24 hours signals professionalism and makes the champion look competent for having recommended the engagement. A delayed response is a small failure that the champion notices, because it reflects on their judgment in making the introduction. Speed of response is part of how multi-threading builds champion confidence rather than eroding it.
4. Close the loop with the champion after every introduced conversation
After each conversation with an introduced stakeholder, send the champion a one-sentence summary: "Good call with Sarah. She flagged that legal review usually adds two weeks, which I’ll build into the timeline." The loop-close does three things: it shows the champion the introduction was productive, it keeps the champion informed about the deal dynamics across stakeholders they may not be directly managing, and it reinforces that the AE is using multi-thread access to serve the deal rather than to build parallel relationships that cut the champion out. Champions who get regular loop-closes become more comfortable making additional introductions.
Using closed-lost contacts as re-open introduction paths
A deal that closes lost leaves behind a set of relationships that most AEs treat as expired. The champion, the economic buyer, the technical evaluator, and the procurement contact who interacted with the AE during the deal are all warm contacts that persist beyond the lost decision, and all of them can become re-open paths or connectors to new accounts.
1. The 90-day window for a closed-lost re-open path
A deal that closes lost is not a dead relationship. Research on win-back timing consistently finds that the highest re-engagement rate occurs in the 30 to 90 day window after a decision, before the losing vendor is fully forgotten and before the chosen solution has had time to prove itself. For an AE, the contacts built during a multi-threaded deal are an asset that survives the lost decision. The champion who did not win the internal budget battle may still be an advocate. The technical evaluator who gave a positive recommendation but lost to a more affordable option may still be the person who flags the chosen solution’s shortcomings six months later.
2. Keep the multi-thread contacts warm, not just the champion
Most AEs maintain contact with the champion after a lost deal and treat the other contacts as gone. The economic buyer, the technical evaluator, and the procurement lead who interacted with the AE during the deal are separate warm paths that survive the decision independently. The economic buyer who chose a different solution may move to a new company where the budget constraints are different. The technical evaluator who liked the product may have more influence in a new role or organisation. Maintaining a light, value-adding contact with the multi-threaded stakeholders (sharing a relevant resource, acknowledging a professional milestone, making an introduction that benefits them) costs very little and preserves optionality across the full set of relationships the deal created.
3. Ask for an introduction out of the lost account
The most underused re-open play is the outbound introduction request from a closed-lost account. At the 30 to 90 day mark, the AE can legitimately contact the champion and say: "I know the timing wasn’t right this cycle. I am working with a few companies in [industry] who face similar challenges, and I’d love to be in touch if the situation changes. Is there anyone in your network who might be a good conversation?" The ask costs the champion nothing, and the champion who maintains a positive view of the AE is often willing to make an introduction to someone at a company where the constraints are different. This converts a lost deal into an active connector relationship.
FAQ
FAQs on the AE warm introduction playbook
How do I ask my champion for a multi-thread introduction without making them feel bypassed?
Frame every multi-thread introduction as something that helps the champion build a stronger internal case rather than something the AE needs for their process. "I want to make sure the compliance team isn’t surprised by the integration requirements" is champion-first framing that invites the champion to facilitate an introduction that protects their position. "I need to talk to more people in your organisation" is AE-first framing that makes the champion feel like a door opener rather than a deal partner. The distinction is not just rhetorical: the champion genuinely needs the buying group aligned, and a skilled AE is offering to help with that, not circumventing it.
What if my champion refuses to make internal introductions?
A champion who refuses multi-thread access is either not truly bought in, is protecting their political position because the deal is at risk internally, or does not trust the AE to handle the conversations well. The first two situations require honest deal inspection: is this champion actually an internal advocate, or are they an enthusiast without internal authority? The third situation is a coaching conversation: have the AE demonstrate, in detail, how they would handle the stakeholder conversation and what they would say. If the champion’s objection is that the AE will say the wrong thing, the right response is to prove that they will not. A champion who refuses access after understanding the AE’s plan is protecting something they have not disclosed.
How many stakeholders should an AE multi-thread in a typical enterprise deal?
Multi-threading is not about quantity but about covering the buying group adequately. For a typical six-figure deal with a standard structure (economic buyer, champion, technical evaluator, legal/procurement), three to four introductions cover the material risk. For a larger deal with a more complex buying group, the number scales with the number of distinct stakeholder types who can independently block the decision. The goal is not to have spoken with everyone in the org chart; it is to have no relevant decision influencer who encounters the solution for the first time in the formal review meeting.
When is it appropriate to reach out directly to a stakeholder without a champion introduction?
Direct outreach to a stakeholder inside an active deal is high risk and almost always counterproductive. It signals that the AE does not trust the champion to facilitate access, it can damage the champion’s standing if they find out from the stakeholder rather than from the AE, and it arrives without the trust transfer that makes an internal introduction valuable. The one exception is when the champion has become genuinely non-responsive and the deal is about to expire. In that case, a direct outreach to the economic buyer, framed as a timeline check, is better than watching the deal die silently. But this is a failure mode, not a strategy.
Should I contact closed-lost stakeholders directly or through the original champion?
The original champion is the preferred path for re-engagement, because the relationship the AE built with the champion during the deal is the warmest and most natural starting point. For multi-threaded stakeholders who had substantive conversations with the AE during the evaluation, direct outreach is appropriate: they had a real interaction, and reaching out on a new opportunity or with a relevant resource is a natural continuation of a relationship that existed, not a cold contact. The key is that any outreach should be framed around value to the recipient, not around the AE’s pipeline needs.
How does LetsBridge support multi-threading and stakeholder introduction management?
LetsBridge gives account executives the infrastructure to request, track, and manage stakeholder introductions across an active deal. When a champion agrees to make an internal introduction, LetsBridge provides the double opt-in mechanism that lets the champion forward the request with full context, confirms the introduction was made, and tracks the resulting conversation. AEs can see which stakeholders have been introduced, which introductions are pending, and which conversations have happened, giving them a multi-thread coverage view across the entire buying group without relying on memory or manual tracking in the CRM.
Give your AEs the infrastructure to multi-thread every enterprise deal
LetsBridge provides account executives with a structured way to request, track, and manage stakeholder introductions inside an active deal. When a champion agrees to make an internal introduction, the double opt-in flow ensures the new contact receives a genuine warm introduction, not a forwarded cold outreach, and the AE can see exactly which buying-group members have been introduced, which introductions are pending, and which conversations have happened, without relying on memory or CRM fields that no one fills in.