Lead Qualification Categories for AI Scoring
Qualified, Nurture, Unqualified — a three-label pipeline gate with numeric confidence and a Strict Other for the leads that fit nothing.
Overview
Lead qualification is a classification problem wearing a scoring costume: the decision is which pipeline lane, not which number. This setup classifies leads into three lanes whose definitions encode the criteria — Qualified requires budget, authority, need, and timeline signals; Nurture is genuine interest without readiness; Unqualified is no realistic path — under Strict ambiguity with a 0–100 confidence score. The score bands are defined in the prompt (90+ unambiguous, 60–89 good fit, below 60 best available), so downstream automation can threshold them meaningfully.
Workflow
-
Extract first, classify second
Run the lead text through extraction for the fields, then through this for the lane — two prompts, two clean jobs.
-
Encode your criteria in the definitions
The Qualified definition IS your qualification bar — tighten or loosen the signals there, not in extra rules.
-
Threshold the score, don't average it
Confidence is self-reported per lead: great for routing thresholds, meaningless as a portfolio average.
Why This Works
- Three exclusive lanes with criteria-bearing definitions beat a 0–100 "score" nobody can audit
- Strict mode keeps junk leads from inflating the Qualified lane
- Defined score bands make the confidence number actionable instead of decorative
Best for
- Sales ops feeding a pipeline from inbound forms and emails
- Teams whose reps disagree about what "qualified" means
- Automations that act differently above and below a confidence bar
Not for
- Extracting the lead's details (name, company, team size) — extraction runs first, this runs second
- Predicting deal size or close probability — that's modeling, not labeling
Use cases
- Gating CRM entries into sales-ready and nurture lanes
- Applying BANT-style criteria consistently across hundreds of leads
- Thresholding numeric confidence for automation rules