Warm introduction mechanics

A warm introduction borrows a prior relationship from a mutual contact.¹ That trust can still disappear in an inbox: warm introductions die there more often than cold emails.² Treat the handoff as a small task for the connector and recipient. Get permission before adding anyone, explain why you want the connection, and give the connector a clean exit. The strongest format leaves everyone knowing why they are on the thread and what happens next.

Decide whether the intro is worth asking for

Before you ask, decide what you want the recipient to do after the connection. That outcome tells you whether a warm introduction will help or create work for the people involved.

A mutual contact who vouches for you improves your chance of establishing trust with the person you want to reach.³ Clarify the outcome before you reach out.⁴ Keep the request voluntary, because neither person is obligated to help.⁵

Warm introductions require substantial effort and trust, so they may not be the most efficient route to a goal.⁶ Check whether the recipient is the right person, whether the mutual contact can speak credibly about the connection, and whether the request deserves the effort.

Get permission before choosing the format

Permission determines the format. Give the connector enough context to decide whether to help, then make the handoff easy to complete.

Do the heavy lifting up front so the connector can help without constructing the request from scratch.⁷ Give them the reason for the introduction, the outcome you want, and a draft they can use or adapt.

Ask, "Do you have dedicated time blocks or days of the week where you like to take intro calls like these?".⁸ The answer tells you whether to include a meeting request or start with a lighter exchange.

Show how the recipient benefits from the conversation. When you show that you add value to the person you want to meet, the mutual contact is more likely to accept because their relationship will benefit too.⁹

Get an opt-in before starting the thread.¹⁰ Starting an email thread without asking creates extra work and social pressure for the people involved.¹¹ If the answer is no, close the request cleanly and leave the relationship intact.

Choose the handoff

Use the mechanism that lets the person with the strongest context make the clearest introduction. Email is usually the practical channel because the referral can come from someone the recipient trusts.

Broker the referral by email when you want it to come from a trusted person.¹² A shared thread works when the connector has agreed to introduce you and everyone is ready to respond directly. A forwarded message works when the connector wants to pass along your note and add their own context. The connector forwards the email and adds a quick note about the introduction request.¹³

For a context heavy introduction, email the intended recipient before making the introduction.¹⁴ This gives that person a chance to understand the reason for the connection before the thread opens.

Use a direct handoff when the connector can name the person to meet and give a clear route for arranging the conversation. A direct handoff can give the recipient a contact route and a meeting action.¹⁵

Write the email

Make the message easy to scan. The connector should be able to forward it, the recipient should understand why you are writing, and the next action should be obvious.

Start with why you are writing before giving background about yourself.¹⁶ Keep your identity to one relevant sentence containing your name, role, and the detail that establishes context.¹⁷ Replace generic placeholders with specific details.¹⁸ Match the language and formality to your relationship with the recipient.¹⁹

A useful structure is:

Subject: [clear reason] via [mutual contact]

Hi [recipient],

[Why I am writing and the relevant context.]

I am [your name], [your role], and [the detail that establishes context].

[The purpose of the conversation.]

Would [the next step] work?

End with one clear next step instead of several competing requests.²⁰ Keep the subject line clear, because clarity beats cleverness there.²¹ Use the mutual contact's name only after receiving permission to use it.²²

Read the draft as the connector would. If they would need to explain the reason, rewrite it. If the recipient would need to guess what you want, rewrite the next step. Replace broad claims with the specific context that makes the introduction sensible.

Release the connector

The connector's work ends when the connection exists. Make that exit explicit so the new conversation can continue without more inbox traffic.

Once you are connected, move the introducer to BCC to spare their inbox from unnecessary additional emails because their job is done.²³ Reply directly to the person you were introduced to and keep the next exchange focused on the agreed purpose.

If the thread stalls, return to the original purpose and make the next message easy to answer. Give the recipient a clear choice to continue, redirect you, or decline.

What not to do

Keep these failure points out of the process:

• Do not make an introduction when you do not know one or both people well or you are not comfortable making it. Decline the request.²⁴
• Do not treat an uneven power dynamic as routine. Give extra thought to the connection request, the message, and whether the introduction makes sense.²⁵
• Do not ask someone to become your mentor before establishing a relationship. Begin with one specific question.²⁶
• Do not add a company name without explaining its relevance to the message.²⁷