Subscription Fatigue Is Reshaping Consumer Software
Recurring pricing solved a real problem for software companies: revenue that arrives predictably rather than in launch-shaped spikes. It also created a quieter one for customers, who now hold a portfolio of small monthly charges that individually look trivial and collectively do not. The correction underway is not a rejection of subscriptions but a tightening of the standard they have to meet.
What changed on the buyer's side
Two things. Banking apps started categorising recurring payments automatically, making the total visible without effort. And enough people had the experience of paying for a year of something they used twice. Once the aggregate is visible, the evaluation shifts from "is this worth five a month" to "is this in my top ten". Consumer-side reporting on the trend, including the pieces at the market coverage on this site, describes the same behavioural shift across unrelated categories.
The models gaining ground
- Perpetual licence with optional paid upgrades — ownership plus a path to revenue
- Subscribe-to-own, where payments stop once the licence is fully paid
- Usage-based billing for tools used in bursts rather than daily
- Generous free tiers that convert on capability rather than time limits
What justifies recurring pricing
Anything with a genuine ongoing cost: hosted storage, synchronisation, live data, moderated communities, security updates against a moving threat. Customers accept those readily. What draws resentment is a subscription attached to software that runs locally and does not change, where the recurring charge protects revenue rather than funding anything. The distinction is obvious to users even when vendors pretend it is subtle.
Practical advice in both directions
If you buy software, run an annual audit and cancel anything you cannot name a use for from memory. If you sell it, make cancellation easy and unpunished — the churn you prevent by obstruction is the reputation you spend to keep it. And publish your pricing. A page that demands a sales call before naming a number is now read, correctly, as a signal about the number.