SAP standard support runs at twenty two percent of the net license value annually. Three independent third party support providers price at half the rate. The decision turns on the roadmap, the audit posture, and the support coverage scope.
SAP charges twenty two percent of net license value annually for SAP Enterprise Support. Three established third party support providers price at eleven to twelve percent annually. The provider cost saving runs forty five to fifty percent.
The three providers are Rimini Street, Spinnaker Support, and Support Revolution. The choice turns on the SAP roadmap, the deployment footprint, and the audit posture. The choice does not turn on the price alone.
Read this article alongside the SAP knowledge hub, the SAP advisory practice, the SAP RISE Negotiation Guide, the Rimini Street SAP reference, and the Vendor Shield subscription.
SAP Enterprise Support is the default support program for ECC, S/4HANA on premise, BW, CRM, and SCM. The annual support fee runs twenty two percent of the net license value. The fee compounds at a five to seven percent annual uplift across most enterprise agreements.
| Tier | Rate | Coverage | Typical fit |
|---|---|---|---|
| Enterprise Support | 22% of net license | All products, SLAs, roadmap access | S/4HANA migration in plan |
| Standard Support | 19% of net license | Core products, longer SLAs | Legacy ECC on extended maintenance |
| Product Support for Large Enterprises | By quote | Custom SLAs, dedicated team | Top fifty SAP accounts |
| Third Party Support | 11% to 12% | Break fix, tax and legal, custom code | Stable ECC or S/4 footprint |
Read the SAP support order document. Confirm the support entitlement scope, the SLA tier, and the renewal uplift clause. Document the net license value baseline. The third party support price quote uses the same baseline as the SAP quote.
Three independent providers cover SAP at scale. Each provider runs a different commercial model, a different geographic coverage, and a different roadmap on tax and legal updates.
Request three proposals in parallel. Compare on price, coverage scope, tax and legal coverage, response SLA, custom code support, and geographic presence. The proposal comparison is a six column grid. The grid is the buyer side selection artifact.
The coverage gap between SAP standard support and third party support sits in three areas. New product releases, regulatory and legal updates outside the contracted countries, and security patch sourcing.
| Coverage | SAP Enterprise | Rimini Street | Spinnaker | Support Revolution |
|---|---|---|---|---|
| Break fix and L1 to L3 | Yes | Yes | Yes | Yes |
| Tax, legal, regulatory updates | All countries | Hundred plus countries | Forty plus countries | Thirty plus countries |
| Custom code support | Limited to standard interfaces | Full custom code coverage | Full custom code coverage | Full custom code coverage |
| New product releases | Yes, included | No, out of scope | No, out of scope | No, out of scope |
| Security patch sourcing | SAP Note channel | Independent patch creation | Independent patch creation | Independent patch creation |
| S/4HANA roadmap access | Yes | No | No | No |
The coverage gap is real but rarely material for stable footprints. The fix is to plan the third party support window. Move to third party support after the last major upgrade. Plan re entry to SAP support twelve to eighteen months before the next major upgrade.
The third party support window typically runs three to seven years. The re entry to SAP support carries a back maintenance fee that runs eighteen to twenty four months. The fee is negotiable when the customer carries a roadmap commitment to S/4HANA.
Plan the third party support window inside the broader SAP roadmap. The window unlocks fifty percent of the support spend for the duration. The window also unlocks the negotiation leverage on the next SAP commercial event.
SAP tightens the audit posture after a customer moves to third party support. The drivers include the loss of the standard support quarterly check ins, the loss of access to SAP system telemetry, and the contractual incentive on the SAP account team.
SAP audit teams treat third party support customers as priority targets. The audit fee schedule is the same. The audit findings tend to be larger. The buyer side fix is contract retention discipline, not third party support avoidance.
The decision turns on five factors. The roadmap, the deployment stability, the custom code estate, the geographic coverage, and the audit posture readiness. The framework runs as a five question decision tree.
The standard reseller pitch is that third party support is mainly a price play, a simple cut of roughly half on the support line. We disagree. In most evaluations we ran, the price was the easy part, and the real risk sat in the audit posture and the re entry math. SAP audit teams treat third party support customers as priority targets, and an undocumented contract turns a saving into an exposure. The buyer side move is to fix contract retention and the re entry path first, the same discipline that protects a RISE with SAP negotiation, and treat the price as the outcome rather than the goal.
The seven step checklist below is the buyer side starting position to evaluate SAP third party support.
The headline saving is 45 to 50 percent on the support line. SAP Enterprise Support prices at 22 percent of net license value annually, while the three established providers price at 11 to 12 percent. With the SAP renewal uplift stripped out, the cumulative five year saving often reaches 55 to 60 percent.
Yes, for on premise S/4HANA. Rimini Street, Spinnaker Support, and Support Revolution all cover the on premise estate, the legacy ECC estate, and BusinessObjects. Coverage for RISE with SAP and S/4HANA Cloud is limited, because the cloud deployment ties to the SAP cloud contract.
Access to new product releases, SAP Notes through the standard channel, and the S/4HANA roadmap documents stops. The provider creates its own patches, sources its own security updates, and runs its own knowledge base. That gap is rarely material for a stable footprint, but it blocks a live migration.
Yes, re entry is possible. SAP charges a back maintenance fee that typically runs 18 to 24 months of the standard support rate. The fee is negotiable when the customer brings a roadmap commitment to S/4HANA, so model the re entry math before the exit, not after.
The move itself does not trigger an immediate audit. SAP audit teams do treat third party support customers as priority targets across the audit cycle. The buyer side fix is contract retention discipline, license grant documentation, and a quarterly internal compliance review, not avoiding the move.
Rimini Street is the largest provider by SAP revenue and is publicly listed. Spinnaker Support is the engineering led option with deeper technical coverage on a smaller SAP footprint. Support Revolution is the European specialist with strong tax and legal coverage. Request all three proposals in parallel.
Move after the last major upgrade, when the footprint is stable for three to seven years. A migration in flight blocks the move, because the provider cannot give roadmap access. Plan re entry 12 to 18 months before the next major upgrade if one is coming.
Redress runs SAP third party support evaluations inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers the decision framework, the three provider proposal comparison, the contract retention exercise, the cumulative saving model, and the re entry path. Always buyer side, never SAP paid.
Redress runs SAP support evaluations inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The SAP commercial leadership sits with the founders.
Read the related benchmarking, about us, locations, and contact pages.
A buyer side reference on SAP commercial leverage, including third party support evaluation, the provider comparison grid, the re entry math, and the audit posture. Built from hundreds of SAP engagements.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying SAP estates. No SAP influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →Source: Redress Compliance advisory engagement file, 2024 to 2025.
SAP audit teams treat third party support customers as priority targets. The audit fee schedule is the same. The audit findings tend to be larger. The buyer side fix is contract retention discipline, not third party support avoidance.
We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.
Third party support evaluation, provider proposal comparison, re entry math, contract retention discipline, and the audit posture across every SAP engagement we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
