Qualification decision before routing
Lead scoring fails when numbers look precise but do not change the next action.
Use one visible scoring rule to classify lead fit, urgency, evidence quality, and next-action readiness, then route the lead with a reason your team can defend.
The scoring leak
Most lead scores are labels, not qualification decisions.
Teams often calculate a score but still debate every lead manually because the score does not show what matters: fit, urgency, evidence quality, and whether the next action is clear.
A useful lead scoring system does not chase perfect prediction. It gives one operational answer now: route this lead to pursue, nurture, enrich, or hold with an evidence-backed reason.
Central action object
Lead scoring rule builder
Paste one lead record and your qualification policy. Return a score breakdown that maps directly to route and next action.
Copy-ready prompt
You are a sales qualification assistant.
Input:
LEAD_RECORD:
[PASTE COMPANY, ROLE, SOURCE, MESSAGE, ACCOUNT STATUS, OWNER, TIMING SIGNALS, AND MISSING FIELDS]
SCORING_POLICY:
[PASTE YOUR FIT RULES, URGENCY RULES, EVIDENCE STANDARDS, AND ROUTING THRESHOLDS]
Task:
Score this lead and recommend one route.
Return this exact output format:
- fit score (0-25)
- urgency score (0-25)
- evidence score (0-25)
- next-action score (0-25)
- total score (0-100)
- route recommendation (pursue, nurture, enrich, hold)
- reason codes
- next action
Ranking criteria:
Prioritize explicit fit, near-term pain, source reliability, data completeness, and action readiness.
Rules:
- do not invent budget, authority, timeline, or intent;
- if evidence is weak, lower evidence score and keep Unknown visible;
- if missing fields block safe action, route to enrich;
- cite the exact lead field or message phrase behind each score;
- keep output short enough for CRM.
QA loop:
List any score claim lacking evidence, then reduce that score or mark Unknown.
Score table
Use 4 scoring dimensions so qualification maps to action.
| Dimension | 0-5 | 6-15 | 16-25 |
|---|---|---|---|
| fit | Wrong segment, irrelevant role, weak offer match. | Partial fit with uncertainty in role, segment, or ownership. | Clear segment and role alignment with explicit need match. |
| urgency | No active problem or timeline signal. | Pain exists but timing unclear or low priority. | Current pain plus a visible trigger or near-term deadline. |
| evidence | Mostly inference, little source-backed proof. | Some explicit proof, some Unknowns still unresolved. | Core claims are explicit with cited fields and source notes. |
| next action | No owner, unclear route, action blocked. | Likely route but owner or step needs confirmation. | Owner, route, and first action are clear today. |
Example lead input
Score one real lead before expanding to batch scoring.
- Company
- Northstar Operations Group
- Role
- VP Operations
- Source
- Inbound operations automation page
- Problem
- Inconsistent handoff and slow urgent lead routing.
- Trigger
- Needs options before next month planning meeting.
- Missing fields
- Budget, CRM platform, account status.
Example output
Lead → score → route recommendation should be visible in one block.
fit score
21/25. Role and workflow match sales operations process improvement.
urgency score
19/25. Current pain plus a planning deadline signal.
evidence score
17/25. Message and source are explicit; budget and account status remain Unknown.
next-action score
20/25. Owner path is clear enough to proceed while collecting missing fields.
total score
77/100
route recommendation
pursue with enrichment attached for missing account context.
Quality boundary
Scores are only trustworthy when evidence and Unknowns stay visible.
Evidence required
Each score line should cite explicit fields, source context, or CRM values.
Unknown stays Unknown
Do not boost urgency, fit, or action readiness using guessed budget or authority.
Route over vanity
The scoring output is successful only when it produces one clear next action.
Review threshold
Low evidence or conflicting ownership should trigger human review before route execution.