The RISE Bill Nobody Budgeted For: Baer’s Ten Hidden Cost Drivers, Read Through 2026

Most conversations about RISE with SAP start with the promise of a rationalized landscape, faster innovation, less technical debt, and a clear path to cloud ERP. The Baer Group wants CIOs to look at the invoice instead. In The CIO’s Playbook for Controlling Cost and Complexity in an ECC to RISE with SAP Migration, James Weller, Baer’s Vice President of Capabilities, lays out ten places where RISE with SAP quietly turns into a runaway cost center, and the small, disciplined moves that keep it from getting there.

The FUE Cliff and the SLA

Two of Weller’s ten cost drivers deserve top billing because they catch even experienced teams off guard. The first is the Full User Equivalent (FUE) tier cliff. As Weller puts it, “A single additional FUE can tip you into a higher pricing tier, adding cost without adding capability.” In the FUE licensing model that underpins RISE with SAP, entitlement is measured by what users are authorized to do, so one loosely scoped role can nudge an entire population into a heavier, more expensive tier. His fix is unglamorous and effective. Run a role-based user census early, simulate FUE tiers with headroom for growth, and automate alerts and dormant-user purges.

The second is the uptime illusion. RISE with SAP typically carries a 99.7% SLA, which sounds airtight until you translate it. That figure allows for under two and a half hours of unplanned downtime per month, and as Weller notes, a 99.7% SLA may look strong until downtime hits during critical business windows. His counsel is to pre-define maintenance windows around critical operations, tie penalties to business impact rather than generic minutes, and demand transparent uptime reporting.

RISE Does Not End The Operations Job

The most persistent myth Weller punctures is that a managed cloud contract retires the Basis team. “RISE with SAP shifts database, platform and cloud infrastructure ownership, but you still need BASIS, CloudOps, and SecOps muscle,” he writes. That is because RISE with SAP moves infrastructure ownership to SAP; it does not move accountability for how the business runs on it. His playbook calls for a lean Cloud Ops hub, operational runbooks, and constant measurement of Mean Time to Acknowledge and Mean Time to Resolve. The same discipline extends to SAP Business Technology Platform (BTP) sprawl to CPI message-volume spikes, and to analytics overhead that accrues with each unused dashboard.

The final driver is the most human. Weller calls it value amnesia, the post go-live drift where teams forget why they moved. “Your biggest post go-live risk is losing focus on why you made the move in the first place,” he warns, prescribing a value scoreboard of pre- and post-go-live KPIs tied to budget.

Why This Lands Harder In 2026

Weller’s warnings look sharper against current data. SAPinsider’s RISE with SAP benchmark report found that only 62% of organizations follow the shared-responsibility model and just one in three conduct regular monitoring, which is exactly the argument for the “RISE does not end Basis gap” in the field.

SAPinsider’s ERP Migration and Transformation 2026 research shows the transition still accelerating under the 2027 deadline, with 36% still implementing or building a business case. More companies signing RISE contracts under time pressure means more exposure to exactly the ten cost drivers Baer catalogs. The pressure to move fast is real. So is the tendency to sign before modeling the full bill.

What This Means for SAPinsiders

Model the FUE tiers before you sign, not after your first true-up. In RISE, authorization defines classification, so scope drives cost more than headcount does. Organizations should run a role-based census now, simulate FUE tiers with growth headroom, and purge dormant users before they get licensed into a higher band.

Treat managed incidents as a division of labor. With only 62% of RISE adopters following shared responsibility, the operational gap is where incidents and overruns live. ERP managers must stand up a lean CloudOps function, write the runbooks, and instrument MTTA and MTTR from day one, rather than assuming SAP owns it all.

Protect the business case after go-live. Value amnesia is the cost driver no dashboard flags automatically. CIOs should publish a KPI scoreboard that compares pre- and post-go-live outcomes, tie budget approvals to it, and cut low-ROI requests fast so RISE stays a platform for transformation rather than a subscription resented by the board.