Financial risk modelling. From point estimate to scenario distribution.

A RISE with SAP commitment is typically modelled as a point estimate. The seven year cost is summarised as a single number derived from the contracted price, the contracted volume, the contracted indexation, and a steady state assumption about consumption. The number lands in the business case, the board paper, and the finance plan. It is wrong. Not because the arithmetic is incorrect, but because the underlying variables are uncertain, the uncertainties compound across the term, and a point estimate cannot represent the actual cost distribution that the buyer will experience. This article walks through the financial risk modelling approach we apply to enterprise RISE commitments, the variables that drive the cost distribution, and the buyer side framework for converting the point estimate into a defensible scenario distribution.

Why the point estimate is misleading.

The point estimate suffers from three structural problems. The first problem is that it ignores the variability in the underlying cost drivers. The FUE count grows or contracts with workforce changes. The BTP consumption grows or contracts with platform adoption. The hyperscaler infrastructure consumption varies with workload patterns. The indexation operates against an inflation environment that may exceed or fall below the contractual cap. Each of these variables is a distribution rather than a point, and the seven year cost outcome depends on the realised values rather than the assumed values.

The second problem is that the variables are correlated. A recession that reduces the workforce also reduces the BTP adoption, also reduces the infrastructure consumption, and also constrains the indexation environment. A growth period that expands the workforce expands the other variables in the same direction. The correlations matter because they produce compound effects in the tail scenarios that do not appear in the independent variable analysis. The third problem is that the point estimate produces false confidence. A board that sees a single number assumes the number is the answer. A board that sees a distribution understands that the number is a central tendency around which substantial variation is possible.

The cost driver inventory.

The financial risk model starts with the cost driver inventory. The drivers include the FUE count and its growth trajectory, the HANA storage consumption, the BTP credit consumption by service, the hyperscaler infrastructure consumption by region and reservation profile, the indexation rate against the contracted index, the currency rate for buyers with multi jurisdiction operations, the expansion activity above the contracted volume, the overage activity on BTP credits, and the recalibration adjustments at the contracted measurement points. Each driver should be documented with its current value, its historical variability, and its assumed forward trajectory.

The inventory should also identify the drivers that are inside the contracted commitment versus the drivers that are outside. Inside drivers, such as the contracted FUE volume and the contracted unit price, are largely fixed. Outside drivers, such as the actual consumption against contracted volume and the expansion activity above contracted volume, are variable and produce most of the cost variability across the term. The buyer financial team should focus the modelling effort on the outside drivers, since they carry the variability that the inside drivers do not.

Scenario construction.

The model should construct at least five scenarios across the cost distribution. The base case represents the documented assumptions and reproduces the original point estimate. The optimistic case represents the upside scenarios where consumption falls below plan, indexation operates below cap, and recalibration delivers downward adjustment. The pessimistic case represents the downside scenarios where consumption exceeds plan, indexation operates at cap, expansion activity is significant, and recalibration does not deliver. The stress case represents the tail scenarios with multiple unfavourable drivers compounding simultaneously. The catastrophic case represents the very tail scenarios with major operational disruption, regulatory intervention, or commercial dispute.

The scenarios should be quantified rather than described. The base case might produce a seven year cost of one hundred twenty million dollars. The optimistic case might produce ninety five million. The pessimistic case might produce one hundred fifty five million. The stress case might produce one hundred eighty million. The catastrophic case might produce two hundred twenty million. The range alone changes the buyer conversation. A board that sees a one hundred twenty million dollar point estimate has a different view from a board that sees a range from ninety five to two hundred twenty million with a central tendency at one hundred twenty.

The point estimate produces false confidence. The board that sees a single number assumes the number is the answer. The board that sees a distribution understands the variation.

Monte Carlo simulation.

For organisations with the analytical capability to run them, Monte Carlo simulations produce a more refined view of the cost distribution than the discrete scenario approach. The simulation defines a probability distribution for each cost driver, draws random values from each distribution across thousands of trials, and produces a full distribution of seven year cost outcomes. The output identifies the median outcome, the percentile bands, and the tail values that the discrete scenarios may not have captured.

The Monte Carlo approach also surfaces the principal drivers of cost variability. A sensitivity analysis of the simulation typically identifies two or three drivers that account for sixty to eighty percent of the variability across the cost distribution. The buyer team can then focus its risk mitigation effort on those drivers specifically, with contractual protections, operational controls, or alternative arrangements that reduce the exposure on the high impact drivers. The remaining drivers receive lighter attention proportional to their lower impact. The discipline produces a focused mitigation programme rather than a generic risk management exercise.

Risk mitigation through contractual protection.

Many financial risks can be mitigated through contractual protection negotiated at signature. The indexation cap reduces the upper bound of the indexation exposure. The recalibration mechanism reduces the downside exposure from over commitment. The expansion pricing lock reduces the exposure from above contract activity. The currency selection or hedging arrangement reduces the FX exposure. The BTP overage rate cap reduces the platform consumption exposure. Each contractual protection has a defined cost in negotiation effort and may carry a small price implication. Each also produces a defined reduction in the cost distribution variability.

The buyer team should evaluate each protection against the variability it reduces, with the protection prioritised against the impact on the cost distribution rather than against the negotiation difficulty. A protection that is difficult to negotiate but reduces twenty percent of the cost variability is worth significantly more than a protection that is easy to negotiate but reduces two percent. The financial risk model gives the buyer team the basis for the prioritisation, with quantified impact figures that the negotiation discipline can rely on.

Reporting the model to the board.

The board should see the financial risk model in summary form, with the scenario range, the principal drivers of variability, and the contractual mitigations applied. The reporting should be revisited annually, with the actual outcomes against the modelled assumptions reviewed and the model updated. The discipline of annual reporting produces accountability for the financial trajectory and ensures that any drift between assumed and actual values is surfaced in time for operational response.

The reporting should also identify the decision points in the contract life that affect the cost distribution. The recalibration windows, the renewal cycle, the strategic review milestones, and any planned expansion activity each represent decision moments where the financial risk profile shifts. The reporting should give the board visibility on the upcoming decisions and the implications for the cost trajectory, so the board can engage the strategic conversation rather than receiving the operational outcome after the decision is made.

Conclusion.

Financial risk modelling converts a RISE commitment from a point estimate into a defensible scenario distribution. The conversion requires the cost driver inventory, the scenario construction, the optional Monte Carlo refinement, the contractual mitigation analysis, and the disciplined board reporting cadence. The investment in the modelling is modest, typically three to four weeks of finance team effort at signature and two to three days per quarter thereafter. The return on the investment is structural. The buyer team understands the actual financial exposure across the contract life, the board has visibility on the distribution rather than the point estimate, and the contractual position can be prioritised against the drivers of greatest variability. Organisations that operate financial risk modelling at this depth routinely produce RISE outcomes that perform inside the modelled range. Organisations that operate on the point estimate alone routinely discover, in year three or year four, that the actual cost is significantly above the planned cost and the contractual protection to manage the divergence was not built into the original arrangement.