Advisory Services · Business case
How to justify an
ERP or CRM replacement.
Quantify the delta difference first. Measure how the process runs today, define how it should run, and express the gap as efficiency gained, steps removed, hours returned per employee, and troubleshooting and support avoided. A replacement is justified when that annual delta pays back the project cost on a timeline the business accepts.
Last updated October 9, 2026
The metrics that make the case
| Metric | What it measures | Where the number comes from |
|---|---|---|
| Efficiency gained | Change in throughput or cycle time for the same work | Measured cycle time and volume, before and after |
| Steps removed | Handoffs, approvals and manual stages eliminated | The mapped current-state and future-state workflows |
| Hours returned per employee | Time given back to the people feeding the process | Hours per task × volume, converted at your own hourly rate |
| Troubleshooting and support avoided | Tickets, rework and downtime the old process generates | Your ticket and incident history |
| Licenses and subscriptions retired | Recurring spend that stops | Contracts and renewal notices |
A business case in six lines
- Baseline: the measured current-state annual cost of the process.
- Future state: the defined target process and its annual cost.
- Annual delta: baseline minus future-state cost.
- One-time cost: the full cost of making the change, including the work around the platform.
- Payback: one-time cost ÷ annual delta.
- Dependencies and risks: what the change touches, and what has to be true for the delta to materialize.
Finance leaders read assumptions first. Show where each input came from and use your own rates and volumes rather than industry averages.
Do we need a new ERP or CRM, or a better process?
Often the process. If the delta is small, replacing the system will not pay back and the money is better spent elsewhere. If it is large, the delta tells you what the new system must fix, which keeps the platform decision tied to the outcome. Moving a broken process onto a new platform reproduces the problem at higher cost.
What if the delta is small?
That is a useful result. It tells you not to spend on a project that would not pay back, and it is far cheaper to learn before committing than after. A small delta in one process can also point to a larger one in a neighboring process worth assessing next.
Start with your own numbers
The free Hidden Cost Diagnostic gives a first estimate of what manual work, workarounds and disconnected systems cost today, using your own inputs. The Growth Ceiling Diagnostic shows where a process caps growth. The assessment turns either estimate into a documented, defensible delta.
Keep reading
Common questions
Frequently asked questions
How do you justify an ERP replacement?
Quantify the delta difference first: efficiency gained, steps removed, hours returned per employee, and troubleshooting and support avoided. The replacement is justified when the annual delta pays back the project cost on a timeline the business accepts.
How do you justify a CRM replacement?
The same way: measure the sales process today, define the future state, and express the gap in hours returned to sellers, support avoided and revenue opportunity captured, then compare the annual delta with the project cost.
Do we need a new ERP, or a better process?
Often the process. If the delta is small, a new system will not pay back. If it is large, it tells you what the new system must fix.
What if the delta is small?
That is a useful result. It tells you not to spend on a project that would not pay back, before you commit.
What do finance leaders want to see in a business case?
Measured inputs, stated assumptions, an annual delta and a payback period built from your own rates and volumes rather than industry averages.
Take a number to your board
We will quantify the delta before you commit to a platform. The first conversation costs nothing.