RISE TCO storytelling, making numbers land in a room.

The RISE TCO model lives or dies in the room where it is presented. A model that is technically perfect, with traceable assumptions and defensible sensitivity tables, will still fail if the team presenting it cannot make the numbers land. Executives do not approve spreadsheets. They approve narratives that are supported by spreadsheets. The TCO storytelling discipline is the difference between a model that drives a decision and a model that becomes a reference document filed and forgotten. This article documents how to make RISE TCO numbers land in a room of executives, board members, and decision makers who do not live inside the model the way the team that built it does.

Open with the bet, not the build

Every TCO model is an articulation of a bet. The bet is that the chosen RISE path will produce a specific cost over a specific term, with a specific operating model, against specific risks. The room needs to understand the bet before it can engage with the math. A presentation that opens with the methodology, the data sources, and the assumption matrix will lose the room before reaching the bet. A presentation that opens with the bet, in one slide, in plain language, gives the room something to engage with.

The bet looks like this. The firm will move to RISE with SAP at a seven year cost of ninety four million dollars, against a brownfield alternative at one hundred and twenty one million dollars, with risks quantified at twelve million dollars across both paths. The firm gains a faster cloud transition and an operating model simplification, at the cost of reduced architectural control. Everything that follows in the presentation supports that one sentence. The room knows what the conversation is about.

Anchor the numbers in something the room knows

Large numbers do not land unless they are anchored. A ninety four million dollar seven year commitment is not a number an executive audience can size against without an anchor. The countermove is to anchor the number against something the room recognises. Annual revenue. Annual technology spend. The cost of a single product line. The cost of a major recent acquisition. The anchor is not in the numbers. It is in the comparison.

The presentation that anchors RISE TCO against annual revenue gives the room a sense of scale. Ninety four million dollars over seven years is one point two percent of annual revenue, or about thirteen and a half million dollars a year on average. The number becomes proportional, and proportional numbers are easier to evaluate than absolute numbers. The room can ask, is this the right percentage of revenue for our ERP commitment? That question is harder to ask when the number is just ninety four million dollars.

Tell the path of the cash

The seven year cash curve has a shape. The shape is part of the story. A path with heavy front loading looks different from a path with even pacing or back loaded growth. The presentation should walk the audience through the cash curve year by year, with the story of what is happening in each year. Year one is migration and ramp. Year two is steady state at growing utilisation. Year three is the first true up window. Year five is the renewal negotiation. Year seven is the exit option.

The cash curve told as a story is more memorable than the cash curve shown as a chart. The audience remembers that year three is the first true up. They remember that year five is the renewal window. When the operating team comes back in six months with a status update, the audience can place the update inside the story. That continuity is what turns a one time approval into an active oversight relationship.

Show the alternative, not just the recommendation

A TCO presentation that shows only the recommended path leaves the audience wondering what was considered and rejected. The countermove is to show the alternative paths with the same level of detail as the recommendation, and to explain why each was rejected. The audience that sees the alternatives sees the work that went into the choice. The audience that sees only the recommendation sees only the answer.

This discipline also protects the team. When the chosen path runs into trouble in year three, the audience remembers that the alternatives were considered. The team is not defending a choice that looks naive in hindsight. The team is defending a choice that was made with full visibility to the alternatives at the time, and the audience that made the choice was part of the consideration.

Quantify the soft factors

Every TCO presentation contains soft factors. Speed to value. Operating model simplification. Risk reduction. Innovation enablement. These factors are real, but they are typically presented as adjectives, which makes them weightless against the hard cost numbers. The countermove is to quantify the soft factors in dollar terms, even when the quantification involves judgement.

Operating model simplification is worth a defined annual headcount equivalent, multiplied by a defined fully loaded cost. Speed to value is worth a defined incremental revenue contribution, with a stated assumption. Risk reduction is worth a defined avoided cost. The quantification is not precise, but it is defensible, and it allows the soft factors to participate in the comparison rather than sitting beside it.

Close with the decision and the path forward

The presentation closes by returning to the decision. The room is asked to approve the recommended path. The path forward is described in concrete terms. The contract finalisation timeline. The signing window relative to the SAP quarter. The internal governance steps. The first six months of operational milestones. The audience leaves the room with a clear sense of what they have just approved and what happens next.

This closing matters because most TCO presentations end with a thank you slide and a question and answer period that does not return to the decision. The audience leaves uncertain about what was actually approved. A closing that returns to the decision and walks the path forward leaves no ambiguity. The decision is on the record. The next steps are on the record. The team that presented can move into execution without revisiting the approval.

Conclusion

RISE TCO storytelling is the discipline that turns analytical work into a decision. The work behind the model is necessary, but it is not sufficient. The presentation has to lead with the bet, anchor the numbers, tell the path of the cash, show the alternatives, quantify the soft factors, and close with the decision. A team that does this work consistently will see different outcomes in the room. A team that treats the presentation as a delivery vehicle for the model will see the model become a reference document that does not drive the decision the model was designed to drive. The investment in storytelling is the investment that protects the investment in the modelling.