segmentationlisted

# Segmentation One message for the whole list wastes a good list. This stage splits the list by **why they would buy**, so stages 13–16 write to a use case instead of an industry. ## Pipeline contract **Stage 12 of 20.** Reads `11-prioritized.csv`, `01-customer-patterns.md`. Writes `12-segments.md` (definitions) and `12-segmented.csv` (adds `segment`, `segment_confidence`, `segment_reason`). Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). ## Steps 1. **Propose 2–5 segments from the customers, not from the list.** Each best customer bought for a reason; group those reasons. A segment is a use case + the trigger that makes it urgent ("replacing spreadsheets after a funding round"), not a firmographic bucket ("fintech, 50–200"). 2. **Write `12-segments.md`**: for each segment a short label, a one-paragraph definition, which customer(s) it came from, what qualifies, what looks close but belongs elsewhere. Add a `partner` label if vendors or agencies that serve your buyers are in the list — stage 15 treats them differently. 3. **Human approves the segments.** They drive all copy downstream. 4. **Classify accounts, not people** — dedupe to unique `account_domain`, classify once, join back to leads. ```bash npx tsx engine/list-builder/scripts/classify-batch.ts --csv=<accounts.csv> \ --prompt-file=<run>/12-segments-prompt.txt --labels=<label1,label2,...> \ --out=<run>/12-classified.csv --scrape ```