We scored 39,000+ software complaints across 13,000+ products for churn risk, then replicated the result on 136,000+ mobile reviews and 9,400+ G2 insights. Complaint frequency and complaint lethality run in opposite directions.
Every article ranking for this question gives you a numbered list of churn reasons, leads with poor onboarding or lack of perceived value, and sources none of it. One of the top-ranking pieces was published in 2016. The single study cited anywhere in that search result sits behind a Medium paywall.
We had the material to answer it differently. Our complaint database holds 39,000+ analysed software complaints covering 13,000+ products, and every one carries a churn-risk assessment and a severity score. So instead of ranking churn reasons by how often people mention them, we ranked complaint categories by how often they come attached to a customer signalling they are leaving.
The two rankings are almost inverted. That inversion is the article.
The standard churn article is built from the author's experience and the other churn articles. That produces a stable consensus with no measurement behind it, which is why the same five reasons appear in every list in the same order.
Our approach was different in one specific way. We did not ask what customers complain about. We took every complaint, and asked how often each type of complaint comes with evidence that the customer is leaving. Across all 39,000+ complaints, 76.1% carry a churn-risk signal, which is high because people writing negative software reviews are, in general, unhappy. The information is in the variation between categories, and that variation runs from 50.8% to 98.6%.
Here is the finding in its shortest form. User experience is the most complained-about category in our data, with over 5,000 documented complaints. It ranks near the bottom for churn risk at 67.5%. Service quality has roughly 140 complaints, about 35 times fewer, and ranks first at 98.6%.
The practical consequence is uncomfortable for any team that prioritises by ticket volume or by review-mining frequency counts. Sorting complaints by how often they appear produces a roadmap aimed squarely at the complaints your customers are willing to live with. Severity tracks the same inversion: average severity is 3.58 for interface complaints and 4.13 for technical reliability complaints.
This also revises something we have published before. Our own most hated software analysis and most requested features research both rank by volume, which is the right way to find what to build. It is the wrong way to find what is killing you.
Every complaint category with enough volume to be meaningful, ordered from most tolerated to most fatal. Read the last column as the summary.
| Complaint category | Complaints | Churn signal | Avg severity | Buildable | Read as |
|---|---|---|---|---|---|
| User Interface | 310+ | 50.8% | 3.58 | 75.7% | tolerated |
| Feature Limitations | 910+ | 57.4% | 3.65 | 91.1% | tolerated |
| Usability | 1,300+ | 64.8% | 3.71 | 80.6% | tolerated |
| User Experience | 5,000+ | 67.5% | 3.75 | 82.2% | tolerated |
| Functionality | 1,100+ | 68.6% | 3.71 | 87.8% | tolerated |
| User Onboarding | 100+ | 70.1% | 3.67 | 85.0% | mixed |
| Reporting | 780+ | 74.8% | 3.89 | 93.2% | mixed |
| Implementation | 170+ | 77.6% | 3.82 | 80.6% | mixed |
| Performance | 730+ | 80.2% | 3.78 | 68.3% | mixed |
| Integration | 650+ | 83.6% | 3.79 | 91.6% | lethal + buildable |
| Cost Management | 180+ | 91.4% | 3.92 | 85.5% | lethal + buildable |
| Pricing | 600+ | 93.4% | 3.86 | 91.9% | lethal + buildable |
| System Reliability | 180+ | 94.5% | 4.11 | 77.9% | lethal |
| Technical Reliability | 230+ | 96.1% | 4.13 | 83.2% | lethal |
| Customer Support | 1,000+ | 96.7% | 4.06 | 89.0% | lethal |
| Customer Service | 920+ | 98.2% | 4.11 | 86.6% | lethal |
| Service Quality | 140+ | 98.6% | 3.99 | 81.9% | lethal |
One structural note before anyone over-reads a single row. Our category labels are generated per product rather than drawn from a fixed taxonomy, so near-duplicates such as Customer Support and Customer Service, or Feature Limitations and Feature Gaps, are reported separately. That means these are reliable tiers and not exact ranks. The tiers are what matter, and the tiers are unambiguous: everything about service, reliability and money sits above 91%, and everything about interfaces and features sits below 70%.
Our complaint records carry a second flag: whether the complaint represents a market opportunity, meaning something a product could actually address. Crossing that against churn risk produces a frame we have not seen anywhere else, and it changes what you should do with any of this.
High churn, low buildability. Service quality (98.6% churn, 81.9% buildable), customer service (98.2%, 86.6%), system reliability (94.5%, 77.9%), performance (80.2%, 68.3%). These end accounts, but they are operational failures rather than product gaps. You cannot ship a feature that fixes another company's support team. If these are your complaints, this is a hiring and process problem wearing a product costume.
Low churn, high buildability. Feature limitations (57.4% churn, 91.1% buildable), user interface (50.8%, 75.7%), usability (64.8%, 80.6%). Easy to build, and customers demonstrably tolerate the gap. This is why "we have a cleaner UI" is such a weak wedge: it is real, and it is not why anybody is leaving.
High churn and high buildability. Pricing (93.4%, 91.9%), integration (83.6%, 91.6%), cost management (91.4%, 85.5%), and reporting sits just below (74.8%, 93.2%, the highest buildability score in the table). This is the intersection, and it is where we would spend. It is also, not coincidentally, the region our G2 review mining research and Capterra complaint mining guide keep landing in.
The quantitative split has a qualitative signature you can learn to recognise in your own support inbox. We pulled real complaints from both ends of the ladder. All quotes are anonymized to role and platform, and product names are removed.
Complaints flagged as carrying churn risk. Note that the subject is consistently the damage to the customer's business, and several explicitly recommend a competitor.
"My calls for support often lead to the same issues months later with no follow-up or resolution. This is damaging my business operations." — Capterra review, Safety Director (Customer Service)
"Customer service is nonexistent, server downtime is too frequent. I have put in service calls that have taken months to answer." — Capterra review, Owner in IT Services (Customer Support)
"Once you buy the software, you're on your own. If you run into the simplest obstacle, no one is there to support you." — Capterra review, CEO of a healthcare company (Customer Support)
"I received zero warning about an automatic renewal. I cannot recommend highly enough that you go with a different service." — Capterra review, Content Strategist in Marketing (Customer Service)
"Support (paid) is horrible. System critical issues take days sometime weeks to get resolved." — Capterra review, IT Director, Financial Services (Customer Support)
"The support is terrible. I mean, they ask questions, don't read answers and reply with canned responses that are inaccurate." — Capterra review, Owner, Management Consulting (Customer Support)
Complaints not flagged as carrying churn risk. Same database, same review format. The subject here is a preference, and the tone is of somebody planning to keep using the product.
"I wish we could arrange customers data by amount spent and the number of orders." — Capterra review, Partner at a restaurant (Feature Limitations)
"Adding color would help with organization and overall feel." — Capterra review, Executive Pastor, Nonprofit Management (User Experience)
"Once you have it down, it's limitless, but the initial learning took a lot longer than expected." — Capterra review, Sales ops manager (User Experience)
"The reporting features need enhancement; we're struggling to compile comparison reports without getting into spreadsheets and wasting hours." — Capterra review, Construction Estimator (Reporting)
"It can be a bit overwhelming at first to run reports and create events." — Capterra review, Executive Director, Nonprofit Management (User Experience)
The difference is not intensity, it is grammar. "I wish we could" and "adding color would help" are requests, and a request presumes a continuing relationship. "This is damaging my business operations" and "I cannot recommend highly enough that you go with a different service" are verdicts. If your support queue is full of the first kind, your retention is probably fine and your roadmap has work to do. If it contains any of the second kind, the roadmap is not the problem.
A finding from one dataset with one scoring method is a hypothesis. So we tested it against a completely different dataset with a completely different measure: mobile app reviews, where we have a star rating rather than an inferred churn flag.
We classified 136,000+ reviews by the language they contain and compared average star ratings. If the ladder is real, money and reliability language should cluster at the bottom of the rating scale and feature-wish language should sit well above it.
| Language in the review | Reviews | Avg rating | vs corpus average |
|---|---|---|---|
| Billing (cancel, refund, charged, scam) | 9,700+ | 1.29 stars | 1.00 below |
| Reliability (crash, freeze, bug, broken) | 11,000+ | 1.90 stars | 0.39 below |
| Feature wishes (wish, would be nice, please add) | 4,900+ | 3.38 stars | 1.09 above |
The gap between billing language and feature-wish language is 2.09 stars. A customer writing about a charge they did not expect is giving roughly one star. A customer asking for a feature is giving roughly three and a half, which on a five-point scale is a person who basically likes your product.
This is the same ordering as the Capterra ladder, produced on a different platform, a different buyer type, and a different measurement instrument. Two independent datasets agreeing is considerably stronger than either alone. Our state of mobile app pain points report goes deeper on this corpus, and finding SaaS ideas from negative reviews covers how we work it.
A third source, a third method. Across 9,400+ extracted G2 insights covering 9,400+ companies, we counted how often each theme appears at all. This measures frequency, not lethality, so it should look like the opposite of the churn ladder if our finding holds.
It does. Feature and capability gaps are the most frequently mentioned theme at 6,200+ insights, roughly two thirds of the corpus. Support and service follow at 3,900+, integration at 3,500+, reliability at 3,400+. Pricing is the least frequently mentioned at 2,400+, roughly a quarter.
So pricing is the rarest complaint on G2 and the second most lethal complaint in our churn ladder. Features are the most common complaint on G2 and among the least lethal. Three datasets, three methods, one conclusion: how often a complaint is voiced tells you almost nothing about whether it ends the relationship. For the mechanics of working this source, see how to analyse G2 reviews for product ideas.
Nearly every competing article leads with onboarding. Our data does not support that as the leading cause of complaint-accompanied churn: user onboarding sits mid-ladder at 70.1% on a small sample of roughly 100 complaints, and implementation at 77.6% on roughly 170. Both are well below pricing at 93.4% and support at 96.7%.
We were ready to call the onboarding consensus unfounded. Then we went and read what founders who actually run exit interviews report, and the honest answer turned out to be more interesting than either position. It is the subject of the next section, and it is the most important limitation on this page.
Review data has a structural blind spot, and it is a large one. A customer who quietly stops logging in and cancels three months later never writes a review. Every number on this page describes churn that arrived with a complaint. It cannot size the churn that arrived with silence.
A founder on r/SaaS who personally interviewed every customer who cancelled in a quarter reported exactly that pattern, and it directly contradicts what our corpus would predict:
"I expected to hear that we were missing features. Or that a competitor was better. Or that pricing was too high. Those did come up occasionally. Maybe 20% of the time combined. The overwhelming majority said some version of the same thing: we just stopped using it. Not because anything was wrong. They got busy. The person who set it up left the company. Priorities shifted. The product sat there unused for a couple months and then someone noticed the charge and cancelled." — r/SaaS
"The second most common reason was closely related. They never really got fully set up. Signed up with good intentions. Poked around. Got pulled in another direction. Never reached the point where it was embedded in their workflow." — r/SaaS
Take that seriously and the two pictures reconcile cleanly rather than competing. There are two churn populations with different causes:
Which means the onboarding consensus is probably right about silent churn and wrong to present it as the whole picture, and our data is right about loud churn and structurally unable to see the rest. The two sources have almost exactly complementary blind spots: product analytics can see silent disengagement but cannot tell you why, and reviews tell you why but only for the people who spoke up. Use both. Anyone selling you one number for "why customers churn" from one source is overselling.
Pricing complaints carry a churn signal 93.4% of the time and score 91.9% on buildability, the strongest combination in the table outside the pure operations categories. Cost management sits alongside at 91.4% and 85.5%. Yet pricing is the least frequently voiced theme in our G2 corpus.
The reason is straightforward once stated: people do not complain about price, they leave over it. A pricing objection is rarely written down because there is nothing to request. This is why price sensitivity is chronically underweighted by teams that listen to their loudest feedback.
It is worth separating two different things that both show up as pricing complaints. One is being too expensive for the value delivered. The other is billing behaviour: surprise renewals, unclear tiers, charges the customer did not expect. Our mobile data suggests the second is more corrosive than the first, since billing language carried the lowest average rating of any category we measured at 1.29 stars. The quote earlier in this piece, "I received zero warning about an automatic renewal", is a billing-practice failure rather than a price-level failure, and it ends with the customer recommending a competitor.
One founder's firsthand account of testing the price level rather than assuming it is worth reading against this:
"Raised prices to $49 for new customers and existing customers at renewal. Spent a week stress-dreaming about the angry emails I was going to get. The mass exodus that would tank everything. Reality was anticlimactic. A few complaints. Some people cancelled who were probably going to cancel anyway. 8% of customers left over the following two months. Revenue went up 29% over the same period." — r/SaaS
That is one data point from one product and we would not generalise it into advice. What it does illustrate is that the price level and the billing experience are separate levers, and teams tend to fear the first while neglecting the second. Our SaaS pricing strategies research covers the level, and SaaS metrics benchmarks plus how MRR, ARR and TTM differ cover measuring the result.
Integration complaints carry a churn signal 83.6% of the time with 91.6% buildability, and the near-duplicate label "Integration Issues" scores 87.2% on roughly 430 complaints. Together they represent over a thousand documented complaints in the lethal-and-buildable quadrant.
The mechanism is that an integration failure is not a missing feature, it is a broken workflow. When a tool will not connect to the system of record, the customer is not mildly inconvenienced, they are doing manual work every week that they were paying you to eliminate. That converts into cancellation far more reliably than a dated interface does.
For anyone building rather than retaining, this is the most reliable wedge in the dataset, and it is the one we keep arriving at independently in niche SaaS opportunities by industry and business pain points research. It is also structurally defensible in a way a feature is not, which we argue in what counts as a moat in the AI era.
Stated positively, because it is genuinely useful for prioritisation. Based on 39,000+ complaints, customers demonstrably tolerate a dated or ugly interface (50.8% churn signal), missing features they have asked for (57.4%), a learning curve steeper than promised (64.8%), and general workflow friction (67.5%).
None of that means these are fine. They cap your growth, they hurt expansion revenue, and they are exactly what to build. The claim is narrower and more useful: they are not why your customers are leaving this quarter. If churn is your emergency, a redesign is not the intervention.
The reverse is also worth stating. The categories with the highest buildability scores in the whole table are reporting at 93.2%, feature limitations at 91.1% and integration at 91.6%. Two of those three are tolerated. So the best product opportunities and the worst retention risks are largely different lists, and conflating them is how teams end up shipping enthusiastically while churning steadily.
In the order the data supports, which is not the order most churn articles use.
The same data reads differently if you are looking for something to build. A complaint that reliably ends a relationship and can be addressed by a product is the highest-quality signal available, because the incumbent's customers are already leaving and have somewhere to go.
That points at pricing, integration, cost management and reporting. Note what it points away from: the "cleaner UI, better UX" wedge that a large share of new products lead with. Our data says customers tolerate the thing those products are fixing.
It also points away from the pure-operations categories. A competitor cannot fix another vendor's support team, which is why "their support is terrible" is a reason customers leave and not, by itself, a product opportunity. The exception is when bad support is a symptom of product complexity, in which case the buildable version is the simplification, not a support desk.
If you want to work this angle, our pain point research method, validating an idea against real reviews and the pain points database guide are the operational versions of this section, and our teardown of customer support software limitations shows the pattern applied to one category.
The most cited figure in retention comes from Harvard Business Review, which in October 2014 summarised research by Frederick Reichheld of Bain & Company finding that increasing customer retention rates by 5% increases profits by 25% to 95%. The same piece states that acquiring a new customer is anywhere from five to 25 times more expensive than retaining an existing one.
We are quoting it because it is the real source rather than the third-hand version, and we want to flag that HBR itself hedges it: their sentence opens with "depending on which study you believe, and what industry you're in". It is one of the most misquoted statistics in software. Treat it as a wide range that justifies prioritising retention, not as a formula that predicts your outcome.
For what retention is worth in your specific category, our SaaS revenue benchmarks, profit multiples by category and growth rate research are built on live revenue data rather than a 2014 range, and revenue intelligence is the tool version.
We checked our conclusions against what founders say when they have actually done the work, because a corpus can be confidently wrong. The exit-interview account in the silent-churn section above is the most important of these, and it is the one that revised our thesis rather than confirming it.
Three more real complaints from the lethal end of our own data, since the specificity is the point:
"It logs you out every 20 minutes. It takes 10 mins to log back in. We pay entirely too much for this site to be this awful." — Capterra review, Business Supplies and Equipment (Technical Reliability)
"I felt completely unsupported and they negatively impacted my business." — Capterra review, Tour operator (Customer Support)
"The customer service experience here has been the worst. When a critical issue arises, it can take forever to get it solved." — Capterra review, Vice President of a shipping company (Customer Support)
And two more from the tolerated end, to make the contrast concrete:
"I can train a person in two hours but advanced features take much longer to master." — Capterra review, Planning Lead in Construction (Usability)
"Although the website theme they provide is great there is a lack of options when it comes to how you would like your website to look." — Capterra review, Capterra reviewer (Feature Limitations)
One negative result worth recording. We checked 5,300+ freelance job posts for churn and retention work and found three. Whatever else is true, companies are not outsourcing this problem, so there is no useful demand signal there. We are reporting that rather than quietly dropping the source, and per our standing note on that dataset we never cite dollar figures from it because the budget fields are unpopulated.
Every figure on this page comes from a searchable corpus of over a million documented complaints across Capterra, G2, the App Store, Google Play, Reddit and Upwork. Filter by category, severity or churn risk and read the underlying reviews yourself.
Explore the complaint database →Four datasets, one pass each, all re-queried on August 24, 2026. Here is exactly what each one can and cannot support.
| Source | Records used | What it establishes | Limitation |
|---|---|---|---|
| Capterra complaint analysis | 39,000+ scored complaints, 13,000+ products | The churn ladder, severity by category, and the lethal-versus-buildable split | The churn flag is inferred from review text, not from an observed cancellation. It measures stated intent and business impact, not confirmed departure. |
| App Store and Google Play reviews | 136,000+ reviews with text and rating | Independent replication using star ratings instead of an inferred flag | Language is keyword-matched, so categories overlap and neutral or positive mentions are caught. Consumer mobile buyers differ from B2B software buyers. |
| G2 extracted insights | 9,400+ insights across 9,400+ companies | That complaint frequency inverts the lethality ranking, on a third method | Counts theme presence only. It carries no churn or severity scoring, so it can corroborate the inversion and cannot rank lethality. |
| Reddit (r/SaaS, live) | Public threads, usernames stripped | Firsthand exit-interview reports, which established the silent-churn limitation | Self-selected accounts from individual founders. Directional evidence about our blind spot, never a measurement. |
| Upwork job posts | 5,300+ posts checked | Nothing. Three retention-related posts, reported as a null result | Budget fields in this dataset are unpopulated, so we never cite dollar figures from it under any circumstances. |
| Harvard Business Review (October 2014) | Summary of Reichheld and Bain & Company research, read live | The value-of-retention range: 5% retention gain, 25% to 95% profit gain | HBR itself hedges it with "depending on which study you believe". It is over a decade old and heavily misquoted. |
Category labels are per-product, not a fixed taxonomy. Our corpus contains thousands of distinct category strings, which is why Customer Support and Customer Service appear as separate rows despite meaning the same thing, as do Feature Limitations, Feature Limitation, Feature Gaps and Feature Set. We deliberately did not merge them, because merging by hand would let us choose the result. The consequence is that these are tiers rather than exact ranks, and no single row should be read as precisely the nth most dangerous complaint.
Small samples are labelled as such. Service Quality (roughly 140), System Reliability (roughly 180), Cost Management (roughly 180) and User Onboarding (roughly 100) sit at the top and bottom of the ladder on the smallest counts in the table. Their direction is consistent with the larger neighbouring categories, which is why we trust the tier, but a 140-complaint category deserves less confidence than a 5,000-complaint one.
The overall churn rate is not a base rate for your product. 76.1% of all complaints in the corpus carry a churn signal, which is high because people who write negative software reviews are self-selected for unhappiness. That number is only useful as the denominator for the between-category comparison. Do not read it as a churn forecast.
The biggest limitation has its own section. Review data cannot see customers who leave without complaining, and the firsthand evidence suggests that population is large and driven by different causes. We would rather state that plainly than publish a ranking that implies completeness. Nothing here is a substitute for your own analytics.
What this cannot tell you. We have no observed cancellation events, no cohort retention curves and no revenue impact per complaint category. So this analysis ranks the relative danger of complaint types, and it cannot tell you your churn rate, what your churn will be, or how much revenue any single fix recovers. For revenue-side evidence see the state of SaaS pain points and our SaaS market research guide.
Among customers who complain before leaving, they churn over service, reliability and price, not over missing features. Across 39,000+ analysed complaints covering 13,000+ products, service quality complaints carried a churn-risk signal 98.6% of the time, customer service 98.2%, customer support 96.7%, technical reliability 96.1% and pricing 93.4%. Feature limitation complaints carried it only 57.4% of the time and interface complaints only 50.8%. The caveat: review data only sees churn that arrives with a complaint, and founders running exit interviews report that the largest real cause is silent disengagement, which leaves no review behind.
The most common complaint and the most dangerous complaint are different things, which is the central finding here. User experience is the most frequent complaint category in our data at over 5,000 instances, yet it sits near the bottom of the churn ladder at 67.5%. Service quality is roughly 35 times rarer at around 140 instances but carries a churn signal 98.6% of the time. Frequency measures what annoys people, not what makes them leave, so ranking a roadmap by complaint volume points you at the complaints customers tolerate.
It depends which kind of churn you are measuring. In our complaint data, user onboarding sits mid-ladder at 70.1% on roughly 100 instances, well below pricing at 93.4% or support at 96.7%, so among customers who complain it is not the leading cause. But onboarding is strongly implicated in silent churn, which our data cannot see: founders running real exit interviews report that never completing setup is one of the two most common reasons given. Onboarding failures make customers drift away quietly. Service, reliability and pricing failures make them leave loudly.
Much less than product teams assume. Feature limitations carried a churn-risk signal in only 57.4% of roughly 910 complaints, and user interface complaints in only 50.8% of roughly 310, the two lowest rates of any substantial category. The language gives it away: feature complaints read as preferences, such as "I wish we could arrange customers data by amount spent", while churn-risk complaints read as business damage, such as "this is damaging my business operations". People request features and then stay.
The overlap between lethal and buildable, which in our data is pricing, integration and cost management. We scored every complaint on both how often it carries churn risk and whether it represents a market opportunity. Service and reliability failures are the most lethal but score lower on buildability, because you cannot ship a feature that fixes another company's support team. Feature and UI gaps are highly buildable but well tolerated. Pricing sits at 93.4% churn risk and 91.9% buildability, integration at 83.6% and 91.6%, cost management at 91.4% and 85.5%.
The widely cited figure comes from Harvard Business Review's 2014 summary of research by Frederick Reichheld of Bain & Company, which found that increasing retention rates by 5% increases profits by 25% to 95%. The same piece notes that acquiring a new customer is anywhere from five to 25 times more expensive than retaining one, while explicitly hedging that it depends on which study you believe and what industry you are in. Treat it as a range that justifies prioritising retention, not as a law.
Only partially, and knowing the boundary is what makes it usable. Reviews capture churn that arrives with a complaint, so our ladder ranks the lethality of complaint types accurately but cannot size the population that leaves silently. Our churn flag is inferred from review text rather than an observed cancellation, so it measures stated intent rather than confirmed departure. Pair it with your own product analytics, which see silent disengagement but cannot explain it, because the two sources have almost exactly complementary blind spots. Our complaint analysis platform and comparison of complaint databases cover the review side, and MRR tracking tools cover the analytics side.
BigIdeasDB Research. (2026). Why SaaS Customers Churn: 39,000+ Complaints, Ranked by Exit Risk. BigIdeasDB. Retrieved from https://bigideasdb.com/why-saas-customers-churn