# Target list + tracker

The sprint goal is **20 real prospects**. This file does not invent names — it
gives you the segments, where to find real people in each, and a tracker to
fill as you source them. Sourcing is yours to do (and keeps the list honest);
the structure below makes it fast.

## How to hit 20 (suggested mix)

| # | Segment | Where to find them | Why they care |
|---|---------|--------------------|---------------|
| 5 | Coding-agent power users | Claude Code / Cursor Discords, r/ChatGPTCoding, X threads about agent autonomy | They already let an agent act and have felt the "oh no" moment |
| 4 | Platform / DevEx engineers | Platform-engineering Slack, internal-tools meetups, "we run agents in CI" blog authors | They own blast radius for other people's agents |
| 4 | Security-minded OSS devs | Maintainers of secrets/policy/supply-chain tools, OWASP folks, OpenSSF | They think least-privilege + audit natively |
| 4 | GitHub App / MCP builders | MCP server authors on GitHub, `modelcontextprotocol` org discussions, GitHub App marketplace devs | They live at the agent↔tool boundary |
| 3 | Authors who wrote about the problem | People who blogged/posted "should I give my agent write access" | Pre-qualified: they already articulated the pain |

## Sourcing checklist (do these, then fill the tracker)

- [ ] Search GitHub for active MCP server repos; note maintainers who engage in issues.
- [ ] Scan the Claude Code / Cursor communities for people describing agents that take actions.
- [ ] Search HN/Reddit/X for "agent permissions", "agent CI access", "AI agent least privilege".
- [ ] Check who starred / opened issues on adjacent OSS (agent sandboxes, policy engines).
- [ ] For each: confirm they run an agent that takes real actions before adding them.

> Do not add someone you can't personalize a first line for. A 20-name list you
> can each write one specific sentence to beats a 200-name blast.

## Tracker

Fill one row per real prospect. Keep it in this file, a sheet, or issues —
whatever you'll actually update.

| # | Name / handle | Segment | Source (link) | Personalization hook | Channel | Status | Notes / issue links |
|---|---------------|---------|---------------|----------------------|---------|--------|---------------------|
| 1 |  |  |  |  | email/DM | not-contacted |  |
| 2 |  |  |  |  |  | not-contacted |  |
| 3 |  |  |  |  |  | not-contacted |  |
| 4 |  |  |  |  |  | not-contacted |  |
| 5 |  |  |  |  |  | not-contacted |  |
| 6 |  |  |  |  |  | not-contacted |  |
| 7 |  |  |  |  |  | not-contacted |  |
| 8 |  |  |  |  |  | not-contacted |  |
| 9 |  |  |  |  |  | not-contacted |  |
| 10 |  |  |  |  |  | not-contacted |  |
| 11 |  |  |  |  |  | not-contacted |  |
| 12 |  |  |  |  |  | not-contacted |  |
| 13 |  |  |  |  |  | not-contacted |  |
| 14 |  |  |  |  |  | not-contacted |  |
| 15 |  |  |  |  |  | not-contacted |  |
| 16 |  |  |  |  |  | not-contacted |  |
| 17 |  |  |  |  |  | not-contacted |  |
| 18 |  |  |  |  |  | not-contacted |  |
| 19 |  |  |  |  |  | not-contacted |  |
| 20 |  |  |  |  |  | not-contacted |  |

**Status values:** `not-contacted` → `contacted` → `replied` → `scheduled` →
`onboarded` → `done` (or `declined`).

## Weekly target

- Source 20, personalize and send to all 20.
- Aim for 3–5 replies, 1–3 live onboarding sessions (that's Day 11).
- Every onboarding produces issues tagged `external-feedback`.
