The Three Software Pricing Models
There are only three software pricing models underneath almost every enterprise contract, and confusing them is the most common reason buyers misjudge cost. A perpetual licence is a single up-front payment for the right to run a specific version of the software indefinitely. It is usually paired with an annual maintenance fee — conventionally 18 to 22% of the licence price — that pays for updates, patches and support; stop paying maintenance and you keep the software but lose the updates. A subscription replaces that structure with a recurring fee, billed monthly or annually, that bundles the licence, updates and support for as long as you keep paying. Stop paying and access ends. A usage-based (or consumption) model charges for what you actually use — active seats, API calls, tokens, workflows or agent runs — so the bill flexes with adoption rather than being fixed in advance.
The distinction matters because each model puts the financial risk in a different place. A perpetual licence front-loads cost and hands the buyer an asset that retains value even after support lapses. A subscription smooths cost into an operating expense but creates an open-ended liability that compounds through renewal uplifts. Usage pricing can be the cheapest of all for variable workloads, but it transfers forecasting risk squarely onto the buyer. Understanding which risk you are accepting is the starting point for the pillar discipline set out in our enterprise software pricing guide.
Total Cost of Ownership and the Breakeven
The headline question buyers ask — is subscription cheaper than perpetual? — has a precise answer only when you model total cost of ownership honestly. On a like-for-like, on-premise comparison, the perpetual licence plus its annual maintenance typically becomes cheaper than the equivalent subscription somewhere between year two and year five, with a widely used rule of thumb putting the crossover around the five-year mark. After that point the subscription is usually the more expensive option for software you intend to keep, and with subscription unit prices inflating near 12% a year, the gap widens with every renewal.
On a like-for-like comparison a perpetual licence plus maintenance usually undercuts the equivalent subscription within two to five years — and the gap widens every year after, because subscription renewal uplifts of 8–10% compound while a perpetual licence does not.
But the breakeven is not the whole story. A perpetual TCO must include the maintenance stream, the infrastructure to host and secure the software, and the cost of falling behind on versions if you ever drop maintenance. A subscription TCO must include every uplift across the term, not just year one. For fast-moving products — security tooling, anything with an AI roadmap — the always-current subscription can still deliver better value even when it costs more in cash terms, because a frozen perpetual version ages out of usefulness. The figures only mean something against current transaction data, which is why we treat benchmarking, covered in our guide to IT contract benchmarking, as inseparable from any model comparison.
| Model | Cost Shape | Where the Risk Sits | Best For |
|---|---|---|---|
| Perpetual + maintenance | High up-front, ~18–22%/yr after | Buyer owns obsolescence risk | Stable, long-life software |
| Subscription | Level recurring, +8–10%/yr uplift | Open-ended renewal exposure | Fast-evolving, cloud-delivered apps |
| Usage-based | Variable with consumption | Buyer owns forecasting risk | Spiky or experimental workloads |
Why Vendors Are Forcing the Shift
The move away from perpetual licences is a commercial strategy, not a technical necessity. Recurring revenue is worth far more to a vendor than a one-off sale: it is predictable, it raises the company's valuation multiple, it compounds through annual uplifts of 5 to 25%, and it sharply increases switching costs once a customer is embedded. That is why Adobe retired perpetual Creative Suite licences over a decade ago, why Autodesk and most major vendors have followed, and why Microsoft and its peers now place AI features behind consumption-metered add-ons rather than one-time purchases. The same logic drives the consumption pricing wave analysed in our guide to pay-per-use versus subscription.
For buyers, the lesson is that the model on the table reflects the vendor's revenue interests, not a law of nature — and that means the terms inside it are negotiable. Where a perpetual option still exists, it remains a legitimate lever even if you ultimately choose subscription, because the threat of buying perpetual changes the subscription discount the vendor is willing to offer. The disappearance of perpetual options is itself a form of price increase, and it should be priced as one when you assess a vendor's effective discount, the mechanics of which we cover in how vendors calculate your discount.
How to Negotiate Each Model
Each model has its own pressure point. For a perpetual licence, the licence price gets the attention but the maintenance percentage is where the long-term money sits — negotiate that percentage down from the default, and cap its annual increase, because an uncapped maintenance escalator quietly rebuilds the subscription you were trying to avoid. For a subscription, the single most valuable clause is a firm cap on the renewal uplift, ideally tied to a published index rather than the vendor's discretion; fix unit prices for the full term, and secure the right to reduce quantities at renewal so you can right-size rather than carry shelfware forward, a tactic covered in our work on the renewal versus replacement lever.
For usage-based pricing, the protections have to be in place before you sign, not after the first overage. Negotiate committed-use discounts in exchange for a baseline commitment, a hard cap on total spend, overage protection that prevents retroactive repricing of consumed units, and real-time monitoring with alerts before a threshold is breached. The governance discipline is the same one that controls cloud spend, and treating a consumption contract with that rigour turns a budget risk into an advantage. Across all three models, the underlying inflation trend — documented in our analysis of software inflation rates — is what makes a cap, not a one-off discount, the term that matters most.
Choosing the Right Model
The right model depends on the software's role and lifespan, not on vendor fashion. For stable, long-life systems that you expect to run unchanged for five years or more — and where you can host and secure them — a perpetual licence with a tightly negotiated maintenance cap is usually the lowest-cost path. For fast-moving, cloud-delivered applications where always-current matters, a subscription with a hard renewal cap is the pragmatic choice. For workloads that are spiky, seasonal or genuinely experimental, usage-based pricing with committed-use discounts and spend caps can beat both — provided you build the monitoring to keep it honest. Most large enterprises end up running all three across the portfolio, which is exactly why a single benchmarked, capped governance standard matters more than any one model decision.
Whatever the mix, the principle holds: the pricing model determines the shape of your cost curve, but the contract terms determine its slope. A subscription with an uncapped uplift is worse than a perpetual licence with a fair maintenance cap, and a usage deal without spend protection is worse than either. Our Price Benchmarking Report tracks effective pricing across all three models by vendor, and the SaaS contract optimisation practice applies it in live negotiations. To model the right pricing structure for a specific renewal against current benchmarks, request a confidential briefing.