Net Shared Intro List

---
name: net-shared-intro-list
description: Sets up a Shared Introduction List, your brief shared with a friend or partner, their own people added against it with an owner column, what stays private, and how and when the list is retired. Use for "run net-shared-intro-list", "a friend offered to help me find clients", "share my brief with a partner", "let someone add people to my list", "introductions from a friend's network", "shared intro list", part of the Claude for Networking on LinkedIn Pack by Polar Bear.
---

# Shared Introduction List

## When To Use
A friend or partner offers to help and you need a way they can add people without you seeing their contacts. Use it when someone says "send me what you are looking for and I will think of people". It answers: what do you share, who writes to whom, and what never leaves each person's own hands?

## When Not To Use
If the help is one introduction, run the Double Opt-In Introduction. If another firm sends you work regularly and you want it written down, run the Partner Agreement. For your own names this week, use the Hand-Picked Shortlist.

## Inputs
- Your Networking Brief, as you are willing to share it
- The friend or partner, and how long the list should run
- Where it will live: a shared Claude Project (redesigned Projects, beta, select plans) holding the brief and names only, or a simple shared file
If you have none of this, I start from your brief's first two fields and mark the output as a first draft.

## Approach
Opening the list to introducers (a practitioner method, described generically): the holders share one brief and each adds people from their own network, and whoever added a person is the one who writes to them. Every introduction then runs double opt-in, after Fred Wilson ("The double opt-in introduction", AVC, 2009). The failure it prevents: a friend's whole contact list pasted into your files, and a stranger hearing from you about a connection they never agreed to.

## Workflow
1. Ask three questions: who will hold the list with you, where will it live, and on what date should it end?
2. Prepare the shared brief: who you help and who you would like to meet, in plain words. Anything you would not show your partner stays out.
3. Set the columns, and nothing more: name, role, reason in the adder's words, added by, status. No email, phone, profile export, message or research brief ever goes in.
4. Each holder adds people from their own memory or records, against the same brief. The adder's reason is theirs; Claude does not rank or sort the names.
5. Owner rule: whoever added a person writes to them. No one else contacts that person, and the adder decides whether to approach them at all.
6. Every introduction runs double opt-in: the adder asks their contact first, and you supply your Forwardable Intro Blurb if asked.
7. Retirement: on the end date the holders set, the owner of the shared Project or file deletes it. Each holder keeps only their own notes.

## Output Format
```markdown
# Shared Introduction List
**Holders:** [you] and [friend or partner] · **Lives in:** [shared Project (beta) / shared file] · **Ends on:** [date]
## Shared brief
- Who I help: [plain words]
- Who I would like to meet: [roles and situations]
## Names
| Name | Role | Reason (adder's words) | Added by | Status |
|---|---|---|---|---|
| [name] | [role] | [reason] | [holder] | [not asked / asked / yes / not now] |
## Never in this list
- Contact details, exports, messages, research briefs
## Rules
- Whoever added a person writes to them; nobody else does
- Every introduction is double opt-in
## Decision
You and [holder] agree the brief and the end date by [date]; each holder decides who to approach from the names they added.
```

## Done When
- The shared brief contains only what you are willing to show
- The columns hold no contact details and no message text
- Every name has an owner and a reason in the adder's words
- The end date and the person who deletes the list are named

## Quality Bar
- Names are added by people, never imported from an export
- No ordering, scoring or ranking of anyone on the list
- "Not now" is a status, never a note about the person
- Your private export and messages stay in your own private Project, never this one
- Whoever added a person writes to them; no export or message ever goes into the shared list, and nothing is sent for you.

## Next
Run net-partner-agreement (Partner Agreement) if a partner keeps sending work.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).