How to write a forwardable introduction email

A forwardable introduction email is a short note you give a connector to pass to someone you would like to meet. State who you are, the specific reason for the conversation and a manageable request. Include only information you are comfortable sharing. The connector should still ask the recipient whether an introduction is welcome.

The note has a narrow job: help another person understand the proposed conversation without making your contact explain your whole business. It is not a pitch deck, an endorsement written on the connector's behalf or permission to add everyone to a shared thread. This guide focuses on writing that reusable note. Our warm introduction guide covers finding and approaching a suitable connector.

Write for the person who has not met you

Your connector already knows something about you. The intended recipient may know nothing. Begin with a plain description of what you are building or doing, then name the question that makes their experience relevant. Avoid an opening that depends on a private conversation, such as “following up on everything we discussed.” A forwarded message should remain understandable outside its original thread.

Imagine a business owner exploring how to hand off customer onboarding. Saying that you want to meet successful operators leaves the recipient to guess what help you need. Saying that you want to understand how an operator assigned responsibility for onboarding explains a real topic. You do not need to describe every operational problem in the business to make that request meaningful.

thoughtbot's guidance on requesting an introduction offers introduction-request examples that explain the people involved and the reason to connect. Build on that emphasis on useful context when preparing a note your connector can pass along. The examples below are original hypothetical messages, not quotations, real AME conversations or evidence of response rates.

Give the note a subject that explains the conversation

A subject such as “Introduction request: onboarding responsibility” tells the connector and recipient what the note concerns. A subject such as “Huge opportunity” makes a claim without explaining it. Choose language the recipient can understand without knowing your internal project name. The subject should match the request in the body.

Keep your own name and business description recognizable. If you use a product name that does not explain the work, add a brief description. Do not use the subject line to imply an existing relationship, an agreed meeting or the connector's endorsement. Being forwarded by someone familiar does not turn an exploratory request into an appointment.

Build a note with context, fit and one request

Start with what you do and the immediate situation. Next, explain why this person's relevant experience fits the question. Finish with the conversation you are asking them to consider and a way to decline. Use a public work sample only when it helps the recipient understand the topic. A link should reduce explanation rather than assign extra preparation.

Subject: Introduction request: making onboarding less founder-dependent

I run a small service business and am working out how to give an operator ownership of customer onboarding. I am especially interested in how teams decide which exceptions should still reach the founder.

Your experience building an operating process looks relevant to that question. Would you be open to a brief conversation about how you approached that handoff? I can share a short, nonconfidential outline of the workflow if useful. If the topic or timing does not fit, I understand.

Adapt every statement to what you actually know. If you have not established that the recipient built an operating process, do not assert it. You could instead refer to a public explanation they published, or ask whether their experience covers the question. A specific but invented reason for relevance is still misleading.

Change the request when you are exploring a partnership

A request for advice should not conceal an intention to recruit someone or sell them a service. If you want to explore a working relationship, say so. Explain the proposed contribution without treating a conversation as agreement. Our strategic partner guide helps define the shared opportunity before looking for a connection.

I am building a service for independent design teams and am exploring a collaboration with someone who understands their operating needs. I would like to compare the customer problem we each see and find out whether a small joint project is worth discussing. Would an introductory conversation be welcome? There is no proposal to agree to at this stage.

This hypothetical version gives the recipient a different choice from the advice request. Do not reuse it unchanged for every person. The business, proposed contribution and reason for contacting that individual must all be accurate. Avoid promising access to customers, commercial returns or a partnership before you have an arrangement you can support.

Keep the connector's message separate from yours

Write your forwardable note in your own voice. Separately tell the connector why you thought of them, whom you hope to meet and that they can decline. Let them decide what they can honestly say about their relationship with you. Do not draft praise for them to present as personal knowledge if they have not seen your work.

You might write, “Below is a short note you can forward if you are comfortable asking. Please change or remove anything that does not reflect what you know.” The connector can add their own introduction without altering the substance of your request. They may also decide that a different person fits better, or that they are not the right route.

Asking the connector to forward a note is different from asking them to add the recipient immediately. Our guide to checking with both people first explains the permission step. A well-written note supports that process. It does not replace it.

Remove material that should not travel

Start a clean note rather than forwarding a long conversation with unrelated details below it. Check attachments, links and document access. A recipient should not receive private customer examples, confidential hiring plans or someone else's contact details because they happened to appear earlier in the thread. Describe the problem using information you can legitimately share.

Read the note as though it reached someone beyond the intended recipient. That is a practical editing check, not a claim that every message will be redistributed. If a detail would create a problem outside a trusted conversation, replace it with a safe summary or leave it for a later discussion with an appropriate sharing arrangement.

Check what the recipient is being asked to do

Remove secondary requests that make the first conversation harder to assess. Asking someone to read a deck, introduce several other people and advise on a hiring decision creates several assignments. Choose the immediate question. Additional steps can follow if the participants decide they are useful.

Check that the ask has an understandable boundary. A short exchange about a handoff is different from ongoing advice or a review of the entire business. Let the recipient suggest a different format if they prefer. Do not include a calendar invitation or describe the meeting as arranged before they have agreed.

After sending, let the permission process work

Tell the connector if your need changes or the introduction is no longer useful. If the recipient declines, close the request without seeking their private explanation. If the introduction goes ahead, use the agreed topic to begin. Our follow-up guide covers moving that conversation forward without pressure.

AME learns what people are building, what they bring and what they need, then makes purposeful introductions one at a time. If that approach fits the person you need to meet next, learn about AME. Whether an introduction comes through a colleague or AME, clear context helps both people decide whether the conversation makes sense.