How to ask for a warm introduction (the double-opt-in way)
Ask with a forwardable email and a double-opt-in: what to write, a real example, and why making it easy to say no gets more intros made.
The right way to ask for a warm introduction is to hand your connector a finished, forwardable email and explicit permission to decline. That structure — the double-opt-in — is what separates intros that get made from requests that die politely in an inbox. Everything else is detail.
What you’re actually asking for
When you ask for a warm introduction, you’re not asking for an email. You’re asking someone to attach their reputation to yours in front of a person they care about keeping. If you waste the target’s time, the connector pays for it — not you. That’s the asymmetry to hold in your head while writing the request.
This is why “could you intro me to anyone in fintech?” fails. It’s not rude, exactly. It’s expensive. The connector now has to figure out who, guess what you’d say to them, draft something, and absorb all the risk of a mismatch. Adam Grant’s Give and Take (2013) makes the long-run case that givers build the strongest networks — but Grant is equally clear that sustainable givers protect themselves from requests that drain them. Your job is to be the kind of ask a giver can grant in ninety seconds.
The practical translation: name one specific person, explain why them in one sentence, and do every bit of the writing yourself.
The double-opt-in: ask permission twice
A double-opt-in intro runs in two stages. First, the connector quietly checks with the target: “Someone I rate wants to talk to you about X — interested?” Only after the target says yes does the actual three-way email happen. Both sides opted in; nobody got ambushed.
Compare that with the cold intro, where the connector simply CCs two strangers into one thread. The target now has a social obligation they never agreed to, created by a person they trust — which is precisely how that trust erodes. If you’ve ever received one of these, you know the feeling: a meeting request wearing a friend’s face.
When you ask for an intro, say explicitly that you expect the double-opt-in: “Feel free to check with her first — genuinely no pressure either way.” You’re signaling that you understand the economics of what you’re asking. Connectors notice, and they remember who made the process feel safe.
Write the forwardable email
The forwardable email is the engine of the whole ask. It’s a short, self-contained block your connector can forward verbatim — no editing, no summarizing, no “let me find a moment to write this up.” You write two things: a two-line note to the connector, and the block below it.
-
Open with the ask, not the windup
The note to your connector is three sentences: “Could you introduce me to Dana Weiss? I’m exploring payment-ops tooling and her time at Mollie makes her the person I most want to sanity-check this with. Forwardable blurb below — and if it’s not a fit, no explanation needed.”
-
One line of who you are
Inside the forwardable block, establish yourself in a single sentence the target can verify: role, company or project, one relevant credential. Not your biography — the one fact that makes the conversation make sense.
-
Why this person, specifically
One sentence proving you did the homework: a talk she gave, a problem her team solved, a post she wrote. Generic flattery (“I admire your work”) reads as a mail merge. Specificity is the difference between a request and spam.
-
One concrete, sized ask
“A 20-minute call about how you handled chargeback disputes at scale” beats “pick your brain” in every measurable way. The target can see the exact cost of saying yes. Unsized asks get deferred; sized asks get scheduled.
-
Close with the easy out
End the block with a release valve: “And if this quarter is the wrong time, a no by silence is completely fine.” It belongs in the forwardable part, because the out is for the target as much as the connector.
Here’s the whole forwardable block assembled, at 90 words:
Hi Dana — I’m Maya Lindqvist, founding engineer at Ferrostack, where I’m building dispute-automation tooling for EU payment teams. Your AltPay talk on chargeback triage is the closest thing I’ve found to a map of this space, and there are two assumptions in our roadmap I’d love to stress-test against your experience. Would you be open to a 20-minute call in the next few weeks? And if this lands at a bad time, no response needed — truly.
Notice what’s absent: no attachment, no deck, no three paragraphs of context. If the conversation happens, context can travel then.
Make “no” cheap
The easy out isn’t a courtesy flourish — it’s load-bearing. People avoid requests they can’t decline gracefully, and they avoid the people who make declining expensive. Every intro request carries an implicit question for the connector: “What happens to our relationship if I say no?” Answer it in the ask itself, and you’ve removed the main reason requests get ignored rather than answered.
A cheap no also produces better yeses. A connector who feels free to decline the mismatched request will route you the matched one — sometimes one you didn’t know to ask for. The long game is not this introduction; it’s being someone whose requests are safe to receive.
Where asks go wrong
Most failed intro requests die from one of five self-inflicted wounds, and all five are avoidable in the drafting stage.
The “anyone” ask. “Do you know anyone in climate tech?” outsources the hardest part — figuring out who — to the person doing you the favor. Connectors aren’t search engines. Come with a name, or with two or three names and a question about which fit is best.
The bait-and-switch. Asking for “advice” when you want a sales meeting is the fastest way to burn both relationships at once. The target feels ambushed, the connector feels used, and neither forgets. If the honest ask is commercial, say so — plenty of people will still make that intro when it’s labeled correctly.
The attachment avalanche. A deck, a one-pager, and a Loom video attached to the request triples the perceived weight of forwarding it. Every attachment is homework. The forwardable block carries the conversation; materials can follow once there is a conversation.
The proxy pitch. “Could you tell her about what we’re building?” asks the connector to sell on your behalf — work they’ll do worse than you and resent doing at all. The connector’s job is vouching, not pitching.
The parallel ask. Requesting the same target through two connectors at once feels efficient until both say yes and the target receives two intros for one stranger in the same week. Ask one connector, wait for the outcome, then try the next path if needed.
The common thread: every failure mode shifts work or risk onto someone who’s doing you a favor. Audit your draft for exactly that, and most of these never happen.
After the intro is made
The intro landing in your inbox is the midpoint, not the finish line. Reply within 24 hours — slow responses embarrass the person who just vouched for your reliability. In your first reply, thank the connector by name and move them to BCC (“moving Jonas to BCC with thanks!”) so the logistics don’t flood their inbox. Offer two or three concrete times. Keep the first meeting to the size you promised.
Then do the step almost everyone skips: report back. One sentence to the connector after the meeting — “We talked Tuesday, she pointed me at exactly the right pilot customer, thank you again” — is what turns a one-time favor into a standing willingness. Connectors keep spending capital on people who show them the return.
Finally, write it down somewhere that will resurface it: what you discussed, what you promised, when to follow up with both the new contact and the connector. Our follow-up email templates cover the wording for each of those touchpoints, and a personal CRM like Endearist will resurface the commitment on the day it’s due instead of relying on your memory. The intro cost someone else trust; keeping track of what you owe on it is the least expensive way to repay them.
FAQ
What is a warm introduction?
A warm introduction is a connection made through a **mutual contact** who vouches for you, instead of a cold email from a stranger. The connector lends you a slice of their **credibility**: the target opens the message because of who sent it, not who wrote it. That borrowed trust is why warm intros convert far better than cold outreach — and why asking for one is a real request, not a small favor.
What is a double-opt-in introduction?
A **double-opt-in intro** means both sides agree before the connection happens. The connector first asks the target privately — usually by forwarding your email — and only makes the three-way introduction after the target says yes. The alternative, a surprise **cold intro**, puts the target in an awkward spot and spends the connector's capital without consent. Double-opt-in has become the default etiquette in professional networks for exactly that reason.
How do I ask for an introduction without being awkward?
Remove every piece of work from the connector's side. Name the **specific person** you want to meet, say **why them** in one sentence, and attach a short **forwardable email** they can pass along without editing. Then close with a genuine out: 'If this isn't a fit, no explanation needed.' Awkwardness comes from vagueness and pressure; specificity and a cheap _no_ remove both.
What should a forwardable email contain?
Four things, in under 150 words: **who you are** in one line, **why this person specifically** (show you did the homework), **one concrete ask** (a 20-minute call about a named topic beats 'pick your brain'), and **an easy out**. Write it in third-person-safe language — no inside jokes, nothing the target shouldn't see — because the whole point is that it gets forwarded verbatim.
How long should the ask be?
Short. The note to your connector should be **three to five sentences**; the forwardable block **under 150 words**. Length signals pressure: a long, heavily justified request makes the connector feel they're being recruited into a campaign. A short one says 'this is easy to do and easy to decline.' If you can't state the ask in one sentence, the ask isn't ready yet.
What if the connector doesn't respond?
Wait **a week**, then send one light nudge — 'No worries if this slipped or if it's a no, just bubbling it up once.' If there's still silence, drop it and treat the silence as a soft no. Intro requests die in inboxes for many reasons that have nothing to do with you, but chasing harder than one nudge converts a non-answer into damaged goodwill.
Is it okay to ask for an intro on LinkedIn?
Yes — the medium matters less than the structure. A LinkedIn message can carry the same **forwardable block** as an email; just keep it self-contained so the connector can copy-paste it. One caveat: LinkedIn's own 'request an introduction' mechanics are clumsy, so most people simply write a normal message. If you and the connector usually talk on another channel, use that channel instead.
How well do I need to know the connector before asking?
Well enough that they can honestly vouch for you. A connector who barely knows you can only say 'this person asked me to forward this' — which is barely warmer than cold email. If the relationship is thin, **strengthen it first** or shrink the ask: ask whether an intro would even make sense, rather than asking for the intro itself. That question costs them nothing and tells you where you stand.
What if they say no?
Thank them — sincerely, not performatively. A no usually protects something you can't see: the target is overloaded, the relationship is delicate, or the timing is wrong. **Adam Grant's** research in *Give and Take* (2013) shows long-run networks are built by people who make generosity feel safe; punishing a no with sulking teaches the connector to avoid your asks entirely. A gracefully accepted no often turns into a proactive yes months later.
How do I thank someone for an introduction?
Twice. First, **immediately**: reply fast to the intro thread, move the connector to BCC in your first response so their inbox is spared, and thank them in that same line. Second, **afterward**: tell them what came of it — a sentence is enough. The report-back is the most skipped step and the most valuable one; connectors keep making intros for people who close the loop.
Should I follow up after the introduction is made?
Yes — and quickly. Reply within **24 hours** of the intro landing, propose two or three concrete times, and keep the first meeting short. Slow responses embarrass the connector who just vouched for your reliability. After the meeting, log what you discussed and set a reminder to update the connector — a simple follow-up cadence keeps the new relationship from going cold the week after it started.