Connection Request Note
When To Use
A blank request will be ignored, and a false "great to connect" is worse. You want to connect with a few people you have not met. This answers: do I have a true reason this person would recognise, and if I do not, am I willing to take them off the list?
When Not To Use
Not for lists, and not for anyone with whom you have no true context: those people come off, and you wait for a real reason or a warm path. Once someone has accepted, the next note is the Conversation Opener.
Inputs
- The few people you want to connect with this week, one line each.
- For each, the context in your own words: a talk of theirs you attended, a public thread you both took part in, a piece of theirs you read, or a mutual contact who agreed to be named.
- One specific detail from that context that only someone who was there, or who read it, would know.
If you have none of this, I start from the names and ask for the context one by one. With no context, the name comes off.
Approach
Real context only, sent by hand within the platform's rules. LinkedIn Help states that software and extensions that automate activity are not allowed, so every note is typed and sent by you through the normal request screen, and nothing here touches LinkedIn. The true-context rule is strict because a stranger can check it: they know whether they gave that talk and whether your mutual contact exists. The failure it prevents: "I came across your profile and was impressed", sent to forty people before lunch.
Workflow
- Ask at most three questions: who you want to connect with, what the true context is for each, and how many notes you can follow up properly this week.
- Test each person against the four accepted contexts: a talk you attended, a thread you both took part in, a piece of theirs you read, a mutual contact who agreed. "Same field" and "would be a good client" are not contexts.
- Ask for the specific detail and where it can be checked. If you cannot give one, the person comes off the list here, with the reason written down.
- Set out the parts for each remaining person: the context, the one detail, why connecting is useful to them, and nothing else. No pitch, no link, no calendar ask.
- Check for false familiarity in what you plan to say: no "great to reconnect" when you never connected, no "as discussed" when nothing was. A mutual contact is named only if they said yes.
- You write each note yourself, short enough for the limit the request screen shows, and send it by hand. I give the parts, not the note.
- Keep the number small. A week with three true notes is better than a week with thirty.
Output Format
# Connection Request Notes
Week of [date] | Notes you can follow up: [number you set]
## People with a true context
| Person | True context (which of the four) | One specific detail | Where it can be checked | Why connecting is useful to them |
|---|---|---|---|---|
| [name] | [talk attended / shared thread / piece read / mutual contact who agreed] | [detail] | [link, date, or the contact's name] | [one line] |
## Taken off the list
- [name]: [no true context / no specific detail / mutual contact has not agreed]
## Decision
[Your name] writes each note in their own words and sends it by hand by [date]; anyone without a true context stays off.
Done When
- Every person left on the list has one of the four contexts and a checkable detail.
- Everyone else is listed as taken off, with the reason.
- No part contains a pitch, a link or a meeting ask.
- No note text was written for you.
Quality Bar
- One note per person, written for that person; no lists, no bulk sending.
- No automation tools, extensions or scheduled sending, in line with the platform's rules.
- No claim of a shared moment that did not happen.
- A context you cannot prove to the reader is treated as no context.
- Real context only; you write each note and send it yourself, and nothing is automated on LinkedIn.
Next
Run reach-conversation-opener (Conversation Opener) once someone accepts and you have a reason to write.
About the makers
This pack is made by 90n (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).
1---2name: reach-connection-request3description: Prepares connection request notes one person at a time, with the true context for each, one specific detail, why connecting is useful to them, no pitch and no link, and the people taken off the list for having no true context. Use for "run reach-connection-request", "connection request note", "LinkedIn connection request message", "what do I write in a connection request", "connect with someone I have not met", "note with my invite", "connection message", "should I add a note", part of the Claude Guide for Outreach Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/reach-connection-request6---78# Connection Request Note910## When To Use11A blank request will be ignored, and a false "great to connect" is worse. You want to connect with a few people you have not met. This answers: do I have a true reason this person would recognise, and if I do not, am I willing to take them off the list?1213## When Not To Use14Not for lists, and not for anyone with whom you have no true context: those people come off, and you wait for a real reason or a warm path. Once someone has accepted, the next note is the Conversation Opener.1516## Inputs17- The few people you want to connect with this week, one line each.18- For each, the context in your own words: a talk of theirs you attended, a public thread you both took part in, a piece of theirs you read, or a mutual contact who agreed to be named.19- One specific detail from that context that only someone who was there, or who read it, would know.20If you have none of this, I start from the names and ask for the context one by one. With no context, the name comes off.2122## Approach23Real context only, sent by hand within the platform's rules. LinkedIn Help states that software and extensions that automate activity are not allowed, so every note is typed and sent by you through the normal request screen, and nothing here touches LinkedIn. The true-context rule is strict because a stranger can check it: they know whether they gave that talk and whether your mutual contact exists. The failure it prevents: "I came across your profile and was impressed", sent to forty people before lunch.2425## Workflow261. Ask at most three questions: who you want to connect with, what the true context is for each, and how many notes you can follow up properly this week.272. Test each person against the four accepted contexts: a talk you attended, a thread you both took part in, a piece of theirs you read, a mutual contact who agreed. "Same field" and "would be a good client" are not contexts.283. Ask for the specific detail and where it can be checked. If you cannot give one, the person comes off the list here, with the reason written down.294. Set out the parts for each remaining person: the context, the one detail, why connecting is useful to them, and nothing else. No pitch, no link, no calendar ask.305. Check for false familiarity in what you plan to say: no "great to reconnect" when you never connected, no "as discussed" when nothing was. A mutual contact is named only if they said yes.316. You write each note yourself, short enough for the limit the request screen shows, and send it by hand. I give the parts, not the note.327. Keep the number small. A week with three true notes is better than a week with thirty.3334## Output Format35```markdown36# Connection Request Notes37Week of [date] | Notes you can follow up: [number you set]38## People with a true context39| Person | True context (which of the four) | One specific detail | Where it can be checked | Why connecting is useful to them |40|---|---|---|---|---|41| [name] | [talk attended / shared thread / piece read / mutual contact who agreed] | [detail] | [link, date, or the contact's name] | [one line] |42## Taken off the list43- [name]: [no true context / no specific detail / mutual contact has not agreed]44## Decision45[Your name] writes each note in their own words and sends it by hand by [date]; anyone without a true context stays off.46```4748## Done When49- Every person left on the list has one of the four contexts and a checkable detail.50- Everyone else is listed as taken off, with the reason.51- No part contains a pitch, a link or a meeting ask.52- No note text was written for you.5354## Quality Bar55- One note per person, written for that person; no lists, no bulk sending.56- No automation tools, extensions or scheduled sending, in line with the platform's rules.57- No claim of a shared moment that did not happen.58- A context you cannot prove to the reader is treated as no context.59- Real context only; you write each note and send it yourself, and nothing is automated on LinkedIn.6061## Next62Run reach-conversation-opener (Conversation Opener) once someone accepts and you have a reason to write.6364## About the makers6566This 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).