How to introduce two people (without burning either side)
The connector's playbook: when an intro helps both sides, double-opt-in mechanics, a five-sentence intro email template, and how to bow out gracefully.
Introduce two people the way you’d want to be introduced: ask each side privately first, write five plain sentences, and disappear from the thread. Connectors who follow that sequence get thanked twice; connectors who skip the asking step quietly stop being asked at all.
The both-sides test
Before any mechanics, one filter: does this introduction help both people? Not “could plausibly be interesting to” — help. The founder gets a hiring lead and the candidate gets a role worth leaving for. The writer gets a source and the expert gets coverage she actually wants.
Most bad intros fail this test in an obvious direction. One person extracts — advice, a pitch meeting, a referral — and the other donates time. When you make that intro, you’ve converted a favor to you into a cost for someone who trusted you. Adam Grant’s Give and Take (2013) is often summarized as “connect generously,” but the book’s sharper point is that sustainable givers are deliberate about where their generosity lands. Indiscriminate connecting isn’t giving; it’s spending other people’s attention.
A practical version of the test: imagine each person reading the intro email with no warning. Would both think “oh, good”? If you hesitate on either face, you’ve answered the question.
There’s a corollary worth saying out loud: it’s fine to make intros where the benefit is lopsided — mentor to student, senior to junior — as long as the giving side knows and agreed. Which brings us to the mechanics.
Ask both sides first: the double-opt-in
A double-opt-in intro means nobody meets anybody until both have privately said yes. You ask the person being asked for something first — their time is what’s being spent — with a short note they can decline in one word: “Lena is building inspection drones and hit the same certification wall you cracked at Aeris. Worth 20 minutes? Totally fine to pass.”
Only after the yes do you write the actual three-way email. The contrast is the surprise CC: two strangers, one thread, an obligation neither chose. The recipient of a surprise intro now has to be rude to a stranger or spend an hour they never offered — and the person they’ll quietly blame is you.
If you’re on the receiving end of this dance — you want the intro rather than make it — that’s a different craft with its own rules; see our guide on how to ask for a warm introduction. The asker’s job is to hand you a forwardable email. When they do, the double-opt-in costs you ninety seconds: forward, await yes, connect.
When the asker doesn’t hand you one, request it: “Send me three sentences I can forward.” That’s not laziness. A self-description in the asker’s own words is more accurate than your paraphrase, and it makes the ask declinable without you in the middle.
The in-person variant deserves a note, because conferences and dinners run on it. When both people are standing in front of you, the double-opt-in compresses to seconds — “Lena, there’s someone here you should meet; got two minutes?” is consent enough, because either party can deflect on the spot at near-zero cost. The mistake is leaving it there. A hallway introduction without a follow-up thread evaporates by Tuesday, so close the loop the same evening: one short email — “delighted you two finally met; contact details attached” — converts the handshake into something both inboxes can find again.
Writing the intro email
Once both sides have opted in, the email itself should be almost disappointingly short. Its only job is to put two consenting people in one thread with enough context to skip the small talk.
-
Subject line: boring and searchable
Use the convention every inbox already parses: “Intro: Maya ↔ Jonas” or “Maya / Jonas (payment ops)”. Both people will search for this thread in three weeks; help them find it.
-
One sentence of context per person
“Maya, meet Jonas — he ran payments at Klarna for six years and now advises early fintech teams. Jonas, Maya is the founding engineer at Ferrostack, building dispute automation for EU payment teams.” Credentials each person would happily claim, nothing more.
-
One sentence on why
Name the overlap concretely: “You’re both circling the same chargeback-triage problem from opposite ends, and I think an hour together saves each of you a month.” This sentence is the intro. If you can’t write it, return to the both-sides test.
-
The explicit handoff
Name who acts next: “Maya, I’ll let you take it from here.” Without this line, two polite people each wait for the other, and the thread dies of courtesy.
-
Stop writing
No biographies, no agenda suggestions, no scheduling on their behalf. Under 120 words total. You’re opening a door, not hosting the meeting.
Assembled, it reads like this:
Subject: Intro: Maya ↔ Jonas (payment ops)
Maya, Jonas — you’ve both said yes, so: Maya, meet Jonas, who ran payments at Klarna for six years and now advises early-stage fintech teams. Jonas, Maya is founding engineer at Ferrostack, building dispute-automation tooling for EU payment teams. You’re attacking the same chargeback problem from opposite ends, and I suspect an hour together saves each of you a month. Maya, I’ll let you take it from here — happy connecting.
If you want ready-made wording for the surrounding messages — the ask, the nudge, the thank-you — our follow-up email templates include a forwardable-intro set you can adapt.
Bowing out gracefully
The connector’s exit is a skill in itself. Stay in the thread and every scheduling email pings you; vanish without a word and the thread loses its witness. The middle path: whoever replies first should move you to BCC — “moving Sam to BCC with thanks!” — and if they don’t, do it yourself after the first exchange. One line: “Dropping to BCC — it’s all yours.”
BCC is the right mechanism because it lets you see that the handshake happened without obligating anyone to keep performing for an audience. What the two of them build from there is theirs, including the option of building nothing.
One thing you don’t get to do after bowing out: demand a report. An intro is a gift. Many recipients will close the loop unprompted — and those people, you’ll notice, are the ones you keep making intros for — but chasing updates converts your gift into an invoice.
Track what you owe and what you made
Here’s the unglamorous part that separates occasional connectors from people whose networks compound: intros generate ledger entries, and memory is a terrible ledger.
Three lists are worth keeping. Intros you promised — “I’ll connect you with my old manager” said at a conference dinner is a debt, and forgetting it costs more trust than never offering. Intros you made — so when you next talk to either person, you can ask the one-line follow-up that shows you cared about the outcome. Intros made for you — because closing the loop with your own connectors is what keeps that channel open.
For a handful of relationships, a notes app works. Past a few dozen active contacts, promised intros are precisely the kind of dated, person-attached commitment that slips — which is the shape of problem a personal CRM like Endearist exists to catch, resurfacing “you told Lena you’d intro her to Tomas” on the day it matters instead of three awkward months later.
The payoff isn’t bookkeeping for its own sake. Connectors are remembered for their hit rate and their reliability, and both are downstream of writing things down. Make good matches, ask first, write five sentences, leave quietly, and close your loops — and being introduced by you becomes something people quietly hope for.
FAQ
What is a double opt-in introduction?
A **double-opt-in intro** means both people privately agree to be connected before any shared email exists. You ask each side separately — usually by forwarding a short, forwardable note — and only write the three-way email after both have said yes. The alternative, the **surprise CC**, creates a social obligation neither person chose and spends your credibility with both. Double-opt-in has become standard etiquette in professional networks for exactly that reason.
Should I ask both people before making an introduction?
Yes, almost always. Asking first protects three relationships at once: each person's time, and your standing with both. The only common exception is a **pre-cleared standing offer** — someone who has explicitly told you 'send anyone working on X my way.' Even then, a one-line heads-up ('sending you Lena tomorrow, the robotics founder I mentioned') costs ten seconds and removes the ambush feeling entirely.
How do I write an introduction email between two people?
Five sentences. **Greeting with both names**, one sentence of context on person A, one on person B, one sentence on **why they should meet** — the overlap, stated concretely — and a **handoff** that names who acts next: 'Maya, I'll let you take it from here.' Keep it under 120 words. The email's job is to start a conversation, not to conduct it.
What should the subject line of an intro email be?
Use the plain convention both inboxes already understand: **'Intro: Maya ↔ Jonas'** or 'Maya / Jonas intro (payment ops)'. Adding a two-or-three-word topic helps both people find the thread weeks later. Avoid clever subject lines — an intro email is infrastructure, and infrastructure should be boring and searchable.
Who should reply first to an introduction?
The person who benefits more — and your handoff sentence should name them explicitly. 'Lena, I'll let you take it from here' removes the politeness standoff where each side waits for the other. If the benefit is genuinely mutual, hand it to the person who asked for the intro, or to the one you know better. Ambiguity here is the most common reason healthy intros stall in week one.
Should I use CC or BCC when introducing two people?
Start with both people in **To** or CC so the connection is visible, then move yourself to **BCC** in the thread — or be moved there by whoever replies first. Well-mannered recipients write 'moving Sam to BCC with thanks' in their first reply. If they don't, you can bow out yourself after the first exchange: one line, no ceremony. Staying in CC through scheduling logistics helps nobody.
What if one person says no to the intro?
Then the intro doesn't happen — and that's the system working, not failing. Tell the asking side a soft, honest version: 'Not the right moment on her end, I'll keep it in mind.' Never reveal details that embarrass either party. A connector who relays a graceful no keeps the trust of both people; a connector who pushes past one loses it with both.
What if the introduction goes nowhere?
Let it go after one nudge at most. Calendars, priorities, and inbox chaos kill plenty of well-matched intros, and that's not your failure. What you should _not_ do is chase both sides for updates — the intro was a gift, not a contract. If the topic resurfaces months later, a light 'did you two ever connect?' is fine, and often revives it.
How many introductions should I make?
As many as pass the **both-sides test** — and no more. Adam Grant's *Give and Take* (2013) describes how giving builds the strongest long-run networks, but indiscriminate connecting erodes the very credibility that makes your intros land. Each weak match teaches both recipients to deprioritize your name in their inbox. Volume isn't the metric; hit rate is.
How do I decline when someone asks me for an introduction?
Quickly, kindly, and without inventing excuses. 'I don't know him well enough for the intro to mean anything' or 'I want to protect that relationship right now' are both complete answers. A slow maybe is crueler than a fast no — it leaves the asker waiting and you dreading the follow-up. If a smaller favor is honest, offer it: a name to research, a public talk to reference, advice on the cold approach.
How do I keep track of introductions I've made or promised?
Log three things the moment they happen: **intros you promised** (with a date), **intros you made** (so you can close loops later), and **what came of them**. Memory handles this for a handful of contacts; past a few dozen active relationships it reliably drops promised intros — the most expensive kind to forget, because someone is waiting on you. A note field plus a reminder, in whatever system you trust, is enough.