Product fit
Can your product solve the problem as described, for this audience, today?
Conversation examplesIllustrative conversation examples
Productivity conversation examples for customer discovery
Learn to qualify productivity recommendation requests, complaints, and buying-intent clues. These are illustrative scenarios, not current leads.
Use these examples to practice deciding whether a conversation deserves a reply, research, or no action. Pay attention to coordination overhead and repeated manual work. Verify the original context when applying this method to a real post.
Decision context
Check constraints, alternatives, and whether the question remains unresolved.
Permission to participate
Read the community rules and thread tone before making a product recommendation.
Evidence limits
The cards illustrate language patterns. They do not establish demand volume, customer outcomes, or a live opportunity.
Worked scenarios
Productivity examples to review
Each card shows a hypothetical situation and a possible next step. Scores and phrasing should never replace reading the original conversation.
Recommendation requestRedditr/projectmanagement
What are you using instead of an overbuilt PM suite for a six-person team?
The buyer wants a simpler tool and frames the problem around team size and operating burden.
Why this matters
Small-team constraints plus tool replacement language make this highly actionable demand.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
project managementalternativessmall team
Competitor complaintXOps thread
We adopted a productivity tool and now spend more time maintaining it than shipping
A public complaint exposes the gap between promised organization and real process overhead.
Why this matters
This kind of complaint often precedes an active switch because the cost is felt daily.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
maintenanceoverheadswitching
Founder pain pointRedditr/startups
Our handoff process breaks every week because tools and notes live everywhere
The team has not necessarily named a product category yet, but the coordination pain is obvious.
Why this matters
Pain-first threads help ReplyRadar surface demand earlier than recommendation-only monitoring would.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
handoffscoordinationops pain
Buying intent discussionXFounder planning thread
We need to pick our next workflow tool before the next sprint cycle starts
The buyer has a deadline, a job-to-be-done, and a narrow evaluation window.
Why this matters
The conversation is close to adoption because there is a real operational event driving the choice.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
deadlineworkflowevaluation
Qualify the context
Check the problem before drafting a reply
For this topic, start with coordination overhead and repeated manual work. A phrase such as “looking for” is a reason to inspect the thread, not proof that someone will buy.
Reply
The problem fits, the question is active, and you can offer a helpful answer within the community rules. Disclose your affiliation when mentioning your product.
Research
The language or objection is useful, but a reply is not appropriate. Save the source and what it actually supports.
Skip
The need is outside your product’s capabilities, the question has closed, or participation would be unwelcome.
Use the workflow
Apply the method to posts you browse
ReplyRadar uses your product profile to help qualify visible posts in the Chrome extension or text submitted through the dashboard. You review and post replies yourself.
Start with a narrow search
Combine your product category with one problem or recommendation phrase. Inspect the results before adding more terms.
Preserve the source
Keep the post URL and date with any useful note. Return to the original thread before following up or citing it in content.
Review saved activity
Eligible daily digests summarize captured opportunities from the previous UTC day; they do not search networks while you are away.
Explore related examples
Continue with a related topic
Compare a related scenario or use a practical guide to plan your next search and decide whether a reply would help.
FAQ
Common questions about public opportunity pages
Are these live leads?
No. These are illustrative conversation patterns for practicing qualification. Search the source platform and inspect current posts before deciding to act.
Does a complaint mean someone wants to switch?
No. Look for explicit replacement language, constraints, and an unresolved decision. A complaint alone may be useful only as research.
Try a starting search
Build a search plan for your own product
The free planner reads your website and suggests Reddit search phrases. Test the suggestions against actual results.