Counter proposal anatomy. A line by line teardown.

The first SAP RISE proposal lands as a single document. The buyer side counter cannot be a single document. The counter must be a structured response across seven cost categories, with each category carrying its own analysis, its own benchmark, its own counter number, and its own argument. The buyer who responds with a global percentage discount request will be met with a global percentage discount concession. The buyer who responds with a structured line by line counter will compound concessions across the contract. This piece walks through the anatomy of a real counter, in the order the work happens, with the numbers that decide each line.

Line one. The aggregate seven year subscription

The first line of the counter is the aggregate seven year subscription value, broken out by year and by component. The SAP proposal will typically present the subscription as an annual number with a discount percentage from list. The counter rebuilds this number from scratch. Each year is calculated independently. Each component, including base subscription, FUE, BTP credits, Digital Access entitlement, hyperscaler infrastructure, and support, is itemised separately. The aggregate seven year value is the sum.

The counter then presents the buyer side modelled aggregate value, sourced from independent benchmarks. The gap between the SAP proposal and the buyer side model is the opening compression target. Across the firm engagement base, this opening gap runs between thirty and seventy percent depending on the deal shape. The counter is presented as a defensible alternative, not as a negotiating position, with the underlying calculations included so that the SAP team can challenge specific lines rather than the global figure.

Line two. The FUE entitlement structure

The second line decomposes the FUE entitlement. The SAP proposal will define a total FUE count distributed across the four bands. The counter rebuilds the distribution from a role mapping baseline. Every named user in the SAP estate is mapped to a functional role profile, and each role is mapped to the appropriate FUE band against the SAP defined criteria. The role mapping is sourced from the SAP estate user log, not from the proposal estimate.

The counter then presents the buyer side modelled FUE distribution. Typically, the buyer side model produces a fifteen to twenty five percent reduction in the named user count that ends up in the higher FUE bands. The counter also rewrites the recategorisation clause, the growth mechanism, and the true down provision, with each rewrite presented as a procedural step rather than a flag to plant. The combined effect of these rewrites moves the FUE line value down by between fifteen and thirty five percent, with the variance driven by the gap between the SAP estimate and the actual role mapping.

Line three. The BTP credit allocation

The third line addresses the Business Technology Platform credit allocation. The SAP proposal will bundle a credit allocation against an expansive integration roadmap. The counter rebuilds the allocation against the funded integration portfolio, which is sourced from the buyer side IT programme governance. The funded portfolio is typically smaller than the SAP modelled roadmap, often by sixty percent or more.

The counter unbundles the BTP allocation from the RISE subscription, with the allocation set against the funded projects and a usage based mechanism for the remainder. The counter also caps the BTP overage rate at the in contract rate, with a defined uplift schedule across the term, and removes the open ended commercial rate that the standard contract carries. The combined effect of these rewrites moves the BTP line value down by between forty and seventy percent, with the savings flowing into the seven year aggregate.

Line four. The hyperscaler decoupling

The fourth line addresses the hyperscaler. The SAP proposal will bundle a single named hyperscaler inside the subscription. The counter requests a hyperscaler agnostic quote, with the RISE subscription priced without the hyperscaler infrastructure and the buyer bringing the hyperscaler under a separate contract. The counter then presents three parallel hyperscaler bids, against the SAP supported configuration, with the chosen provider becoming the buyer side preferred option.

The counter brings the hyperscaler decision back into the RISE contract on the buyer side terms, with the buyer retaining the right to migrate hyperscaler during the RISE term. The hyperscaler line value is typically reduced by eighteen to twenty eight percent against the bundled rate. The structural benefit, which often matters more than the immediate compression, is the separation of the SAP subscription from the infrastructure cost, which preserves the buyer ability to renegotiate the hyperscaler choice at renewal without reopening the SAP subscription.

Line five. The Digital Access entitlement

The fifth line addresses Digital Access. The SAP proposal will price an entitlement against estimated annual document volume, with the estimate typically running above the buyer historical actual. The counter rebuilds the document volume against three to five years of historical data from the buyer side SAP estate, sourced from the order entry, EDI, supplier portal, and adjacent systems that generate Digital Access events.

The counter then rebases the entitlement against the actual historical volume plus a documented growth assumption, with a true up mechanism replacing the flat commitment. The counter also fixes the true up rate inside the contract at the year one rate, with a maximum three percent annual uplift across the remainder of the term, removing the open ended rate that the standard contract carries. The combined effect of these rewrites consistently moves the Digital Access line value down by between thirty and sixty percent, with the variance driven by the gap between the SAP estimate and the buyer historical actual.

Line six. The contract surfaces

The sixth line addresses the contract surfaces. The standard RISE contract template carries seven uplift surfaces that recover value across the term, including the annual price uplift, the FUE recategorisation clause, the BTP overage rate, the Digital Access true up rate, the hyperscaler pass through mechanism, the support and maintenance escalation, and the renewal pricing clause. The counter rewrites each of these surfaces against the buyer side template.

The annual price uplift is capped at three percent with a hard ceiling, not indexed to an external metric that can run above the cap. The FUE recategorisation clause is bound to a documented process with a quarterly review cadence and a true down mechanism. The BTP overage rate is capped at the in contract rate plus a defined uplift. The Digital Access true up is bound to a defined per document price across the term. The hyperscaler pass through is converted to a documented pass through plus a fixed margin. The support and maintenance escalation is bound to the same three percent annual cap. The renewal pricing clause is rewritten with a documented basis for the renewal calculation, a minimum twelve month renewal notice from SAP, and the buyer right to take the contract to market at renewal without penalty.

Line seven. The exit posture

The seventh and final line addresses the exit posture. The counter attaches a four part exit package to the contract. Transition assistance for twelve months post termination, with named SAP resources and a defined service level. Data extraction in a defined open format with a maximum sixty day extraction window. Knowledge transfer with a documented runbook for the buyer side team. Exit credits attached against early termination at a defined recovery rate.

The exit posture is the line that protects the next negotiation. Without it, the buyer signs into a seven year term with no leverage at renewal. With it, the buyer walks into the renewal conversation carrying the same leverage as the original signature. The counter presents this line as a procedural completeness step, not as a confrontation, which is the framing that consistently gets it through the SAP contract review with minimal resistance.

The seven lines compound the counter into a single coherent posture

The structured seven line counter is not seven separate negotiations. It is a single coherent posture, presented across seven dimensions, with each dimension reinforcing the others. The buyer who presents this counter walks into the conversation with a defensible alternative across the entire deal, not a request for a discount on a deal the SAP team has already shaped. The compression that results is not a percentage discount on a SAP modelled value. It is a contract that compounds value across seven years on terms the buyer has set. Across the firm engagement base, the seven line counter consistently produces between forty and seventy percent compression against the SAP first proposal, with the structural improvements in the contract delivering additional value across the term that the headline number does not capture.