lead-prioritizationlisted

# Lead Prioritization ## Pipeline contract **Stage 11 of 20.** Reads `10-scored.csv`, `09-signals.csv`. Writes `11-prioritized.csv` (adds `intent_score`, `engagement_score`, `priority_score`, `tier`), sorted best first. - Engagement for a cold list = audience evidence: `source_type` (engager > follower > member/attendee > search) and `source_count`. - Keep the three component scores next to `priority_score` so anyone can see why a lead ranks where it does. - Rows with `screen=fail` are carried through unranked, not deleted. - Cap the outreach set here (default: top 500, or fewer if fewer qualify — never pad). - On a net-new cold list engagement is 0 and intent is thin, so the absolute tiers below bunch at the bottom. The ORDER is still valid: work from the top. Say this in the stage report; if the human wants cold-run thresholds, propose them, do not edit the tables. Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). Standalone use: ignore this block. ## When to Use - Processing a new lead list and need to decide who to contact first - Building a priority queue for SDR teams to work through daily - Designing lead scoring models for CRM or marketing automation - Optimizing campaign ROI by focusing outreach on highest-probability prospects ## Framework ### Why Prioritization Matters Without prioritization, your team works leads in the order they were imported — alphabetically, randomly, or whoever the SDR happens t