Final RISE TCO model review before signature.

The seven year RISE with SAP TCO model has carried the negotiation from the first proposal to the final round. The numbers have been refreshed at each revision, the sensitivity bands have been tightened, the contract surfaces have been negotiated, and the headline price has compressed against the benchmark range. The final round is closing. Before the signature, the model gets one last review. This review is not a recalculation. It is the audit pass that confirms the model is internally consistent, that the contract language matches the model assumptions, and that the boardroom version still survives the questions that will arrive in the post signature reporting cycle. This article documents the pre signature checklist the firm runs against every model.

Test one. The six cost categories reconcile to the contract

The first test is the reconciliation between the six cost categories in the model and the corresponding lines in the final contract. The compute and storage line in the model has to reconcile to the bundled infrastructure cost in the contract, with the hyperscaler region, workload size, and reserved capacity term explicitly matching the contract supporting paperwork. A model that prices compute against a five year reserved tier against a contract that runs at the on demand tier is a model that overstates the cost by between thirty and fifty percent on the infrastructure line.

The FUE entitlement line in the model has to reconcile to the named user count and band allocation in the contract. The role mapping baseline that produced the model FUE allocation has to match the band allocation that the contract documents, with the recategorisation clause and the growth schedule mirrored between the two. The BTP credit consumption line has to reconcile to the funded portfolio and the overage rate, with both the in contract credit volume and the overage multiplier matching between the model and the contract.

The migration cost line has to reconcile to the SI partner contract or the internal staffing plan, with the parallel run cost recognised as a separate line in both. The application support line has to reconcile to the included RISE coverage scope, with the in scope work types matching the model assumption. The exit cost line has to reconcile to the transition assistance, data extraction, knowledge transfer, and termination penalty clauses in the contract, with each clause priced against the model assumption.

Test two. The seven contract surfaces match the negotiated position

The second test is that each of the seven contract surfaces that the negotiation has targeted is documented in the final contract on the negotiated terms. The annual price uplift cap has to be in the contract at the negotiated percentage, with the indexation basis explicit and the hard ceiling documented. The FUE recategorisation clause has to be in the contract with the documented review process, the agreed criteria, the quarterly cadence, and the true down mechanism. A contract that documents the cap and the cadence but omits the true down mechanism is a contract that has accepted half the negotiated position.

The BTP overage rate has to be in the contract at the negotiated multiple of the in contract credit rate, with the multiplier locked across the term rather than indexed to the prevailing rate at the time of overage. The Digital Access true up rate has to be at the negotiated per document price, with the documentation methodology agreed and the audit obligations in the schedule. The hyperscaler pass through mechanism has to be at the negotiated structure, with the markup converted to a documented pass through plus a fixed margin if that was the negotiated outcome.

The support and maintenance escalation has to be at the negotiated cap, mirrored to the price uplift cap. The renewal pricing clause has to be in the contract with the documented basis, the twelve month notice from SAP, and the buyer right to test the market at term end without penalty. Each of the seven surfaces is read against the negotiated position from the negotiation log, with the contract language compared word for word against the agreed redline. A contract that has been rewritten in the final round without the buyer side review is a contract that may have shifted the negotiated position back to the SAP supplied default.

Test three. The sensitivity bands still produce defensible outcomes

The third test is to rerun the sensitivity bands against the final negotiated numbers, with the same six dimensions that the model carried through the negotiation. The user growth band, the FUE recategorisation band, the BTP consumption band, the hyperscaler market rate band, the support coverage scope band, and the exit timing band each have to produce outcomes that the boardroom can accept. The post negotiation sensitivity is typically tighter than the pre negotiation sensitivity, because the contract surfaces have bound the assumptions on the upside.

The post negotiation sensitivity has to be documented in the final boardroom version, with the high case, central case, and low case totals for each option. The high case has to remain inside the approved spending envelope. If the high case overshoots the envelope, the negotiation has to revisit the contract surfaces that produced the overshoot before the signature. A common failure mode is to close the negotiation on the central case without testing the high case, which means the post signature high case scenario produces a budget conversation that the procurement team did not anticipate.

The low case has to remain operationally viable. A low case that produces a total below the operational floor for the workload is a low case that may not be realistic. The low case is the test that the model has captured the fixed components of the contract correctly, with the in contract minimums and the unused capacity recovery mechanisms reflected in the calculation. A low case that does not capture the in contract minimum is a low case that understates the downside, which exposes the buyer to a surprise in the post signature year one if the actual consumption runs below the central case.

Test four. The audit trail is complete and defensible

The fourth test is the completeness and defensibility of the audit trail behind the model. Each line in the model has to point to a documented source, with the source captured in the audit trail, with the date of the source, with the version of the source, and with the link to the original document or extract. The compute and storage benchmark has to point to the hyperscaler price list, with the date and the URL. The FUE benchmark has to point to the engagement library, with the deal count, the median, the band ranges, and the as of date.

The audit trail has to survive a challenge from the internal audit team, the external auditor, the SAP account team in joint session, and the SI partner. Each of these stakeholders may challenge a specific line. The audit trail has to produce the source within minutes, not days. A model that cannot produce the source for a challenged line is a model that gets repriced inside the boardroom, with the SAP supplied number substituted for the buyer side number on the challenged line, which is the failure mode the audit trail discipline exists to prevent.

The audit trail also has to capture the assumption changes across the negotiation. The version of the model that closed the negotiation is not the version that opened the negotiation. Each version change is documented, with the date, the change reason, the supporting source, and the impact on the seven year total. The final boardroom version reads against the initial model, with the cumulative compression captured against the SAP first proposal, and the per round movement attributed to the specific concessions the negotiation produced. The cumulative compression is the headline number that the board level pack carries against the savings claim.

Test five. The ESG and disclosure alignment is locked

The fifth test is the ESG alignment between the model and the contract supporting paperwork. The hyperscaler region selected has to match the region in the contract, with the corresponding Scope 2 line in the model derived from the regional grid factor and the regional PUE. The disclosure framework choice between location based and market based methodology has to be reflected in the contract supporting paperwork, with the corresponding contractual data rights from the hyperscaler and SAP attached as a schedule.

The seven year ESG projection has to be reviewed alongside the seven year financial projection, with the year on year emissions line reconciled to the year on year cost line. A buyer who reports on market based methodology has to have the contractual right to the hyperscaler supplied renewable energy attribution, with the documentation cadence and the audit obligations attached. A buyer who reports on location based methodology has to have the contractual right to the regional grid data, with the same documentation cadence and audit obligations.

The ESG audit trail mirrors the financial audit trail, with each emissions line pointing to a documented source. The hyperscaler PUE source. The regional grid factor source. The workload utilisation profile source. The renewable energy attribution source, if applicable. The audit trail discipline applies on both sides of the model. The board level pack that closes the deal carries both audit trails side by side, with the cumulative emissions movement against the initial model captured against the cumulative cost compression.

Test six. The post signature operating model is ready

The sixth and final test is whether the post signature operating model is ready to take the contract into production. The TCO model is the financial baseline. The contract is the legal baseline. The operating model is the bridge between the two. The post signature operating model captures the in contract baselines for each cost category, with the actual run rate measured against the baseline on a monthly cadence, and with the variance attributed to a specific cause.

The operating model also captures the contractual review cadence for each of the seven surfaces. The quarterly FUE recategorisation review. The quarterly BTP overage review. The annual support coverage review. The annual price uplift application. The semi annual renewal preparation work. Each cadence is loaded into the operational calendar, with the named owner, the documentation obligations, and the escalation path for each surface. A contract that closes without the operating model in place is a contract that drifts inside the first six months because the contractual cadences are not loaded into the operating rhythm.

The post signature optimisation work begins on day one, not in year two. The optimisation runs against the operating model, with the variance against the in contract baseline triggering the renegotiation conversations on the surfaces where the actual run rate differs from the modelled assumption. The discipline of the pre signature review is the discipline of the post signature operation. The model is the financial baseline. The contract is the legal baseline. The operating model is the daily reality that the contract has to deliver against across the next seven years.

Six tests, one signature

The pre signature checklist runs in the final week of the negotiation, with the model, the contract, and the operating plan on the same table. The six tests are read in sequence. The contract reconciles to the model. The seven surfaces match the negotiated position. The sensitivity bands produce defensible outcomes. The audit trail is complete. The ESG alignment is locked. The post signature operating model is ready. Each test that passes moves the deal closer to the signature. Each test that fails sends the deal back to the negotiation team for a targeted fix.

Across the firm engagement base, the pre signature checklist has caught contract drift in approximately forty percent of deals, with the most common drift on the FUE recategorisation clause, the BTP overage multiplier, and the hyperscaler pass through structure. The drift is corrected before the signature in every case where the checklist has been run, with an average per deal correction worth between four and twelve percent of the seven year contract value. The model is the negotiation. The checklist is the verification. The signature is the closing event, not the closing decision.