Warm introduction emails
Ask for an introduction without putting either person on the spot. Use separate permission checks, a forwardable summary, and a clear introduction after both people agree.
A warm introduction uses a real mutual relationship to explain why two people might benefit from talking. Ask the connector first, let them check the other person's interest, and make the shared introduction only after both people agree. A useful introduction provides context, not a claim on someone's time.
Choose an introduction for a reason, not a badge
A mutual contact shown on a profile may barely know the person. Before asking, consider whether your connector understands your work and can honestly explain the relevance. Do not ask them to imply an endorsement they cannot give.
A direct, concise message may be simpler when the recipient publishes a preferred contact channel or the connector does not know them well. In his investor-email guidance, Michael Seibel explicitly cautions against spending too much time chasing a warm introduction. It is one route into a conversation, not a prerequisite or a guarantee of a reply.
| Situation | A reasonable route | Do not assume |
|---|---|---|
| A connector knows both people and sees a relevant overlap | Ask whether they are comfortable checking interest separately. | They have already agreed to recommend you. |
| The recipient publishes a channel for this kind of request | Consider a short direct message through that channel. | An introduction is needed to be taken seriously. |
| The only link is an unfamiliar profile connection | Check the actual relationship or use an appropriate direct route. | A connection badge means a close relationship. |
| Either person declines or does not opt in | Do not make the shared introduction. | Silence means permission. |
1. Ask the connector, with a forwardable summary
Explain who you want to meet, the specific reason, and the small next step you hope to propose. Give the connector a version that makes sense on its own, without requiring access to your previous thread. Ask what they are comfortable forwarding and leave them room to decline.
The names and work below are fictional. Replace them with accurate, shareable details; they are not customer results or real endorsements.
Request to the connector
Hi Dev, would you be comfortable asking Jordan whether an introduction would be useful? I'm working on multilingual onboarding, and Jordan's public talk about welcoming new members raised a question about first-week participation. I'd like to compare one approach. I've included a short summary you can forward if appropriate. No problem if you aren't the right person to ask.
Forwardable summary, written by the requester
I'm Nina, a product designer working on onboarding for multilingual communities. I'm testing how a first contribution can help new members participate. Jordan's talk about community welcomes prompted a question about balancing guidance with choice. Would exchanging one example by email be useful? I can share a non-confidential outline of the approach we're testing.
The summary says what Nina does, why this person is relevant, and what she is actually asking for. It does not claim Jordan wants to collaborate, include someone else's private details, or attach an unrequested confidential deck.
2. Check interest privately before connecting the thread
Fred Wilson's double-opt-in approach asks for agreement from each person before making the introduction. As the connector, share only the context the requester approved and describe your relationship accurately. If the proposed purpose, participants, or information to be shared changes, check again rather than stretching the original yes.
Permission check from the connector
Hi Jordan, Nina, a designer I worked with on a community project, asked about an introduction around multilingual onboarding. She would like to compare one first-contribution example by email. May I forward her short summary so you can decide whether an introduction is useful? I'll wait before putting you both on a thread.
In a real message, use only a relationship you can honestly describe. A yes to reading a summary is not yet a yes to a meeting, a group chat, or recurring contact. Wait for the actual introduction permission before moving to the next step.
3. Make a clear introduction after both people agree
Confirm the agreed channel, names, and purpose. Keep the connection short enough for each person to recognize why they are there. Do not add a calendar invitation, new participants, or unrelated sales material to an introduction they accepted for another reason.
The shared introduction
Nina and Jordan, thanks for agreeing to the introduction. Nina is testing first-contribution prompts for multilingual communities; Jordan has been exploring how new members choose to participate. You both wanted to compare one onboarding example by email. I'll leave you two to take it from here.
If you are receiving the introduction, thank the connector and continue with the agreed topic. Ask before expanding the commitment. The follow-up guide covers the next exchange without turning it into a pressure sequence.
Make a no easy to give and respect
A connector can decline without explaining another person's private circumstances: "I'm not able to make this introduction, but thanks for the clear context." If the recipient declines, close the request rather than forwarding the refusal or asking the connector to keep pressing. Do not share their address or move the conversation to a personal phone number.
Where a twin can help, and where people decide
A SyncedIn twin can help draft the context and explore a possible next step. Use a specific conversation goal and review the names, claims, and scope. A simulated recipient-side reply is not the person's words or permission to introduce them. Confirm the real people's choices in the channel you intend to use.
For a possible cofounder, start with the work and expectations to explore together. For an investor introduction, make the purpose and current professional context clear. Neither a warm introduction nor a promising twin draft guarantees a role, funding, or a relationship.
Sources and limits
SyncedIn's original fictional examples and editorial guidance, reviewed November 20, 2026. Fred Wilson's double-opt-in introduction supplies the permission-first principle. Michael Seibel's investor-email guidance provides a concise, direct-contact counterpoint. These are authors' practices, not measured SyncedIn response rates or a universal requirement for every relationship.