Quarterly RISE business reviews. How to run them.

The quarterly business review is the most under used governance instrument in a RISE with SAP contract. Most buyers treat the QBR as a status meeting where SAP presents adoption metrics and the buyer nods. That structure produces no leverage, no insight, and no preparation for the renewal conversation that arrives at year five. A properly run QBR is the buyer governance moment of the quarter. It is where consumption is measured against contract, where performance is measured against SLA, where contract drift is documented, and where the renewal posture is shaped one quarter at a time. Buyers who run the QBR with discipline arrive at renewal with a documented record, a defined position, and the leverage that comes from being prepared. Buyers who let the QBR remain a vendor presentation arrive at renewal as a captive audience.

The four agendas that belong in every QBR.

A useful QBR covers four agendas in sequence. The first agenda is consumption. The buyer reports actual FUE counts, actual document volumes, actual storage consumption, and actual transaction throughput against the contracted commitments. The second agenda is performance. The buyer reports actual availability, actual response time, actual incident counts, and actual service credit eligibility against the SLA. The third agenda is contract. The buyer documents any changes in scope, any changes in the operating model, any new integration points, and any contract drift the quarter has introduced. The fourth agenda is forward looking. The buyer raises the renewal posture, the future demand profile, and any commercial flexibility the quarter has revealed.

The four agenda structure forces the QBR away from the SAP adoption narrative and toward the buyer governance position. The agenda is owned by the buyer, distributed by the buyer ahead of the meeting, and chaired by the buyer in the meeting. SAP attends as a service provider, not as the convener. The shift in convening authority is small in appearance and large in effect. The convener controls the metric set, the comparison points, and the time allocation across topics. A SAP convened QBR will allocate time to adoption metrics that flatter the SAP narrative. A buyer convened QBR will allocate time to consumption variance, performance gaps, and contract drift.

The metric pack the buyer brings to the room.

The metric pack is the artifact that makes the QBR substantive. The pack should include actual consumption against contract for every metered element of the RISE deal. FUE consumption sits at the top, broken into Advanced Use, Core Use, and Self Service Use tiers. Document counting under indirect and digital access follows, with monthly counts for the quarter and the trailing twelve months. Storage consumption, both transactional and archival, with the cost per terabyte at contract rate compared to the public hyperscaler reserved instance rate the buyer could obtain directly.

The performance section of the pack reports availability against the contracted target, response time against the application performance commitments, and incident counts broken into severity tiers. Each metric is reported with a numerator, a denominator, and a comparison to both the contractual commitment and the trailing four quarter average. Where the metric falls below the contractual commitment, the pack documents whether a service credit has been triggered and whether the credit has been applied to the next invoice. Service credits are frequently earned and rarely applied. The QBR is the moment when the credit is claimed in writing.

The contract drift register.

Contract drift is the gradual divergence between the contract the buyer signed and the contract the buyer is actually operating under. The drift arises from informal scope additions, side agreements documented in email threads, operational practices that emerge over time, and SAP product changes that affect the buyer environment without contractual amendment. Drift is the quiet enemy of buyer position at renewal. The QBR is where the drift is captured and addressed.

The drift register is a single document maintained by the buyer governance team. Each entry records the date of the change, the description of the change, the contract reference if any, and the disposition. The disposition options are limited. The change is either incorporated into a contract amendment, reverted to the original contract position, or accepted as a documented variance. The discipline of forcing every drift item to a disposition is what prevents the renewal conversation from being dominated by SAP claims about what the operating relationship has become. The buyer who can produce a drift register at renewal can show exactly what was agreed and exactly what diverged.

The forward demand profile.

The QBR is also where the buyer surfaces the forward demand profile. The forward profile is the buyer projection of consumption, headcount, geographic footprint, and use case expansion for the next four to eight quarters. The profile drives two conversations. The first conversation is internal. Does the buyer expect to consume more than the contracted commitment, in which case overage exposure is rising. Or does the buyer expect to consume less, in which case the renewal posture should reflect a step down. The second conversation is external. Where the forward profile suggests changes that would benefit from a commercial amendment, the QBR is the moment to raise the amendment with SAP and to set the timing for the negotiation.

The forward profile also surfaces the demand for ancillary SAP products, including BTP services, signavio, ariba, and the various SAP cloud add ons that account teams attempt to upsell into the RISE relationship. Each upsell decision can be made deliberately with full visibility of the forward demand and the alternative options, or made reactively as the account team raises them. The deliberate approach almost always produces better commercial outcomes.

The renewal posture conversation.

Every QBR from year two onward includes a renewal posture conversation. The renewal posture is the buyer evolving position on the renewal that arrives at year five or year seven. The posture covers three dimensions. The first dimension is volume. Does the buyer expect to renew at the same volume, more volume, or less volume. The second dimension is scope. Does the buyer expect to renew the same scope, expand scope, or contract scope. The third dimension is structure. Does the buyer expect to renew the RISE relationship as a single contract, split it across multiple commercial structures, or convert to a different SAP delivery model.

The renewal posture is recorded as a working position, not a public commitment. It evolves quarter by quarter as the operating relationship evolves. The discipline of recording the posture every quarter forces the buyer team to remain calibrated on the renewal even when the renewal is years away. The discipline also produces a documented trail that the buyer can reference when the renewal negotiation begins. A buyer who has documented a declining renewal posture across four quarters has a stronger position than a buyer who arrives at renewal with no prior position.

The quarterly business review is not a status meeting. It is the buyer governance moment of the quarter, where consumption is measured against contract, performance is measured against SLA, and the renewal posture is shaped one quarter at a time.

The participants and the cadence.

The QBR is attended by the buyer governance team, the SAP account team, the implementation partner, and where relevant the hyperscaler account team. The buyer governance team chairs the meeting and owns the agenda. The SAP account team presents the SAP delivery report, which is supplied in advance and treated as one input among several rather than the main event. The implementation partner contributes operational data on the application landscape, integration interfaces, and customisation surface. The hyperscaler account team contributes infrastructure consumption data and reserved capacity utilisation where the buyer manages the hyperscaler relationship directly.

The cadence is calendar quarter. The QBR is scheduled six weeks ahead of the quarter end and held within two weeks of the quarter close. The schedule allows the buyer to receive the SAP delivery report, prepare the buyer metric pack, and circulate the agenda before the meeting. The discipline of the calendar cadence is the discipline that produces the documented trail across the contract term.

Conclusion.

The quarterly business review is a governance instrument, not a status meeting. Run with discipline, it produces a documented record of consumption against contract, performance against SLA, contract drift, and renewal posture across the seven year term. Run without discipline, it produces an SAP narrative the buyer cannot challenge at renewal. The four agenda structure, the buyer owned metric pack, the contract drift register, the forward demand profile, and the rolling renewal posture conversation are the components that move the QBR from passive to active. Buyers who adopt the structure arrive at renewal with leverage, evidence, and a defined position. Buyers who do not adopt the structure arrive at renewal as a captive audience to an SAP narrative they had no part in shaping.