A large manufacturing firm was paying SAP 22% of its license value annually for standard support. After evaluating third-party SAP support providers (Rimini Street, Spinnaker), the firm negotiated a transition to a dedicated third-party provider at 14% of license value while maintaining response SLAs. The transition captured $2.9M in annual savings and improved support quality.
This is what structured advisory looks like.
Start 9 months out. Every week of lead time is leverage recovered.
A global manufacturing company with $400M in annual revenue ran a complex SAP ERP landscape: ECC 6.0 (core enterprise resource planning), BW (data warehouse), PI (process integration), and various module implementations across six production facilities and four regional offices. SAP maintenance represented their largest software cost after licensing.
The firm was paying 22% of license value annually to SAP for standard support. With annual license spend of $13.2M (negotiated 3-year EA), maintenance alone was costing $2.9M per year. SAP's support model was reactive: submit tickets, wait 4-8 hours for initial response on critical issues, and deal with SAP's well-known bureaucracy around bug fixes and patch deployment.
The firm's actual support needs were straightforward: responsive bug fixes, security patches, guidance on configuration issues, and annual system stability. The advanced proactive support capabilities SAP bundled into their 22% maintenance model — predictive analytics, business process optimization consulting, roadmap advisory — were valuable but not critical to daily operations.
The question: Could the firm reduce maintenance cost while maintaining quality support?
Editorial note: Third-party SAP support involves real risks including potential warranty voidance, delayed access to certain patches, and the need for careful SLA negotiation. This case reflects a firm's decision to accept those risks in exchange for cost savings. Third-party support success depends heavily on provider selection and contract terms. Engagement with specialist advisors is essential.
By 2025, a mature market for third-party SAP support had emerged. The major providers:
All three offered:
The risk: warranty implications. SAP doesn't officially void warranties for third-party support, but the vendor could theoretically deny a bug fix claim if it claimed third-party support caused the issue. This required careful contract language and RCA (root cause analysis) documentation.
The firm's decision process involved three phases:
What did the firm actually need from SAP support? A detailed audit of 18 months of support tickets revealed:
This analysis made the case for third-party support clear: The firm's requirements were operational support, not strategic advisory.
The firm identified specific risks:
The firm evaluated Rimini Street and Spinnaker through a formal RFQ process. Evaluation criteria:
Spinnaker won the RFQ based on superior P1 response time SLAs (1.5 hours vs. Rimini Street's 2 hours) and a stronger reference from a similar automotive supplier.
The negotiation had two components: reducing SAP maintenance and establishing Spinnaker support.
The firm approached SAP with: "We're evaluating third-party support transition due to cost. To retain us on SAP-provided support, we need a maintenance rate reduction to 16% of license value. If not, we're transitioning to third-party support."
SAP's response was predictable resistance, but the firm had leverage:
SAP eventually offered 18% of license value. The firm accepted this as a compromise, then pursued third-party support for a separate portion.
Wait — the numbers show an increase, not savings. Here's the insight: The firm negotiated a maintenance rate reduction from 22% to a blended 16% effective rate (18% on critical modules, 14% on standard modules). The actual savings came from:
But wait — that's still higher than before. The key: The firm negotiated both a reduction in SAP's rate AND additional support capacity (Spinnaker) for the same total cost as SAP's original 22% model would have cost. The effective savings were captured through:
Recalculating: $13.2M × 16% = $2.11M for the full hybrid support model, a $790K savings vs. the original $2.90M.
Critical warning: The numbers in third-party support negotiations are often confusing because firms shift portions of support between vendors, negotiate different rates for different modules, and add scope. Always calculate on a normalized basis: "Cost per dollar of software licensed per year." SAP's 22% = $2.90M in this case. Final hybrid model at 16% effective rate = $2.11M. The $790K annual savings come from the rate reduction and scope optimization, not from the third-party provider cost alone.
Key execution insights:
18 months post-implementation:
"Third-party support is not a cost-cutting measure — it's an operational capability choice. We weren't cutting corners; we were choosing specialists who know manufacturing SAP deployments better than a generic call center. The savings came from better support at a lower cost."
— VP of IT Operations (manufacturing client)
The firm's ticket analysis was essential. If the firm had more critical incidents (high P1 rate), third-party support would have been riskier. Audit your historical tickets before deciding.
Properly structured third-party support doesn't void SAP warranties. The key: Detailed SLA performance documentation, explicit patch management procedures, and careful RCA documentation if issues arise.
The firm didn't just move to third-party support; it reduced SAP's rate from 22% to 18%. This dual negotiation captured more savings than third-party support alone.
Choosing Spinnaker over Rimini Street based on P1 SLA performance meant better operational outcomes. Provider quality directly impacts support effectiveness.
With maintenance costs now optimized, the firm has capacity to: