lead-qualificationlisted

# Lead Qualification A positive reply is not a qualified lead. This stage spends a few minutes per replier so the calendar fills with the right meetings, and so the wrong ones get a useful answer instead of a call. ## Pipeline contract **Stage 18 of 20.** Reads `17-replies.csv` (rows with `is_positive=true`), `10-scored.csv`, `09-signals.csv`, `02-client-profile.yaml`. Writes `18-qualified.csv` (adds `decision`, `decision_reason`, `open_questions`, `suggested_reply`). Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). ## Four checks | Check | Question | Evidence | |---|---|---| | **Person** | Can they buy, champion, or introduce? | title vs the profile's `job_titles`; what they said about their role | | **Account** | Does the company still pass the hard filters? | `screen` and `fit_components` from stage 10 — re-verify anything that was blank | | **Timing** | Is there a reason to act now? | dated signals from stage 9; timing words in the reply ("next quarter", "evaluating now") | | **Reply** | What did they actually ask for? | the reply text and its stage 17 label | Record what is known and what is not. An unknown is an open question for the call, not a fail. ## Decision - **go** — person and account pass, nothing in the reply contradicts fit. Book it. Hand to [`/account-notes`](../account-notes/SKILL.md). - **nurture** — fit is real but timing is not ("reach out in Q3"). Log the re-engage date and the trigger th