How to Find Product Gaps in Competitor Reviews
Turning What Their Customers Ask For Into Evidence for Your Roadmap
Short answer
To find product gaps in competitor reviews, start with the two to four star reviews, which name what is missing. Tag each request as a missing capability, broken capability, wrong fit or workaround. Count how often each gap recurs over six months, then validate the strongest ones with your own customers before building anything.
1. What counts as a product gap in a competitor review?
A product gap is a need the reviewer has that the competitor's product does not meet, stated clearly enough that you could build against it. Complaints about service, delivery or tone are real problems, but they are not product gaps.
- Product gap
- A recurring customer need that a competitor's product fails to meet, evidenced by reviews that describe the missing or inadequate capability rather than a one-off service failure.
- Also known as: Unmet need, Feature gap
Four kinds of gap show up in reviews, and they call for different responses:
- Missing capability: "there is no way to export by client". The product simply does not do it.
- Broken capability: "the sync fails every few days". It exists but does not work reliably.
- Wrong fit: "great for freelancers, useless once we hired". The product serves a segment the reviewer has outgrown or never belonged to.
- Workaround: "I copy everything into a spreadsheet to get the report I need". The reviewer built the missing feature by hand, which is the clearest demand signal there is.
The general guide to competitor reviews covers how to map weaknesses for positioning. This one is narrower: it treats reviews as unpaid user research for the product team.
2. Which competitor reviews contain the most product gaps?
Middle ratings. Two, three and four star reviews come from people who still use the product and can say exactly what is missing. One-star reviews skew toward service failures, and five-star reviews rarely mention gaps at all.
A one-star review is usually about a moment: a refund, a cancellation, a support ticket nobody answered. That is useful for messaging, and the negative reviews guide in this cluster covers it. A three-star review is usually about the product: "does most of what we need, but" is the most valuable sentence in the whole dataset.
Read in this order to get the most gaps per hour:
- Three-star reviews, all of them for the last six months.
- Four-star reviews that contain the word "but", "wish" or "only".
- Two-star reviews that describe what they use the product for.
- Company replies that say a feature is "not currently supported" or "on our roadmap".
- Reviews that mention switching, in either direction.
Company replies deserve their own pass. When a competitor answers a review by confirming a limitation, you have the gap acknowledged by the vendor, often with a hint about whether they plan to fix it.
3. How do I extract product gaps from reviews?
Read middle-rated reviews from the last six months, write each request as a one-line need in the customer's words, tag its type and the reviewer segment, and merge duplicates into a counted list.
Plan on two hours per competitor for the first pass, then twenty minutes a month.
- Set a six-month window. Older reviews may describe problems that were fixed long ago. Six months is recent enough to be current and long enough for a real gap to repeat. Record the window with the date you pulled it.
- Write each request as a one-line need. Phrase it as the customer would: "I need to send invoices in more than one currency". Keep the reviewer's own words in a second column. Paraphrase loses the vocabulary you will want later.
- Tag the gap type and the segment. Missing, broken, wrong fit or workaround, plus whatever the review reveals about the reviewer: company size, role, industry, country. A gap that clusters in one segment is a segment opportunity, not a general feature.
- Merge duplicates and count. Group lines that describe the same need, even in different words, and count the reviews behind each group. Keep the date of the earliest and latest mention, so you know whether the gap is growing or fading.Merge on the underlying need, not the proposed feature. Three people asking for three different buttons may all want the same outcome.
- Check whether the competitor already fixed it. Look at their changelog, release notes or feature pages for the need. A gap they closed last month is not a gap anymore, and a gap they have acknowledged in replies may close soon.
4. Which phrases in a review point to a gap?
Wishes, workarounds, conditions and exits. "I wish", "I have to", "only works if" and "we moved to" each signal a different kind of gap, and learning to spot them makes a first pass several times faster.
| Phrase pattern | Usually signals | What to record |
|---|---|---|
| "I wish it could", "it would be great if" | Missing capability | The need and how central it is to their job |
| "I have to", "we ended up", "I export it to" | Workaround | The manual steps they take, which describe the feature |
| "Only works if", "as long as you" | A capability with hidden limits | The condition, which is often a segment boundary |
| "Keeps failing", "stopped working after" | Broken capability | Whether it clusters after a date, which suggests a release |
| "Fine for small teams, but" | Wrong fit for a growing segment | The size or stage at which it breaks |
| "We moved to", "we are looking for an alternative" | A gap severe enough to cause churn | The trigger, and where they went if named |
| "Not available in my country", "no support for" | Market or localization gap | The country, language or regulation |
5. How do I decide which gaps are worth building for?
Score each gap on four things: how often it recurs, whether it is growing, whether the segment is one you want, and whether you can solve it better than a quick fix by the competitor. Frequency alone is not enough.
| Criterion | Question to ask | Weak answer |
|---|---|---|
| Recurrence | How many unrelated reviewers name it in six months? | One or two mentions, however detailed |
| Trend | Is it appearing more often in recent months? | All mentions are old and none are recent |
| Segment fit | Are the reviewers the customers you want? | They belong to a segment you do not serve |
| Defensibility | Would solving it give you an advantage they cannot copy in a sprint? | It is a small setting they could add next week |
6. How do I validate a gap before building it?
Check it against your own evidence: your support tickets, your own reviews, your sales call notes and a few direct conversations with customers in that segment. A gap confirmed from two independent sources is worth a roadmap slot.
Start with your own product. If your reviews and support queue show the same need, the gap is category-wide rather than a competitor weakness, and whoever solves it first gets to talk about it first. If your customers never mention it, ask whether that is because you already solve it or because you do not serve the people who need it.
Then talk to five customers in the segment the gap came from. Describe the problem, not the feature, and listen for whether they recognize it unprompted. A gap that only exists in text on a review site will not survive a conversation, and it is cheaper to learn that before building.
Finally, write down what you will not build. A clear no, with the reason, stops the same gap coming back every quarter as if it were new.
7. Which competitor gaps should I not chase?
Gaps from segments you do not want, gaps the competitor is visibly fixing, and gaps that exist because of a deliberate trade-off in their product that you share. Building those turns their review page into your roadmap.
A competitor built for small teams will collect reviews from larger customers asking for enterprise controls. If you are also built for small teams, those requests belong to a market neither of you serves well, and chasing them dilutes your product for your real buyers.
Keep the list, but mark those gaps as out of scope with a date. When your own direction changes, the evidence is already collected.
Oppira collects Trustpilot reviews continuously for the competitors you track on the Basic and Pro plans and summarizes their sentiment, and the findings flow into each competitor battlecard. The extraction and the validation described here are still product judgment, and they are worth doing by hand for the gaps that could shape your roadmap.
Key Takeaways
Middle ratings hold the gaps
Three-star reviews come from people still using the product who can name exactly what is missing.
Four gap types need different responses
Missing, broken, wrong fit and workaround each point to a different kind of opportunity.
Workarounds are the strongest signal
A reviewer who rebuilds a feature by hand has already proven the demand.
Merge on the need, not the feature
Different requested buttons often describe one underlying outcome.
Rank on recurrence, trend, fit and defensibility
A frequent gap in a segment you do not want is not worth building.
Validate with your own customers
A gap confirmed by your support queue or five customer conversations is worth a roadmap slot.
Frequently Asked Questions
Sources
- Trustpilot's review labels Trustpilot Help Center, September 2026.How to tell invited from unprompted reviews, which affects how representative a sample is.
- Terms of Use for Consumers Trustpilot, September 2026.Reviewers own their content, so quote findings internally rather than republishing reviews.
Explore More
Related analyses, benchmarks, and industry insights
Related Guides
Glossary Terms
Turn reading into a reaction
Oppira watches your competitors, keeps your playbook current, and drafts the response. See your market clearly by tomorrow.