Product fit
Can your product solve the problem as described, for this audience, today?
Conversation examplesIllustrative conversation examples
SaaS conversation examples for customer discovery
Learn to qualify saas 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 setup effort, team fit, and replacement timing. 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
SaaS 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/SaaS
Need a simple tool for tracking recommendation requests without a giant team dashboard
A founder wants a founder-scale workflow and explicitly rejects enterprise-style software.
Why this matters
The buyer is naming product constraints and asking for alternatives, which is excellent fit language.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
founder-led growthmonitoringsaas ops
Competitor complaintXGrowth operator thread
Our current onboarding analytics tool still does not explain activation drop-off
The team is frustrated that more reporting has not produced clearer answers.
Why this matters
The complaint is attached to a concrete job-to-be-done, which makes category messaging easier.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
analyticsactivationcomplaint
Founder pain pointRedditr/startups
We keep adding tools but our support handoff is still messy
A support workflow problem appears before the founder has picked a replacement category yet.
Why this matters
This is valuable because it reveals early-stage demand before it hardens into product-comparison language.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
supportopsworkflow pain
Buying intent discussionXSaaS founder thread
Shortlisting tools we can test before the next pricing push
The buyer is actively narrowing options around an upcoming go-to-market milestone.
Why this matters
Decision-stage timing and shortlist language indicate a higher-value conversation than generic category chatter.
ReplyRadar angle
Check whether your product solves the stated problem. Review the full thread and community rules before drafting a reply.
shortlisttimingevaluation
Qualify the context
Check the problem before drafting a reply
For this topic, start with setup effort, team fit, and replacement timing. 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.
SaaS analytics conversation examples for customer discovery
Learn to qualify saas analytics recommendation requests, complaints, and buying-intent clues. These are illustrative scenarios, not current leads.
Find customers on Reddit
Follow a practical search, qualification, and reply workflow.
Qualify a recommendation request
Work through fit, timing, context, and participation rules.
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.