Classify language without overclaiming

Hypothetical phraseInitial interpretationNext question
“Looking to hire a designer”Explicit service requestIs the scope and commercial model compatible?
“Our landing page is not working”Problem-awareWhat does “not working” mean?
“Tool A or Tool B?”Research or evaluationIs there an active implementation decision?
“How do I become a designer?”EducationUsually not a buyer request

These are synthetic examples, not customer cases. Classifications describe evidence strength, not conversion probabilities.

Look for context that changes the category

Read whether the author has a deadline, existing system, defined deliverable or decision to make. Then check whether later replies resolve the issue. A strong-looking title can become irrelevant after one comment.

Do not assume “we” identifies a company or that urgency implies budget. Mark these as unknown until supported. The useful outcome is a more accurate next step, not a more confident label.

Match the response to the signal

Research signals usually justify education or criteria. Problem-aware signals can justify a diagnostic question. Explicit compatible requests may justify a scoped service response when rules permit.

A clear request still needs fit checks. If the buyer wants a volunteer or an unsupported platform, intent strength does not make the opportunity suitable.

Review the taxonomy against outcomes

Compare original classifications with later qualification. Record closed requests, unsuitable scope and misunderstandings. Use those reasons to refine the discovery brief.

Do not optimize only for phrases that sound commercial. Useful context can appear in detailed problem descriptions that never say “hire.” Human review should remain able to challenge the category.