Yes — give incomplete rows their own needs more information bucket. Missing budget shouldn’t auto-mean low intent; score only when the required fields are present.

(Diagram: follow-up / needs-info / mismatch — incomplete stays in needs-info.)

(Local demo: CRM / leads scenario session)

(Local demo: completed task session)
Suggested steps
- Define “complete”
e.g. need description, timing, contact; treat budget as required only if your process depends on it.
- Three outputs in the Skill
- Follow up first: fit + complete;
- Needs more information: missing required fields or one-line needs — include questions to ask;
- Mismatch / hold: explicit rules, separate from needs-info.
- Score only the complete set
Needs-info lists gaps; it doesn’t get a “low score” stigma.
- Work the needs-info list on a cadence
After answers arrive, re-run or move manually into follow-up.
How to confirm
- A clear-need row with no budget lands in needs-info, not low priority.
- Each needs-info row carries concrete questions.
- Mismatch rows cite which rule fired.
Boundaries
- Needs-info isn’t a junk drawer — schedule revisits.
- Write rules into the Skill so the Agent doesn’t invent intent.
- Qualification assists prioritization; it doesn’t replace your compliance process.