How to Use Reddit for Competitor Research: Method and Limits

Reddit is a collection of self-governing communities in which people ask strangers questions they cannot ask a vendor, and other people answer from experience. For competitive work that produces three things that are genuinely hard to buy: the words buyers use for the problem before any marketing reached them, the shortlist they build in private, and the specific reasons somebody left a product. All of it is written by people with no relationship to you and no idea you are reading.

Scale is not the constraint. Reddit’s annual report for 2025 describes more than two billion posts and more than 22 billion comments through 31 December 2025, across more than 100,000 active communities, with an average of 121.4 million daily active uniques in the final quarter of the year. The constraints are that nothing is verified, that the population who post is nothing like the population who buy, and that a great deal of what you want is in communities whose rules forbid naming vendors at all.

1. 1Find the subreddits where your buyers are, not the ones named after your category. A community named after a software category is usually thin and full of vendors. The useful ones are named after a job. Search a competitor's name, see which communities the results cluster in, and build your list from that rather than from what sounds relevant.
2. 2Search from outside Reddit before searching inside it. A general web search restricted to the site returns better results for a competitor's name than Reddit's own search does, because it ranks whole threads by how much the wider web engaged with them. Use Reddit's own search afterwards, with its community and author filters, to work a specific corner you have already located.
3. 3Read the rules and the pinned posts before reading the threads. Many communities ban vendor names, self-promotion or recommendation requests outright, and moderation is done by volunteers who set their own policy. Absence of discussion about a competitor is often a rule rather than an opinion, and knowing which it is stops you reporting silence as a signal.
4. 4Sort by top over a fixed window rather than by new. Sorting by top for the last year gives you what the community itself weighted, which is the whole reason this source is different. Fix the window and keep it fixed, because a comparison between a twelve-month sort and a three-month sort is a comparison between two different populations.
5. 5Read the comments rather than the post. The post is a question. The answers are the data, and the disagreements underneath them are the best part, because that is where somebody with direct experience corrects a confident generalisation. A highly upvoted reply that contradicts the accepted answer is often the most useful sentence in the thread.
6. 6Check who is speaking before you quote them. Open the commenter's public history and look for whether they work in the field, whether they have described using the product elsewhere, and whether they only ever post about one vendor. Two minutes here separates a practitioner's account from an enthusiast, a disgruntled former employee or somebody doing marketing badly.
7. 7Save the permalink, the date, the score and the community for anything you keep. Comments get edited and deleted, accounts get removed, and a thread you cite in a battlecard may not exist in six months. Record the four fields and take a copy of the text at the moment you find it, so the claim survives the source disappearing.

Every source of customer opinion has a ranking problem. Reviews are ordered by the platform’s formula, survey results by whoever wrote the questions, support tickets by whoever escalated loudest. Reddit hands that job to the audience, and it does so in a way worth understanding precisely, because it is the reason this source behaves unlike the others.

Read commercially, that mechanism produces something no review platform does. When a person writes that a competitor’s onboarding takes four months and three hundred other people push that comment to the top, several hundred readers with no stake in the outcome have silently agreed that the complaint matches their experience. That is a crude but real weighting of whether an objection is representative, and you cannot obtain it from a review corpus, where nobody votes on whether a review is typical.

Now the limit, and it needs stating as plainly as the strength. The same filing describes bad actors automating one account or many to mimic authentic activity including posting, commenting and voting, notes that this has become harder to detect because language models are available to them, and describes continuing investment in technology to detect content and vote manipulation. So a score measures how much a claim resonated with an unverified audience. It does not measure how many customers are affected, how large the product’s user base is, or whether the underlying claim is true. Three uses of a score are defensible: comparing two claims inside the same thread, comparing the same complaint across several communities, and watching whether a theme rises over successive quarters. Everything beyond that is arithmetic on a number that was never counting anything.

This is the newest reason to read Reddit and the one most competitive teams have not caught up with. Reddit describes its corpus in its annual report as one of the internet’s largest bodies of authentic, constantly updated human conversation, names content licensing as a revenue strategy alongside advertising, and states that it is often cited as one of the most sourced domains in AI across models. It is the company’s own characterisation of its product, so treat the emphasis accordingly, but the direction is not seriously disputed by anybody.

The consequence for you is concrete. When a buyer asks an assistant which tool they should use for your category, part of what shapes that answer is a set of threads written by strangers, weighted by an anonymous vote, in communities you may never have opened. Reading those threads is therefore two exercises at once. It is competitor research, and it is a preview of the answer your next prospect will be given before they ever reach your website.

Practically, that changes what to record. Alongside the objections and the vocabulary, note which competitors get named in the recommendation threads that rank, whether you appear at all, and what the top reply says about you when you do. If your product is absent from the threads that answer your category’s central question, that absence is a finding about your discoverability rather than a gap in your research, and it belongs in front of whoever owns marketing.

Most people start by searching for their category and land in a small community full of other vendors. The conversation you want is usually in a much larger community named after a job rather than after a piece of software, because that is where the people who use the product spend their time. Work backwards from where a competitor’s name actually appears.

Before adding a community to your list, check three things: how many members it has, whether anything was posted this month, and what the rules say. A dormant community wastes a pass, and a community that bans vendor names will show you nothing about competitors no matter how large it is. Both facts take ten seconds to establish and save you from concluding that nobody discusses your category.

1. Category and product subreddits

The communities named after your software category. Smaller than you expect and frequently populated by people who sell rather than buy, which does not make them useless: a vendor-heavy community is a good place to see how rivals position themselves when they think no customer is watching. Read them for competitive framing, and go elsewhere for buyer reality.

2. Role and profession subreddits

The single highest-value surface here, and the one people skip. Communities named after a job title are large, active and full of the people who actually operate the software all day. The complaints there are specific, operational and describe the product in use rather than the product in a demo, which is exactly the material that is missing from every marketing page on both sides of a comparison.

3. Company-named subreddits

Many vendors have a community named after them, and the important thing to establish first is who runs it. An officially moderated one is a support channel and will read like one, with the worst material removed. An unofficial one is the opposite and often contains the outage history, the billing disputes and the cancellation threads. Check the moderator list and the sidebar before you weight anything you find.

4. Recommendation threads

Somebody asks what everyone is using for a job, and thirty people answer. This is the closest thing to watching a buying committee that exists in public, and it is worth reading in a specific order: which products are named first, which are named repeatedly, which get contradicted underneath, and what the objection is when somebody argues against a recommendation. That last one is the most useful sentence in the thread, because it is the objection stated by a peer rather than by a seller.

5. Switching and migration threads

A person explaining why they left a product and what they moved to, unprompted and with no incentive. In a discipline where voice of customer evidence usually has to be gathered deliberately, this is the same material arriving free. Read for the trigger rather than the destination: the reason a renewal failed is more transferable than the product they chose next, and it tells you what to put in front of that competitor’s customers.

6. Pricing and contract threads

Unverifiable, occasionally precise and always worth reading. People state renewal increases, seat minimums and what a rival offered them to stay, none of which appears in any published price list. Treat every figure as an unconfirmed claim by an anonymous person, record the company size where they mention it, and never build a position on one number. Several consistent numbers from different communities is a different matter.

7. Outage, bug and complaint threads

The fastest failure detector available. A community frequently notices a competitor’s incident before the status page acknowledges it, and it always describes the impact in more detail than the status page will. The commercially useful part is not the incident but the replies underneath it, which reveal how many people are affected in the same way and whether this is the first time.

8. Vendor participation: official accounts and AMAs

When a competitor answers questions in public without controlling which ones get asked, read every word. Nothing else in this cluster gives you a rival responding to hostile, specific, unscreened questions on the record. Watch particularly for what they decline to answer and how they decline it, because a carefully deflected question about pricing or a missing capability is a competitor telling you where the soft ground is.

9. Vote scores and comment counts

Covered in full above. Use them to rank claims against each other inside a fixed context, never to estimate how many people are affected. A high comment count with a low score is its own signal, and usually means the thread is an argument rather than a consensus, which can be more informative than agreement.

10. Subreddit rules, wiki and pinned posts

Read before anything else in a new community. The rules tell you what the corpus structurally cannot contain, the wiki frequently contains a maintained comparison of the tools in the field written by practitioners, and the pinned posts show what the moderators consider settled. A community wiki listing recommended tools is a curated competitive landscape that somebody else maintains for free, and it is one of the most under-used artefacts on the platform.

11. A commenter’s public history

One click, and it changes how you weight everything they said. Look for whether they post about the field consistently, whether they have described their own role or deployment elsewhere, and whether their entire history concerns one vendor in one direction. A strong claim from somebody with a long, varied, credible history is worth quoting. The same claim from an account that has only ever criticised one company is not evidence, it is a hypothesis about who owns the account.

• Reading is free and needs no account. Every public community, thread and comment is readable without signing in, which is also how search engines reach them. An account adds subscriptions, saved posts and the ability to view communities that have restricted themselves.
• The site’s own search is the weakest part of it. Relevance ranking on long threads is poor and date handling is coarse. Locate material with a general web search restricted to the site, then use the platform’s community and author filters to work the area you found.
• Commercial reuse of the content requires an agreement. Reddit’s published public content policy permits non-commercial and academic use of public content and requires an arrangement with Reddit to use it in a commercial product. Reading threads and taking notes is not what that policy is aimed at, and it is all this method needs.
• Nothing you find is guaranteed to persist. Users delete and edit comments freely, accounts are removed, and communities are archived or set to private by their volunteer moderators. Copy the text of anything you intend to cite at the moment you find it, along with its address and date.
• Your own visibility depends on somebody else’s search product. Reddit names changes in search engines’ methodologies as a business risk in its annual report, and notes that visitors arriving from search are generally not logged in. A shift there can change what surfaces for your category without a single thread changing.

The exposure on this source is not about access, since the content is public and indexed. It is about participation and about attribution, and both are places where competitive teams get themselves into genuine trouble rather than theoretical trouble.

• Do not post about your own company without saying so. Recommending your product from an account that does not disclose the connection breaches most communities’ rules and, where it is presented as an independent endorsement, sits under the same consumer-protection rules that cover undisclosed advertising. It also poisons the source for your own researchers.
• Do not contact people to extract more. Messaging a commenter to ask about their employer’s vendor contract, without saying who you are and who you work for, is exactly the practice this field’s ethics rules exist to forbid. If you do reach out, lead with your name and your company, and accept a refusal.
• Do not try to identify a pseudonymous account. People post under a handle for reasons that are theirs. Piecing together an identity from somebody’s posting history to work out which company they work for is a privacy problem and, if the resulting note ever surfaces, an embarrassment that outlives whatever it proved.
• Quote a person, not the platform. The comment is its author’s. Quote briefly, link the original and attribute it as one person’s statement on a date. Writing that Reddit says a competitor is unreliable converts an anecdote into a claim about a business, and that is the version that gets you a letter.
• Commercial reuse is contractual territory. Building a product or a saleable dataset on this content is governed by Reddit’s public content policy and requires an agreement. Reading and taking notes for internal work is not that, and nothing on this page asks you to go near it.

• Anything about enterprise buyers. People running six-figure contracts under a corporate policy do not post about them. The higher your average deal size, the thinner this source gets. Proxy: analyst evaluations, public contract awards and your own win-loss conversations.
• How many people feel this way. There is no denominator anywhere. A thread tells you a view exists and that some readers share it. Proxy: a coded review corpus, where the population and the sample size are at least knowable.
• Whether a complaint is still true. Threads are dated but the product is not, so a top-ranked complaint may describe a version withdrawn a year ago. Proxy: the competitor’s own changelog, and a trial where you test the specific claim.
• Anything from a regulated market. Financial services, healthcare and defence buyers are largely absent for compliance reasons, and whole categories have no active community at all. Proxy: industry associations, conference agendas and specialist trade press.
• Who the person actually is. Role, employer, tenure and whether they ever used the product are all unverified and unverifiable. Proxy: a named reviewer on a platform that verifies identity, where the firmographic fields come attached.

Fortnightly, spend twenty minutes on a fixed list of five or six communities you have already validated, sorted by top over the last month, reading only what is new. Keep a running note per competitor with three columns: the objection, the community it appeared in, and the date. The value compounds because the same objection appearing in a third community six weeks later is a pattern, and you will only see that if the first two were written down.

Reopen properly on four triggers: a competitor’s price change, a major release, an outage, and any acquisition. Each of those produces a burst of unusually candid threads within days and almost nothing a month later, which is the awkward part of this source. Feed what you find into the objection handling work rather than leaving it in a document, since a customer’s own words are the reason to collect them.

The specific decay here is unusual, and it runs in two directions at once. A thread that will matter to you is at its most visible for about forty-eight hours and then falls off every feed in the community, so if nobody was reading that week it is effectively invisible even though it is still there. At the same time the evidence itself is perishable: comments get edited, accounts get deleted, and a community can be set to private by a volunteer moderator with no notice. Miss the window and you lose both the signal and the ability to prove it later.

A person cannot read six communities every day, which is why continuous coverage of public customer conversation is a job for competitive intelligence software rather than for discipline. Flares keeps watch on what buyers say about rivals in public and separates a criticism that has just appeared from one that has been there for two years, which is the distinction a weekly manual sweep is worst at making. What no tool can do is judge the speaker. Deciding whether an anonymous account is a practitioner, an enthusiast or a competitor with a grievance takes a person reading their history, and that judgement is where this source is either useful or dangerous.