CRM Topped Vertice's Q3 2026 SaaS Cancellation Leaderboard at 19.8%. 95.5% of Those Contracts Were Supposed to Auto-Renew.

Procurement spend platforms sit on top of a lot of contract data that most SaaS vendors never see — not survey responses about how buyers feel about renewing, but what actually got canceled, by category, every quarter. Vertice runs one of those platforms, managing more than $75 billion in software spend across its customer base in 2026, and its Q3 2026 breakdown of cancellation rates by category puts one category well ahead of everything else it tracks: CRM.

That number alone would be a decent trivia fact. What makes it worth a closer look is a second figure sitting right next to it in the same report: 95.5% of CRM contracts in Vertice's dataset are set to auto-renew by default. Those two numbers shouldn't comfortably coexist. An auto-renewal default is supposed to suppress exactly this kind of churn — it's the entire mechanism behind why we've written at length about notice windows and cancellation friction elsewhere on this blog. CRM has more of that protection than almost any category, and it's still losing more contracts than anything else on the list.

What the Q3 2026 leaderboard actually says

Vertice doesn't publish the full methodology behind the number — it doesn't define the exact population of contracts or time window the percentage is measured against. What it does say is that the figures come from actual contract outcomes inside the spend it manages, not a survey of intentions. Treat it the way you'd treat any single vendor's internal data: directionally real, not peer-reviewed, and worth corroborating against your own category if you can.

Source: Vertice, "Most Canceled SaaS Tools," Q3 2026 category leaderboard.

Vertice is explicit, in its own FAQ for the report, that the CRM explanation "isn't confirmed by the underlying data" — it's their working theory, offered alongside the number, not a separate finding. That's worth taking at face value rather than dressing up as more certain than it is. And for Supply Chain & Logistics, Vertice doesn't offer a theory at all; we don't have a clean one either, and we'd rather say that plainly than invent a mechanism to fill the row.

The auto-renewal number that doesn't fit the story you'd expect

Here's the part that should surprise anyone who's internalized the usual logic around renewal friction: 95.5% of CRM contracts in Vertice's data default to auto-renew. That's a high number even by enterprise SaaS standards, and it means the overwhelming majority of CRM buyers who want to leave have to take an active, deliberate step to do it — send the notice, make the call, decline the renewal inside whatever window their contract specifies. Nothing about a CRM contract is making cancellation easy on paper.

If auto-renewal defaults worked the way inertia-based churn suppression usually works, CRM should be sitting near the bottom of this list, not the top. We've covered why defaults matter this much elsewhere — our piece on dark patterns in cancellation flows cites usability research showing friction measurably suppresses the decision to leave, and that's exactly the mechanism a 95.5% auto-renewal rate is supposed to be leaning on. CRM has that lever pulled about as hard as it goes, and buyers are still opting out of it more than they are for any other category Vertice tracks. The friction isn't failing. It's being overridden at an unusually high rate.

It's probably not the platform you think it is

The detail that makes Vertice's theory plausible, even uncertain as they say it is, is that "CRM" as a spend category almost never means just Salesforce or HubSpot. It means the core platform plus however many sales engagement tools, data enrichment subscriptions, dialers, forecasting add-ons, and reporting layers have been purchased on top of it, usually by different people, at different times, for different reasons. None of those individual purchases felt big when they were made. Collectively, they're exactly what a renewal review finds when it goes looking for redundancy.

This is the same mechanism we described in our piece on vendor consolidation churn: a procurement review doesn't ask "is this tool good," it asks "how many tools do we have in this category, and which ones can we cut without anyone really noticing." A core CRM platform is almost never the thing that gets cut — it's load-bearing, data lives in it, and replacing it is a migration project nobody wants to run. A sales engagement add-on that three reps use is a much easier line to strike. Enough of those get struck in the same quarter, and the category-level cancellation rate climbs even though the platforms everyone actually depends on didn't move at all.

If you sell into this layer — a CRM-adjacent tool rather than the CRM itself — your contract is also disproportionately likely to be seat-based, which compounds the exposure. We've written separately about how seat-based renewals shrink even when nobody formally cancels: a tool that three reps actively use inside a 40-person sales team can look fine on usage and still get zeroed out the moment someone asks whether it's worth keeping as a separate line item at all.

Office Management and Vertical Industry: the same pattern, a different cause

The second and third spots on the leaderboard — Office Management at 18.2% and Vertical Industry software at 16.7% — share a driver that's different from CRM's but just as structural. Vertice's explanation here is straightforward: both are categories where tools are commonly bought by individual teams or office locations rather than through a centralized process, which means duplication accumulates quietly until someone finally goes looking for it. A five-office company can easily end up running five slightly different versions of the same tool, purchased independently, each one invisible to the others until a consolidation pass puts them side by side.

That's structurally close to what we covered in our piece on shadow SaaS — software that accumulates through individual expensing and team-level purchasing decisions rather than a formal procurement process. The mechanism there was budget-policy enforcement catching up to spend nobody centrally tracked. Here, it's the same accumulation pattern, just caught by a scheduled category review instead of an expense-policy crackdown. Either way, the lesson for a vendor selling into this layer is the same: a healthy usage number inside one office or one team tells you almost nothing about whether the account survives a review that's comparing you against three other tools doing roughly the same job in three other locations.

What this means if you're the thing that gets cut

None of this says CRM or office-management tools are bad categories to sell into — they're large, durable markets precisely because the core use case is real and ongoing. What it says is that if your product sits above or beside a sticky core platform rather than being one, you're exposed to a review cycle that's faster and less forgiving than the one the platform itself gets, and a 95.5% auto-renewal default on the contract won't protect you from it, because the decision to leave is usually made well before the renewal notice window even opens.

A few things actually change the outcome here:

• Find out early whether your champion owns the renewal decision or just influences it. If a CRM add-on's renewal gets decided inside a broader tooling review, the rep who loves your product often isn't the one making the call — that's the same gap we cover in our piece on champion turnover, and it applies even when the champion hasn't left, just lost the authority to decide alone.
• Get your usage data in front of the reviewer before the review, not after. A consolidation pass defaults to cutting whatever doesn't obviously justify itself. If three reps use your tool daily and that's not visible outside the tool itself, make it visible — a one-page usage summary sent proactively beats a plea made reactively once the cut is already on a spreadsheet.
• Distinguish yourself from the platform's native feature, explicitly. Most CRM platforms ship a cheaper, weaker version of whatever your add-on does. The pitch that survives a review isn't "we're good" — it's a specific answer to "what do we lose if we just use what's built in," backed by something concrete your product does that the native feature doesn't.
• Treat an auto-renewal default as a notice-window problem, not a safety net. If your own contracts auto-renew with a 30-, 60-, or 90-day opt-out window, that's the real clock — see our piece on auto-renewal notice windows for how to find it in your own terms. A high auto-renewal rate buys you time to catch a cancellation in progress; it doesn't buy you immunity from one.

If you want a sense of what a category-level review actually costs you across your book, our churn calculator is a quick way to model a plausible cut rate — run your own renewal cohort through something in the 15-20% range this report suggests is normal for an exposed category, and compare it against what you're currently budgeting for churn. For most teams selling anything adjacent to a bigger platform, that gap is the argument for building the account-level visibility this section describes before the next review cycle, not after.

The accounts that do cancel anyway are still worth more to you after the fact than before — a cancellation flow that captures whether the reason was "replaced by a bigger platform's native feature" versus "not using it" versus something else entirely tells you which of these mechanisms is actually driving your churn, rather than leaving every CRM-adjacent cancellation lumped into one generic bucket. That's the same distinction CancelFlow's reason capture is built to make, and it's the difference between guessing at which category-level pressure is hitting your renewals and actually knowing.

Frequently asked questions

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.