RISE renewal preparation. Eighteen months out.

The renewal negotiation for a RISE with SAP contract does not begin at month sixty. It begins at month forty two. The eighteen months between month forty two and month sixty are the window in which the buyer assembles the position, the documentation, and the leverage that will determine the renewal outcome. Buyers who treat the renewal as an event that happens at month sixty enter the negotiation reacting to an SAP proposal that has been in preparation for two years. Buyers who treat the renewal as a programme starting at month forty two enter the negotiation with a position of their own, a counter proposal of their own, and a credible alternative the SAP account team understands. The difference between the two postures is typically twenty to thirty percent of the renewal value.

Month forty two. The renewal posture is locked.

At month forty two, eighteen months before expiry, the buyer governance team locks the renewal posture. The posture is a written document covering three dimensions. The first dimension is the renewal scenario the buyer expects to pursue, ranging from straight renewal at current volume to renewal at reduced volume, expansion renewal, partial unbundling, conversion to a different SAP delivery model, or exit. The second dimension is the financial envelope the buyer is prepared to commit. The third dimension is the timeline the buyer expects to operate under, including the gates that must be passed before signature.

The locked posture becomes the reference document for every internal conversation across the next eighteen months. It is reviewed quarterly at the QBR. It is updated as conditions change, but the structure of the document remains stable. The discipline of the locked posture prevents the buyer team from drifting into the SAP narrative as the renewal approaches. Without the locked posture, the buyer team often arrives at month fifty four with no defined position, which gives the SAP account team room to set the agenda.

Month thirty six. The current state assessment.

At month thirty six, the buyer governance team completes the current state assessment. The assessment documents the actual consumption profile across the contract term, the actual performance profile against SLA, the contract drift register, and the operational pain points that have emerged. The assessment is the evidence base for the renewal position. Where the buyer team wants to negotiate a reduction in FUE count, the assessment shows the actual FUE consumption trend. Where the buyer team wants to negotiate stronger performance commitments, the assessment shows the actual incident pattern.

The current state assessment is a sixty page document with appendices, not a slide deck. It is owned by the buyer governance team and refreshed every six months until the renewal closes. The document is shared selectively. Some sections are shared with the SAP account team at appropriate moments in the negotiation. Other sections are retained as buyer internal artifacts that inform the buyer position but are never shared. The discipline of preparing the document in detail produces the buyer position. The discipline of sharing it selectively preserves the buyer leverage.

Month thirty. The alternative scenarios.

At month thirty, the buyer governance team commissions the alternative scenarios. The alternative scenarios are the credible options the buyer could pursue if the renewal negotiation does not produce an acceptable outcome. Brownfield S/4HANA on private cloud. RISE with a different commercial structure. GROW with SAP for entities that fit the midmarket profile. Conversion to a different ERP. Continued operation of the existing landscape with extended maintenance. Each alternative is sized, costed, and time bound. Each alternative is supported by a credible delivery partner who has been engaged to participate in the scenario.

The alternative scenarios are not bluffs. They are real options the buyer would pursue if the renewal terms required it. The discipline of preparing the alternatives at month thirty rather than month fifty four is what makes them credible at the negotiation table. A buyer who walks into the renewal with a brownfield TCO model that was produced six months earlier, with a partner who is named and engaged, presents a different position than a buyer who walks in with a vague claim that alternatives exist. SAP account teams calibrate proposals against the credibility of the alternatives, and credibility is built in advance.

Month twenty four. The internal alignment.

At month twenty four, the buyer governance team completes the internal alignment. The internal alignment is the documented agreement across the executive sponsors, the technology leadership, the finance leadership, the legal team, and the procurement leadership on the renewal posture, the alternative scenarios, and the negotiation mandate. Alignment is recorded in a single document signed by each of the named stakeholders. The document is treated as a working artifact, not a public commitment, and it is refreshed as the negotiation progresses.

The internal alignment is the discipline that prevents the SAP account team from finding a path around the buyer negotiation team during the renewal. Account teams routinely identify the executive sponsor, the operational lead, or the finance approver and attempt to engage that stakeholder outside the negotiation channel. The internal alignment document, properly distributed, makes every stakeholder aware of the position and the agreed negotiation channel. Side conversations become identifiable as side conversations, and the buyer team can address them when they arise.

Month eighteen. The first SAP conversation.

At month eighteen, the buyer team has the first explicit renewal conversation with the SAP account team. The conversation is structured. The buyer team introduces the renewal calendar, the negotiation channel, the principal contacts, and the working timeline. The buyer team does not introduce the position, the alternatives, or the financial envelope. The first conversation is process, not substance. The substance comes later in a sequence the buyer team controls.

The early conversation produces two outcomes. The first outcome is that the SAP account team learns the buyer is treating the renewal as a structured negotiation, not a renewal formality. The framing shifts the SAP preparation. The second outcome is that the buyer team learns the SAP commercial calendar, the named participants, the executive sponsor, and the approval chain on the SAP side. Knowledge of the SAP approval chain is essential for the later phases, where the buyer team needs to escalate, time, or sequence proposals against the SAP cycle.

The eighteen months between month forty two and month sixty are the window in which the buyer assembles the position, the documentation, and the leverage that will determine the renewal outcome.

Month twelve to month one. The negotiation.

The final twelve months are the negotiation. The negotiation runs on a calendar the buyer team has prepared and the SAP team has accepted. The calendar includes the proposal exchange, the position exchange, the BAFO sequence, the approval gates on the buyer side, and the contract drafting window. The calendar accounts for the SAP quarter end pressure points, which typically fall at March, June, September, and December. The buyer team uses the quarter end pressure deliberately, scheduling key proposal exchanges to align with the SAP quarter close where buyer leverage is highest.

The negotiation phase produces the renewal contract. The buyer team is supported by a contract review specialist who reads every page, a TCO model that updates with each commercial movement, and an executive escalation channel for the moments when the negotiation needs senior involvement. The discipline of the prepared calendar, the prepared position, and the prepared alternatives is what makes the negotiation productive. Without that discipline, the final twelve months become a reactive scramble against an SAP team that has been preparing for two years.

Conclusion.

RISE renewal preparation is a programme, not an event. The eighteen month calendar produces the locked posture, the current state assessment, the alternative scenarios, the internal alignment, the first SAP conversation, and the structured negotiation. Each artifact takes months to build and cannot be assembled at the last minute. Buyers who run the programme arrive at month sixty with a position, an evidence base, credible alternatives, and a calendar the SAP team has accepted. Buyers who do not run the programme arrive at month sixty reacting to a proposal that was prepared two years earlier. The work is concrete and the timeline is fixed. The eighteen months start at month forty two whether the buyer team is ready or not.