Net Run Of Ten

---
name: net-run-of-ten
description: Plans this week's Run of Ten Plan from your shortlist, with a reason to write and a status per person, what is ready to send and what still waits for research, one run at a time. Use for "run net-run-of-ten", "plan my networking this week", "who am I writing to this week", "set up my next run", "I only network when work dries up", "keep my outreach steady", "where is each message at", part of the Claude for Networking on LinkedIn Pack by Polar Bear.
---

# Run of Ten Plan

## When To Use
You network in bursts when work dries up, then stop when it returns. This turns your shortlist into one small run for this week and answers: who am I writing to, why, and what is each message waiting on?

## When Not To Use
If you have not chosen your names yet, run Hand-Picked Shortlist first; this plan never picks people for you. Once messages are sent and replies start, the Follow-Up Tracker takes over what is due.

## Inputs
- Your Hand-Picked Shortlist, with fit, tier and your reason per name.
- Any Reason to Write, Talking Points or Person Research Brief already done for these names.
- The time you will block for this run this week, in your own calendar.
If you have none of this, I start from the names you paste and a reason in your words for each, and mark the output as a first draft.

## Approach
Small runs are a practitioner method: about 10 people at a time, every week, good weeks included. The steady run is the answer to the feast or famine cycle, because the network is tended before the pipeline empties, not after. The failure it prevents: a panicked week where forty people get the same rushed note, followed by two quiet months and a network that now remembers you only asking.

## Workflow
1. Ask up to three questions: when your time block is this week, whether the previous run is done or closed, and whether any name on the shortlist has changed since you chose it.
2. Check the run before it starts. One run at a time: if the last run has messages still unsent, finish or close it first. Take about 10 names from the shortlist, never the whole list; fewer is fine.
3. For each person, carry over your reason to write from the five (share, catch up, congratulate, introduce, suggest a conversation). If none is chosen yet, the status is "to research" and the next step is the research brief.
4. Give each person one status, about your actions only: to research, points ready, written, sent by you, reply. Status never describes the person or how likely they are to answer.
5. Mark "ready to send" only when you have written the message yourself and run it through the Message Checklist and Grammar Check. Points ready is not ready.
6. Write the next step per person and split the run into what is ready now and what waits for research. Anything still waiting at the end of the week goes back to the shortlist, not into a rushed send.
7. Close the run: count what you sent, note who goes to the Follow-Up Tracker, and set the date the next run starts.

## Output Format
```markdown
# Run of Ten Plan
Run: [number] · Week of: [date] · Time block: [day and time you set] · Previous run: [done / closed]
## The run
| Person | Reason to write | Status | Next step |
|---|---|---|---|
| [name] | [one of the five, in your words] | [to research / points ready / written / sent by you / reply] | [your next action] |
## Ready to send
- [name]: written by you, checklist and grammar check done
## Waiting for research
- [name]: [what is missing]
## Back to the shortlist
- [name]: [your reason, about this run, never about the person]
## Decision
[You decide by [date] which messages you send this week and when the next run starts.]
```

## Done When
- The run holds about 10 names or fewer, all from your shortlist.
- Every person has one reason, one status and one next step.
- Nothing is marked ready that you have not written and checked.
- The next run has a start date.

## Quality Bar
- One run at a time; a run never grows into a batch.
- Status describes your actions, never the person.
- The run continues in good weeks, at a size you can keep.
- No message text appears in the plan; it lives where you write it.
- About 10 people, each message written and sent by you; never a batch.

## Next
Run net-follow-up-tracker (Follow-Up Tracker) to track replies and follow-ups.

## 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).