BTP Negotiation Inside the RISE Bundle.

SAP Business Technology Platform sits inside almost every RISE proposal as a bundled entitlement, expressed in cloud credits, capacity units, or named services. The bundle reads as a benefit. In the seven year TCO, it more often reads as a liability. The credits expire if unused. The services included in the bundle are not always the services the buyer needs. The services the buyer needs are often outside the bundle and priced separately. The net effect is that BTP can quietly add five to fifteen percent to the total RISE cost without the buyer noticing where the spend went.

This paper takes the BTP bundle inside a typical RISE order form and rebuilds it from the buyer side. It documents how cloud credits actually convert into service consumption, where the burn down accelerates, and which services consume disproportionately. It covers the relationship between BTP entitlements and on premise developer licences that the buyer may already hold, and how to avoid paying twice for the same capability during the conversion window. It addresses Integration Suite, Build Apps, AI Foundation, Datasphere, and the analytics stack in turn, with the negotiation points specific to each.

The paper closes with the contract architecture for BTP under RISE. Rollover provisions for unused credits. True up and true down mechanics. Conversion rights between credit pools and named services. Sunset protections for services SAP discontinues during the contract term. The defensible buyer position on each is documented with example clause language.