SAP Support & Maintenance Negotiation: Challenging the 22% Annual Cost That Never Shrinks
SAP's standard 22% annual maintenance fee is one of the most consistently overpaid costs in enterprise IT. This paper maps every cost reduction strategy — from third-party alternatives to SAP retention concessions — and delivers the negotiation playbook to reduce support costs whether you switch providers or not.
Executive Summary
SAP's annual maintenance fee — nominally 22% of net licence value — represents one of the largest recurring costs in enterprise IT. For a mid-sized SAP deployment with $20M in cumulative licence investment, the annual maintenance bill exceeds $4.4M. Over a decade, the enterprise pays more than twice the original licence cost in maintenance alone. And unlike most costs that face periodic scrutiny, SAP maintenance is typically renewed automatically, year after year, without substantive commercial review.
This paper challenges that default. It examines every available strategy for reducing SAP support costs — from internal optimisation through third-party alternatives to direct negotiation with SAP — and provides the tactical framework for executing each approach. The core finding: you do not need to switch to third-party support to reduce your SAP maintenance costs. You need SAP to believe you might.
The credible threat of third-party maintenance consistently unlocks SAP concessions of 15–30% that the standard renewal process never surfaces.
SAP has dedicated retention programmes (often branded as "Value Acceleration" or "Support Optimisation") that are only activated when an enterprise demonstrates genuine intent to explore alternatives. These programmes offer discounts, service credits, and commercial flexibility that are unavailable through normal procurement channels.
Third-party maintenance providers deliver equivalent break-fix support at 40–60% lower cost — but the decision carries strategic implications that extend beyond price.
Leaving SAP support means forfeiting access to enhancement packs, legal change patches, and the roadmap to S/4HANA. For enterprises on a clear modernisation path, this is a genuine constraint. For those with stable, mature ECC deployments, it is a cost with no corresponding value.
SAP's maintenance base calculation is inflated at most enterprises due to dormant licences, decommissioned modules, and legacy products that no longer provide value.
The maintenance fee is calculated as a percentage of net licence value — which includes every licence ever purchased, regardless of whether it is still in use. Cleaning the licence base before negotiating the rate compounds the savings.
RISE with SAP and the transition to S/4HANA Cloud are creating a one-time window where SAP is more commercially flexible on maintenance terms than at any point in the past decade.
SAP is incentivised to move customers to cloud subscriptions. Enterprises that leverage the RISE migration discussion as context for maintenance renegotiation have a uniquely powerful position — SAP wants the migration more than it wants to defend the 22% maintenance rate.
Fewer than 10% of SAP customers have ever conducted a formal support cost review. The remaining 90% are almost certainly overpaying.
The annual maintenance renewal is the most auto-piloted procurement decision in enterprise software. Even a basic review — licence base validation, utilisation assessment, and market comparison — produces actionable savings at virtually every enterprise.
The 22% Maintenance Model: How SAP Structures Support Costs
SAP's enterprise support model charges an annual fee calculated as a percentage of the customer's net licence value — the cumulative list price of all purchased SAP licences, net of any negotiated discounts applied at the time of purchase. The standard rate is 22% for SAP Enterprise Support, reduced from the original SAP Standard Support rate of 17% that SAP phased out through a controversial mandatory migration between 2008 and 2014.
What 22% Buys
SAP Enterprise Support includes several components: break-fix support (incident resolution through SAP's support portal and global support organisation), enhancement packs and feature packs (functional improvements delivered within the current release), legal change patches (regulatory and tax updates), security patches (vulnerability fixes), and access to SAP Solution Manager for system monitoring and lifecycle management. The service also includes defined SLA response times based on incident priority — from 1 hour for Priority 1 (business-critical system down) to 4 business days for Priority 4 (general inquiry).
The Value Gap
The fundamental question is whether these services deliver value proportionate to their cost. For a customer paying $4.4M annually in maintenance, SAP's support value proposition must justify that spend every year — not just the year the software was purchased. In practice, most enterprises use a narrow subset of the included services. Break-fix support is essential but represents a fraction of the fee. Enhancement packs are consumed selectively, if at all. Legal change patches are critical for some industries and irrelevant for others. The majority of the 22% fee subsidises SAP's R&D investment in new products — including products the customer may never adopt.
| Support Component | Included in SAP Enterprise Support | Included in Third-Party Support | Enterprise Usage (Typical) |
|---|---|---|---|
| Break-Fix Incident Resolution | Yes — SAP global support org | Yes — dedicated engineers | High — used by all customers |
| Security Patches | Yes — monthly patch cycle | Yes — custom patching | High — critical for compliance |
| Legal/Regulatory Updates | Yes — country-specific patches | Varies — custom development | Industry-dependent |
| Enhancement Packs | Yes — functional improvements | No — not available | Low — selectively adopted |
| S/4HANA Migration Rights | Yes — included in maintenance | No — forfeited | Future — not currently consumed |
| SAP Solution Manager | Yes — included | No — alternatives used | Low-Medium — often underutilised |
The Net Licence Value Problem
SAP's maintenance base includes every licence ever purchased — including licences for products that have been decommissioned, modules that were never deployed, and user types that have been over-provisioned. The maintenance fee compounds on a base that only grows. SAP does not proactively offer to reduce the base when products are retired. The customer must identify, document, and negotiate the removal of every redundant licence. This is an administrative burden that SAP's model exploits — most customers lack the visibility to even identify which licences in their base are no longer delivering value.
The Third-Party Maintenance Alternative
Third-party maintenance providers have established a credible alternative to SAP's own support offering, delivering equivalent break-fix and operational support at substantially lower cost. The market has matured significantly since its inception, with providers now supporting thousands of enterprise customers across all major SAP products and geographies.
Founded in 2005, publicly listed (RMNI). Supports SAP ECC, S/4HANA (limited), BW, CRM, SRM, and other SAP products. Pricing model: 50% of the annual SAP maintenance fee in year one, with no annual increases. Provides a named primary service engineer (PSE) model with direct access to senior technical resources.
Strengths: scale, geographic coverage (200+ countries), established legal position (survived SAP litigation), comprehensive tax and regulatory update service. Limitations: cannot provide SAP enhancement packs, S/4HANA migration path support, or SAP-delivered innovations.
Typical savings: 50% in year one, growing to 60%+ over time as SAP increases rates while Rimini holds pricing flat.
Founded in 2008, backed by Mainsail Partners. Supports all major SAP products including ECC, S/4HANA (limited), BW, and industry solutions. Pricing model similar to Rimini Street: approximately 50% of SAP maintenance with no annual escalation. Emphasises a white-glove service model with smaller client-to-engineer ratios.
Strengths: highly responsive service model, strong customer retention rates, flexible contract structures. Limitations: smaller scale than Rimini Street, narrower geographic footprint for on-site support requirements.
Typical savings: 50–60% depending on contract size and term commitment.
SAP's own support organisation, operating through global support centres and the SAP ONE Support Launchpad. Provides the full spectrum of support services including enhancement packs, legal patches, security updates, Solution Manager, and the pathway to S/4HANA and RISE. Staffing model relies on tiered support escalation through L1/L2/L3 teams.
Strengths: sole provider of enhancement packs and S/4HANA migration rights, deepest product expertise, regulatory patch coverage across all jurisdictions, integration with SAP's product roadmap. Limitations: highest cost, response quality varies by region and priority level, no dedicated engineer model as standard.
Annual cost: 22% of net licence value, subject to annual price increases on any new licence additions.
The Decision Framework
The third-party maintenance decision is not binary. It sits on a spectrum that ranges from full commitment to third-party support (maximum savings, highest strategic risk) through credible evaluation (moderate savings from SAP retention concessions, minimal strategic risk) to passive renewal (zero savings, zero effort). The optimal position for most enterprises is somewhere in the middle — leveraging a genuine third-party evaluation to extract SAP concessions while preserving the option to switch if SAP's response is inadequate.
The decision is fundamentally shaped by one question: what is your S/4HANA timeline? Enterprises with an active S/4HANA migration programme within the next 3–5 years face a genuine constraint — leaving SAP support complicates (though does not prevent) the migration. Enterprises with stable ECC deployments and no near-term S/4HANA plans have no such constraint. For this second group, third-party maintenance is a straightforward financial optimisation with minimal strategic risk.
Every SAP Support Cost Reduction Strategy
The landscape of SAP support cost reduction extends well beyond the binary choice of SAP versus third-party. The following strategies can be deployed individually or in combination, and their effectiveness compounds when multiple approaches are layered.
Licence Base Rationalisation
Reduce the net licence value on which the 22% fee is calculated. Identify and remove dormant licences, decommissioned modules, retired products, and over-provisioned user types from the maintenance base. This is a permanent reduction — every dollar removed from the base eliminates 22 cents of annual maintenance in perpetuity. Requires forensic licence inventory analysis and formal negotiation with SAP to accept the base reduction.
Third-Party Maintenance Migration
Transition from SAP Enterprise Support to a third-party provider for break-fix support, security patching, and tax/regulatory updates. Applicable to stable deployments with no near-term SAP upgrade path. Requires careful evaluation of which SAP services are genuinely consumed versus theoretically available.
Hybrid Support Model
Maintain SAP Enterprise Support for products on an active upgrade path (e.g., S/4HANA core) while migrating stable, non-strategic products (e.g., legacy BW, CRM, SRM) to third-party support. This preserves SAP's upgrade pathway for strategic products while capturing savings on the long tail of the licence portfolio. SAP contractually discourages this approach but cannot technically prevent it.
SAP Retention Programme Activation
Trigger SAP's internal retention programmes by demonstrating credible intent to evaluate third-party alternatives. SAP maintains structured retention offers — discounts, service credits, dedicated support engineers, premium SLA commitments — that are only deployed when a customer is genuinely at risk of leaving. The evaluation must be genuine; SAP's retention teams can distinguish real intent from posturing.
RISE Migration Leverage
Use the RISE with SAP migration discussion as a context for maintenance renegotiation. SAP's strategic priority is cloud migration — the RISE sales organisation has authority and incentive to offer maintenance concessions that facilitate the transition. Position maintenance cost reduction as a condition for RISE adoption, not a separate negotiation.
Support Level Downgrade
For products where enterprise-grade support is not required, explore whether SAP Standard Support (17%, where still available) or Product Support for Large Enterprises (PSLE) offers adequate coverage at lower cost. SAP does not advertise these options, and the availability varies by product and contract structure — but the conversation alone signals cost awareness.
Multi-Year Commitment Discount
Offer SAP a longer-term maintenance commitment (3–5 years) in exchange for a reduced annual rate. SAP values revenue predictability, and a multi-year commitment removes the annual renewal risk that drives their retention cost. This approach trades flexibility for price — appropriate when the enterprise has certainty about its SAP roadmap.
"You don't need to leave SAP support to reduce your SAP support costs. You need SAP to believe you're seriously considering it. The credible threat is worth more than the actual switch for most enterprises."Redress Compliance — SAP Practice
Third-Party Support Migration: Risk Analysis
Moving to third-party maintenance is not without risk. Understanding, quantifying, and mitigating these risks is essential to making an informed decision — whether the goal is an actual migration or a credible evaluation that drives SAP concessions.
Loss of Enhancement Pack Access
Leaving SAP support forfeits access to enhancement packs — functional improvements delivered within your current release. For enterprises actively consuming enhancement packs to extend functionality, this represents a genuine capability loss.
Assess Actual Enhancement Pack Usage
Most enterprises consume a small fraction of available enhancement packs. Audit which enhancement packs have been applied in the past 3 years and assess future requirements. If the answer is "few or none," this risk is theoretical rather than practical.
S/4HANA Migration Path Complexity
Third-party support customers who later decide to migrate to S/4HANA must re-enter SAP's support ecosystem, which may involve back-payment of maintenance fees or penalty pricing. The re-entry cost can partially or fully offset the savings accrued during the third-party period.
Model the Re-Entry Economics
Calculate the total savings from third-party support over the expected period, minus the projected re-entry cost. In many cases — particularly where the S/4HANA timeline is 5+ years — the net savings remain substantial even after re-entry. SAP's re-entry terms are negotiable, not fixed.
Regulatory & Legal Patch Coverage
SAP delivers country-specific tax, legal, and regulatory patches through its support programme. Third-party providers offer equivalent coverage for major jurisdictions, but coverage depth varies by country and regulatory domain. Enterprises operating in complex regulatory environments need to validate specific country coverage.
Validate Country-Specific Coverage
Request detailed regulatory coverage documentation from the third-party provider for every jurisdiction where you operate SAP. Compare against SAP's patch history for your specific systems. Most major providers offer contractual SLAs for regulatory update delivery.
Security Patch Methodology
SAP delivers security patches through its monthly Patch Tuesday cycle. Third-party providers cannot distribute SAP-authored patches — they develop custom security fixes using their own engineering resources. The question is whether custom patches provide equivalent protection.
Evaluate Patching Track Record
Review the third-party provider's security patching history: response times, coverage of critical CVEs, methodology for custom fix development, and customer references from security-sensitive industries. Mature providers have multi-year track records of equivalent security coverage.
The "Point of No Return" Myth
A persistent misconception is that leaving SAP support is irreversible — that once you switch to third-party, you can never return. This is not accurate. SAP allows customers to re-enter its support programme, typically with a back-payment requirement covering the period of absence. The re-entry cost is a financial calculation, not a technical barrier. Importantly, the re-entry terms are negotiable, and SAP's desire to bring customers back onto its support (and into the RISE pipeline) means re-entry conversations are increasingly commercially favourable.
The Negotiation Playbook: Reducing SAP Support Costs
Whether your goal is to switch providers, trigger SAP retention concessions, or simply rationalise the maintenance base, the following playbook provides a structured approach to reducing SAP support costs through commercial negotiation.
Audit the Maintenance Base
Conduct a forensic review of every licence in the SAP maintenance base. Identify dormant licences, decommissioned products, over-provisioned user types, and legacy modules that no longer deliver value. Quantify the over-payment: the difference between what you're maintaining and what you're actually using. This analysis produces immediate, defensible savings regardless of which strategy you pursue.
Evaluate Third-Party Alternatives
Engage at least one third-party maintenance provider in a formal evaluation. Request a proposal, conduct reference calls, and assess service coverage against your specific requirements. This evaluation must be genuine — not a paper exercise. SAP's retention teams will probe the depth of your engagement, and only a substantive evaluation triggers the retention response.
Signal Intent to SAP
Inform your SAP account team that you are conducting a formal review of support options, including third-party alternatives. Do not present this as a negotiation tactic — present it as a legitimate business decision driven by cost-value alignment. Request a meeting to discuss "support optimisation" and "commercial flexibility." These keywords activate SAP's retention protocols.
Present the Rationalised Base
Before discussing rates, present the licence base reduction proposal. SAP should be addressing two separate issues: the inflated base and the inflated rate. Sequencing is critical — if you negotiate the rate first, SAP will argue the base reduction wasn't part of the agreed terms. Base reduction first, rate negotiation second.
Negotiate the Retention Offer
SAP's retention offer will typically include a rate reduction (10–20%), service enhancements (dedicated support engineer, premium SLA, named account contacts), and possibly innovation credits for RISE or BTP evaluation. Evaluate the total value of the retention package against the third-party alternative. Push back on the initial offer — it is rarely the best available. Escalation to SAP sales leadership typically unlocks additional concessions.
Execute or Maintain Optionality
If SAP's retention offer meets your requirements, execute the renewed agreement with the rationalised base, reduced rate, and enhanced service terms — all documented contractually. If not, proceed with the third-party migration. In either case, establish a governance programme to prevent base inflation from eroding the savings over time.
SAP's Retention Tactics & How to Navigate Them
SAP has refined its customer retention programme over a decade of competition from third-party providers. Understanding these tactics — and their limitations — allows you to extract maximum value from the retention conversation while avoiding common traps.
The "Innovation Roadmap" Lock-In
The ECC End-of-Maintenance Deadline
The Audit Threat Escalation
The "Value Acceleration" Programme
The Conditional RISE Discount
Recommendations: 7 Priority Actions
The following actions provide a structured approach to SAP support cost reduction, ordered by implementation priority and designed to be actionable regardless of whether you intend to switch providers or negotiate improved SAP terms.
Audit Your Maintenance Base Before Your Next Renewal
Conduct a forensic review of every licence contributing to your net licence value. Identify dormant licences, decommissioned products, over-provisioned user types, and legacy modules. Quantify the maintenance overpayment attributable to the inflated base. This analysis produces permanent savings that compound with every subsequent year of maintenance — and it is a prerequisite for effective rate negotiation.
Conduct a Genuine Third-Party Support Evaluation
Engage Rimini Street, Spinnaker Support, or another third-party provider in a formal evaluation process. Request proposals, conduct technical due diligence, check references, and assess coverage for your specific SAP products and geographies. The evaluation must be genuine — it produces a costed alternative that either becomes your implementation plan or your negotiation leverage. Half measures produce half results.
Quantify Your Actual SAP Support Consumption
Analyse your support ticket history, enhancement pack adoption, patch consumption, and Solution Manager utilisation over the past 3 years. Calculate the cost-per-incident and the cost-per-service-consumed. Compare this against the total annual maintenance fee. The delta between what you pay and what you consume is the value gap — and it is the factual foundation for any cost reduction conversation with SAP.
Sequence Base Reduction Before Rate Negotiation
Present the licence base reduction to SAP before discussing the annual rate. Every dollar removed from the base eliminates 22 cents of annual cost permanently. Once the base is rationalised, negotiate the rate on the reduced foundation. This sequencing compounds the savings and prevents SAP from treating the base reduction as a concession that offsets rate flexibility.
Trigger SAP's Retention Programme with Credible Intent
Signal to SAP that you are formally evaluating support alternatives, including third-party maintenance. Provide enough specificity to activate the retention response — share that you've engaged a provider, conducted technical evaluation, and are assessing the commercial case. SAP's retention team will engage with offers that are unavailable through normal renewal channels. Push back on the first offer; it is the floor, not the ceiling.
Model the Re-Entry Economics for Your S/4HANA Timeline
If you're considering third-party support, model the complete financial scenario including savings during the third-party period, projected re-entry costs, and the impact on your S/4HANA migration timeline. For enterprises 5+ years from S/4HANA, the net savings are almost always positive even with re-entry. For those within 3 years, the calculus favours SAP retention negotiation over third-party migration.
Establish Annual Support Cost Governance
Do not allow the maintenance renewal to return to auto-pilot. Implement an annual review cycle: licence base validation, support consumption analysis, third-party market scan, and SAP relationship assessment. The review takes weeks, not months — and it prevents the gradual base inflation and rate creep that erode any negotiated savings over time.
How Redress Can Help
Redress Compliance's SAP Practice provides independent advisory on support cost optimisation — from maintenance base audits through third-party evaluation to SAP retention negotiation. We operate with zero vendor affiliations, no reseller agreements, and no commercial relationships with third-party support providers — ensuring our recommendations are driven by your commercial interests alone.
Maintenance Base Audit
Forensic review of your SAP licence base to identify dormant licences, decommissioned products, and over-provisioned user types contributing to inflated maintenance costs.
Third-Party Evaluation Support
Independent management of the third-party support evaluation process — provider selection, technical assessment, commercial comparison, and risk analysis — without commercial bias toward any provider.
SAP Retention Negotiation
Shadow advisory or active negotiation support for SAP retention conversations. We understand SAP's retention programme structure, the available concession levers, and how to escalate effectively for maximum impact.
Support Value Assessment
Analysis of your actual SAP support consumption — ticket history, patch adoption, enhancement pack usage — to quantify the gap between what you pay and what you consume.
RISE Migration Advisory
Integrated advisory for enterprises using the RISE transition as context for maintenance renegotiation — ensuring maintenance and RISE are negotiated as separate commercial tracks with aligned but independent outcomes.
Ongoing Support Governance
Annual support cost review programme to prevent base inflation, monitor consumption patterns, and maintain negotiation leverage for future renewal cycles.
100% Independent Advisory
Redress maintains zero commercial relationships with SAP, Rimini Street, Spinnaker Support, or any other support provider. We are not a reseller. We receive no referral fees. Our only commercial relationship is with you — ensuring our analysis and recommendations are always aligned with your interests, regardless of which provider or strategy delivers the best outcome.
Book a Meeting
Schedule a confidential consultation with our SAP Practice team. We'll review your current support costs and identify the most impactful reduction strategies for your specific situation.