write-intro-email

name	write-intro-email
description	Draft professional mutual introduction emails connecting two people, with double opt-in best practices and structured templates.
version	1.0.0
last_updated	"2026-02-10T00:00:00.000Z"
tools_required	["Gmail"]
agent_type	main_agent
use_cases	["Introduce two people over email","Write an intro email connecting contacts","Draft a mutual introduction","Double opt-in introduction"]
tags	["email","introductions","networking","communication"]
author	Team Member
contributed	["Team Member","Rebel"]
last_modified_by	Rebel
last_modified_at	2026-02-10

Write Intro Email

Draft professional mutual introduction emails connecting two people who could benefit from knowing each other.

When to Use

• Connecting two contacts who could benefit from knowing each other
• Someone asks for a specific introduction or referral
• You identify a valuable connection opportunity
• Following up on a promise to introduce someone

Before You Write: Double Opt-In

Always use double opt-in unless the user explicitly says otherwise. This is the gold standard for professional introductions (popularised by Fred Wilson, Union Square Ventures).

The Process

1. Decide if the intro makes sense. Is there a compelling reason for both people? If one person only wants a favour, think about what value they bring to the other.
2. Ask the right person first. Check with the person you've known longer, have a deeper relationship with, or who is more senior. If they decline, the other person never knows.
3. Provide context in the permission request. Include: who the person is (LinkedIn URL if possible), how you know them, what the ask is, and why it's valuable for the recipient specifically.
4. Give people an easy out. Use phrasing like: "If for any reason you aren't into it, just tell me or ignore this — I completely understand."
5. Only proceed if both agree.

Pre-Introduction Check Email Template

Hi [Name],

[1-2 lines about the other person and why you're thinking of connecting them]

Would you be up for an introduction?

[sign-off]

The Introduction Email

Core Structure

Every introduction email follows this structure:

1. Subject line — Clear and searchable
2. Opening greeting — Name both parties
3. Opening line — Brief, warm
4. Person A description — 1-2 paragraphs with context
5. Person B description — Balanced treatment
6. Context / rationale — Why this connection makes sense
7. Handoff — Signal you're stepping out

Subject Line Formats

Standard: Intro: [Name A] <> [Name B] Descriptive: Intro: [Name A] <> [Name B] re [topic] With companies: Intro: [Name] ([Company]) <> [Name] ([Company])

Keep it brief, clear, and searchable. Never just "Intro" or "Quick intro."

Template

Hi [Name A] and [Name B],

It's a pleasure to introduce you.

[Name A] ( [LinkedIn URL] ) [is/leads/founded] [role/company]. [Key accomplishment
or context — be specific, not generic]. [Your relationship to them]. [Optional:
specific superpower or notable detail].

[Name B] ( [LinkedIn URL] ) [is/leads/founded] [role/company]. [Key accomplishment
or context]. [Your relationship to them]. [Optional: specific superpower or notable
detail].

[Context paragraph: Why this connection makes sense. Reference a recent conversation
if possible. What the opportunity or need is. Include honest caveats if uncertain
about fit.]

Over to you,

[sign-off]

Person Description Formula

For each person, include (in roughly this order):

1. Name + LinkedIn link — Always include when available
2. Current role/company — Lead with what they do now
3. Key accomplishments — Specific and concrete, not generic praise. Quantify when possible ("grew to 70M users", "raised $10M Series A")
4. Your relationship — Always be explicit ("friend", "worked together for 3 years", "met at [conference]")
5. Unique superpower (optional but powerful) — A vivid, specific descriptor ("wizard at prompt engineering", "one of the sharpest product thinkers I know")

Context Paragraph

The "why this makes sense" paragraph should:

• Reference a recent conversation when possible ("In our last chat, you mentioned...")
• Explain the opportunity/need clearly and specifically
• Include honest caveats when uncertain ("It's hard to know whether this is a good fit, but...", "I haven't checked whether [Name] is still looking for...")
• State the value proposition for both sides — why would each person want this connection?

Tone Guidelines

DO:

• Be warm but professional
• Use specific, concrete details (name the project, the metric, the tech stack)
• Be honest — acknowledge uncertainty or conflicts of interest
• Keep paragraphs short (1-3 sentences)
• Use active voice ("Viktor has assembled..." not "A team was assembled...")

DON'T:

• Use generic praise ("great person", "talented professional")
• Oversell or exaggerate capabilities
• Hide conflicts of interest or business relationships
• Make promises about outcomes
• Write walls of text

Transparency & Honesty

Always disclose when relevant:

• You have a business relationship with one party
• You haven't worked with someone personally (yet)
• You're uncertain about fit or availability
• There's a potential conflict of interest

After the Introduction

BCC Switcheroo

When replying to an intro email, move the introducer to BCC on your first reply. Say it explicitly:

"Thanks for the kind introduction, [Connector Name] — moving you to BCC."

This is widely considered a hallmark of professional email etiquette.

Who Replies First

The person who asked for the introduction (or the more junior person) should reply first.

Close the Loop

Always circle back to the connector after the meeting happens:

• Tell them how it went
• Share a few key points or next steps
• Thank them genuinely

Chris Fralic (First Round Capital): "Nine out of 10 people don't follow through. Not only does the relationship stop there, but I'll never use the word 'reliable' to describe them."

The Forwardable Email Pattern

An alternative approach: instead of the connector writing the full intro, the person seeking the introduction writes a short email addressed to the target recipient that the connector can simply forward with a line of endorsement.

How It Works

1. The person seeking the intro writes a short email addressed to the target person
2. They send it to the connector, asking them to forward it along
3. The connector adds 1-2 sentences of endorsement at the top, then forwards

Forwardable Email Template

Subject: Intro TO [Target Name] FROM [Your Name], [Company]

Hi [Target Name],

[Your Name] here — I [role] at [Company] ( [URL] ). [2-3 sentences on what you do
and why it's relevant]. [1-2 sentences on traction/credibility].

I'd love to connect because [specific reason related to them]. Would you be open to
a quick 15-minute call?

[sign-off]

Key rules: Keep it under 250 words. Address the email to the final recipient. Include traction/credibility facts. Make it possible for the connector to forward in 15 seconds or less.

Common Scenarios

Contractor/Hire Introduction

• Lead with technical capabilities and specific tech stack
• Reference their team or consulting company
• State the hiring need clearly

Founder-to-Founder

• Lead with company/role
• Mention specific parallel experiences or challenges
• Keep it peer-to-peer

Service Provider Introduction

• Lead with expertise and longevity of relationship
• Explain the specific need
• Note personal experience when relevant

Proactive/Future Introduction

• Explain you're connecting them now to avoid urgency later
• Acknowledge the speculative nature
• Focus on potential alignment

Agent Instructions

• IMPORTANT: Draft the email first, never send without user approval
• Look up LinkedIn profiles if URLs are provided to get accurate titles/context
• Search prior communications (email, Slack, CRM) for relevant context about both parties
• Make both parties look good in the introduction — balanced treatment
• Be clear about why the connection makes sense
• Ask the user for missing context rather than guessing
• Never fabricate details about people, roles, or accomplishments
• Use HTML formatting when creating Gmail drafts (isHtml: true)

References

• Fred Wilson, The Double Opt-In Introduction
• Mark Suster, Why You Should Think Twice Before You Send That Intro Email
• Chris Fralic, How to Become Insanely Well-Connected

Extensions

This skill can be extended with personal or team preferences (sign-off style, bio templates, signature blocks). See @customise-and-extend-skill.