Where do users complain about competitor products?
Users complain in five places: the lowest-star reviews on review sites and app marketplaces, Reddit and other forums, public issue trackers, social posts, and in conversations with people who switched to you. Each source has a different bias, so use at least two. A product manager at a small startup asked how to track what users hate about competitor products on r/ProductManagement in January 2026, after spending three hours reading Notion's GitHub discussions. The 15 or so replies named Reddit, review sites, LinkedIn, GitHub and people who switched, with very different opinions on their value.
| Source | What you find | Watch out for |
|---|---|---|
| 1- and 2-star reviews (app marketplaces, review sites) | Billing, support and onboarding pain, often with numbers | Reviewers who used the product for minutes |
| Reddit and forums | Comparisons, switching stories, dealbreakers in plain words | Vendors posting as users |
| GitHub issues (open-source competitors) | Missing features, ranked by votes | One commenter argued these come from the top 0.01% of power users |
| LinkedIn and X posts | Public gripes, plus posts from integrators who sell the product | Posts written for engagement |
| People who switched to you | Why they left and what never got fixed | Small numbers, and they already chose you |
One commenter said talking to people who switched gave far more signal than hundreds of GitHub issues. Another suggested a split of 80% customer research and 20% competitor tracking. Both are single opinions, but they agree on the main point: complaints tell you where to look, and conversations tell you whether it matters to your buyers.
What do 30 one-star reviews actually show? A worked example
They show where the pain clusters: in our Klaviyo sample, more than half were about price or billing. On 24 October 2026 we read the 30 newest one-star reviews of Klaviyo on the Shopify App Store, posted or edited between 1 March and 19 October 2026. Klaviyo is a fair test because it is popular: 3,406 reviews with a 4.7 rating, 88% of them five stars, and 268 one-star reviews (8%). Klaviyo had replied to several of the newest complaints within a day or two. Even one of the one-star reviews said the email marketing itself worked very well; its complaint was the price for growing companies.
Two of the 30 had no text, leaving 28. We tagged each one by theme; a review can carry more than one tag. The tagging is our own reading, and another reader could move a review or two between themes; neither Shopify nor Klaviyo produced it.
| Theme | Reviews (of 28) |
|---|---|
| Price or billing | 16 |
| Support (slow, automated, or paid plans only) | 9 |
| Hard to use or set up | 9 |
| Bugs or something not working | 5 |
| Hard to cancel, disconnect or remove | 5 |
| Bot or fake sign-ups inflating profile counts | 4 |
The useful finding sits inside the biggest row. Only 6 of the 16 price complaints said the product was simply expensive. The other 10 were about how the bill changed: profile counts rising, tier jumps, charges or billing emails after leaving. Klaviyo's pricing page ties plans to profile counts: the free plan allows up to 250 active profiles, which it defines as contacts who may receive marketing emails, and upgrading means picking a tier that matches your active profile count and sends. It also says full email support on the free plan lasts only the first 60 days.
Two cautions. Five of the 28 reviewers had used the app for less than a week, one for 24 minutes, so weight long-time users more. And one-star reviews are a small slice: 30 complaints out of thousands of reviews say nothing about the typical customer. They tell you which promise a competitor's unhappy customers would value from you, such as a predictable bill.
Which searches find complaints fastest?
Use search operators to skip the noise. Google's help page on refining searches documents quotes for exact phrases, site: for one website, a minus sign to exclude words, and before: and after: for dates. Copy these and replace [Tool]:
- Switching stories: site:reddit.com "[Tool]" "switched from" after:2026/01/01
- Dealbreakers: "[Tool]" ("cancelled" OR "moved away from" OR "dealbreaker")
- Feature gaps: "[Tool]" "wish it had" -site:[tool's own domain]
- Price shocks: "[Tool]" ("price increase" OR "renewal") after:2026/06/01
One commenter in the r/ProductManagement thread suggested the same language: phrases such as "wish it had", "frustrating that" and "switched because" separate complaints from bug reports.
For open-source competitors, sort their issues by votes. GitHub's search documentation lists a sort:reactions-+1-desc qualifier that orders issues by thumbs-up reactions, most first. Try: is:issue is:open sort:reactions-+1-desc in the competitor's repository. When we ran it on n8n's repository on 24 October 2026, the top open issue was an AI Agent memory bug with 29 thumbs-up and 57 comments, opened in April 2025. If you sell an alternative to n8n, that is a concrete fix some of its AI Agent users are asking for.
How do you tell a real pattern from noise?
Count, don't read. A complaint becomes a pattern when it shows up in several sources, phrased in different ways, from people who used the product for a while. One commenter in the r/ProductManagement thread put it this way: when the same complaint appears phrased five different ways, that is usually the real insight. Use four filters:
Tag every complaint with one theme
Keep the list short: price, billing, support, ease of use, a missing feature, reliability, leaving. A spreadsheet is enough.
Record tenure
Note how long the reviewer used the product when the site shows it. In our Klaviyo sample, tenure ran from 24 minutes to almost nine years.
Check a second source
A theme that only appears in one place may be a feature of that place. Billing anger on an app marketplace and on Reddit is a pattern; on one site only, it is a lead.
Ask whether your buyers care
A complaint from a segment you don't sell to is not your opportunity. Several commenters in the thread made this point: focus on your own customers first.
Then confirm with people. Ask three customers who switched to you: what made you look, what did you try to get fixed that never was, and what nearly stopped you moving.
How do you turn complaints into positioning and outreach?
Turn a pattern into a promise you actually keep, then lead with the problem and leave the competitor's name out. Review mining tells you what a competitor's unhappy customers want and aren't getting, which is the raw material for positioning. Our post on April Dunford's positioning, rewritten as a cold email shows how to carry that into a first message.
| Complaint pattern | Positioning line (only if true for you) | Outreach opener |
|---|---|---|
| The bill jumps as the contact list grows | Pricing you can predict a year ahead | "Did your last renewal match what you budgeted?" |
| Support only on paid tiers | A human answers on every plan | "Who do you ask when a template breaks?" |
| Hard to cancel or disconnect | Leave in two clicks, export included | Use on the switching page, not in outreach |
| Top-voted missing feature | Ships with that feature on day one | "Still waiting on [feature]? We built it in." |
The openers are examples we wrote for this guide, with no measured reply rates. Three rules keep this fair. Never quote or name a reviewer in outreach. Never claim a competitor does something you can't link to. And put competitor comparisons on a page built for them; our guide to writing fair alternatives and vs pages covers the format.
For direct outreach, the best targets are people complaining in public right now. Our guide to finding people who publicly describe the problem you solve covers where to look and how fast to reply.
How do you run this every week without it taking over?
Give it 30 minutes a week, on a fixed day, and keep one running sheet. One commenter in the r/ProductManagement thread said they automate the collection and spend their time on spotting patterns; another said reading by hand still catches nuance that tools miss.
- Minutes 0 to 10: open each competitor's lowest-star reviews sorted by newest, and tag anything new.
- Minutes 10 to 20: run the four saved Google searches with an after: date of last week.
- Minutes 20 to 25: check the top-voted open issues for any open-source competitor.
- Minutes 25 to 30: update the counts, and write one line: "what changed, and does it matter to our buyers?"
Pair it with a check of what competitors ship and charge. Our guide to tracking competitors' pricing, changelogs and hiring sets out that side of the routine.
The people behind the complaints are leads too. Siela's AI SDR can track competitors on LinkedIn and X: people who post about or engage with them become leads, and people looking for an alternative to a competitor are one of the signals it looks for. Each lead is scored hot, warm or cold with a one-line reason, so you can see why each person was picked.
Frequently asked questions
Is it worth reading competitors' one-star reviews?
Yes, in small doses. One-star reviews are a tiny share of most products' ratings, so they say little about the typical customer. They do show which problems make people angry enough to write, often with numbers attached. Tag 20 to 30 of the newest, count the themes, and weight reviewers who used the product for months over those who used it for minutes.
How many reviews do you need before calling something a pattern?
There is no fixed number, but a theme should appear several times, in different words, and in at least two kinds of source, such as a marketplace and Reddit. In our sample of 28 one-star Klaviyo reviews, price and billing came up 16 times, which is enough to investigate but not enough to describe all of its customers.
Can you use a competitor's negative reviews in your marketing?
Use the pattern and leave the individual review alone. Build a promise around the problem, such as predictable billing, and explain how you deliver it. Avoid quoting or naming reviewers in outreach, and don't claim a competitor does something you can't link to. Put direct comparisons on a dedicated page where readers can check the sources themselves, and link each claim.
What should you ask customers who switched from a competitor?
Ask three questions: what made you start looking, what did you try to get fixed that never was, and what nearly stopped you moving. The first gives you the trigger to watch for in others, the second gives you the complaint that matters, and the third tells you which part of switching to make easier on your migration page.
Should a small startup spend time on competitor complaints at all?
Some, but not much. Commenters in a January 2026 r/ProductManagement thread split on this, with several saying to focus on your own customers first. A 30-minute weekly routine is a reasonable middle: enough to spot a pattern your buyers care about, without turning competitor research into a second job.
Sources
- r/ProductManagement: How do you track what users hate about competitor products? (6 Jan 2026, checked 24 Oct 2026)
- Shopify App Store: Klaviyo reviews, one-star, newest first (checked 24 Oct 2026)
- Klaviyo pricing (checked 24 Oct 2026)
- GitHub Docs: Sorting search results (checked 24 Oct 2026)
- GitHub: n8n issue #14361, AI Agent doesn't store the Tool usages in memory (opened 2 Apr 2025, checked 24 Oct 2026)
- Google Search Help: Refine Google searches (checked 24 Oct 2026)