Separate four kinds of conversation
A direct request names a job and asks for a tool or provider. A switching question describes a limitation in a current solution. A problem description explains a painful process without asking to buy anything. A general discussion may mention the category without needing help.
These categories are a reading aid, not labels you can assign from one word. “Alternative” can mean a shopping request or an abstract argument. Read enough of the thread to understand which it is.
| Signal | Illustrative question | What to inspect |
|---|---|---|
| Direct request | Any invoicing tool for recurring client work? | Team size, workflow, and required integrations. |
| Switching | Our current tool costs too much for two users. | Actual cost issue and features they must keep. |
| Problem | I spend Friday chasing invoices. | Whether they want help or are sharing a story. |
| Discussion | Why does every app have a subscription? | Context; a product recommendation may be irrelevant. |
Look for constraints, not just frustration
A budget, deadline, existing workflow, or required integration makes a question more specific. It also gives you a reason to rule out your product. A request for offline software is a poor fit for a web-only service even if the category matches perfectly.
A frustrated person is not automatically looking to buy. Sometimes they need a process change or help using what they already have. Suggesting that practical fix can be more useful than offering a new subscription.
Use a score to order your review
Leaddit assigns keyword-matched posts a 0–100 buyer-intent score and an explanation. Higher scores can help you find direct requests sooner; the reason helps you understand why the post was prioritized.
The score is not a conversion probability, a financial forecast, or an independent verification of the author’s situation. Compare it with the full thread and your own product knowledge. If the reason misses an important constraint, follow the evidence in the thread.
Make the next action explicit
For a strong fit, draft one relevant answer. For a possible fit, ask a useful clarifying question. For a research-only conversation, save the language for your keyword work. For an unrelated discussion, move on.
This keeps scoring connected to a real decision. Increasing the threshold alone will not fix vague keywords or a product that does not fit the audience. Review the match, the keyword that found it, and the reason as one unit.
Learn from your own qualification decisions
A simple review log should capture which signals you saw, whether you replied, and whether the exchange continued. Avoid attributing a signup to a thread just because they happened on the same day.
Over time, you may find that a certain problem phrase produces fewer matches but better conversations. Use that evidence to refine your keywords. You do not need to label every post on Reddit; you need enough clarity to choose the next worthwhile answer.