The 22% Nobody Negotiates
Annual maintenance is the most overlooked line in the enterprise software budget, and the most negotiable. The industry standard set by Oracle and matched by SAP is 22% of net licence value every year — meaning that over a five-year horizon you pay for the software roughly twice again in support alone. Because it arrives as a predictable annual renewal rather than a one-off purchase, most organisations pay it on autopilot. That habit is expensive: vendor margin on annual support typically exceeds 90%, so the fee bears almost no relationship to the cost of delivering the service. A maintenance line that large, that profitable and that routine is precisely the kind of spend that rewards a deliberate pushback.
What You Are Actually Paying For
Maintenance bundles three things: the right to new versions and updates, security patches, and access to vendor support. The reduction case begins with an honest audit of how much of each you actually consume. Many enterprises run stable, mature releases years behind the current version, take few if any major upgrades, and log a handful of support tickets a quarter — yet pay full 22% maintenance on the entire estate, including licences that are shelfware. Quantifying real consumption is the foundation of every lever that follows, and it mirrors the utilisation discipline that drives every good renewal.
The Reduction Levers
Several levers reduce maintenance without changing vendors. The first is capping the escalator: support fees commonly rise 4% or more each year, and negotiating a fixed cap or CPI link removes a compounding cost. The second is decoupling maintenance from new licence purchases — vendors routinely tie a discount on new licences to maintaining support on the whole estate, and separating the two lets you reduce one without forfeiting the other. The third is removing maintenance on shelfware: you cannot always drop support on a subset of licences under a single agreement, but where licences can be segregated or terminated, the associated maintenance goes with them. The fourth is matching support tier to need — paying premium 24/7 support on a system that runs business hours only is a common, avoidable overspend.
A fifth lever is timing the reduction to the licence negotiation itself. Maintenance is calculated on net licence value, so every pound you remove from the licence baseline at renewal — through right-sizing, tier downgrades or dropping shelfware — reduces the maintenance base permanently, year after year. This compounding effect is why the maintenance conversation must run alongside the licence negotiation rather than as a separate annual renewal: a 20% reduction in the licence baseline is also a 20% reduction in every future maintenance bill, and capturing both in one negotiation is far more effective than attacking the support line in isolation.
| Support option | Typical annual cost | Best suited to |
|---|---|---|
| Full vendor maintenance | 22% of licence value | Estates taking frequent major upgrades |
| Capped vendor maintenance | 22% with fixed/CPI escalator | Stable estates wanting vendor patches |
| Third-party support | ~50% of vendor fee | Mature, stable releases not upgrading |
| Self-support / community | Internal cost only | Non-critical or end-of-life systems |
Third-Party Support as a Lever
The most powerful maintenance lever is the credible option of leaving vendor support altogether. Independent providers typically deliver support at around 50% of the vendor's annual fee, with total-cost-of-ownership reductions reported up to 90% once you factor in the upgrades you were funding but not using. The strategic value is not only the saving; it is that a documented third-party support evaluation reframes the vendor renewal entirely, because the vendor's 90%-plus margin gives it enormous room to discount when the alternative is losing the maintenance stream completely. Third-party support suits mature, stable releases that are not pursuing major upgrades; it is less appropriate where you depend on the vendor's newest features. Either way, building the evaluation is what turns a fixed-looking fee into a negotiable one — the same renewal-versus-replacement logic set out in our renewal-versus-replacement guide.
Be realistic about what a third-party move involves so the threat stays credible. Independent support typically matches or exceeds vendor response times for break-fix and tax-and-regulatory updates, but it does not provide new product versions, and it changes how you handle security patching, since you no longer receive the vendor's own fixes. For a mature ERP estate that is not pursuing major upgrades, that trade is often clearly worthwhile; for a fast-moving platform whose newest features you actually use, it may not be. The point of building the evaluation is not always to switch — it is to know precisely what switching would cost and gain, because only a buyer who genuinely could move negotiates the vendor renewal from strength.
You are not negotiating against the cost of support — you are negotiating against a 90%-plus margin. That margin is the room the vendor has to move, and a credible third-party option is what forces it to.
The Reinstatement Trap
Before dropping or reducing vendor support, read the reinstatement clause — this is where vendors recapture leverage. Oracle and SAP agreements typically impose steep penalties to rejoin support after a lapse, often requiring payment of all back-maintenance for the gap period plus a reinstatement fee that can exceed 150% of the avoided fees. The clause is designed to make leaving feel irreversible. It is manageable, but only if you understand it before you act, which is one more reason to read these terms with the care we describe in reading a software contract and to fold maintenance into a broader audit and compliance review rather than treating it in isolation.
Sequencing the Approach
Sequence the reduction like any negotiation. Start with the utilisation and consumption audit to establish what you actually use. Benchmark the fee against market rates using data such as our price benchmarking report. Develop the third-party support evaluation as a credible alternative. Then present a written position to the vendor that pairs a capped, decoupled, right-sized maintenance proposal with the explicit alternative of moving away. Introduce the third-party option after the vendor's first response, not before, so it lands as a considered escalation. To benchmark your maintenance spend or build the third-party evaluation on your behalf, request a confidential briefing.