When to start. Renewal timing decides the outcome.

A RISE with SAP renewal is a different commercial event from the original signature. The buyer is operationally committed to the platform. The migration cost has been spent. The custom code has been remediated. The integrations have been built. The institutional knowledge sits on the system. From a leverage perspective, the buyer enters a renewal in a structurally weaker position than the buyer in an initial negotiation. The only way to recover negotiating power is to start early and to invest in the renewal as a programme rather than as a deal. This article walks through the timing model we apply to every renewal engagement, the specific milestones at eighteen, twelve, six, and three months before expiry, and the consequences of compressing the timeline.

Why renewal timing decides the outcome.

The SAP renewal playbook is designed to compress the buyer timeline. The initial proposal often arrives nine to twelve months before expiry. The proposal is positioned as a comfortable starting point that, with light negotiation, can be closed inside the next quarter. The framing is deliberate. A buyer who accepts the timeline accepts the structural disadvantage of negotiating against a deadline that the SAP team controls. The buyer who refuses the timeline, and instead begins the renewal preparation eighteen months in advance, controls the conversation rather than reacting to it.

The arithmetic of leverage is straightforward. A buyer with twelve months of preparation, three months of structured negotiation, and three months of contractual closing has time to build credible alternatives, to engage the SAP commercial team from a position of options, and to refuse positions that do not meet the requirement. A buyer with three months total has time only to accept what is offered, with marginal adjustments at the closing margin. The outcome difference is typically twenty to forty percent on the bundled price, twenty four months on the term flexibility, and one or two structural protections in the contract drafting.

Eighteen months out. The strategic review.

The eighteen month milestone is the strategic review. The buyer team commissions a review of the operating model, the platform strategy, the cost trajectory, and the contractual position. The review identifies what is working, what is not working, what the next seven year horizon needs to look like, and what specific changes in the RISE contract would best serve the operating environment. The output of the review is a strategic position document that the executive sponsor signs off and that becomes the buyer reference for the subsequent negotiation.

The eighteen month milestone is also the point at which credible alternatives begin to be evaluated. A move to a different hyperscaler, a partial repatriation to brownfield S/4HANA, a sub plant migration to a different vendor, or a comprehensive renegotiation with SAP at the existing contractual relationship are each evaluated in outline. The evaluations do not need to be definitive at this stage. They need to be credible enough to give the buyer team negotiating optionality when the SAP commercial team begins the renewal conversation.

Twelve months out. The data exercise.

The twelve month milestone is the data exercise. The buyer team produces the FUE inventory, the consumption profile across HANA storage and BTP credits, the actual usage of the contracted entitlements, the documented growth assumptions for the next term, the indexation effect through the existing contract, and the seven year TCO outcome under the existing arrangement. The data exercise produces the evidentiary basis for the renewal negotiation. Without it, the buyer team is negotiating against the SAP narrative rather than against the operating reality.

The data exercise also produces the recalibration opportunity. The original contract may include a recalibration clause that operates at year three or year five. If the clause was drafted but never exercised, the buyer should exercise it now, before the renewal negotiation begins, to lock in any adjustment that the consumption profile justifies. The recalibration sets the baseline for the renewal at the actual operating volume rather than at the originally contracted volume.

Six months out. The position document.

The six month milestone is the position document. The buyer team produces a comprehensive renewal position covering term length, pricing, discount stack, indexation, volume commitments, recalibration, BTP entitlement, exit provisions, expansion pricing, and any structural protections specific to the operating environment. The position is sent to the SAP commercial team formally, as the buyer commercial requirement, with a defined response window of thirty days.

The position document is the moment at which the buyer team takes control of the negotiation agenda. The SAP commercial team is now responding to the buyer position rather than presenting its own. The conversation that follows is structured around the buyer requirement rather than around the SAP playbook. The procedural shift produces material commercial benefit. Buyers who lead with a position document routinely achieve outcomes that are ten to fifteen percent better than buyers who accept the SAP initial proposal as the starting point.

The buyer who accepts the SAP timeline accepts the structural disadvantage of negotiating against a deadline the SAP team controls.

Three months out. The closing window.

The three month milestone is the closing window. The substantive negotiation is largely complete. The remaining work is contractual drafting, executive approval, and the procedural closing process. The buyer team focuses on the closing tests outlined elsewhere in this journal, particularly the verification that the indexation cap is in the contract, the recalibration is bilateral and dated, the discount stack is itemised, and the exit provisions are operational.

The three month window is also the moment of greatest risk. The deal has commercial momentum. The procurement team wants to close. The executive sponsor has visibility on the negotiation and the political cost of holding firm is rising. The temptation to accept a soft position to close the deal is significant. The discipline of the buyer team is what determines whether the closing window converts the negotiation into a strong outcome or quietly erodes the position to land the deal.

The consequences of starting late.

Three failure patterns emerge when the renewal conversation starts late. The first pattern is acceptance of indexed pricing. The contract renews on a price uplift that is presented as standard, the buyer team has no time to challenge it, and the bundled cost increases by ten to twenty percent. The second pattern is acceptance of contractual erosion. The renewal removes protections from the original contract, replaces bespoke language with standard language, and weakens the buyer position for the next renewal cycle. The third pattern is the strategic concession, where the buyer accepts term length extension, volume commitment increase, or BTP commitment growth in exchange for a discount that does not justify the additional risk.

Conclusion.

RISE renewal timing decides the outcome. A buyer who starts eighteen months out has time to build credible alternatives, to engage the data exercise, to produce a position document, and to run the closing tests with discipline. A buyer who starts six months out has time only to react. The difference in outcome is not skill. The difference is preparation time. The SAP commercial team is unchanged in both scenarios. The buyer team that gives itself the time to prepare produces a renewal that protects the operating model and reduces the cost trajectory. The buyer team that allows the SAP timeline to compress the preparation produces a renewal that confirms the SAP narrative and accepts the cost trajectory the SAP team prefers. The choice is the buyer team. The timing is the variable that converts the choice into the outcome.