Software maintenance and support fees represent one of the largest and most poorly negotiated line items in enterprise technology budgets. At 18–22% of licence value annually — and climbing — these recurring costs demand the same rigour as initial licence negotiations. Most organisations overpay by 20–40% because they treat maintenance as a fixed cost rather than a negotiable one.
This article is part of our IT Contract Negotiation Strategy guide. Software maintenance negotiation is vendor-specific in its tactics — for Oracle, see our dedicated Oracle support cost reduction guide; for SAP, see our SAP maintenance negotiation guide; for Broadcom/VMware, see our Broadcom support pricing guide. This article addresses cross-vendor principles and the general negotiation framework applicable to any enterprise software vendor.
Enterprise software maintenance and support fees are typically expressed as a percentage of net licence value (NLV) — the discounted price paid for the software licences — charged annually. For the major on-premise software vendors, this rate has been steadily creeping upward. Oracle standard support is 22% of NLV; SAP standard maintenance is 22% of NLV; Broadcom/VMware has moved to premium support tiers with no baseline equivalent.
The compounding effect of annual maintenance fees is dramatic. An organisation that paid £5m for Oracle licences in 2016 at a 22% support rate is paying £1.1m per year for support — and that rate is calculated on the original NLV, not the current market value of those licences. Ten years of support payments represent 220% of the original licence cost. Over a 15-year horizon, maintenance often represents the largest single cost item in a technology investment, dwarfing the initial licence spend.
What makes maintenance particularly difficult to negotiate is that vendors position it as a fixed policy. "Our maintenance rate is 22% — that's not negotiable" is the standard vendor response. This is not true for large accounts, but it takes deliberate strategy to move vendors off their published rate structure.
In a typical enterprise Oracle estate of £10m NLV, annual support costs at the standard 22% rate are £2.2m per year. Specialist negotiation advisors routinely achieve 15–30% reductions in net support cost through a combination of rate negotiation, NLV challenge, third-party support pressure, and cloud migration leverage — delivering savings of £330k–£660k annually on this profile.
Understanding the baseline maintenance rate structure and what is negotiable across the major enterprise software vendors is the starting point for any support cost reduction initiative.
| Vendor | Standard Rate | What's Included | Negotiable? | TPS Alternative? |
|---|---|---|---|---|
| Oracle | 22% of NLV | Bug fixes, patches, new versions, tax/regulatory | Rate: limited. NLV basis: yes | Yes — Rimini Street, Spinnaker |
| SAP | 22% of NLV | SNOTE patches, system upgrades, regulatory | NLV reduction achievable | Yes — Rimini Street, Spinnaker |
| Microsoft (SA) | 25–29% of licence value (via SA) | Version upgrades, cloud rights, training vouchers | EA structure gives indirect leverage | Limited — SA tied to upgrade rights |
| Broadcom/VMware | Premium Support 18–25% of subscription | Varies by tier; Active vs Premier tiers | Tier selection negotiable; rate limited | Limited for VMware-specific issues |
| Salesforce | Standard Success (bundled); Premier 30% uplift | Standard: community/docs. Premier: named CSM | Success Plan tier very negotiable at scale | Not applicable — SaaS platform |
| IBM | 12–25% depending on product | Bug fixes, PTFs, software subscription | Very negotiable for large estates | Rimini Street covers major IBM products |
Enterprise software maintenance is routinely oversold by vendors and underscrutinised by buyers. Before negotiating maintenance costs, it is essential to understand the actual value delivered by the maintenance contract — and how much of it your organisation actually uses.
What standard maintenance includes: Bug fixes and security patches applicable to your current version; regulatory and tax updates (payroll, VAT, statutory reporting); access to new software versions and major releases; access to the vendor's online support portal and knowledge base; and the right to log support cases with the vendor's support organisation. The scope of these inclusions varies significantly across vendors and versions.
What standard maintenance does not include: Implementation assistance for new versions or upgrades (typically charged separately as professional services); custom code support; training; significant product enhancements beyond the roadmap; and in many cases, the actual hands-on support that organisations need when encountering complex issues. Many enterprises discover that their maintenance fee entitles them to raise tickets that are then triaged to overloaded support queues with days-long response times.
Version currency and its impact: Maintenance on older software versions often provides significantly less value than on current versions. Oracle Sustaining Support (for products past Premier Support) provides no new fixes and no regulatory updates. SAP maintenance on legacy ECC is progressively limited as SAP focuses resources on S/4HANA. Organisations should audit the support entitlements for their specific product versions before assuming standard maintenance delivers the full package.
Before your next maintenance renewal, ask your IT team: "In the last 12 months, how many support cases have we raised? How many patches have we applied? Are we on a supported version that receives full maintenance entitlements?" For most enterprises, the answers reveal significant maintenance underutilisation — which is your negotiating position.
The existence of credible third-party support (TPS) providers is the most powerful structural lever in enterprise software maintenance negotiations. Companies like Rimini Street and Spinnaker provide support for Oracle, SAP, and other major enterprise software products at rates typically 50% below vendor rates — providing custom code support, faster response times, and coverage of multiple product versions simultaneously.
The leverage value of TPS extends beyond the cost saving: it fundamentally changes the negotiating dynamic by removing the vendor's monopoly on support. A buyer who has benchmarked TPS pricing and has the organisational approval to switch if the vendor does not move on rate is in a qualitatively different negotiating position than one who treats vendor support as the only option.
Effective TPS leverage requires: (a) genuine evaluation of TPS options, not just a threat; (b) internal stakeholder alignment that TPS is an acceptable strategic option; (c) a timeline that gives the vendor a credible competitive threat at renewal; and (d) awareness of the risks of TPS (Oracle's intellectual property challenges against Rimini Street have created some hesitation among buyers, though the court outcomes to date have been mixed).
The vendor response to a credible TPS threat typically includes: a maintenance rate reduction (typically 10–15% for Oracle; similar for SAP); an enhanced support tier upgrade at no charge; a shorter renewal term with a review right; and in some cases, professional services credits or cloud migration incentives. None of these are available to buyers who have not established TPS as a credible alternative.
Maintenance rate reductions are achievable through several mechanisms, each suited to different vendor relationships and negotiating contexts.
Net licence value challenge: Most maintenance fees are calculated as a percentage of NLV — but what constitutes NLV is often contested. Organisations that have divested business units, decommissioned applications, over-purchased licences historically, or have unused technology in their estate can challenge the NLV basis of their maintenance calculation. Reducing the NLV basis reduces the maintenance fee without requiring the vendor to change their published rate. This approach is often more achievable than a direct rate negotiation and can deliver equivalent savings.
Support tier rationalisation: For vendors that offer multiple support tiers (Standard, Enhanced, Premier), buyers often carry higher-tier support across products that do not require it. Downgrading to a lower tier on stable, low-touch products reduces total support cost without reducing support on mission-critical systems.
Migration incentive programmes: Oracle, SAP, and other on-premise vendors actively offer maintenance discounts as incentives for cloud migration commitments. A buyer willing to commit to a cloud migration roadmap — even with a 3–5 year horizon — can often leverage vendor-provided maintenance discounts as a "transition incentive." This works even when the migration commitment is genuine, as it sequences the benefit before the migration, reducing costs during the transition period.
Competitive renewal leverage: Organisations with significant multi-vendor estates — for example, companies running both Oracle and SAP — can use the negotiation process with one vendor to extract concessions from another. Signalling credibly that maintenance budget is limited and that decisions are being made about which platform to consolidate onto creates urgency in vendor support renewal negotiations that is not present in isolated product-level negotiations.
Ready to reduce your software support costs?
Our advisors have cut maintenance costs by 20–40% for enterprise clients across Oracle, SAP, and Microsoft — without disrupting support quality.
Support tier upgrades — where the vendor provides a higher-tier support package at the rate of a lower tier — are among the most accessible maintenance negotiation wins available to enterprise buyers. Vendors are often willing to provide tier upgrades rather than rate reductions because upgrades do not set a pricing precedent in the same way that published rate reductions do.
Enterprise buyers should understand what each tier actually delivers in the context of their specific usage patterns. Common improvements achievable through tier negotiation include: dedicated customer success managers (CSMs); named support engineers with product-specific knowledge; faster initial response SLAs (30 minutes vs 4 hours for critical issues); priority queue status; and proactive monitoring services.
Before accepting a tier upgrade as a substitute for rate reduction, buyers should evaluate: how frequently they use high-intensity support; whether the upgrade delivers services they would actually use; and whether the tier upgrade has any financial value relative to the alternative of rate reduction. In many cases, tier upgrades are most valuable as part of a package that also includes rate improvement, not as a standalone replacement for cost savings.
Beyond rate and tier, several contract terms materially affect the value and risk of a maintenance commitment.
Annual escalation cap: Maintenance fees that are not contractually capped will escalate at the vendor's discretion — and vendors routinely increase maintenance rates faster than inflation. Negotiate a contractual cap on annual maintenance fee increases (CPI or a fixed percentage of 2–3%) for the duration of any multi-year maintenance commitment.
Termination rights: Unlike licence agreements, maintenance agreements are often annual by default — but many vendors auto-renew them with insufficient notice periods. Ensure maintenance agreements include a clear right to terminate or downgrade with 30–60 days' notice, without triggering any penalty or loss of licence entitlements.
Version coverage: Confirm explicitly in the contract which product versions are covered by the maintenance agreement and for how long. Oracle and SAP both have support lifecycle policies that reduce coverage for older versions — ensure your specific versions receive the full coverage you are paying for, and negotiate extended support commitments if your upgrade cycle means you will be on a version approaching end-of-standard-support.
Response SLAs: Vendor support SLAs often specify response times by severity level, but the SLAs are rarely contractually binding with financial consequences for breach. Negotiate specific, financially-backstopped SLAs for Severity 1 (production down) and Severity 2 (significant impact) cases — and require that breach triggers a support credit rather than just a service review.
1. Start the maintenance negotiation 9–12 months before renewal. Maintenance renewal leverage is highest when the vendor does not yet have certainty that you will renew. Starting engagement 9–12 months out creates competitive urgency and gives your organisation time to genuinely evaluate TPS alternatives if the vendor is unresponsive.
2. Commission a maintenance audit before negotiating. Build a comprehensive picture of what you are paying for maintenance, what you actually use, and what your estate includes — including legacy products, decommissioned applications, and over-purchased licences. This audit is both the foundation for NLV challenge and the starting point for a rate negotiation conversation.
3. Introduce TPS as an evaluated option, not a bluff. Get a formal TPS quote from Rimini Street or Spinnaker. Share this with your vendor account team in a commercial discussion — not as a negotiating gimmick, but as evidence that your organisation has genuinely evaluated the alternative and is making a commercially informed decision. The credibility of the alternative is what drives vendor response.
4. Challenge the NLV calculation directly. Request a formal list of the products and licence quantities used as the basis for your maintenance fee calculation. Compare this against your actual deployed estate. Discrepancies — which are extremely common — provide a direct basis for maintenance reduction without requiring the vendor to change their rate policy.
5. Separate on-premise maintenance from cloud migration negotiations. Vendors will often try to bundle maintenance negotiations with cloud migration pitches. While there is value in cloud migration incentive programmes, do not allow the vendor to reframe your maintenance cost reduction negotiation as a cloud migration pitch — these are distinct commercial conversations with different leverage dynamics.
6. Use peer benchmarking data. Specialist negotiation advisors have visibility into what comparable organisations pay for maintenance across the same vendor platforms. Using peer benchmarking data — "organisations of our size typically pay X% of NLV for support" — provides an objective basis for rate negotiation that is more powerful than internal cost pressure arguments.
7. Negotiate extended version support before upgrading. If your organisation is approaching an end-of-standard-support date and has not yet upgraded, negotiate extended support terms before moving to the upgrade. Vendors are often willing to provide free or discounted extended support as an incentive to begin an upgrade programme — which is easier to negotiate before the deadline than after.
8. Disaggregate your maintenance estate. Large organisations often pay maintenance on products used across multiple business units with different strategic priorities. Disaggregating the estate — identifying which products are strategic long-term vs which are candidates for replacement or decommission — creates a basis for selective maintenance reduction on non-strategic products without touching the core estate.
9. Leverage the multi-year discount framework for maintenance. If you are willing to commit to a 2–3 year maintenance contract, use this commitment to negotiate a rate reduction or a cap on annual escalation. The vendor's desire for maintenance revenue certainty is as strong as their desire for licence revenue certainty — and it can be leveraged in the same way.
10. Document all commitments in the order form, not just the MSA. Maintenance terms negotiated verbally or confirmed only in email are frequently lost at the next renewal cycle when the account team changes. Ensure all negotiated maintenance rate reductions, tier upgrades, escalation caps, and version coverage commitments are documented in the signed order form or schedule to the master agreement.
Software maintenance is one of the most negotiable costs in your IT budget — and most organisations never negotiate it. Our advisors have a proven playbook for reducing support costs by 20–40%.