Co terming RISE with other SAP products.

The SAP account team frequently proposes co terming of the RISE with SAP contract with adjacent SAP products such as the Business Technology Platform, Ariba, SuccessFactors, Concur, and Signavio. The co terming proposal positions the consolidated contract as a simpler operating arrangement that reduces the administrative overhead, provides a single commercial relationship, and unlocks a bundle discount across the consolidated portfolio. The proposal is sometimes a fair commercial offer that genuinely benefits the buyer, and sometimes a structured manoeuvre that reduces the buyer renewal leverage by aligning the commercial events across multiple products. The analysis that separates the two cases is the analysis that protects the buyer position across the contract term. This article walks through the SAP motivation for co terming, the buyer side analytical framework, the cases where co terming creates leverage, the cases where it removes leverage, and the way to negotiate the co terming structure when the buyer team chooses to proceed.

Why SAP account teams push co terming

The SAP account team pushes co terming for three commercial reasons that are internally consistent with the SAP account profile metrics. The first reason is the consolidation of the buyer commercial events into a single window, which simplifies the SAP forecasting cycle and reduces the number of renewal cycles that the account team manages across the contract term. The simplification is a real operating benefit for the SAP account team, and the SAP commercial leadership rewards the account team for achieving the consolidation.

The second reason is the protection of the SAP installed base across the adjacent products. The Ariba renewal carries its own competitive risk from Coupa and Procurify, the SuccessFactors renewal carries its own competitive risk from Workday and Oracle HCM, the Concur renewal carries its own competitive risk from the modern expense management ecosystem, and each renewal is a moment at which the buyer team can credibly assess the alternative path. The co terming proposal protects the SAP position on each of the adjacent products by aligning the renewal to the RISE renewal, where the buyer switching cost is highest and where the buyer willingness to assess the alternative path is lowest.

The third reason is the reduction of the buyer renewal leverage on the RISE contract itself. The RISE renewal is the moment at which the buyer team holds the strongest position across the contract term, because the SAP account team needs the renewal to defend the account and because the buyer team has accumulated seven years of evidence about the SAP delivery performance. The co terming structure dilutes the buyer position at the RISE renewal by entangling the renewal with the adjacent product renewals, which carry different competitive dynamics and different decision criteria.

The buyer side analysis of co terming

The buyer side analysis of co terming begins with the identification of the buyer commercial position on each of the products inside the proposed consolidation. The position should cover the competitive context of each product, the buyer satisfaction with the delivery performance, the buyer roadmap for each product, the operating dependencies between the products, and the buyer willingness to assess an alternative path on each product at the renewal point.

The analysis should then identify the renewal windows that the buyer team would carry under the standalone contracts, the renewal windows that the co terming structure would create, and the difference between the two windows. The difference is the leverage cost or the leverage benefit of the co terming structure, and the analysis should quantify the difference in terms of the buyer renewal position rather than the published discount of the consolidation.

The analysis should finally identify the strategic objective that the buyer team carries on each of the products and on the portfolio as a whole. The objective covers the role of SAP in the buyer technology strategy across the contract term, the buyer position on the SAP ecosystem versus the multi vendor ecosystem, and the buyer willingness to deepen the SAP commitment in exchange for the consolidation discount. The strategic objective frames the commercial calculation, and the commercial calculation should serve the strategic objective rather than the inverse.

Cases where co terming creates buyer leverage

Co terming creates buyer leverage in the cases where the consolidated commercial event aligns with the buyer strategic position and where the buyer team has the resourcing to manage the consolidated event effectively. The clearest case is the buyer that has selected SAP as the long term strategic platform across the portfolio, that holds a strong satisfaction position on each of the adjacent products, and that wants to consolidate the operating and commercial overhead of the SAP relationship into a single managed event.

The second case is the buyer that holds a weak position on one of the adjacent products at the standalone renewal point and that would face a difficult solo renewal on that product. The co terming structure carries the weak product into the consolidated event, where the broader SAP commercial position absorbs the difficulty of the individual product. The buyer team should validate that the absorbed position is genuinely better than the solo position before concluding that the co terming creates leverage.

The third case is the buyer that has structural reasons to deepen the SAP commitment, including the consolidation of multiple business units onto a single SAP estate, the migration of an acquired entity onto the SAP platform, or the implementation of a major SAP programme that benefits from the consolidated commercial relationship. The structural reasons should be documented in the buyer strategic plan and should support the co terming decision rather than emerge as a justification for the decision.

Cases where co terming reduces buyer leverage

Co terming reduces buyer leverage in the cases where the consolidated event removes a moment of competitive assessment that the buyer team would otherwise carry, and where the consolidated discount does not compensate for the lost leverage. The clearest case is the buyer that holds a strong competitive position on one of the adjacent products at the standalone renewal point and that would credibly consider the alternative path. The co terming structure removes the standalone moment and absorbs the competitive position into the broader SAP commercial relationship, with the leverage carried into the consolidated event diluted by the broader portfolio dynamics.

The second case is the buyer that holds a weak satisfaction position on one of the adjacent products and that needs the standalone renewal as the moment to address the satisfaction position. The co terming structure removes the dedicated focus on the weak product, and the broader consolidated event will not address the specific issues that the buyer team needs to raise.

The third case is the buyer that does not have the resourcing to manage the consolidated event effectively. The consolidated event requires the simultaneous negotiation of multiple products, the simultaneous engagement with multiple SAP product teams, and the simultaneous evaluation of multiple alternative paths. The buyer team that does not have the resourcing to support the consolidated event will reach a worse outcome on the consolidated event than the team would reach on the standalone events.

Negotiating the co terming structure

The buyer team that decides to proceed with co terming should negotiate the structure to preserve the buyer protections that the standalone contracts would carry. The first protection is the right to remove individual products from the consolidated contract at the renewal point, without triggering an early termination charge on the consolidated structure. The second protection is the documented discount that the consolidation delivers, expressed against the standalone pricing that the products would carry, with the documentation supporting the buyer position at the next renewal. The third protection is the alignment of the contractual mechanisms across the products, including the audit provisions, the data portability provisions, the service level provisions, and the dispute resolution provisions, so that the consolidated contract does not import the weakest mechanism from any single product. The fourth protection is the price hold provision that limits the SAP ability to reprice the consolidated contract at the renewal point above a defined ceiling, expressed against the consolidated baseline that the original co terming establishes.

Conclusion: co terming is a structural decision, not a commercial discount

The co terming proposal that the SAP account team brings to the buyer organisation is a structural decision about the renewal leverage that the buyer team will hold across the contract term, not a commercial discount on the immediate contract. The decision should be assessed against the buyer strategic position on each of the products, the buyer resourcing to manage the consolidated event, and the buyer alternative paths on each of the products at the standalone renewal point. The cases where co terming creates leverage are real and the buyer team should pursue those cases. The cases where co terming reduces leverage are equally real and the buyer team should resist those cases regardless of the headline discount that the SAP account team offers. The buyer team that frames the decision as a structural question rather than a commercial question protects the renewal position across the seven year contract term.