S/4HANA RISE: What SAP Won't Tell You in the Sales Deck

The hidden costs, hidden benefits, and what to actually negotiate in your RISE contract. The move most architects never make, and the three hidden costs that surface at go-live.

#sap#s4hana#rise

Sarah, a CIO at a mid-size manufacturer, signed a RISE contract in December. Beautiful six-month sales cycle — polished demos, executive alignment sessions, a TCO model that made the CFO nod. By March, three months after go-live, I was in a conference call helping her explain to her board what had gone wrong.

The infrastructure was sized for 500 concurrent users. They had 2,000. Month-end close — a four-hour window where the business is effectively running blind if the system is slow — became a performance disaster. Jobs that had run in 20 minutes were taking 90. The finance team was calling the help desk. The CIO wanted names. And the number that kept coming up was: why didn't anyone check the actual concurrent usage before signing?

That wasn't the only surprise. The BTP consumption they'd assumed was bundled had its own separate line item. The SAP integration scenarios they'd planned required capacity above what the bundle included — nobody on the account team had flagged it as an exception. And the 400-plus custom ABAP objects they'd accumulated over 15 years of ECC? Needed full remediation before the migration could actually begin. Scope that hadn't been estimated, let alone budgeted.

I've been the person called in to figure out what went wrong on more than one of these. Let me tell you what you need to know before you sign — and the one negotiation move most architects never think to use.

The Move Most Architects Never Make

Even if you are fully committed to SAP — even if Azure or Google Cloud is genuinely not on the table — get a competing quote from Azure (SAP on Azure) or Google (SAP on Google Cloud) before you sign RISE. I have personally used this in negotiations. Not as a bluff. As a concrete alternative with different BTP bundle terms on paper. "We have an alternative quote with expanded integration capacity" is a fundamentally different conversation than "we'd like more BTP credits." The best RISE deals I've observed had at least one competing quote on the table when the commercial terms were finalized. Get one. It costs nothing but a few calls and it's worth six figures.

Pre-signature leverage: right-sizing review at 6 months, BTP capacity top-up, clean core tooling. Retroactive re-tier is a no — get it in writing now.

What RISE Actually Includes (the short version)

S/4HANA Cloud Private Edition license. Infrastructure hosting — SAP manages the cloud layer, you manage the application. SOLA support. A BTP Basic bundle: Integration Suite at limited capacity, Extension Suite at limited capacity, Event Mesh. Embedded support is in. Premium engagement is not.

The BTP bundle is scoped for connecting SAP systems to each other. If you plan to build custom extensions, run high-volume third-party integrations, or use AI services at any real scale, you will hit the ceiling. How fast depends on your integration architecture — but I've seen customers hit it inside 90 days on a moderately complex landscape. Map your actual endpoints and message volumes against the bundle capacity before signing. It's a two-hour exercise that prevents a six-figure line item in year one.

BTP Bundle Limit: What the Contract Doesn't Itemize

The base RISE contract states BTP Integration Suite is "included." It does not state the message volume ceiling, the number of concurrent runtime instances, or which integration scenarios count against that cap. Customers discover the ceiling when they hit it. The fix is pre-signature: request the explicit capacity allocation in writing, measured in million API calls/month and number of integration flows. If SAP won't put a number on it, that number is negotiable — use it.

The Three Hidden Costs

Contract review: BTP "included" with no volume ceiling. 47 endpoints = 12M API calls/month. 80 deep core mods = $4M remediation.

The Three Hidden Costs

1. Infrastructure Sizing

RISE contracts set your infrastructure tier at signing, based on your current license count. License count and actual concurrent usage are often very different numbers. The people who sign the contract know the license number. They don't know to pull SM66. Go into your current system, pull the workload monitor, look at 12 months of peak concurrent sessions. Not averages — peaks. Month-end close, quarter-end, the last Friday before a holiday. If your peak hits 1,800 and you're signing for 500, you will have this conversation in a conference call three months after go-live. Know the number before you're in the room.

The number you don't know: SM66 peak concurrent sessions. 2,000 in production, 500 on the contract. That gap costs real money.

Infrastructure Tier: No Auto-Remediation Clause. Standard RISE contracts set the infrastructure tier at signing and do not include an automatic right-sizing review. If you are undersized at go-live, the process for remediation is a commercial negotiation — not an SLA response. The fix: negotiate a written right-sizing review right at 6 months post go-live, with a defined escalation path and SLA for SAP response. Without this in the contract, "we'll look at it" means nothing after signature.

2. BTP Consumption Beyond the Bundle

I've covered this above, but it gets its own entry because I see customers hit it independently of the general BTP discovery — usually when a specific integration scenario surfaces during implementation that nobody scoped against the bundle. The fix is explicit architecture: not "we'll use Integration Suite" but "we have 47 integration endpoints, here is their average daily message volume." Then you check that against the included capacity and you know exactly what you're buying. Anything that doesn't fit gets negotiated as an add-on before signature, not funded as an emergency line item six months in.

3. Custom Code Remediation

RISE assumes clean core. Your ECC landscape almost certainly isn't. Before any RISE conversation, run the ABAP Test Cockpit. Know your custom object count and have a rough classification: which objects are business-critical modifications you genuinely need, and which are 15-year-old copies of SAP standard code that nobody has touched since the original implementation. Remediation cost estimates vary wildly — I've seen $200k and $4M on similarly-sized landscapes, and the difference comes down almost entirely to the composition of the custom code, not the quantity. A landscape with 600 lightweight enhancements is a different problem than one with 80 deep core modifications. Know which you have before the implementation partner quotes you after signature.

RISE contracts are signed by procurement. Architects need to be in the room before signature — not called in to explain what happened after.

What You Can Actually Negotiate

SAP is significantly more flexible pre-signature than post-signature. This is not a secret, but it is widely underestimated. Here is what I have personally seen successfully negotiated, in contracts that were initially presented as standard:

The move: "We have an alternative quote with expanded integration capacity." That's a fundamentally different conversation than "we'd like more BTP credits."

What's Actually Negotiable — Pre-Signature

Contract term flexibility. A shorter initial term with defined renewal terms, particularly for customers willing to commit to a longer-term relationship in principle. SAP will do this. Ask for it explicitly.

Infrastructure right-sizing review at 6 months. Written into the contract, with a defined process and defined SLA for response. This is the single most valuable thing you can negotiate if you have any uncertainty about your concurrent user peaks. I've seen customers negotiate this and use it. Get it in writing before signature — it's essentially worthless as a verbal commitment afterward.

BTP credit top-ups in year one. Particularly if you can show a specific use case — a named integration scenario, a named extension — that demonstrably exceeds the bundle. SAP has an interest in you succeeding on BTP. A well-scoped ask with supporting documentation gets funded. A vague request after you've already hit the limit does not.

Clean core tooling and remediation support. The Business Transformation Center tooling and ABAP Test Cockpit extensions. SAP Clean Core remediation credits. Ask for both. SAP's long-term commercial interest is in you completing the migration successfully. That creates leverage before you sign that disappears the moment you do.

When RISE Is the Right Call

I don't want this to read as an anti-RISE argument. For the right customer it is genuinely the right call: the managed infrastructure removes real complexity from your IT organization, the support model is a floor that can be built on, and the total cost of ownership math — with accurate inputs — is often compelling.

The customers I've seen extract real value from RISE share a pattern. They ran the ABAP Test Cockpit before the sales cycle concluded — not during implementation scoping. They had a cloud integration architect involved in BTP capacity planning alongside the SAP account team, not reviewing it afterward. They negotiated infra right-sizing review rights into the contract. They treated the SOLA support layer as a floor and budgeted for premium engagement during the critical go-live window.

The customers who've had the painful post-signature surprises either didn't have technical leadership in the room during commercial negotiations, or they had technical leadership who deferred to the SAP account team's estimates without independent validation. Independent validation is a two-week exercise. It's never as convenient as trusting the vendor's model. The companies that do it anyway are the ones who don't call me three months after go-live.

Pre-Signature Checklist — Verify Before You Sign

What the Sales Cycle Won't Surface

The SAP account team's job is to close the deal. They will not proactively surface information that complicates the close. That's not bad faith — it's sales. But it means these things will not appear in the sales deck: your actual concurrent user peak at month-end close. The specific BTP services that exceed the bundle for your integration architecture. The implementation partner's custom code remediation estimate, which many partners will not finalize until after contract signature. The 6-to-9-month typical timeline for a full clean core assessment on a complex landscape. None of these are secrets. All of them require you to ask before you're in the room.

The Window You Have

The TCO model SAP presents shows cost reduction over time. For the right customer with accurate inputs, that model is real. For the wrong customer — or the right customer with inputs that came from the license count instead of SM66, from the sales deck instead of the ABAP Test Cockpit, from the account team instead of an independent integration architect — it is aspirational fiction that becomes a very expensive problem to unwind.

Once the contract is signed, the leverage inverts. SAP is no longer competing for your business — they have it. The infra tier is set. The BTP bundle is set. The remediation scope, if it wasn't estimated before signature, is now an implementation partner problem that the customer pays for. The negotiating window is before signature. It is not large, and it closes completely the moment the ink dries.

If you call me after you've signed and tell me about the month-end performance problem, I can help you work through it. But I cannot give you back the leverage you had before you signed. That's the one thing I can't recover.

Stay with us · decision

What's Your Next Move in S/4HANA RISE Negotiations?

Friendly challenge: What will you do differently next time you negotiate an S/4HANA RISE contract to avoid the pitfalls Sarah faced?

No account needed — pick a take, then keep reading. We rotate these prompts so each piece feels like a conversation, not a clone.

Ayraix.com publisher analysis

What we're really seeing

The journey of adopting SAP S/4HANA RISE can be fraught with hidden pitfalls, as Sarah's experience vividly illustrates. The allure of a smooth sales cycle and polished demos often obscures the critical details that could spell disaster post-go-live. Infrastructure sizing, BTP consumption, integration capacity, and custom ABAP objects are just some of the factors that require meticulous planning and oversight. By securing competing quotes from Azure or Google Cloud, architects can leverage alternative terms and negotiate more favorable deals. It's not about bluffing but using concrete alternatives to drive better outcomes.

The key takeaway is that transparency and thorough due diligence are non-negotiable in any major technology transformation. As you navigate the complexities of S/4HANA RISE, remember that the devil is often in the details. Embrace a proactive stance and leverage available tools to ensure a smoother transition.

Keep exploring on ayraix.com

• SAP Go-Live Delays COMMUNITY
• Clean Core ABAP: The Migration Nobody Wants to Do But Everyone Needs COMMUNITY

Quick check — did this stick?

Question 1 of 3

Originally published on ayraix.com, practical AI for enterprise builders.