← Back to blog
·11 min read
Written by:
CL
Casey Lin
Verified by:
JR
Jordan Reyes

How to Find Feature Requests on Reddit

Find feature requests on Reddit for your product or a rival with exact search strings, a tagging scheme and an honest way to count duplicates.

Share:

Key Takeaways

  • Feature requests hide in competitor subreddits, support threads, "alternative to" posts and reactions to changelogs, not just in posts titled as requests.
  • Tag each request by type, such as missing capability, workaround or switching trigger, so a roadmap list reflects need and not volume.
  • Count duplicates by separate threads and people, and keep a threshold in writing so one loud commenter cannot inflate a request.
  • A request describes a symptom, so record the underlying job the person is trying to do before deciding what to build.
  • Reply to requests only when you add real help, disclose your affiliation and follow each community rule to avoid looking like spam.

Quick answer: To find feature requests on Reddit, search your own and your rivals' subreddits for wish and workaround language, read support threads and "alternative to" posts, and check how people react to announcements. Then tag each request, count separate threads honestly and turn the clusters into a roadmap list.

Reddit is a useful place for this because people describe what is missing in plain words, with no survey prompting them. They do it in odd places, though. Most requests are not titled "Feature request." They show up as complaints, workarounds and questions.

This guide covers where to look, the search strings to use, how to tag and count what you find, how to turn it into a roadmap and how to reply without turning into the person everyone mutes. It works whether you are mining requests for your own product or for a rival's. For the wider method, see our Reddit research methods and Reddit market research guide.

Where Feature Requests Hide on Reddit

Look in five places. Each reveals a different kind of request.

PlaceWhat you findStrengthWeakness
Product or competitor subredditDirect requests from usersSpecific, in contextSkews to power users
Support and help threadsRequests phrased as problemsShows real painOften solved by existing features
"Alternative to" postsRequests from people leavingShows buying intentReasons can be mixed
Changelog and announcement reactionsRequests people say were missedTimely, directShort, can be flamewars
"Is there a tool that" threadsNeeds with no clear solutionReveals gapsOften vague

Competitor and Product Subreddits

If your product or a rival has its own subreddit, start there. Sort by Top for the past year to see persistent themes, then by New for fresh requests. Check the pinned post and any wiki, because moderators often collect "known requests" there, and that list shows what the community already knows is missing.

Not every rival has a subreddit. In that case, search the product name inside broader category subreddits. Our guide to researching competitors on Reddit covers finding mentions at scale.

Support and Help Threads

People post "how do I" when a feature does not exist, or exists and cannot be found. Both are useful. A missing feature is a gap. A hidden feature is a discoverability problem, which you can fix without building anything. Treat the two separately when tagging.

The way customers compare support experiences also surfaces unmet needs. Our post on finding support comparisons on Reddit shows how to read those threads.

"Alternative to" Posts

These are gold. Someone who writes "alternative to X that can do Y" has told you the exact capability that made them look elsewhere. They are mid-search, which means the request carries buying intent. Collect both the stated reason for leaving and the feature they ask for.

Changelog and Announcement Reactions

When a rival ships an update, read the replies. People say what they hoped for and did not get. "Great, but still no way to export" is a feature request in a very short sentence. The same goes for pricing change threads, where feature complaints surface as people explain why the new price is not worth it.

"Is There a Tool That..." Threads

These are requests for a product, not a feature, but they show where categories have holes. A question asked repeatedly with no good answer is a gap worth noting. Our market gap analysis framework helps you judge whether a gap is real.

Search Strings That Surface Requests

Reddit supports operators such as subreddit:, title: and selftext:, with uppercase AND, OR and NOT. Search can be inconsistent between the site and the app, so treat these as starting points and read the results.

Wish language:

  • title:("I wish" OR "why can't" OR "would be nice") subreddit:yourcommunity
  • selftext:("feature request" OR "please add" OR "missing feature")

Capability questions:

  • title:("is there a way to" OR "can it" OR "does it support")
  • selftext:("no way to" OR "doesn't support" OR "can't figure out")

Alternative and switching:

  • title:("alternative to" OR "replacement for")
  • selftext:("switched from" OR "left because" OR "cancelled because")

Workaround language:

  • selftext:("I use a spreadsheet" OR "workaround" OR "duct tape")
  • selftext:("I ended up building" OR "wrote a script")

Add the product or category name in quotes to each string. Then run the same strings without the product name, using the customer's task instead, so you see requests that do not name any brand. Our Reddit keyword research guide and how to find pain points on Reddit list more phrase patterns, and how to find product ideas on Reddit shows how to run the same approach from scratch.

Step by Step: Collect, Tag, Count

Follow these steps and keep the notes in one spreadsheet.

  1. Pick the target. Your product, one rival or a category. Do one at a time.
  2. Pick communities. Two or three, including any dedicated subreddit.
  3. Run the search strings from the section above. Save every thread that contains a request, with the link and date.
  4. Open the thread and read the comments. The most specific detail is often in replies.
  5. Record one row per request, not per thread. A thread can hold three.
  6. Tag each row using the scheme below.
  7. Merge duplicates by underlying job, and count honestly.
  8. Rank by evidence, then check against your own customers.

A Tagging Scheme for Requests

Tags make the list sortable. Use a small set so you actually apply it.

TagMeaningExample (hypothetical)
Missing capabilityCannot do X at all"No way to export to CSV"
WorkaroundDoes X by hand"I copy it into a spreadsheet"
Switching triggerLeft because of X"Moved away over lack of teams"
DiscoverabilityFeature exists, not found"Where is the bulk edit?"
Quality gapExists but poor"Sync works, but loses data"
Pricing gateWanted feature locked"Only on the top tier"
IntentLooking to buy now"Need something by Friday"

The examples are invented to show format. Add two more columns: the job the person is trying to do, and a short verbatim quote. The job matters most. "Add a dark mode" is a symptom. "I work at night and the screen hurts" is the job. Different jobs have different solutions, and the job often reveals a simpler fix than the one requested. The jobs-to-be-done framework goes deeper, and write a problem statement from Reddit research shows how to turn a cluster into a testable sentence.

Counting Duplicates Honestly

This is where requests most often get inflated. A few rules keep the tally fair.

  • Count threads, not comments. Twenty replies saying "same" in one thread are one thread.
  • Count people where you can. If one username posts the same request in five threads, that is one person.
  • Merge by job, not by wording. "Export," "download my data" and "get it into Excel" may be one request.
  • Do not count cross-posts twice. The same post in two subreddits is one request.
  • Watch for brigading. A sudden pile of identical comments after a link was shared elsewhere is not organic demand.
  • Record dates. A request from three years ago may have shipped.
  • Write the threshold first. For example, "needs five separate threads from at least two communities before it enters the roadmap list."

Upvotes on a request tell you it resonated, not that anyone would pay for it. Treat them as a hint. Our post on Reddit research mistakes explains why votes mislead, and how to analyze Reddit data covers tallying in more detail.

For SaaS specifically, our write-up on SaaS feature request patterns on Reddit shows what the language of a high-value request tends to look like, and SaaS integration requests covers a common category of request on its own.

Turn Requests Into a Roadmap List

A tally is not a roadmap. Convert it in four moves.

  1. Group requests into clusters by job.
  2. Score each cluster on evidence (separate threads and communities), pain (severity of the workaround) and fit with your product. Our guide on prioritizing pain points offers a scoring method.
  3. Check against your own data: support tickets, interviews, usage. Reddit is one input.
  4. Write the list in plain words with the job, the evidence count and a link.

A simple output table:

Cluster (job)Separate threadsCommunitiesTag mixDecision
Get data out93Missing, workaroundInvestigate
Team sharing62Switching, pricingInterview users
Dark mode41QualityBacklog

These numbers are invented to show format. Yours come from your tally.

If the requests are for a rival, the list becomes a gap map. Which jobs go unserved by that product, and could you serve them better? See what is competitor gap analysis and competitor analysis for startups. To go from a cluster to a launched product, the plan in pain point to product applies.

If you would rather not do the first pass by hand, PainPointMap scans the subreddits you choose, extracts and ranks pain points with quotes and source links, and scores severity and frequency. On the Professional plan it adds competitor mapping and gap analysis. A 3-day free trial is the entry point (card required, billed monthly unless cancelled). Feature requests are one kind of pain point, so open the linked threads and tag them yourself. Other tools are compared in best Reddit research tools.

Replying to Requests Without Spamming

You will be tempted to jump into a thread with "we just built that." Pause. Reddit communities tend to dislike unsolicited promotion, and many subreddits have explicit rules about it.

A safer approach:

  1. Read the rules first. Check the sidebar and pinned posts before posting.
  2. Answer the question. If you can help without mentioning your product, do.
  3. Disclose your affiliation if you mention your own product at all.
  4. Do not reply to every request. Pick threads where you add something.
  5. Never use fake accounts or have friends post praise.
  6. Consider listening only. For rival requests, you may gain more from reading than from replying.
  7. Move the conversation private only when invited, and respect a no.

Our posts on how to promote on Reddit without getting banned and Reddit marketing mistakes go through the details, and how to market on Reddit covers the longer game. If the request reveals a prospect, Reddit lead generation shows ethical ways to follow up.

A Short Example of the Whole Flow

Here is a hypothetical illustration, not a real case. Say you run a small invoicing tool. You search a freelance subreddit for "wish" and "is there a way to" strings, and a rival's subreddit for "alternative to." You save 40 threads, read the comments, and tag 55 requests. After merging by job, you find that "get paid faster" and "see who has viewed my invoice" are really one cluster, supported by threads in two communities. You write the job, the thread count and the links beside it, then interview a few of your own users about it before deciding whether to build. That is the whole loop: collect, tag, merge, check, decide.

Final Thoughts

Feature requests on Reddit are scattered, loosely worded and easy to overcount. A tagging scheme, a written counting rule and a habit of recording the underlying job turn them into something you can plan around. Treat the result as a hypothesis, then confirm it with your own users.

If you want the first pass done for you, start your 3-day free trial of PainPointMap. A card is required, and it is then $19 a month for Starter or $49 a month for Professional unless you cancel. Either way, keep every link and read the threads before you build. More walkthroughs live in the Reddit research guides hub, and niche ideas by platform is a good next stop.

Frequently Asked Questions

Where do people post feature requests on Reddit?

People post them in product subreddits, support and help threads, "is there a tool that" questions, "alternative to" posts and replies to announcements or changelogs. Many requests are not labelled as requests at all, so search for frustration and workaround language, not just the word feature.

How do you search Reddit for feature requests?

Use phrase searches such as "I wish it could", "is there a way to", "does anyone know a tool that" and "alternative to", combined with the product or category name and a subreddit filter. Reddit supports operators like subreddit: and title:, but results can be inconsistent, so read what comes back before you trust it.

How do you count duplicate feature requests fairly?

Count separate threads and, where you can tell, separate people, not comments. Merge requests that describe the same underlying job, even in different words. Write down your counting rule first, and keep the links, so someone else can recheck the tally. Do not count a thread twice because it was cross-posted.

Can I use competitor feature requests for my roadmap?

Yes, as input, not as instructions. A request on a rival subreddit shows an unmet need among that rival users, which may or may not match your customers. Check the request across several threads, understand the job behind it and test it with your own users before building.

Is it okay to reply to feature requests on Reddit?

Only if you add real help and follow the community rules. Disclose your affiliation, answer the question first, and do not drop links by reflex. Many subreddits restrict self-promotion, so read the rules before replying, and consider that listening without posting is often the better choice.

See exactly where competitors are falling short.

PainPointMap surfaces what real users complain about in your competitors' communities — the gaps they're leaving wide open.

Start 3-Day Free Trial
CL
Casey Lin
Research Writer, PainPointMap

Covers competitor analysis, SaaS go-to-market strategy, and how founders use community research to find product-market fit.