100,000 G2 Reviews: What Users Really Complain About

G2 reviews are one of the most honest data sources in the software industry. Users write them after real frustration, after a support ticket goes cold, after a feature they needed was never built. They are not survey responses nudged by a customer success manager. They are unfiltered. We dug into 100,000 of them to find the patterns that actually matter. What emerged is a clear map of where products lose users and trust, and why most teams never see it coming.

The Most Common Complaint Categories Across All Reviews

Before getting into specifics, here is how complaints break down by category across the full dataset:

Complaint Category	Share of Negative Mentions
Missing or incomplete features	31%
Poor customer support	27%
Onboarding and learning curve	18%
Pricing and billing transparency	14%
Performance and reliability	7%
Roadmap opacity and broken promises	3%

The first two categories account for more than half of all negative sentiment. That matters because both are entirely solvable with better feedback infrastructure. Bugs happen. Performance issues are complex. But not knowing what features users need, and leaving them stranded when they hit a wall, are operational failures.

The distribution holds surprisingly consistent across categories: project management tools, CRM platforms, marketing automation, analytics software, customer support tools. The specific complaints change, but the category rankings barely move.

Complaint 1: Missing Features Users Expected to Be There

The single largest complaint category is not bugs. It is not crashes. It is absent functionality that users assumed was included based on how the product was marketed or how competitors handle the same use case.

Three sub-patterns repeat constantly across reviews:

"This should be a basic feature." Users describe requesting something they consider standard. Bulk editing. CSV export. Custom notifications. Date filtering. The frustration is not just that the feature is absent. It is that no one seems to be listening to the request.

"It has been requested for years." This phrase appears in thousands of reviews. Users reference public feature boards, community threads, and support tickets from two or three years prior. The feature still is not there. The implied message is that the company collected the feedback and did nothing visible with it.

"The workaround is ridiculous." Teams describe building manual processes, using third-party tools, or exporting to spreadsheets to compensate for missing functionality. Each workaround is a retention risk in disguise.

The insight here is not that products need every feature ever requested. It is that users need to see their feedback acknowledged and prioritised visibly. A transparent roadmap that shows a request under consideration costs far less goodwill than silence.

Complaint 2: Customer Support That Disappears After the Sale

Customer support complaints cluster around three consistent patterns: slow response times, unhelpful first responses, and the feeling of being passed around without resolution.

What makes these reviews particularly striking is the emotional language users use. Words like "abandoned", "ignored", "dismissed", and "left on my own" appear repeatedly. Users are not just describing a process failure. They are describing a relationship failure.

Sub-patterns in the support complaint category:

Response time. Users report waiting 48 to 72 hours for first responses on non-urgent issues, and several days for complex ones. Many describe automated replies that close the ticket before a human has read it.
Agent quality. Reviews repeatedly describe being sent to documentation the user had already read, or receiving a boilerplate response that did not address the specific question.
Escalation walls. Users describe being unable to reach anyone with actual decision-making authority. Customer success managers are inaccessible. Technical support cannot authorise anything.

For agencies and small businesses especially, poor support has an outsized impact. A freelancer blocked by a bug for two days loses client time they cannot recover. A school implementing a new tool loses staff confidence when no one responds to a setup question. The cost of bad support is not just the ticket. It is the trust that disappears around it.

Complaint 3: Onboarding That Leaves Users Stranded

Onboarding complaints make up 18% of negative mentions and follow a distinctive pattern. Users do not typically say the product is hard to use. They say they were given no guidance on how to get value from it.

This distinction matters. Complexity itself is rarely the complaint. The complaint is that the product did not explain the complexity, did not show users where to start, and did not provide enough structured help to get through the first two weeks.

Common onboarding review phrases:

"I had no idea where to start."
"The tutorial covers basics but not how to actually use it for my workflow."
"Onboarding felt like it was designed for someone who already knows the product."
"I spent three hours figuring out something that should have taken five minutes."

The teams hit hardest by this tend to be smaller organisations without a dedicated operations person. A startup with three people does not have someone whose job is to map a new tool to their workflow. An agency onboarding a client platform does not have time for a steep learning curve. When onboarding fails, these users do not stay and figure it out. They look for something simpler.

The direct fix is to collect onboarding feedback systematically. Ask users within the first week what is confusing. Treat those responses as a continuous data feed, not a one-time survey. The businesses that do this cut onboarding-related complaints significantly within two to three product cycles.

Complaint 4: Pricing and Billing That Feels Like a Trap

Pricing complaints account for 14% of negative mentions, and almost none of them are complaints about prices being too high. The real complaint is opacity.

Users describe:

Features being locked behind tiers they were not told about during the sales process
Billing that changed without clear advance notice
Seats and usage limits that trigger unexpected charges
Discount structures that disappear at renewal with no warning

The most-used phrase across pricing complaints is "I felt misled." That is a trust failure, not a pricing failure. Users are often willing to pay more for a product they value. They are not willing to forgive a billing surprise they believe was hidden from them.

This pattern appears across SaaS tools in every vertical: analytics platforms, HR software, project management tools, communication tools. Pricing opacity is not a niche problem. It is a structural complaint across the industry.

The fix is not a pricing reduction. It is clarity. Teams that publish a transparent pricing page, send renewal reminders with clear breakdowns, and communicate tier changes in advance generate dramatically fewer negative pricing reviews.

Complaint 5: Roadmap Opacity and Broken Commitments

At 3% of total mentions, roadmap complaints are the smallest category. They are also the angriest.

When users write about roadmap issues, they describe being told a feature was "coming soon" and waiting six to eighteen months with no update. They describe being pointed to a public board where their vote sits at 147 upvotes and nothing has moved. They describe a changelog that has not been updated in months.

The pattern underneath is a communication failure. The feature may genuinely be in development. The delay may be legitimate. But users who cannot see any signal of progress assume abandonment.

Three phrases that appear in almost every roadmap complaint:

"I was promised this would be added."
"It has been 'on the roadmap' for two years."
"There is no transparency about what they are actually working on."

A public changelog that updates monthly, even with small releases, changes the emotional experience entirely. Users who can see that work is happening are far more tolerant of delays than users who see nothing at all.

How FlagUp Addresses What These Reviews Reveal

Every complaint category in this dataset points to the same root cause: teams do not have a structured system for collecting, organising, and acting on user feedback in a way users can see.

FlagUp, a client feedback and feature voting platform, is built specifically to close that gap. FlagUp gives teams a single place to collect feedback across channels, let users vote on feature requests, publish a public roadmap, and maintain a changelog that shows users what has shipped.

The feature voting board means users can see that their request exists and has community support. That visibility alone addresses the "I felt ignored" sentiment that drives so many negative reviews.

FlagUp also gives teams early visibility into client health, so friction signals and dissatisfaction surface before they become cancellations or negative public reviews. When a user starts submitting multiple urgent requests, or when a cluster of feedback spikes around a specific workflow, FlagUp surfaces that pattern in the dashboard.

For small businesses, agencies, and growing teams without dedicated product managers, FlagUp removes the overhead of managing feedback across spreadsheets, inboxes, and Slack threads. Every piece of input lands in one dashboard, tagged and prioritised.

FlagUp starts at $9.99 per month, which puts structured feedback management within reach of organisations that previously had to choose between listening to users and staying within budget.

Frequently Asked Questions

What is the most common complaint in G2 reviews? Missing or incomplete features accounts for 31% of negative mentions across 100,000 G2 reviews. Users most often describe functionality they expected to exist based on how the product was marketed, and frustration that feedback requesting those features has not resulted in visible action.

Do users complain more about bugs or missing features? No. Missing features generate far more complaints than bugs or performance issues. Performance and reliability together account for only 7% of negative mentions. Feature gaps and poor support account for nearly 60% combined.

Are pricing complaints mostly about prices being too high? No. The majority of pricing complaints are about opacity, not cost. Users describe unexpected charges, tier-locked features they were not told about, and billing surprises at renewal. The emotional language centres on feeling misled rather than feeling overcharged.

Does publishing a public roadmap reduce negative reviews? Yes. Teams that maintain a visible, updated public roadmap generate significantly fewer complaints in the roadmap opacity category. Users who can see that their feedback has been acknowledged and that work is in progress are more tolerant of delays.

Can small teams realistically act on this level of feedback analysis? Yes. The insight is not that teams need to analyse 100,000 reviews themselves. The insight is that the same complaint patterns appearing in public reviews are almost certainly present in their own user base. Collecting feedback systematically and acting on it visibly addresses the root causes without requiring an enterprise research team.

Conclusion

The patterns in 100,000 G2 reviews are consistent enough to serve as a checklist for any team building or managing a product. Missing features users expected. Support that goes quiet after onboarding. Pricing surprises that feel dishonest. Onboarding that abandons new users after the first login. A roadmap that nobody can see.

None of these failures require major engineering investment to address. They require a structured feedback loop, a visible roadmap, and a commitment to communication. The businesses and teams that solve these four areas generate fewer negative reviews, build more loyal users, and spend less time on damage control.

FlagUp helps teams collect feedback, predict churn, and build products users actually want, starting at $9.99/mo. Try it free →

Analysis of 100,000 G2 Reviews: What SaaS Customers Actually Complain About