What Fair Maintenance Pricing Looks Like
The benchmark for software maintenance on traditional on-premise products is well established: 20 to 25% of the net licence price per year. Oracle and SAP Enterprise Support are both anchored at 22%, so a $1 million licence carries roughly $220,000 a year in support; SAP Standard Support sits a little lower, around 19%. That percentage buys patches, version upgrades and the right to log support cases. Whether it is fair, though, depends entirely on what you actually consume — for stable, mature software where you rarely raise a ticket or take a major upgrade, 22% a year is poor value, and it is one of the most negotiable and replaceable costs in the whole estate, as our enterprise software pricing pillar sets out.
The structural point buyers miss is that maintenance is priced as a fixed percentage of licence value, not as a function of the support you use. A heavily-supported, frequently-upgraded deployment and a stable system that has not changed in three years pay the same rate. That disconnect is where the unfairness lives, and recognising it — rather than treating 22% as a law of nature — is the first step to paying less, closely related to the over-payment patterns in our guide to vendor overcharging red flags.
Why the Fees Keep Climbing
Maintenance is not just expensive; it grows. Most support contracts contain an annual uplift — commonly around 3% in normal years and higher recently — applied to the fee regardless of whether you consume any more support than the year before. For vendors such as Oracle and SAP, this stream is strategically vital: support is high-margin, highly predictable recurring revenue, and the commercial incentive is to keep it compounding. Over a long deployment, a 3% uplift on a 22% base turns into a substantial and entirely passive cost increase for software that has not changed at all.
At 22% a year with a compounding uplift, support on a $1 million licence costs over $2.4 million across a decade — more than twice the original software — for a system that may not have changed at all.
The compounding is the same mechanism that makes uncapped renewal increases so damaging elsewhere, which is why the maintenance escalator belongs in the same category of contract term as a renewal cap — and should be capped the same way, using the language in our guide to price protection clauses. A maintenance fee you would never accept as a one-off lump sum is exactly what an uncapped escalator delivers, one quiet renewal at a time.
The Third-Party Support Alternative
The most powerful lever against unfair maintenance pricing is the existence of a market alternative. Independent third-party support providers commonly deliver immediate savings of up to 50% on annual Oracle and SAP maintenance fees, and up to 90% on total support cost over the longer term, frequently with faster response guarantees than the vendor's own service. Providers have committed to supporting mature releases — including SAP ECC and S/4HANA — for many years to come, removing the deadline pressure that vendors use to force upgrades and migrations.
| Support Option | Typical Annual Cost | Best For |
|---|---|---|
| Vendor support (Oracle/SAP) | ~22% of licence value | Frequent upgrades, new features |
| SAP Standard Support | ~19% of licence value | Lower-tier vendor option |
| Third-party support | ~50% less than vendor | Stable, mature, as-is software |
The trade-off is real: third-party support means no new vendor version upgrades or first-party patches, so it suits software you intend to run as-is rather than continuously evolve. For an organisation on a stable release with no near-term migration plan, it is one of the largest single savings available anywhere in the IT budget — and it interacts directly with the model decision in our guide to software pricing models, since only owned, perpetual software can move to third-party support at all.
Negotiating Maintenance Down
Even where you stay with vendor support, the fee is negotiable, and three levers do the work. First, cap the annual uplift in the contract rather than accepting an open escalator — the single most valuable maintenance term. Second, align the support renewal with a new purchase or the vendor's fiscal year-end, so more is at stake in one conversation and the vendor has reason to concede, the timing mechanism set out in our guide to a better deal at fiscal year end. Third, keep a credible third-party support alternative visibly on the table; even if you never switch, the fact that you could is what makes the vendor's own renewal negotiable, and the detailed playbook lives in our guide to negotiating software maintenance reductions.
The fourth lever is the simplest and most overlooked: do not pay maintenance on shelfware. Support is charged on licences whether or not you use them, so cancelling support on unused licences is an immediate, clean saving — one that the secondary-market option in our guide to software licence resale can extend further by recovering value from the licences themselves. Vendors will not prompt you to drop support on idle products; the reduction has to be raised proactively.
One trap deserves a specific warning: the matched-set rule that several vendors apply to support. Oracle, in particular, resists allowing a customer to drop maintenance on part of a licence set while keeping it on the rest, treating the licences as a single bundle so that partial cancellation forces repricing of what remains at a higher effective rate. The effect is to make right-sizing of support look uneconomic even when large parts of the estate are idle. The answer is to understand the rule before you buy — structuring licence purchases into separable sets where possible — and to model the repricing impact before cancelling, rather than discovering it after. Where the matched-set rule makes vendor support reduction impractical, the third-party route often becomes the cleaner path to the same saving.
Governing Support Over Time
Fair maintenance pricing is not won once; it is governed continuously. Treat support as a managed cost with its own annual review: reconcile what you pay against what you use, test the third-party market at each renewal, confirm the uplift cap is holding, and strip out support on any licence that has fallen idle. The vendors raising fees fastest are betting that maintenance is the line nobody scrutinises — a standing charge that renews on autopilot. Subjecting it to the same rigour as a new purchase is what turns a passive cost into a controlled one.
Across a large estate the cumulative effect is significant: capping uplifts, eliminating shelfware support, and using the third-party option as leverage routinely takes double-digit percentages off the annual support bill. Our Price Benchmarking Report tracks maintenance benchmarks by vendor, and the Oracle vendor hub details how support fees are structured and where they can be challenged. To benchmark and renegotiate a maintenance and support bill against fair-market terms, request a confidential briefing.