How to get product feedback from Reddit
The export still mangles my formatting, so I moved to Obsidian. That user never filed a ticket — they told three thousand strangers exactly why they churned.
Why Reddit feedback is different from everything else you collect
Most teams already have feedback inputs: support tickets, NPS, post-cancellation surveys, sales-call notes, a feature board nobody checks. They share one blind spot — the person has to choose to talk to you, and that filter quietly removes your most honest critics. Tickets skew to people who hit a blocker and still care; the user who quietly gave up never files one. Surveys reward the agreeable. NPS gives you a number with almost no “why.”
Reddit inverts all of that. People post there to talk to peers, not to you, so the feedback is unsolicited, often brutally honest, and public — you can read both your users and your competitors’ users without anyone moderating their words for your benefit. Someone comparing your tool to a rival in r/SaaS is not being diplomatic; they’re helping a stranger pick, and that motive produces the cleanest signal anywhere. The cost is that Reddit feedback is loud and not statistically representative, which I’ll be straight about below.
The core idea: the feedback already exists
Here is the mental shift. You are not creating feedback by going to Reddit — you are discovering feedback that already exists. Right now your product is being discussed somewhere you’re not looking: your category’s subreddit, a “what’s the best X for Y” thread that names you in passing, a competitor’s sub where someone explains why they switched.
That reframing changes the question from “how do I get people to give me feedback” (a marketing problem) to “how do I find the feedback that’s already out there and structure it” (a search-and-organization problem, and far more tractable).
The kinds of feedback Reddit actually yields
When you read systematically, the mess resolves into recognizable types, each feeding a different decision:
- Feature requests — the “I’d use this if it could…” comments, the closest thing to a free backlog, though the same ask hides behind ten different sentences
- Bug reports and complaints — especially the bugs nobody reported to you; a “yeah this happens to me too” reply is a reproduction case you’d never see
- Sentiment and love — what people would defend tells you what not to break
- Comparisons — “I switched from Asana to Linear because the keyboard shortcuts actually work” is competitive analysis done for you
- Churn reasons — the specific thing that made someone leave, caught weeks later when they’re venting to peers
- Workarounds — a Zapier hack or spreadsheet built around your gap is a feature request with a working prototype attached
A repeatable loop for mining product feedback
- 1
Find where your product is discussed
Three buckets: your brand and product name (plus misspellings), your competitors’ names (their churned users map onto your roadmap), and your category subreddits. Cast a wider net than feels comfortable — the candid stuff is often three comments deep in a thread that never names you in the title.
- 2
Collect the mentions
Pull the threads and comment trees into one place you can read end to end. Manual works for a one-time audit; the downside is deep comment trees, buried gold, and Reddit’s weak search. This is roughly where a tool starts to earn its keep.
- 3
Categorize by type
Sort into feature request, bug, sentiment, comparison, churn, workaround. The same request worded ten ways must collapse into one line with a count, or you badly underweight your most common ask. Consistent labeling across hundreds of messy comments is exactly where an LLM helps.
- 4
Prioritize by frequency and intensity
Two axes, both needed. Frequency is how many distinct people raised it; intensity is how strongly each felt (“would be nice” vs “this is why I cancelled”). A request mentioned twice but tied to churn can outrank one mentioned eight times as a mild nice-to-have.
- 5
Close the loop
Act on it internally; optionally reply externally. Shipping the fix and returning to the thread to say “we shipped this, thanks for the nudge” turns a critic into a public advocate. Disclose that you work on the product, and never astroturf — Reddit’s immune system is ruthless.
An honest note on representativeness
Reddit feedback is not a representative sample of your users, and you’ll hurt yourself treating it like one. Posters self-select toward strong feelings, skew technical, and skew toward people who enjoy arguing about tools online. A feature that lights up r/SaaS may be irrelevant to the silent majority who never visit Reddit.
So use it for what it’s good at: qualitative depth, the “why” behind a number you already saw in analytics. Then triangulate. If churn is up and Reddit keeps naming a missing integration, act. If Reddit is screaming about something your analytics and tickets show no trace of, treat it as a hypothesis to validate. Quantitative metrics tell you how big a problem is; Reddit tells you what the problem actually is. You want both.
One-off audit, then continuous monitoring
Most teams start with a one-time audit to build a baseline from the back catalogue, then keep a lightweight monitor running so the signal never goes stale. The audit is the highest-leverage way to start.
Set up continuous monitoringFrequently asked questions
Is Reddit good for product feedback?
Yes, with a clear caveat. Reddit is excellent for qualitative, unsolicited, brutally honest feedback about an existing product, including from people who would never tell you directly. The catch is that it is not a representative sample, so it skews toward strong opinions and technical, vocal users. Use it for depth and the “why,” then triangulate against your analytics and support data.
How is Reddit feedback different from a survey?
A survey only captures people who chose to answer, which quietly removes your most honest critics and the users who already left, and it constrains answers to the questions you thought to ask. Reddit feedback is unsolicited and unprompted, so people raise problems and praise you never would have asked about, often with specific detail. It is messier but surfaces things surveys structurally cannot.
How do I find feedback about my product on Reddit?
Search three buckets: your own brand and product names plus common misspellings, your competitors’ names, and your category’s subreddits. The best feedback is often buried in replies rather than thread titles, so read comment trees, not just headlines. Cast a wider net than feels natural, since people rarely tag your product cleanly.
Is Reddit feedback representative?
No, and you should not treat it as such. Posters self-select toward strong feelings and skew technical and vocal, so a feature that dominates a subreddit may not matter to your quiet majority. Reddit tells you what a problem is and why it hurts; your metrics tell you how big it is. Use them together, and treat a loud Reddit signal with no analytics support as a hypothesis.
Do I need a tool to do this?
Not for a small, one-time audit — you can search, open threads, and copy quotes into a doc by hand, and doing it manually once is useful for learning the texture of the data. The manual approach breaks down at scale because Reddit’s search is weak, good comments hide deep in reply trees, and consistent categorization is tedious. A tool helps by pulling threads and auto-classifying feedback by type.
How often should I check Reddit for feedback?
For a baseline, run a one-time audit across the last year, then revisit before each planning cycle. For catching problems early, like a bad release or a competitor’s churned users, set up continuous monitoring so new mentions reach you within days. Most teams do the audit first to build context, then keep a lightweight monitor running so the signal stays fresh.
Keep reading
Find the pain points your customers never put in a ticket
Surface the frustrations customers vent everywhere except your inbox.
Read →See what people really say about your competitors
Track how buyers really compare tools and why they switch.
Read →How to find feature requests on Reddit
The phrases that signal a feature request, where they hide, and how to tell real demand from a one-off — including the gold in “switched away because.”
Read →How to monitor Reddit for product feedback
Catch mentions of your product as they happen — what to watch, which free alerts to use, and how to route mentions into action without drowning.
Read →Reddit product sentiment analysis
How to measure how Reddit feels about your product without fooling yourself — the three approaches, why sarcasm breaks naive scoring, and what to actually track.
Read →How to find bug reports and complaints on Reddit
The bugs that hurt most are the ones nobody filed a ticket for. How to find them, read their severity, and turn a vague rant into a reproducible ticket.
Read →How to build a product roadmap from Reddit feedback
The loudest request is almost never the most important. How to score Reddit feedback into a ranked roadmap that ships what actually moves the number.
Read →How to get launch feedback on Reddit
Stop waiting for feedback and ask for it. Where to post for honest critique, how to frame the ask, and how to take the roasting without arguing back.
Read →