The Client Challenge: RISE with SAP at Inflated List Price
The client is a U.S. technology services firm with approximately 8,500 employees, 12,000 concurrent users of SAP systems, and a complex infrastructure spanning multiple environments: on-premises data centers, AWS, and Azure. The firm had been running legacy SAP ECC systems on-premises for over 12 years, with a mix of custom development, third-party extensions, and deep integrations into non-SAP platforms including Oracle Middleware, MuleSoft APIs, and Salesforce.
SAP sales engaged the firm in Q3 2025 with an aggressive timeline: migrate to S/4HANA as part of a RISE with SAP contract by the fiscal year-end deadline of December 31, 2025. SAP's positioning emphasized cloud-first architecture, simplified licensing, and integrated operations. The initial proposal: $5.2 million annually for three years, bundling infrastructure, database, SAP SLES support, S/4HANA licence, and BTP starter credits.
The client's procurement team flagged several concerns. First, the bundle combined infrastructure (which they could source competitively from AWS at lower rates), database licensing (already committed to on their own terms), and subscription fees into a single opaque price. Second, RISE locked them into SAP's cloud-exclusive model, eliminating the option to run certain workloads on-premises or via third-party providers. Third, SAP's annual support baseline for RISE was unclear—does it replace the historical 22% of net licence value model, or represent something different?
Understanding RISE with SAP: What's Actually Included
Before negotiation, the client needed clarity on RISE's scope. SAP markets RISE with SAP as an integrated offering, but the contract and billing line items reveal distinct components.
What RISE with SAP Includes (and Doesn't)
RISE with SAP bundles four core elements: infrastructure (compute, storage, networking on SAP-managed cloud), S/4HANA licence (the ERP system itself), SLES support (SUSE Linux Enterprise Server maintenance), and BTP starter credits (SAP Business Technology Platform, valued at approximately $3,000 to $5,000 per month for integration scenarios).
Critically, RISE does NOT include: migration costs (estimated at 15-25% of first-year licence spend), custom development work, implementation partner fees, premium BTP usage beyond the starter bundle, SuccessFactors if you add HR, Ariba if you add procurement, or any third-party add-ons. SAP's sales process often implies these are "included," but they are sold separately or consumed from the BTP budget.
The client's situation illustrates this gap. The firm planned to deploy custom integration modules post-migration, requiring 200+ hours of development work. SAP's initial quote treated migration as a separate line item ($800,000) and custom development as out-of-scope, leaving the client to engage a partner. In reality, the "RISE with SAP" price did not encompass the full cost of transformation.
The Licence Baseline Reset: S/4HANA Migration Changes Your Starting Point
A critical but underappreciated aspect of RISE negotiation is that S/4HANA migration resets the licence baseline. Under legacy ECC, the client was licensed on a traditional cost-plus-support model: licence fees plus annual support at approximately 22% of net licence value. S/4HANA represents a new system, with a new licensing footprint, metered usage, and different indirect access exposure.
SAP's implicit strategy is to use the migration as a point of contractual reset. The firm loses visibility into whether they're actually paying more for S/4HANA than they paid for ECC, because RISE bundles the comparison away. Was the client's ECC licence worth $1.8M annually, with support at $400K? Or was it $2.2M with support? RISE obscures this baseline, allowing SAP to embed margin escalation into the migration.
Additionally, S/4HANA's analytics capabilities, real-time processing, and cloud-native architecture change the indirect access surface. The firm's use of APIs to connect third-party systems triggers SAP's DDLC (Document and Data Licensing Compliance) metric—a critical concern we address below.
SAP's DDLC Metric: The Hidden Licensing Trap
Technology firms face unique SAP licensing risks. Unlike traditional manufacturing or retail environments, tech firms have extensive third-party system integration: APIs, webhooks, microservices architectures, and cloud-native patterns that access SAP data indirectly.
SAP uses the DDLC metric to quantify indirect access. DDLC measures the number of documents and data records accessed through non-SAP front-ends or APIs. If your MuleSoft integration layer queries 50,000 customer records daily to enrich a third-party system, those 50,000 accesses represent DDLC exposure. SAP can audit DDLC via logs, API telemetry, and database query patterns—and SAP's audits often claim significantly higher DDLC volumes than clients anticipated.
The client's environment was especially exposed: 12,000 concurrent users, plus API access from MuleSoft (customer data enrichment), Salesforce (order sync), and internal analytics platforms. Without a DDLC audit and explicit exclusion in the RISE contract, the client faced the risk of post-migration DDLC restatements, with retroactive licence adjustments.
Concerned about DDLC exposure or indirect access audit risk?
Our team has defended 80+ SAP indirect access disputes. Let's assess your environment.Negotiation Strategy 1: Bundle Decomposition
The first lever was to disaggregate the RISE bundle and price each component separately. This revealed why the $5.2M annual price was inflated.
Infrastructure Decomposition
RISE with SAP positions infrastructure as a managed service: SAP handles cloud operations, patching, disaster recovery, and performance optimization. For a firm of this size, SAP's infrastructure was quoted at approximately $1.8M annually (compute, storage, network, disaster recovery).
The client compared this to AWS Direct Connect pricing. For equivalent compute (16 x r6i.2xlarge instances), storage (8TB SSD + 50TB warm archive), and network bandwidth, AWS pricing was $1.1M annually—a 38% reduction. The client also retained the option to shift workloads to Azure or on-premises without incurring migration costs or licence penalties. SAP's managed service included value-adds (integrated monitoring, SAP-tuned performance), but the client's internal ops team could absorb these functions.
Negotiation outcome: The client successfully argued for infrastructure credits. Rather than accepting SAP's managed cloud, the client negotiated a RISE variant where SAP licenses S/4HANA and provides BTP credits, but the client self-manages infrastructure via AWS. The savings: $700K annually, allocated to license price reduction rather than infrastructure line items.
BTP Credit Allocation and Burn-Down
RISE with SAP includes BTP starter credits, typically valued at $36,000 to $60,000 annually (depending on contract language). BTP is SAP's platform-as-a-service offering, used for integration, extension, and analytics workloads. The client's MuleSoft and Salesforce integrations could theoretically run on BTP instead of external platforms.
However, the client's negotiating insight was that BTP credits are often not fully utilized. Firms use MuleSoft (already licensed), Salesforce (already cloud-native), and internal Kubernetes clusters for integration—leaving BTP credits unused, effectively gifting them to SAP as margin. The client proposed: allocate BTP credits explicitly to measurable integration projects, with any unused credits applying as a discount to the base licence fee rather than carrying forward to future years. This single clause shifted $180K in annual credit value from SAP's future optionality to the client's immediate cost reduction.
Negotiation Strategy 2: FUE Volume Tiers and Per-FUE Rate Negotiation
RISE with SAP pricing often uses a Full Use Equivalent (FUE) metric to scale licence costs with concurrent users. The client's 12,000 concurrent users translated to approximately 3 FUEs under SAP's metric (assuming 4,000 users per FUE). SAP's initial quote was roughly $1.7M per FUE annually for S/4HANA + support.
Challenging the FUE Baseline
The client requested SAP itemize the FUE calculation and defend the 4,000-user-per-FUE ratio. SAP's response referenced customer benchmarks and industry standard density. The client countered with data from its own SAP environment: ECC sustained 12,000 users on fewer named users than SAP was proposing for S/4HANA, because concurrent usage patterns were heavily time-zoned and role-differentiated. North American users (40% of base) were active 9am-5pm Eastern; international users (25%) worked in different zones; contractors and partners (35%) used the system only for specific transactions.
Through log analysis, the client demonstrated that true peak concurrent usage was closer to 8,000 users at any given moment, not the 12,000 nominal count. This supported a revised FUE calculation: 2.3 FUEs instead of 3.0 FUEs. While SAP resisted, the client's data-driven approach (supported by independent benchmarking) moved SAP to a 2.5 FUE compromise.
Tiered Pricing and Discount Negotiation
With 2.5 FUEs confirmed, the client negotiated tiered pricing. SAP's standard model charges a flat per-FUE rate. The client proposed a volume-tiered approach: FUE 1 at full rate ($1.7M), FUE 2 at 15% discount ($1.445M), FUE 2.5 at 20% discount ($1.36M). The cumulative effect: $4.205M for 2.5 FUEs instead of $4.25M for 3.0 FUEs—a modest savings but combined with other levers, material.
Negotiation Strategy 3: Fiscal Year-End Timing and Competitive Pressure
SAP's fiscal year ends December 31. Enterprise sales are under maximum pressure in Q4 to close deals before year-end, especially large RISE with SAP deals which carry higher ARR (annual recurring revenue) targets. The client's timing was intentional: engage SAP in late October 2025, establish negotiations, and use the December 31 deadline as leverage.
The Workday and Oracle Competitive Advantage
The client's procurement team ran parallel RFQs with Workday and Oracle Cloud ERP. Neither was a perfect replacement (Workday excels in HR and financials but lacks the supply chain depth; Oracle is strong in procurement and global finance but weaker in manufacturing modules), but both demonstrated credible alternatives. The client shared (selectively) that Workday's all-in cost for the finance and HR use cases was approximately 60% of SAP's RISE quote, and Oracle Cloud ERP's cost for supply chain modules was approximately 70% of SAP's position.
These competitive offers did not change the client's commitment to SAP (their core supply chain, manufacturing, and distribution systems required SAP's depth), but they provided negotiating leverage. SAP's Q4 sales team faced a choice: accept a compressed margin deal at list price or risk losing the account entirely to competitive migration. The competitive dynamics compressed the final negotiation from 8 weeks to 3 weeks, accelerating SAP's concession timeline.
Negotiation Strategy 4: Hybrid Flexibility and Workload Optionality
The initial SAP quote tied the client exclusively to SAP's cloud infrastructure, eliminating the option to run certain modules on-premises or on third-party clouds without incurring additional licensing or penalty fees.
Negotiating the Hybrid Clause
The client proposed explicit carve-outs: three specific modules (Manufacturing Execution System, Legacy Supply Chain Dashboard, and a custom Analytics Layer) would continue running on-premises SAP infrastructure, maintained by the client's IT team, without triggering additional RISE fees. SAP's standard position is that all RISE systems must run on SAP-managed cloud, but the client negotiated an exception: as long as the on-premises environment remained isolated from the SAP cloud systems (separate network, no real-time bidirectional sync), the licensing applied only to data access through the primary cloud instance.
This preserved the client's flexibility. If AWS infrastructure costs rose, the client could migrate back to on-premises. If a third-party vendor offered a cheaper alternative (e.g., a specialized manufacturing execution cloud platform), the client could adopt it without SAP licensing penalties. The hybrid flexibility clause added negligible cost to SAP but delivered significant strategic optionality to the client.
Annual Support and the 22% Baseline
Under traditional SAP licensing, annual support is approximately 22% of net licence value—a standard metric across the industry. The client sought clarity on whether RISE's subscription model replaced or supplemented this 22% baseline. SAP's response: RISE is a unified subscription, and support is embedded in the per-FUE annual charge. However, SAP did not itemize the support component separately, leaving ambiguity about whether post-contract support escalations would carry the 22% uplift or remain fixed to the current subscription rate.
The client negotiated an explicit cap: annual support adjustments (e.g., for additional modules or premium support tiers) would be capped at 3% annual inflation, rather than SAP's standard escalation of 5-7%. This protection matters in year 3 and beyond, as small percentage differences compound.
The Negotiated RISE with SAP Contract: What Changed
The final negotiated contract reduced the client's total three-year commitment from $15.6M ($5.2M x 3) to $9.3M—a 40% reduction. Breaking down the changes:
- Infrastructure Carve-Out: Client manages AWS, SAP licenses S/4HANA only. Savings: $700K annually x 3 = $2.1M
- FUE Optimization: 2.5 FUEs instead of 3.0, with tiered pricing. Savings: $45K annually x 3 = $135K
- BTP Credit Reallocation: Unused credits apply to base fee reduction. Savings: $180K annually x 3 = $540K
- Support Cap: 3% annual escalation vs. standard 5-7%. Year 1 savings: $0, Year 2: ~$60K, Year 3: ~$120K. Total: $180K
- Competitive Discount: Q4 sales urgency and competitive offers yielded 5% base price reduction. Savings: $260K annually x 3 = $780K
Total three-year savings: $3.735M. The client negotiated the contract from $5.2M annually to $3.1M in Year 1, with a 3% cap on annual escalation, bringing the three-year total to $9.3M.
DDLC Audit Protection and Indirect Access Safeguards
Throughout the negotiation, the client's team raised SAP's DDLC metric and the risk of post-migration indirect access restatements. The client negotiated explicit DDLC baselines in the contract: SAP agreed to conduct a pre-migration DDLC audit (measuring current-state indirect access), document the baseline in the contract, and cap any post-migration DDLC restatements to measurable changes in the client's integration footprint (e.g., new API connections, expanded third-party syncs).
This protection matters because SAP's audit methodology can be aggressive. Without contractual caps, a DDLC audit post-migration could claim 50% more indirect access than the client anticipated, triggering licence restatements and retroactive fees. The client's contractual baseline protects against this risk.
Critical Learnings: What This Case Reveals About RISE Negotiation
Bundle Decomposition Is Non-Negotiable
RISE's bundled pricing obscures cost comparisons and locks clients into SAP's preferred infrastructure. Technology firms should always demand line-item breakdowns and compare infrastructure costs to AWS, Azure, and on-premises alternatives. The 35-40% infrastructure overpayment in this case is typical for firms accepting RISE's all-in positioning.
FUE Calculations Are Debatable
SAP's FUE ratios often rest on benchmark data from SAP's largest, most resource-constrained customers. Smaller firms with concentrated usage patterns or global distribution (where peak concurrent use is time-zoned) can justify lower FUE counts with supporting data. This client saved 17% on FUEs ($300K+ over three years) through rigorous log analysis and negotiation.
BTP Credits Have Real Optionality Value
BTP is positioned as "free" integration platform within RISE, but most clients don't use it. Redirecting unused credits as direct price reductions is a clean negotiating win that SAP will often accept, especially if the client commits to higher S/4HANA adoption or longer contract terms.
S/4HANA Migration Resets the Baseline—Document Your ECC Starting Point
The licence baseline shift from ECC to S/4HANA is the implicit leverage point in RISE negotiations. Clients who can document their ECC licence spend, support costs, and usage patterns have stronger negotiating positions. Without this baseline, SAP controls the narrative of "fair" pricing.
SAP's Fiscal Year-End Is Your Leverage Point
December 31 is SAP's fiscal year-end. Q4 sales pressure is real, especially for large RISE with SAP deals. Clients negotiating in October-November have materially better outcomes than those negotiating in Q1. The timing alone created 15-20% price improvement for this client.
Hybrid Flexibility Clauses Protect Against Vendor Lock-In
RISE's cloud-exclusive model is a feature for SAP, not the client. Negotiating the right to run specific workloads on-premises or on third-party clouds (with clear isolation requirements) preserves strategic optionality without additional licensing cost. This protection becomes critical if infrastructure costs escalate or if SAP's pricing becomes uncompetitive in years 2-3.
Conclusion: How 40% RISE Savings Is Achievable
The client achieved a 40% discount on RISE with SAP not through aggressive negotiation tactics or threats, but through disciplined analysis, competitive positioning, and timing. The firm:
- Decomposed the RISE bundle to expose infrastructure overpayment
- Used FUE log data to challenge SAP's concurrent user assumptions
- Redirected unused BTP credits as direct price reductions
- Leveraged Workday and Oracle competitive RFQs without committing to alternative vendors
- Engaged SAP in Q4 when fiscal year-end sales pressure peaks
- Negotiated explicit carve-outs for hybrid deployment and DDLC baselines
- Capped annual support escalation at 3% instead of accepting SAP's standard 5-7%
These strategies are available to any mid-market technology firm negotiating RISE with SAP. The specific 40% discount in this case reflects the client's strong negotiating position (credible alternatives, clear infrastructure alternatives, and timing at SAP's fiscal year-end), but 25-35% discounts are achievable across most enterprise environments.
Critically, the client preserved operational flexibility: the hybrid deployment option ensures that if infrastructure costs or SAP's pricing becomes uncompetitive, the client can migrate workloads or shift to alternative vendors without incurring penalties. This optionality is not "free" in RISE negotiations—it requires explicit contractual language—but it is absolutely worth the negotiating effort to secure.