Networking
What Makes an Introduction Worth Making: The Connector’s Decision Framework
Every time a connector agrees to make an introduction, they are lending their reputation to the requester. The quality of that loan, and whether they get repaid in the form of a useful outcome for the recipient, depends on the standards they apply before saying yes. Four signals that tell a connector the introduction is worth making, three red flags that should stop it, and how recipients should quickly evaluate an introduction they have received.
Most writing about warm introductions is addressed to the person asking for one. The mechanics of the forwardable brief, the double opt-in, the follow-up sequence are all techniques for requesters. The connector, who is the person the whole system depends on, is treated as a resource to be activated rather than a decision-maker with legitimate criteria for when to say yes.
This is a structural problem. The quality of the warm introduction ecosystem in any professional network depends entirely on whether connectors maintain a genuine standard, one that makes their introductions reliably worth accepting. Connectors who say yes to every request quickly see their introductions discounted: recipients learn that the connector’s name on an introduction email does not carry a meaningful selectivity signal, and treat it accordingly.
Schmitt, Skiera and Van den Bulte’s research in the Journal of Marketing found that referred customers generated 16–25% higher lifetime value than non-referred ones. Granovetter’s foundational research on weak ties shows that bridge-position connectors, those who span communities and industries, hold disproportionate influence in professional networks precisely because they are selective about the relationships they bridge. The connector’s value is inseparable from the quality standard they maintain.
What follows is a framework for connectors: four signals that indicate an introduction is worth making, three red flags that should stop it, and a brief guide for recipients navigating an introduction they have received.
Four signals that tell you the introduction is worth making
A connector who applies these four criteria consistently will make introductions that recipients welcome, that produce useful outcomes for requesters, and that protect the connector’s reputation as a source of genuinely valuable connections.
Genuine fit between the parties
The first question a connector should be able to answer before agreeing to make an introduction is: would this meeting be useful for the recipient even if nothing comes of it? Not "might the requester benefit from meeting this person" (that is a given; they are asking because they believe they would) but "would the person being introduced gain something from the conversation?" A fit that only runs in one direction is not a fit. It is an ambush with good manners. Genuine fit means the recipient has a problem the requester can plausibly help with, or a goal that the connection advances, or a conversation that would be genuinely interesting for them at this moment. Connectors who maintain this standard as a baseline produce introductions that recipients welcome and remember. Connectors who skip it produce introductions that recipients accept politely once and decline to repeat.
The requester has proof of value
The second signal is evidence that the requester can deliver what they claim. For a vendor seeking a customer introduction, this is a customer outcome: a named result, a verifiable metric, a recognisable reference. For a job seeker, it is a portfolio, a record of relevant work, or a mutual contact who can speak to their contribution. For a partnership requester, it is traction data that demonstrates the partnership is worth the recipient’s time. Proof of value matters to the connector because they are staking their own credibility on the introduction. When they say "you should meet this person, I think it will be useful for you," they are borrowing against their reputation with the recipient. If the meeting disappoints (if the requester has overstated their position, or if the recipient’s time is wasted on an early-stage pitch with nothing concrete behind it), the connector’s reputation absorbs the cost. A connector who asks for proof of value before agreeing to an introduction is protecting not just their own relationships but the quality standard that makes their future introductions worth accepting.
The ask is specific and low-friction
A high-quality introduction request tells the connector exactly who they want to meet, why that person specifically, and what the meeting would accomplish. Specificity has two functions. The first is that it enables the connector to make a fast, informed yes-or-no decision about their relationship with the proposed recipient. "Do you know anyone at tech companies in London?" requires the connector to conduct an internal mapping exercise before they can evaluate whether they can help. "Do you know Sarah Chen, the VP of Operations at Brightwave? I noticed you both went to Edinburgh and overlapped by three years in product management" takes thirty seconds to confirm and act on. The second function of specificity is that it signals the requester has done genuine research into why this particular introduction matters, rather than casting a wide net of requests in the hope that something lands. Connectors are more willing to extend their reputation for a targeted, thoughtful ask than for a spray of requests that suggests the requester values their introduction as a volume play.
The timing makes sense for the recipient
The best-structured introduction request can still be the wrong ask if the recipient is in the wrong moment for it. A company that just went through a leadership transition is unlikely to be evaluating new vendors. A person who has just changed jobs is processing their own priorities, not fielding introduction requests on behalf of their former company. A potential customer who is mid-procurement with a competing vendor will likely decline the meeting or take it with a disposition that makes it almost impossible to be useful. Connectors who have active relationships with the recipients they are being asked to introduce are in a position to know these contextual factors. Connectors who do not should ask, or should tell the requester that they cannot assess the timing and leave the decision to the requester. Making an introduction at the wrong moment for the recipient does not just waste the recipient’s time; it uses relationship capital the connector cannot easily recover.
Three red flags that should stop the introduction
These patterns appear frequently in introduction requests. Recognising them early, and responding with a specific conditional decline or a redirect, protects the recipient’s time, the connector’s reputation, and ultimately the requester’s standing with the people they are trying to reach.
A vague pitch with no defined problem
When the requester cannot explain in two sentences what problem they solve and for whom, the connector has no way to evaluate whether the introduction would be useful for the recipient, and the recipient will not be able to evaluate it either. A vague pitch puts the burden of sense-making on the connector and the recipient simultaneously. The result is a meeting that the recipient takes out of politeness, spends the first fifteen minutes trying to understand why they are there, and files as a negative data point about the connector’s judgment. Connectors who notice this red flag can either ask the requester to sharpen the brief before they agree to proceed, or decline the introduction on the grounds that they cannot make it in a way that would be useful for the recipient.
A misaligned product or a stretch fit
Some requesters ask connectors for introductions to recipients who are technically reachable but demonstrably not a natural fit for what is being offered. A B2C consumer app seeking introductions to enterprise procurement teams is a stretch fit. A niche vertical software seeking introductions to a generalist executive who does not buy in that category is a stretch fit. These introductions fail not because the requester is dishonest about what they do, but because the connector does not take seriously enough the question of whether the recipient would have any genuine reason to care. Saying yes to a stretch fit is a short-term social cost reduction (it is easier than explaining why the introduction is not the right one) that produces a long-term reputation cost when the recipient experiences the meeting as a waste of time.
The ask treats the connector as a directory
The clearest red flag in an introduction request is when it is structured as if the connector is a searchable database rather than a person with relationships that carry their own social weight. Requests that begin "I am looking for anyone with a connection to X" or "can you introduce me to people in the Y space" are not asking for an introduction. They are asking for a list, and expecting the connector to convert that list into relationships through the force of their own credibility. Connectors who notice this pattern can decline on the grounds that they cannot make introductions they would personally stand behind, or can ask the requester to identify the specific person they want to meet and why, turning the open-ended ask into a specific one that they can evaluate and act on responsibly.
The recipient’s perspective: evaluating an introduction you have received
How to quickly evaluate an introduction you have received
The recipient of a warm introduction faces a simpler but related set of questions. The first is whether the connector’s judgment is reliable: has this connector introduced you to useful people before? Do they typically match people with genuine fit, or do they make introductions whenever someone asks? A connector with a strong track record is a strong signal; a connector who introduces everyone to everyone is a weaker one, because the selectivity that makes introductions valuable is absent. The second question is whether the fit description in the introduction makes sense: does the requester solve a problem you actually have, or have any reason to think you have? A well-written introduction from the requester will give you enough context to make this assessment quickly. A vague introduction ("you should meet Felix, he does interesting things in the sales space") gives you nothing to evaluate and leaves the decision to whether you trust the connector’s judgment entirely. The third is timing: even if the fit is genuine, is this the right moment for you to invest time in a new relationship? An honest no like "the fit makes sense but I am heads-down through Q3; can we revisit in October?" is a better outcome than a meeting that neither party has the bandwidth to make useful.
The goal of evaluating an introduction quickly is not to decline more often but to invest time in the introductions that have genuine potential and to give an honest signal when the timing or fit is not right. A recipient who declines with a specific reason ("the fit makes sense but Q3 is the wrong moment; let’s revisit in October") is a more useful participant in the introduction ecosystem than one who accepts every meeting out of obligation and engages with none of them substantively.
FAQ
FAQs on what makes an introduction worth making
Should I always give the requester feedback when I decline to make an introduction?
Yes, when the reason for declining is something the requester can act on. If the introduction request has a structural problem (a vague pitch, a stretch fit, a timing mismatch), telling the requester specifically what would need to change for you to say yes is more useful than a polite no. It gives them the opportunity to sharpen their brief, recalibrate their target, or return at a better moment. If the reason for declining is confidential or personal, because you have a competing obligation to the proposed recipient or the relationship is one you prefer not to use for introductions, a simple "I am not the right person to make this particular introduction" is sufficient without elaboration.
How do I handle a request from someone I want to help but whose pitch is not yet strong enough?
The most useful response is a conditional yes: "I would be happy to make this introduction once you have [a named customer outcome / a clearer problem statement / a tighter brief for the specific recipient]. Here is what I would want to be able to say on your behalf." This framing helps the requester without committing your reputation to an introduction you cannot yet stand behind. It also signals the standard you apply, which makes the requester more likely to return with a stronger ask once the conditions are met, and makes the introduction, when it happens, easier to make because the groundwork has been laid.
What if the recipient is my close friend or colleague and the fit is uncertain?
The closer the relationship with the recipient, the higher the bar for the introduction. A close friend or colleague expects your filter to be more rigorous, not less, because they will naturally attribute any wasted meeting to your judgment rather than to the introduction process in general. Making an introduction to a close connection that wastes their time damages the relationship disproportionately relative to the same introduction made to a less close connection. The right approach with close connections is to be honest: tell the requester that you have a close relationship with the recipient and that you will only make the introduction if you believe it is genuinely useful for them, and then apply that standard strictly.
Should I ask the recipient for permission before making the introduction?
Yes, in most cases. This is the double opt-in model, and it is the standard that produces the highest-quality outcomes for everyone involved. Before sending the connecting email or message, send a note to the recipient explaining who you want to introduce them to and why you think the conversation would be useful for them. Ask if they are open to the introduction. This step gives the recipient the chance to decline gracefully if the timing or fit is wrong, and ensures that the introduction arrives with positive anticipation rather than obligation. The additional friction of the double opt-in is worth it: an introduction accepted after opt-in converts to a useful conversation at a much higher rate than one that lands without prior notice.
How many introduction requests should I agree to per month?
The right number is the number you can make in a way that maintains the quality standard that makes your introductions worth accepting. For most professionals, this is two to five per month: enough to be genuinely useful to requesters who have built a relationship with you, but few enough that each introduction receives the attention it deserves. Connectors who agree to every request quickly see their yes rate with recipients decline, because recipients learn that the connector’s introductions do not carry a genuine selectivity signal. The quality of your network as an introduction resource degrades in direct proportion to how much you overuse it.
What is the most common mistake connectors make when evaluating introduction requests?
The most common mistake is optimising for social comfort rather than genuine fit. Saying yes to a request because declining is awkward, because the requester is a friend, or because it feels unhelpful to say no is a pattern that systematically produces poor introductions. The connector’s reputation as a source of useful introductions depends entirely on the reliability of their filter, and a filter that cannot say no is not a filter. Connectors who decline requests when the fit is not genuine protect not just the recipient’s time and their own reputation, but also the requester’s reputation: a poor introduction from a well-intentioned connector does more damage to the requester’s standing with the recipient than no introduction at all.
Track which introductions are worth making, and which ones land
LetsBridge gives sales teams and their connector networks a shared view of which introductions are in progress, what context the connector provided, and whether the meeting produced a useful outcome. When connectors can see how their introductions are used, and when requesters close the loop automatically, the quality standard that makes introductions worth making becomes visible and self-reinforcing.