The One Question Every CFO Should Ask Before Approving an ERP Budget
Most ERP business cases are well constructed.
They include:
ROI projections
Efficiency gains
Headcount assumptions
Technology rationalization
On paper, they hold up.
But there’s one question that rarely gets asked directly:
“What specifically will be done differently on Day 1 after go-live?”
Not in theory. In practice.
Because if the answer is vague, the business case is incomplete.
Why This Matters
ERP value is not created by implementation.
It is created by behavior change after implementation.
If:
Forecast cycles don’t shorten
Decision rights don’t shift
Reporting doesn’t simplify
Then the system has modernized the infrastructure, not the business.
Where Business Cases Fall Short
Most cases assume adoption.
They don’t define:
What stops happening
What starts happening
Who is accountable for the change
Without that clarity, benefits remain theoretical.
A Better Framing
Before approving funding, CFOs should press for:
Specific process changes
Named ownership of those changes
A timeline for when they become standard
Not “improvement.”
Replacement of current behavior.
Final Thought
Technology enables change.
It does not enforce it.
If the organization hasn’t agreed on what will change, the system will reflect the past more than it shapes the future.
Clarifying that distinction is a key part of how we support finance leaders at 7Dimensions Consulting, particularly when investment decisions need to translate into measurable outcomes.
