The ERP modernisation business case — the honest case, build-vs-buy, and the cost of not acting
The short answer
An ERP modernisation business case has two halves the steering committee usually conflates: the inspirational case (competitive advantage, agility) that gets the budget, and the honest case (the obligation, the deadline, the consequence) that the programme is actually run on. Build both. The honest case for most SAP estates is 'ECC mainstream maintenance ends 31 December 2027, our capacity is finite, and the cost of not acting is rising' — then the model decides the path: which of the five options (brownfield, greenfield, selective/bluefield, stay-and-extend, replace), a five-year TCO that includes the data-remediation line most cases omit, and a weighted scorecard so the decision is defensible rather than vendor-led. The obligation-driven programme survives the reorganisation that kills the inspiration-driven one.
The business case — the seven moves that make it defensible
- 01
Write the inspirational case to get the budget — then put it away
The steering committee approves on the language it approved: competitive advantage, agility, transformation. That case is not dishonest, it is incomplete. Write it, win the budget, then run the programme on the honest one. Every actual decision — scope, sequencing, resourcing — is made against the obligation, not the aspiration.
- 02
State the honest case: the obligation, the deadline, the consequence
The durable case usually starts with 'we have to.' We have to move off ECC because mainstream maintenance ends 31 December 2027; our transformation capacity is finite; the longer we wait the more it costs and the fewer skilled hands are available. An obligation-driven programme keeps running when the executive sponsor changes roles — the deadline did not move when they did.
- 03
Run the estate diagnostic — are you past the point of deferral?
Before choosing an option, score the estate: custom-code volume, integration sprawl, version currency, business criticality, and how much runway the 2027 date actually leaves once you subtract scoping, build and a realistic cutover. The honest read is often that the practical deadline is well before the headline date.
- 04
Lay out the five options, each with its trap
Brownfield (technical conversion — fast, but you carry the legacy mess), greenfield (clean rebuild — clean, but expensive and disruptive), selective/bluefield (hybrid — flexible, but complex to govern), stay-and-extend (defer — cheapest now, most expensive later), replace (different ERP — rare, high-risk). Name the trap on each so the choice is eyes-open.
- 05
Apply the asset-vs-liability test (brownfield vs greenfield)
The real question is whether your current configuration and customisations are an asset worth carrying forward or a liability worth leaving behind. Score them honestly; a brownfield 'lift' of a liability estate just moves the mess onto a more expensive platform.
- 06
Model the five-year TCO — including the data-remediation line
Licences (or RISE subscription), implementation/SI cost, infrastructure, internal FTE through the programme and into run, AND the data-remediation cost most business cases omit — master-data clean-up is where timelines and budgets actually go. Put a real number on it; a TCO without the data line is fiction.
- 07
Score the options on a weighted scorecard, then write the one-page board decision
Weight the criteria (fit, 5-year TCO, risk, disruption, time-to-value, capability fit) and score each option on the same basis, so the decision is defensible and not the option the loudest vendor pitched. Compress it to a one-page board recommendation: the chosen path, why, the cost, and the cost of not acting.
The two business cases every programme has
Every enterprise ERP programme has two cases: the one written for the steering committee and the one the operator actually believes. The inspirational one talks about competitive advantage and agility — it uses the language the budget gets approved in. The honest one is shorter and usually starts with “we have to.” For most SAP estates today the honest case is: ECC mainstream maintenance ends 31 December 2027, our capacity to deliver is finite, and the cost of waiting is rising while the pool of skilled hands shrinks.
Write the inspirational case to win the budget. Then put it away and run the programme on the honest one — because the obligation-driven programme keeps running when the sponsor moves roles in February, and the inspiration-driven one dies with their calendar.
The line that blows up the budget
The data-remediation line. A modernisation business case that models licences, implementation and infrastructure but leaves out master-data clean-up is fiction, because clean-up is exactly where the timeline and budget actually go. Put a real number on it up front — it is the difference between a case that holds and a programme that surfaces a 12% Business Partner conversion error rate in the dress rehearsal and slips its go-live.
Concrete beats abstract — even in a board paper
“Modernise the ERP estate” is not a decision. “Selective transition for finance and supply chain, brownfield for the rest, five-year TCO of €X including €Y data remediation, versus a cost-of-not-acting of €Z by 2028” is a decision an executive can own. The weighted scorecard exists so the choice is defensible and traceable — not the option the loudest vendor pitched.
This guide is operator practice, not SAP or financial advice — confirm licensing, maintenance dates and figures against your own estate, SAP’s published schedule, and your finance function. The deadline reasoning is worked in the essay The S/4HANA deadline math most organizations calculate wrong; the cutover side is in the S/4HANA cutover checklist.
Frequently asked
When does SAP ECC maintenance end, and why does it drive the business case?
SAP ECC mainstream maintenance ends 31 December 2027. It drives the case because it converts an optional 'transformation' into a dated obligation — and obligation-driven programmes survive sponsor changes and budget rounds that kill inspiration-driven ones. Because transformation capacity is finite, the practical planning deadline for most mid-market estates is well before the headline date.
Brownfield, greenfield or selective — how do I choose?
It turns on whether your current configuration and customisations are an asset to carry forward (favours brownfield) or a liability to leave behind (favours greenfield), and how much disruption the business can absorb (selective/bluefield is the hybrid). Score them on a weighted basis rather than accepting the option a vendor or SI pitches by default.
What do ERP business cases most often get wrong?
Two things: they run on the inspirational case instead of the honest obligation, so they collapse at the first reorganisation; and they omit the data-remediation line from the TCO, so the budget and timeline blow out exactly where master-data clean-up actually consumes them. Build both cases, and put a real number on data remediation.
Is this financial or SAP advice?
No. It is an operator-grade decision and business-case framework. Confirm figures, licensing and maintenance dates against your own estate and SAP's published schedule, and validate the financial case with your finance function.
The done-for-you version: a 15-page operating handbook (the readiness self-check, the five options each with its trap, the asset-vs-liability test, the seven failure modes as a symptom-to-fix catalogue) plus a 6-tab business-case workbook with a worked 5-year TCO, the data-remediation line, and the weighted decision scorecard. Built for the operator who has to make the case before a consultant is on site.
Get the ERP Modernisation Strategy Playbook + Business Case Workbook — $49 →Written by Petko Petkov — 15 years inside enterprise IT operations. Vihren Labs publishes operator-grade templates and playbooks for the enterprise IT stack.