RISE with SAP Is a Bundle. Price It Like One.

One Contract, Many Products

When SAP launched RISE with SAP in January, it described it as business transformation as a service. In practice it is a bundle: an S/4HANA Cloud subscription, the infrastructure it runs on with your choice of hyperscaler, technical managed services, and a set of tools for process analysis, the SAP Business Technology Platform, and the SAP Business Network, all under one contract and one subscription price.

Eight months in, the offer is reaching nearly every ECC customer, often with a sense of urgency attached. Mainstream maintenance for ECC is scheduled to end in 2027, with optional extended maintenance to 2030 at additional cost. That deadline is real. But a bundle offered against a deadline is precisely the situation in which buyers sign things they have not fully priced.

Why Bundles Are Hard to Evaluate

A bundle can be a good deal.

A bundle can be a good deal. Bundling is also the oldest way in software to make a price difficult to compare.

When infrastructure, managed services, platform credits and the application itself arrive as one number, it becomes difficult to answer basic questions. What are you paying for the hosting compared with running the same workload on a hyperscaler under your own contract? What are the managed services worth compared with a partner's? How much of the platform credit will you actually use? Without component pricing, you cannot tell whether the bundle is cheaper than the alternatives or simply more convenient.

Ask for the components to be priced separately, even if SAP will only sell them together. If the answer is no, build your own estimate of each piece from the market. The point is not to haggle over every line. It is to know which pieces of the bundle carry the value and which ones you are paying for without needing.

What RISE Does Not Include

The most common misunderstanding about RISE is that it moves you to S/4HANA. It does not. RISE provides the subscription, the infrastructure and tools to help, but the migration project itself, the data cleansing, the process redesign, the testing and the training, is still a project you staff and pay for, usually through a systems integrator.

That project is where most of the cost and nearly all of the risk sits. A RISE contract signed today without a realistic plan and budget for the migration does not reduce your exposure to the 2027 deadline. It adds a subscription to it.

The Questions to Ask Before You Sign

Start with the metric. RISE is priced by full user equivalents, a blend of user types weighted differently. Understand exactly how your user population converts into that metric, how it is measured over time, and what happens when you add a plant or acquire a company.

Next, renewal. Ask what protections exist on the subscription price when the initial term ends. A move from a perpetual license with maintenance to a subscription is a move from a cost you control to a cost the vendor resets at every renewal, and the leverage at renewal belongs to whoever is harder to replace.

Then, exit. Ask what happens to your data and your system if you leave at the end of the term. In a perpetual license model you own the software. In a subscription model you own your data, and you need to know in what form you get it back and how long it takes.

Finally, the edition. RISE comes in more than one deployment flavor, and the differences in how much you can customize matter a great deal to manufacturers with unusual processes. Make sure the version on the quote supports how your plants actually run.

The Option Nobody Puts on the Slide

RISE is one path. There are others: a conventional S/4HANA license deployed on infrastructure you choose, a staged move that buys time with extended maintenance, or a fair look at whether a different ERP fits a mid-market manufacturer better than any SAP option. The vendor presenting RISE will not put those alternatives on the slide, and there is no reason it should. Somebody on your side of the table should.

The Bottom Line

RISE with SAP may well be the right answer for many ECC customers. It should be chosen on its merits, with every component priced, the migration project budgeted separately, the subscription metric understood and the renewal and exit terms negotiated, not signed because a deadline six years away has been made to feel like next quarter.

At Cherry Street, this is the work we do. We are independent of SAP and every other ERP vendor, so we can price the bundle against the alternatives, build the business case for the migration itself, and sit on your side of the table when the contract is negotiated.