# Start Warm Intro Request

> Prepares a Warm Introduction Request through someone you know, with the path check, the ask to the connector with an easy no, a forwardable blurb they can send unchanged, the double opt-in steps, the thank-you and the close-the-loop note. Use for "run start-warm-intro-request", "ask for an introduction to someone", "can you introduce me to", "warm introduction email", "forwardable email", "double opt-in intro", "they said they would introduce me and it never happened", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-warm-intro-request` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-warm-intro-request`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-warm-intro-request/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-warm-intro-request

---


# Warm Introduction Request

## When To Use
Someone you know knows the person you need, and you do not want to put them in an awkward spot. Or they already said "happy to introduce you" and nothing happened, because the introduction is theirs to write. Run this for one named person through one connector.

## When Not To Use
To ask for a type of person, not a named one, use Introduction Ask. If the connector barely knows the person, the introduction will not carry trust; wait for a better path.

## Inputs
- The person you hope to meet: role, organisation, and why them, with a public link
- The connector: how you know them, and how well you think they know the other person (they may correct you)
- The one conversation you would ask for, and your Positioning Statement line
If you have none of this, I start from the two names and your reason, and mark the points as a first draft.

## Approach
The double opt-in introduction, described by Fred Wilson on his AVC blog in 2009: the connector asks the other person first, and introduces only on a yes. It is paired with the forwardable note, as Harvard Business Review summarised it in 2019: the connector is lending you their network, so hand them a short note they can forward and do not make them write one. The failure it prevents: a surprise group email to a busy person who never agreed, which costs your connector goodwill and stops them introducing you again.

## Workflow
1. Ask at most three questions: how well the connector knows the person (close, acquaintance, barely), what one conversation you hope for, and whether any limit from your terms check touches this person.
2. Check the path. If the connector barely knows them, I say so and suggest waiting. Never press someone to vouch for a person they cannot.
3. Give points for the ask to the connector: why this person, what you hope for, how small the first step is, and an explicit easy no. You write it.
4. Give points for the forwardable blurb, in four parts: who you are (your line, no adjectives about yourself), why this person specifically (a sourced public fact about their work), the one conversation you would ask for with its length, and how easy it is to decline.
5. You write the blurb. I check what you wrote: short enough to forward unchanged, no claim the connector would have to vouch for and cannot, no attachment needed.
6. State the order: the blurb goes to the connector, who asks the other person. You do not contact them before their yes.
7. Prepare the thank-you to the connector whatever the outcome, and the close-the-loop note telling them what happened.

## Output Format
```markdown
# Warm Introduction Request
To meet: [name, role, organisation] (source: [link]) | Connector: [name] | Their closeness (connector confirms): [level]
## Ask to the connector (my words)
[my message, including the easy no]
## Forwardable blurb
| Part | Points | Source |
|---|---|---|
| Who I am | [from my line] | my positioning |
| Why this person | [points] | [link, date] |
| What I would ask, and the easy way out | [one conversation, topic, length; how to decline] | my brief |
My blurb (my words): [text]
## Double opt-in steps
| Step | Who | Done |
|---|---|---|
| Connector asks first | [connector] | [yes / no] |
| The other person says yes | [name] | [yes / no] |
| Introduction made | [connector] | [date] |
## Thank-you and close the loop
Thank-you sent: [date] | What I told the connector afterwards: [note, date]
## Decision
[Your name] sends the ask and the blurb to [connector] by [date]; the connector decides whether and when to forward it.
```

## Done When
- The connector's closeness to the person is checked before anything is written.
- The ask contains an explicit easy no.
- The blurb is in your words and can be forwarded unchanged.
- The thank-you and the close-the-loop note are planned whatever the answer.

## Quality Bar
- The person is never contacted before their yes.
- The connector is never pressed, chased more than once or quoted without consent.
- Public work facts only about the person you hope to meet.
- You choose the path, write the ask and the blurb, and send them yourself; the connector decides the rest.

## Next
Run start-coffee-chat-prep (Coffee Chat Prep) once the introduction is made and a first call is in the calendar.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

