B2B sales
How SDRs Can Use Their Team’s Network to Get Warm Introductions
Every cold sequence an SDR sends is being made in front of a warm path that might not exist, or might be one Slack message away. Five minutes before picking up the phone changes the conversion math more than five hours of sequence optimisation.
An SDR who dials cold all day is not wrong to do so. Cold outreach works, and for accounts where no warm path exists, it is the only route available. The problem is that warm paths exist far more often than SDRs check. And the check, when it is built into the pre-call routine, takes under five minutes per account.
The team’s collective network contains connections to target accounts that the individual SDR does not know about, because no one has made those connections searchable. An AE who worked with the CFO at a previous company. A CSM who went to university with someone in the procurement team. A founder who has three genuine relationships at the account the SDR is about to cold-dial. None of this surfaces without a process, and building that process takes one deal review conversation, one CRM field, and a thirty-second Slack message.
Why the warm path goes unused
Three structural reasons explain why most SDRs default to cold outreach even when a warm alternative exists.
1. The warm path is in the company but invisible to the SDR
A mid-size B2B company running a sales team of fifteen people has, collectively, thousands of professional relationships. Some of those relationships run directly through target accounts: an AE who worked with the CFO at a previous company, a CSM who went to university with a head of operations, a founder who has three mutual connections with the VP of Sales you are trying to reach. None of this is visible when the SDR opens a cold sequence. It is locked inside individual LinkedIn profiles and personal memories that the SDR has no structured way to access before picking up the phone.
2. Cold outreach is the default because it requires no coordination
Cold outreach is the path of least resistance not because it is most effective but because it requires nothing from anyone else. An SDR who has to identify which colleague knows someone at the target account, check whether the relationship is genuine, frame the ask without being presumptuous, and follow up on whether the introduction was made is doing coordination work on top of quota work. Without a clear process, it is easier to skip it. The result is that the team’s collective network, one of the most valuable assets in the building, sits unused while SDRs grind through sequences that convert at two to three percent.
3. Mutual connections on LinkedIn are not warm paths
The most common mistake SDRs make when they do think about warm introductions is treating a mutual LinkedIn connection as a warm path. It is not. A mutual connection is evidence that two people are connected on a platform. It is not evidence that either relationship is strong enough to support a credible introduction. Using LinkedIn to identify the connection and then cold-messaging the connector ("Hi, I noticed you’re connected to [prospect name]. Would you be willing to introduce me?") is socially awkward and usually ineffective. The connector does not know why this SDR is reaching out, does not know whether the introduction would benefit the prospect, and is being asked to put their name on something they know nothing about. A genuine warm path requires a genuine relationship, and verifying that requires asking inside the company, not searching LinkedIn.
The five-minute pre-call network audit
The audit runs in a fixed sequence, shortest-to-longest, and stops as soon as a genuine warm path surfaces. The goal is to find one, not to exhaust every possibility before making a call.
1. Check the CRM before checking LinkedIn
The first stop is the CRM, not LinkedIn. Most CRMs contain logged activity from previous outreach attempts, contact notes from AEs or CSMs who touched the account, and sometimes explicit connector fields if the team has built that habit. A contact note that says "introduced through Karen at [former company]" is the most direct warm-path signal available, and it is already in the system. An SDR who spends two minutes reviewing the account history before opening a cold sequence finds warm paths that otherwise go unnoticed, and avoids the embarrassment of cold-calling someone who already spoke to an AE six months ago.
2. Ask the AE or CSM who owns the account
For accounts that are in active territory (assigned to an AE or with a CSM managing an existing relationship), the fastest network audit is a direct question: "Do you know anyone at [Company] who might be the right intro for me to the VP of Sales?" This takes thirty seconds to ask. It surfaces connections that are not in the CRM because they exist in the AE’s personal network rather than the company’s logged history. AEs and CSMs are generally willing to help when the ask is specific and low-effort, particularly if the SDR is offering to write the introduction message, so all they need to do is forward it.
3. Check LinkedIn for team members’ first-degree connections, not mutual contacts
If the CRM and the account owner have nothing useful, LinkedIn is worth checking, but the right search is not "who do I have in common with this prospect." It is "do any of my colleagues have a first-degree connection to anyone at this account." This is a different search. First-degree connections between a colleague and someone at the target account are meaningful: they indicate an actual relationship between two people, not just a shared platform connection at two degrees of separation. It takes under a minute to search the target company on LinkedIn and look for any team members appearing as connections. Finding one is the trigger for an internal conversation, not a cold outreach.
4. Check for champions in similar roles at other accounts
The most underused warm path available to an SDR is not a network connection. It is a satisfied customer in a similar role. If the target is a VP of Sales at a mid-size SaaS company, and the company has three VP-of-Sales customers at similar-size SaaS companies who are happy with the product, any one of them is a potential introducer. A peer-to-peer introduction carries more trust than almost any other source: someone who holds the same job title and faces the same problems vouching for a solution is the highest-trust introduction that exists. SDRs who map existing customers by role and sector, and who ask customer success for introductions to peer accounts, are operating on a source that most of their counterparts have not discovered.
How to make the internal ask without being annoying
Most SDRs who do think to ask a colleague for an introduction do it once, get an uncertain response, and stop. The mechanics of the ask are what determine whether it becomes a repeatable part of the workflow or an occasional experiment.
1. Be specific about the target and the ask
A vague internal ask like "do you know anyone at [Company]?" produces vague responses. A specific ask ("I’m trying to reach Sarah Nordström, who is the VP of Sales at Teknosolutions in Stockholm. Do you have a relationship with her that is warm enough to make an introduction?") is easier to answer because it requires a binary response. The colleague either knows Sarah or does not. Specificity also signals that you have done your research and are not asking them to do the work for you. An SDR who can name the exact person, their title, and the company they work for is demonstrating the kind of preparation that makes colleagues comfortable putting their name on an introduction.
2. Offer to write the introduction message
The highest-friction part of making an introduction is composing the message. Most colleagues who are willing in principle stall because they do not know what to say, how to frame the connection, or what to highlight about the SDR’s company that would be relevant to the contact’s situation. Offering to write a forwarding paragraph removes this friction entirely. The SDR writes something like: "I wanted to connect you with [SDR name], who works on the sales team at [Company]. We help [target profile] [specific value prop], and I thought you two would benefit from a conversation given your work on [relevant topic]. Happy to make the intro if useful." The colleague reads it, decides whether to send it, and hits forward. The ask requires perhaps forty-five seconds of their time rather than five minutes of thinking.
3. Give the colleague an easy way to say no
An internal introduction ask that creates social pressure is one that will be agreed to grudgingly or not followed through. The framing should make it straightforward for the colleague to decline: "If the relationship is not close enough or you’d rather not, that is completely fine. I can find another path." This is not false modesty. It is structurally important: a colleague who feels obligated to say yes but does not have a genuinely warm relationship with the prospect is worse than no introducer at all. A lukewarm introduction that the connector cannot back up damages the SDR’s credibility and puts the connector in an uncomfortable position. The opt-out should be as easy as the opt-in.
Champion introductions: the most underused SDR source
A satisfied customer in the same role as your target prospect is a more credible introducer than almost any colleague connection. Schmitt, Skiera and Van den Bulte’s research on referred customers found a 16 to 25 percent lifetime value premium over non-referred customers, with the mechanism being peer trust transferred through an introduction. SDRs who have access to a champion introduction path and use it are not working a softer version of sales; they are working on higher-quality pipeline from the moment the first conversation happens.
Identify customers who are in the same peer group as your prospect
The value of a champion introduction depends on peer proximity. A satisfied VP of Sales at one company is a credible introducer to a VP of Sales at another company in a similar sector and size band, because the recipient knows the introducer faces the same problems, makes the same trade-offs, and has the relevant frame to evaluate whether the product is worth looking at. A CFO who loves your product is not a useful introducer to a VP of Sales, even if they happen to know each other. The match between the champion’s role and the prospect’s role is what makes the introduction land with weight rather than curiosity.
The ask to customer success
The mechanism for sourcing champion introductions at scale is a standing conversation with customer success. The SDR (or the sales team manager) identifies the target peer group (role, sector, size) and asks the CSM: "Who among our customers in this segment would be willing to have a fifteen-minute conversation with a prospect if we asked?" Most customer success teams can identify two or three enthusiastic customers per segment who are open to acting as references or connectors. These customers have usually already offered to help: the referral instinct exists in happy customers; it simply needs to be activated with a specific ask rather than a general "let us know if you can help."
The peer-to-peer introduction message
When the champion agrees to make an introduction, the SDR should again offer to draft the message. A champion introduction that is composed by the champion and based entirely on their own experience will be stronger in voice, but most champions will not write it unless prompted, and a draft they can edit is better than a blank page that goes unfilled. The draft should be in first person from the champion’s perspective, specific about the problem it solved for them, and low-pressure for the recipient: "I thought you might find it worth a conversation. Not a sales pitch, just a fifteen-minute exchange on how you’re handling [X] and whether what they have built would be relevant." The champion edits what needs editing; the SDR has done the structural work.
The CRM layer: making warm paths a team asset
An SDR who finds a warm path and uses it has done something useful for this deal. An SDR who finds a warm path, uses it, and logs it has done something useful for every person who works that account in the future, including themselves when they come back to it in six months. The difference between the two is a convention and ninety seconds of logging.
Create a consistent connector field on the account or contact record
The team’s warm-path knowledge is only durable if it is logged. An SDR who discovers that a colleague has a first-degree connection to the head of procurement at a target account should not keep that in their head. They should put it in the CRM, attached to the account record, in a field or note that the next person to work the account will find. The field does not need to be complex: connector name, their relationship to the prospect, and whether an introduction was requested and with what result is enough. A convention that is consistently applied means the next SDR who picks up the account in six months does not start the network audit from zero.
Flag warm paths in deal reviews and pipeline calls
Logged connector information only becomes a team asset if it is reviewed. An SDR who updates the CRM connector field but never mentions it in a deal review is doing useful administrative work that produces no workflow change. The mechanism that turns the data into action is the manager asking about it: "Before you call these five accounts, what does the CRM show on connector coverage?" The question normalises the check and makes it a step in how the SDR works accounts rather than an optional audit they run when they think of it.
Close the loop after an introduction attempt
A CRM connector record that says "introduction requested, outcome unknown" is only marginally better than no record at all. The SDR who makes an introduction request should log the outcome: whether the connector sent the message, whether the prospect replied, and whether the introduction led to a meeting or conversation. This serves two purposes. It tells the next person who works the account whether a warm path has already been attempted and with what result, which prevents awkward re-asks of the same connector. And it generates the data the team needs to understand which connector types and introduction formats actually convert, the kind of ground-level evidence that distinguishes an introduction discipline that is working from one that feels productive but is not.
FAQ
SDR warm introduction FAQs
How much time should an SDR spend on a pre-call network audit?
Five minutes per account is the realistic ceiling for most outreach workflows. The audit is: check the CRM for logged connections (one to two minutes), ask the account owner if there is one (thirty seconds, usually asynchronous via Slack), and check whether any colleague has a first-degree LinkedIn connection to anyone at the account (two to three minutes). If nothing surfaces in five minutes, the account is genuinely cold and the SDR should proceed with cold outreach rather than continue searching. The point is to make the warm-path check a default step, not to make it a research project.
What if the colleague does not know the prospect well enough to make a warm introduction?
This is exactly the right question to ask before the introduction happens, not after. If the colleague’s relationship with the prospect is superficial (a one-time conference meeting, a LinkedIn connection from years ago, a distant industry acquaintance), the introduction will not carry the trust that makes it useful. The honest test is whether the colleague could call the prospect right now and be remembered as someone they have a genuine relationship with. If the answer is uncertain, the SDR should look for a stronger connector or proceed with cold outreach rather than asking the colleague to put their name on something they cannot back up.
How do you ask for a champion introduction without it feeling like a sales favour?
The framing that works is peer-to-peer curiosity rather than vendor referral. The draft the champion forwards should read as one peer telling another about something worth knowing, not as a customer promoting a vendor to a prospect. "I thought you’d find it useful to compare notes on how you’re handling [specific problem], and this is what we did" reads differently from "I recommend you speak to this company." The peer frame is more accurate to how satisfied customers actually talk about solutions they value, and it lands more naturally on the recipient side. The SDR is writing the draft; the champion is choosing whether it reflects how they actually feel about the product. If they would not say it themselves, they should say so, and the SDR should rewrite it.
What do I do when the prospect already spoke to a colleague six months ago and it went nowhere?
Check the CRM before doing anything else. If there is a record of a previous conversation, read it: what was the outcome, why did it not progress, who was the contact, what did they say about timing or fit. A prospect who was not ready six months ago may have a different situation today. One who said the price was too high may have a different budget. One who had a competing vendor evaluation in progress may have finished it. The previous conversation is useful intelligence, not an obstacle. The SDR who goes into a re-approach knowing what happened last time is in a better position than one who approaches cold, even if the previous conversation did not convert.
How does LetsBridge help SDRs find warm introduction paths?
LetsBridge structures the introduction request and the double opt-in that makes warm introductions work at scale. For an SDR, the platform provides a systematic way to identify which connectors in the company’s extended network have genuine relationships with contacts at target accounts, to make an introduction request with enough context that the connector can forward it credibly, and to track whether the introduction was made and whether it led to a meeting. The double opt-in structure means the introduction only happens when both the connector and the prospect have agreed to it, which means the first conversation starts on ground that has already been prepared, rather than with a recipient who received an unrequested email and does not know why.
Give your SDRs a systematic warm introduction path
LetsBridge structures the introduction request and double opt-in that turns a team’s collective network into a searchable warm-path layer for outbound. SDRs identify genuine connection paths, request introductions with enough context that colleagues and champions can forward them credibly, and reach prospects who already know someone vouches for the conversation.