Ask for an introduction

The best first message is one someone else sends for you, after asking first.

An introduction from someone the other person trusts gets read. A careless one burns that trust: the connector gets dropped into an awkward thread, and the person being introduced feels ambushed. The fix is the double opt-in. Ask the connector, give them a short note they can forward unchanged, and only make the introduction when the other person has said yes.

This skill writes each piece of that exchange.

What you need

1. Who you want to meet and why, specifically.
2. Who could introduce you, and how well they know each of you.
3. What you'd like from the conversation, in one sentence.

The four messages

1. Asking the connector

Short, specific and easy to decline. Say who, why them, and what you'll send.

Hi <connector>, would you be comfortable introducing me to <person>?

They posted about <their problem> last week, and <one sentence on why you're useful to them specifically>.

I've written a short note below you can forward as is. If it's not a good fit or the timing's wrong, no problem at all.

2. The forwardable note

This is what the connector sends to the other person to ask if they want the introduction. It must stand on its own, mention the person's situation, and make no requests beyond "would you like to meet". Keep it under 80 words.

<Your name> builds <one plain line>. They mentioned <the person's situation> and thought <one specific, useful reason>. Would you like an introduction? Completely fine to say no.

3. The introduction itself (only after a yes)

Both names, why they should talk, and then the connector steps back.

Subject: <Person> / <You>

<Person>, meet <you>, who <one line>. <You>, meet <person>, who <one line>.

<Person> mentioned <their situation>, and <you> <the specific reason>. I'll let you two take it from here.

4. Your reply

Reply quickly, move the connector to BCC, thank them, and give one clear next step that doesn't require a call if a call isn't needed.

Thanks <connector>, moving you to BCC.

<Person>, good to meet you. <One line that shows you know their situation.> Easiest next step: <a link, a short question, or two times that work>. Whatever's simplest for you.

Steps

1. Check the reason is real. If you can't say why this person, specifically, would want to meet you, don't ask.
2. Pick the connector who knows the person best, not the most important name you know.
3. Write the forwardable note first. It's the one that decides everything.
4. Write the ask to the connector around it.
5. Draft the reply you'll send after the introduction, so it goes out within hours.

Rules

• Never ask for an introduction you wouldn't make yourself.
• Never introduce two people without asking both first.
• One request per connector at a time.
• If the person says no, or doesn't answer, that's the answer. Don't ask the connector to chase.
• Thank the connector afterwards, whatever happens, and tell them how it went.

Why double opt-in works when there's no mutual contact

The same structure works without a connector. A message that asks "would you like an introduction to someone who can help with this?", and takes no as an answer, gets read differently from a pitch. It's a question the person controls, about something they already said they wanted to fix.

With MyPip (coming)

This is how MyPip works: it writes to the person it found, asks if they'd like an introduction, and only copies you in when they say yes. When the MyPip MCP is live, this skill will be able to show your introductions and draft your reply the moment someone accepts.