Executive Clarity · Decision 5 of 8

SAP Business Case & TCO

The transformation does not need a bigger benefits slide. It needs an honest economic contract: what changes, what it costs, who owns the value and when the board will know.

The question

What must an SAP transformation earn to justify the investment — compared with the real alternatives of keeping, stabilising, selectively modernising or replacing the current landscape?

Decision factors

The documented facts

  • SAP's ERP ROI guidance evaluates both the legacy baseline and the proposed system over a five-year horizon, including implementation and ongoing operating costs.
  • SAP's cloud-deployment guidance frames lifecycle TCO over roughly five to seven years rather than comparing only annual subscription and infrastructure charges.
  • An ERP investment includes internal time, process and implementation consulting, software and cloud services, devices, integration, data work, training and support — not only the software contract.
  • SAP Signavio value cases can link process-improvement potential to transformation initiatives and monitor progress toward value realisation.

Source caveat: these are SAP's own planning frameworks and product guidance. They are useful structures, not independent proof that a specific customer will achieve the stated value.

Inference

  • “Do nothing” is not a zero-cost baseline. It includes rising support effort, ageing skills, delayed change, risk concentration and the opportunity cost of processes that cannot improve.
  • A subscription model changes the cost profile; it does not remove implementation, data, integration, change or governance costs.
  • The business case weakens when benefits are expressed as generic productivity percentages rather than named process outcomes with accountable owners.
  • Clean Core, standardisation and automation create value partly by reducing the cost and risk of future change. That value appears after go-live and must be measured there.

Point of view

The business case is not the document used to win approval. It is the operating contract used to govern the programme after approval. If the benefits disappear from steering meetings once funding is released, the case was theatre.

Conditional, not ideological — the recommendation grid

If

The current core is stable but expensive

Price selective modernisation against full transformation. Retire unused custom code, simplify interfaces and remove avoidable operations before assuming a wholesale replacement is the only answer.

If

The business model is changing

Build the case around capabilities and decision speed, not technical currency. Show which revenues, margins, working-capital outcomes or service levels the current system prevents.

If

The programme is mandatory

Do not abandon value discipline. Separate compliance or lifecycle necessity from optional value investments, then govern both transparently.

If

The value depends on adoption

Fund process ownership, data quality, role redesign and post-go-live improvement. A technical go-live cannot realise benefits that require people to work differently.

The minimum economic model

  • Baseline: five-to-seven-year cost and risk of the current landscape.
  • Alternatives: keep, stabilise, selectively modernise, transform or replace.
  • Investment: external and internal costs, including change and post-go-live capability.
  • Value: named operational and financial outcomes with owners.
  • Timing: when each benefit begins, ramps and can be independently measured.
  • Uncertainty: ranges and scenarios rather than one false-precision number.

Monday-morning questions

  • What is the five-year cost of keeping the current landscape, including internal labour and delayed change?
  • Which five benefits have a named business owner who will report them after go-live?
  • Which benefits depend on process adoption, data quality or policy changes outside the technology programme?
  • Which cost and value assumptions would make the decision change if they moved by 20 percent?
  • When will the board review realised value rather than delivery activity?

Where this sits in the decision chain

This is decision 5 of 8 in the Executive Clarity decision library. It follows the Clean Core decision and leads to BTP and extensibility: where the differentiation funded by the case should live.

Sources

Editorial standard: vendor guidance, inference and point of view are kept separate above. Published 2026-08-03 · By Andreas BORN.