Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 36 ยท Selection and Case Studies

Total Cost of Ownership and ROI

Build a total cost of ownership model for ERP or CRM, estimate benefits, and compute ROI, payback and NPV with sensitivity analysis, using runnable Python examples.

The price quoted by a vendor is only a fraction of what an ERP or CRM costs over its life. Licences or subscriptions, implementation, data migration, integration, training, internal staff time, hosting, support, upgrades and the productivity dip after go-live all add up. On the other side, the system should produce benefits: lower costs, faster processes, higher sales, fewer errors. Total cost of ownership (TCO) and return on investment (ROI) put both sides into a model you can discuss, challenge and track.

All figures in this lesson are invented to show the method; use your own numbers.

What belongs in TCO

One-time costs

Licences or setup Perpetual licences, subscription start.
Implementation Consulting, configuration, extensions.
Data and integration Migration, interfaces, testing.
Training and change Courses, backfill, communication.

Often 1.5 to 3 times the first-year licence cost.

1 / 2

Do not forget hidden costs: internal staff time spent in workshops and testing (often the biggest unbudgeted item), parallel running, temporary staff to cover the learning curve, extra storage and API volume charges, customization maintenance and the cost of leaving the old system (contract termination, data archiving).

Python A five-year TCO model

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Estimating benefits

Benefits come in four kinds, from easiest to hardest to measure:

  1. Hard savings: fewer licences for retired systems, lower stock holding, reduced overtime, discounts from better purchasing.
  2. Productivity: time saved per task times number of tasks times loaded labour cost. Count it as a benefit only if the time is really redeployed or avoided; an hour saved per person per week is not money unless something changes.
  3. Revenue effects: better conversion, upselling, retention and faster quoting. Use cautious assumptions and share credit with other initiatives.
  4. Risk and compliance: fewer errors, audit findings and fines. Estimate expected loss avoided (probability times impact).

Ask the benefit owner in the business (not the project team) to commit to each number. A benefit without an owner rarely materialises.

ROI, payback and NPV

  • ROI = (total benefits - total costs) / total costs, over a stated period.
  • Payback period = the time until cumulative benefits cover cumulative costs.
  • NPV (net present value) discounts future cash flows to today's value at a discount rate (the return the company could get elsewhere, or its cost of capital): NPV = sum of cash flow in year t divided by (1 + r) to the power t. A positive NPV means the project beats the discount rate.
  • IRR is the discount rate at which NPV is zero.
Python ROI, payback and NPV

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sensitivity and risk

A single ROI number hides uncertainty. Test what if scenarios: costs 25 percent higher, benefits 30 percent lower, benefits delayed by a year. If the project only works in the best case, it is fragile; if it still pays off in the pessimistic case, it is robust.

Python Scenario analysis

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Soft benefits and the honesty rule

Some benefits resist numbers: better decisions, happier customers, employer attractiveness. List them, but do not force a number just to inflate the case. Be equally candid about costs of doing nothing: a legacy system that is out of support, a manual process that cannot scale, regulatory deadlines. Sometimes the alternative is not "no cost" but "a different, growing cost".

Tracking after go-live

A business case is not a document to file. Assign an owner to every benefit, measure it against a baseline (see KPIs, dashboards and business reports), review it quarterly, and update the model with actuals. This turns the case into a management tool and builds credibility for the next project.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which cost is most often left out of an ERP business case?

    Internal time is large, spread across departments and rarely budgeted, so it is a classic hidden cost.
  2. 2. What does a positive NPV mean?

    NPV adds all cash flows discounted to today's value; positive means the project beats the required return.
  3. 3. Why run scenario analysis?

    Scenarios reveal how fragile the single-number answer is.
  4. 4. Who should commit to a benefit figure?

    Benefits are only realised when a business owner takes accountability for them.

Summary

  • TCO includes one-time and recurring costs and the hidden items, especially internal time.
  • Benefits are hard savings, productivity, revenue effects and risk reduction; each needs an owner.
  • ROI, payback, NPV and IRR summarize the case; discounting reflects the time value of money.
  • Test scenarios and be honest about soft benefits and the cost of doing nothing.
  • Track actuals after go-live.

Next: Case Studies and Lessons Learned