How to Find Competitor Customer Reviews and Feedback

Key takeaways

• Search G2, Capterra, Product Hunt, app stores, Reddit, and support forums using exact query strings like site:reddit.com plus the competitor name, filtered to 1-3 star reviews sorted by most recent.
• Collect 30-50 reviews per competitor and paste each verbatim quote into a spreadsheet with source, URL, product area, and an emotion score from 1 to 5.
• Rank complaint themes by frequency and average emotion intensity; a theme recurring across two or more independent sources is your roadmap and positioning wedge.
• Flip the top themes into positioning claims and test them by replying in the same threads where the complaints appeared.
• Re-run the full pass monthly in a two-hour block, appending only new quotes and logging contradictions to existing themes.

Search review sites, app marketplaces, Reddit, and support forums with exact query strings, then code what you find into complaint themes in a spreadsheet. This playbook shows every search to run and how to turn recurring complaints into positioning and roadmap calls, all manually, with zero paid monitoring tools, in one afternoon.

How to find competitor customer reviews and feedback in one afternoon

Skip the paid monitoring tools. Your workflow: search review sites first, then Reddit, then support forums, then code what you find into recurring complaint themes. G2 and Capterra make competitor reviews publicly browsable and filterable by rating and company size, no account needed to read them (G2's own documentation walks through filtering by star rating and segment).

The end-to-end pass looks like this: pick 3-5 competitors, pull their 1-3 star reviews, screenshot complaints that repeat, then move to Reddit and niche forums where users complain more honestly than they do on review sites. Sort every complaint into a short list of themes.

For the full method, including how to code feedback without software, see our guide to customer feedback analysis and mining competitor reviews.

Which review sites should you search first?

Three platforms hold most of the useful software feedback: G2, Capterra, and Product Hunt. Start with G2 and Capterra because reviewers there answer specific prompts ("what do you dislike?"), which hands you complaint themes pre-sorted. Product Hunt matters less for volume and more for launch-day objections in the comments, which show what skeptics said before buying anything.

Search each one the same way: your competitor's product name, then filter reviews to 1-3 stars first. Sort by most recent so you see current pain, not old bugs they fixed. Screenshot or paste every negative and lukewarm review into one doc. For a deeper walkthrough of that capture step, see https://heycatch.ai/blog/customer-feedback-analysis-a-competitor-review-guide.

App marketplaces and extension stores

If your competitor ships a Chrome extension, Slack app, or mobile app, those stores often have more honest reviews than G2, because nobody there is being courted by a sales team. Check the Chrome Web Store, Shopify App Store, and the Apple App Store.

Aim for 30-50 reviews total before moving to Reddit.

How do you mine Reddit and forums for competitor complaints?

Review sites give you curated ratings. Reddit gives you the unfiltered version: what people say when no vendor is listening.

Site: searches and Google operators

The site: operator restricts results to one domain, and you can combine it with quotes and exclusions to zero in on complaints. Google documents this in its guide to refining web searches. Three searches to run for each competitor:

• site:reddit.com/r/SaaS "competitor name" — swap in subreddits where your buyers post
• site:news.ycombinator.com "competitor name" (frustrating OR switched OR cancelled)
• "competitor name" "any alternative" — finds people already shopping for a replacement

Sort Reddit results by new, not top. A complaint from 2022 describes a product that no longer exists.

Support forums and community archives

Most competitors run a public forum or Discord with a searchable archive. Search it for words like "broken", "waiting on", or "is there a way to". Discord history is harder to search, but many communities keep a GitHub issues board or changelog where users file feature requests. Copy every hit into a spreadsheet with the date and the exact quote. If you want a structured way to score what you collect, sentiment analysis on competitor reviews shows how to turn raw quotes into feature decisions.

How do you code feedback into themes without paid software?

The spreadsheet coding method

Open a sheet with five columns: source, URL, verbatim quote, product area, and emotion. Paste every quote you collected from review sites, Reddit, and forums as its own row. Copy the words exactly as written; paraphrasing kills the signal, because the phrasing is what you will reuse in positioning later.

Then code each row by hand. Assign the product area (onboarding, pricing, speed, support, missing feature) and an emotion score from 1 (mild annoyance) to 5 (rage-quit, refund demanded, or "I'm switching"). No tooling needed beyond filters and a count formula. This is the same manual read that turns one-star reviews into a gap list, covered step by step in our one-star review walkthrough.

Ranking themes by frequency and emotion

Once every row has a code, sort by product area and count two things: how many quotes hit the theme, and the average emotion score. A theme with 12 mentions averaging 4.5 beats a theme with 30 mild grumbles. Rank your themes in a simple grid: frequency on one axis, intensity on the other. The top-right quadrant is where your roadmap and your positioning both start, and if a theme is frequent, intense, and the incumbent never fixed it, that is your wedge.

Which complaint themes are worth acting on?

Not every theme deserves a roadmap change. A complaint is a signal when it passes three filters: it recurs across at least two independent sources, it names a specific moment ("I gave up at onboarding"), and the complainer is your target user, not someone who was never a fit.

Use Reddit's own search operators to verify recurrence before you act. The Reddit help center documents how to search within a single subreddit and combine terms, so you can confirm the same complaint appears in r/SaaS and r/indiehackers rather than one angry thread.

Rank what survives by cost-to-fix versus how often it blocks purchase. "No free trial" is cheap to fix and blocks everyone; "missing enterprise SSO" is expensive and blocks people you're not selling to anyway.

The same filters apply to your own product decisions. We break down which review signals actually tell you what to build in 7 competitor review signals that tell you what to build.

How do recurring complaints become your positioning?

Take your top three themes and write them as sentences your buyers would say: "the setup took a weekend," "support never answered," "it broke every time I changed one thing." Then flip each one into a claim only you can make. If competitors keep getting dinged for slow onboarding, your homepage hero becomes the fastest way from prompt to first shipped feature, not a list of features.

The wedge works the same way. Pick the single loudest theme and build one page, one comparison, or one workflow that answers it head-on. If the pattern is "dashes but no answers," your wedge is showing the fix, not the chart.

Test it where you mined the feedback. Reply in the same threads with one sentence of positioning and see if anyone clicks. If a theme shows up in three different places and your flipped claim gets replies, it goes on the roadmap and the homepage. If it gets silence, it was a nice-to-have.

What should you do with praise, not just complaints?

Praise is positioning data. When reviewers say "finally stopped guessing" or "the daily moves are the whole product," that is the language your homepage should borrow, because it is already how your target users describe value. Skim the positive reviews on competitor listings, and note which features get named repeatedly. Product Hunt's maker tips even encourage makers to explain the problem their product solves in the first comment, so early praise often mirrors the exact promise that landed.

Then flip it: recurring praise tells you what the incumbent must keep doing, which is a constraint, not a weakness. Your wedge is the complaint theme that sits next to the praise. If users love a tool's output but hate its setup, your messaging leads with the setup, not the output.

How often should you repeat the review-mining pass?

Run the full pass monthly, not weekly. Competitor reviews accumulate slowly, and a weekly sweep mostly re-reads what you already coded. Set a recurring calendar block, two hours, same day each month, and append new quotes to your existing theme sheet rather than starting over.

Two exceptions justify an off-cycle pass: a competitor ships a major update (watch their review spike for the next 30 days), or your own positioning changes and you need fresh evidence for it.

Keep the monthly pass lightweight: re-run your saved searches, skim only reviews newer than your last pass, and log anything that contradicts an existing theme. Contradictions matter more than confirmations, because they signal a theme is fading or splitting into two.

FAQ

Is it legal or ethical to use competitor customer reviews this way?

Yes. Reviews on G2, Capterra, app stores, and Reddit are public, and reading them costs nothing. The lines to respect: don't scrape behind logins, don't copy reviews into your marketing as if customers said them about you, and don't reply to competitor threads pretending to be a user. Quote patterns, not people.

Can I do this for free without any competitor monitoring tool?

That's the whole method. You need Google's site: operator, a browser, and a spreadsheet. Paid monitoring tools mostly automate alerting, which matters at scale, not for a one-afternoon pass across 3-5 competitors. Re-run saved searches monthly and append new rows to your theme sheet, and the free workflow keeps working indefinitely.

How many reviews do I need to read before the themes are reliable?

Aim for 30-50 reviews per competitor before you trust the theme counts. Below that, one loud thread can look like a pattern. Reliability also depends on source diversity: a theme that shows up in G2 reviews and independently on Reddit and a support forum is far stronger than 15 mentions in one place.

What if my competitor is too new and has almost no reviews yet?

Fall back to the places early users talk regardless of review volume: Reddit threads, Hacker News launches, Product Hunt comment objections, GitHub issues, and the competitor's own Discord or forum archive. Even a dozen raw quotes reveal what early adopters stumble on. Re-check review sites after 60-90 days, since listings accumulate slowly at first.

How is this different from just reading one-star reviews?

One-star reviews are the starting point, not the method. Reading them alone gives you raw complaints with no weighting, no cross-source verification, and no capture of praise or lukewarm feedback. The full pass adds coding each quote by product area and emotion, ranking themes by frequency and intensity, and verifying recurrence across Reddit and forums before acting.