Part of High-intent leads
Compare observable evidence
| Dimension | Higher intent | Lower intent |
|---|---|---|
| Need | Specific current problem | Broad topic interest |
| Decision | Provider or solution evaluation | Learning or exploring |
| Timing | Supported project window | Unknown or distant |
| Next step | Scope or feasibility discussion | Education or clarification |
| Risk | Assuming urgency means fit | Discarding a good future-fit buyer |
A label should be supported by evidence and reviewed when context changes. Low intent is not a criticism of the person; it describes the current commercial interpretation.
Keep fit separate
A scoped hiring request for an unsupported platform is high intent but poor fit. A relevant company reading a basic guide may be good fit but low intent. These observations need different actions.
Use a two-axis matrix: fit and readiness. Reject poor fit; educate good-fit early interest; qualify good-fit active requests. Do not collapse the matrix into a single “hot” label.
Match the ask to readiness
A broad research question usually needs criteria or an explanation. A detailed project request may justify a feasibility discussion. An unclear problem needs a diagnostic question.
Asking every reader for a sales call can turn useful interest into friction. Let the next step earn its size from the evidence.
Review classification quality
Record why a signal was classified and whether later context supported it. A closed project or academic inquiry is a false positive for an active-sales queue.
Refine categories using your own qualification outcomes. Avoid claiming a universal conversion advantage without reliable, comparable data.