The SAP Implementation Business Case: Fund the Change, Not the Software

A CFO and transformation-office workbook for cost, value, risk, options and ownership

Altivate | Published 12 July 2026 | Updated 26 July 2026

1. Define comparable transformation options before estimating the case

The financial case should help the board select between credible transformation choices, not merely justify an architecture chosen elsewhere.

Define and compare the credible operating options on one boundary:

• continue or minimally change the current estate;
• modernise selected capabilities without replacing the core;
• use non-SAP products where they better fit a bounded capability;
• SAP Cloud ERP or SAP Cloud ERP Private;
• new implementation, system conversion or selective data transition;
• single tier or two tier;
• retained custom code and clean-core boundary;
• target operating regions and statutory constraints;
• systems to retire, retain or integrate;
• business scope and rollout sequence.

Those options create different cost, duration, risk, capability and change profiles. Estimate them separately so the case selects an architecture rather than hiding it inside one blended total.

The SAP Modernisation Decision Tree helps define edition, path, clock and regional constraints. Use its output to structure the option set, then let the evidence in the business case determine which eligible option should be funded.

SAP’s current guidance describes the S/4HANA business case as a strategic, technical and financial exercise. Its fit-to-standard guidance places business scope and standard-process fit before configuration. Both are vendor guidance. The practical implication is sound: the case must explain which operating model is being bought, not only which product.

Altivate’s SAP S/4HANA business-case service supports the discovery and investment work that follows path selection.

2. Frame options, including the cost of delay

Every case needs at least three genuinely distinct options:

Add “do nothing” only if it is described honestly. In a maintenance-driven programme, doing nothing is an active option with support, security, skills, change, infrastructure, delay and business continuity costs.

Cost of delay

avoidable run cost + deferred benefit + additional risk exposure + future price or capacity effect

Do not force every term into money if the evidence is weak. Record a dated qualitative exposure, its owner and the event that will allow it to be quantified.

Options should share a common boundary and time horizon. A minimum technical conversion cannot be compared fairly with a transformation case if one includes five years of run cost and the other stops at go-live.

3. Build the full investment stack

Product and subscription

• software subscription or licence;
• infrastructure or hyperscaler services;
• SAP support and success plans;
• partner or third-party products;
• non-production environments;
• consumption-based services;
• contract transition and overlap.

Programme delivery

• discovery, architecture and business design;
• process ownership and fit-to-standard workshops;
• configuration and development;
• integration and extension;
• data profiling, cleansing, migration and reconciliation;
• security, controls and role design;
• testing, environments and release management;
• localisation and statutory validation;
• programme management and assurance;
• cutover, hypercare and stabilisation.

Business change

• business subject-matter capacity;
• backfill and overtime;
• process redesign;
• role and organisation change;
• communications and training;
• adoption support;
• local rollout teams;
• temporary productivity decline;
• customer, supplier and partner transition.

Transition and retained estate

• dual running;
• legacy support and infrastructure;
• data archive and access;
• interface bridges;
• systems that cannot retire at go-live;
• contract termination;
• decommissioning and evidence retention.

Future operating model

• product ownership;
• application management;
• release and regression testing;
• master-data governance;
• integration operations;
• security and access reviews;
• process performance management;
• continuous improvement;
• SAP and partner commercial management.

The cost model should distinguish initial, transition and steady-state cost. It should also state whether internal labour is incremental cash, displaced work, backfill, or absorbed capacity.

4. Use ranges before precision

Early programme estimates should be ranges tied to assumptions, not a single number with false accuracy.

Contingency is not a flat percentage added because the template has a row. Build it from named risks where possible:

probability x financial impact

Keep severe non-financial risks visible even when expected value looks small.

5. Build benefits from changed process mechanics

Start with a process driver, not an SAP feature.

Then calculate from local data.

Efficiency benefit

annual volume x baseline effort reduction x loaded rate x adoption x realisation factor

Working-capital benefit

validated change in inventory, receivables or payables x approved cost-of-capital treatment

Avoided run cost

retired contract + retired infrastructure + avoided support - replacement run cost

Revenue or margin benefit

incremental qualified volume x probability of realisation x contribution margin

Keep revenue attribution conservative when several programmes contribute.

SAP Value Accelerators and fit-to-standard content can help teams identify process opportunities and reduce design effort. They do not prove the customer-specific baseline, adoption or financial outcome. A benchmark is a challenge to investigate, not a benefit to book.

6. Separate hard, enabled and strategic value

Use three benefit classes in the board paper.

Hard financial value

Accepted budget, cash-flow, working-capital, revenue or risk-loss effect with a finance owner.

Enabled operating value

Measured cycle, quality, service, capacity or control improvement that has not yet converted into a booked financial result.

Strategic option value

A future decision or capability enabled by the platform, such as a faster acquisition integration, new business model, AI use case or regulatory response.

Do not add all three into one ROI total. A programme can have a compelling strategic case with limited near-term hard value. Say that honestly. The board needs to understand what kind of value it is approving.

7. Model timing and adoption

Benefits do not begin at full run rate on go-live day.

For each benefit, record:

• baseline date and source;
• process owner;
• enabling capability;
• rollout wave;
• adoption measure;
• stabilisation period;
• ramp to target;
• disbenefits and temporary performance loss;
• finance recognition rule;
• first review and expiry date.

Realised benefit in period

validated unit improvement x actual eligible volume x adoption x finance recognition factor

Eligible volume is the total pre-adoption population that meets the benefit’s scope criteria in the period. Adoption is the measured fraction of that population following the intended process. Keeping them separate prevents the same adoption reduction being applied twice.

This formula forces four different questions:

1. Did the process measure change?
2. Did enough volume use the changed process?
3. Did people adopt the intended behaviour?
4. Will Finance accept the effect?

The SAP Value Realisation paper turns those questions into the post-funding operating ledger.

8. Calculate the case transparently

Total investment

product + delivery + business change + transition + contingency

Incremental annual run cost

target annual run - current annual run retained after decommissioning

Annual net benefit

recognised hard benefits - incremental run cost - sustaining change and improvement cost

Simple payback

The decision-grade method is cumulative cash flow:

first month in which cumulative discounted or undiscounted net cash flow becomes non-negative

total investment / steady-state monthly net benefit may be shown only as a labelled steady-state payback proxy. It is not the payback date when benefits ramp, costs overlap or transition disbenefits vary by month.

Net present value

sum of discounted net cash flows - initial investment

Risk-adjusted net present value

sum of probability-weighted discounted scenario cash flows - initial investment

Use the organisation’s discount rate, tax treatment and capital policy. Show nominal and real currency treatment where inflation or multiple markets matter. Do not import a vendor composite ROI. The purpose of the calculator is to make local assumptions visible.

Worked example: why the ramp matters

Assume AED 12 million initial investment, AED 1 million of transition cost across the first six months, benefits ramping from zero to AED 700,000 per month by month 13, and AED 180,000 monthly incremental run and sustaining cost. The steady-state proxy is about 23 months (12m / (700k - 180k)). A monthly cumulative cash-flow schedule reaches payback later because it includes the benefit ramp and transition cost. The board should approve against that schedule, not the proxy.

Download the editable SAP implementation business-case workbook. It compares four options, blocks incomplete inputs, and calculates downside, base, upside and probability-weighted NPV.

9. Run the challenge workshop

Ask one person to defend each assumption and another to challenge it.

Scope challenge

• Which processes and countries are actually in the funded scope?
• Which requirements are legal, differentiating or inherited?
• Which systems retire, and on what date?
• Which historical data must be migrated rather than retained elsewhere?

Cost challenge

• Which internal roles need backfill?
• Which integrations and controls are undercounted?
• Which contracts overlap during transition?
• What will the target operating model cost?

Benefit challenge

• Which local baseline supports the number?
• What behaviour must change?
• Who owns the benefit?
• What other initiative also claims it?
• What causes Finance to recognise it?

Risk challenge

• Which risk can move the critical path?
• Which assumption depends on a vendor roadmap or contract?
• What happens if one rollout wave slips?
• Which severe consequence needs a hard boundary rather than contingency?

Record the response in the workbook. A risk discussed but not reflected in scope, cost, timing, control or contingency has not been handled.

10. The board-paper workbook

The final case should contain:

• ☐ architecture and transformation-path decision;
• ☐ option comparison with a common boundary;
• ☐ cost of delay;
• ☐ initial, transition and steady-state cost;
• ☐ internal capacity and backfill;
• ☐ risk-based contingency;
• ☐ benefits with local baselines and named owners;
• ☐ hard, enabled and strategic value kept separate;
• ☐ adoption and ramp assumptions;
• ☐ decommissioning dates and owners;
• ☐ downside, base and upside scenarios;
• ☐ payback, NPV and key sensitivities;
• ☐ post-go-live value governance;
• ☐ decisions that reopen the case.

The case is ready when a reviewer can change any material assumption and see the decision move. If the model is a static total, it is a presentation, not a decision tool.

11. Fund a management system for value

The business case should survive funding. Its baselines, assumptions, owners and review dates become the first version of the value ledger.

That changes the programme conversation. Design decisions can be tested against benefit mechanics. Scope changes can show which benefit, risk or cost they move. Adoption is planned before go-live. Decommissioning is treated as a value event. Finance is present before the first realisation review, not invited after the number is missed.

The strongest SAP case is not the one with the largest ROI. It is the one that remains useful when the programme encounters reality.

Altivate provides SAP advisory and implementation services and therefore has a commercial interest in SAP transformation. Test the option set and benefit mechanics against minimum-change and non-SAP alternatives, and give the financial challenge role independence from the delivery recommendation.

Continue with SAP Value Realisation Starts Before Go-Live, or return to White Papers.

Sources and verification status

Checked 26 July 2026. SAP sources are vendor guidance. No SAP benchmark, composite customer ROI or Altivate client result is used as a calculator default.

• SAP Community by SAP, Building a Compelling S/4HANA Business Case – vendor framing of strategic, technical and financial business-case work.
• SAP Help Portal, Value Accelerators in a Fit-to-Standard Scenario – current vendor guidance on scope, fit-to-standard workshops and value-accelerator use.
• SAP News Center, Why a Business Case Is the Secret to a Smooth Path to SAP S/4HANA – vendor perspective on using the case as a transformation roadmap.
• SAP, Upgrading SAP S/4HANA: Why, How, and Best Practices – vendor guide covering business case, upgrade planning and continued value.