An IT investment can be on time and within budget yet still fail to create useful value. The real test is whether it improves an agreed business outcome after people start using it. ROI helps with that conversation, but it should sit beside lifetime cost, risk, adoption and strategic value rather than replace them.
The useful question: Do not begin with “What return can we claim?” Begin with “What decision are we making, what outcome should change, and what evidence would show that it worked?”
Start with the outcome
Give the investment a purpose that a business owner can recognise. Faster month-end reporting, fewer account takeovers, shorter customer waiting time and less manual re-entry are measurable outcomes. “Move to the cloud” or “implement AI” describes technology, not the result.
Choose a baseline before the project changes the process. Without a starting point, an improvement can be plausible but difficult to prove.
Count the full lifetime cost
The purchase price rarely tells the whole story. Include implementation, internal staff time, migration, integration, security work, training, change support, support contracts, infrastructure, licence growth, upgrades and eventual retirement.
Separate committed costs from estimates and show the assumptions. If adoption, volume or exchange rates can move the total significantly, model more than one scenario.
- Software, hardware and subscription charges
- Implementation and specialist services
- Internal staff time
- Data preparation and migration
- Integration and custom development
- Security, privacy and compliance work
- Training and organisational change
- Operations, support and future upgrades
- Exit, replacement and data-retention costs
Measure benefits without pretending
Some benefits can be translated into money: reduced external spending, avoided overtime, lower error handling or additional capacity. Others matter without a reliable cash value, such as improved resilience, better regulatory evidence or a safer customer experience.
Keep both, but label them honestly. Do not turn every minute “saved” into cash unless the organisation can explain how that time produces a real financial effect.
Use ROI correctly
A common simple calculation is:
**ROI (%) = (benefits − costs) ÷ costs × 100**
If an investment costs €100,000 and produces €130,000 in measured benefits over the chosen period, the net benefit is €30,000 and the simple ROI is 30%. The calculation is only as reliable as the period, costs, benefits and assumptions behind it.
ROI also ignores the timing of cash flows. For larger or longer investments, finance may add net present value, internal rate of return or payback period. GAO’s IT investment framework recognises several financial and qualitative methods because no single number answers every decision.
A quick comparison of net benefit with cost. Easy to understand, but sensitive to assumptions.
Shows how long it takes to recover the investment. Useful for liquidity, but weak on value after payback.
Brings future cash flows into today’s value. Better for comparing investments over time.
Shows whether the service actually became faster, safer or more reliable.
Review value after launch
The business case is a forecast. Treat it as a testable promise, not a finished result. Agree when benefits should appear and review actual performance after launch.
Check who is using the new service, how often and where workarounds remain.
Use the same measurement method used before the change.
Replace estimates with actual implementation and operating cost.
Record why benefits or costs differ from the forecast.
Continue, improve, reduce scope, renegotiate or stop based on evidence.
A useful dashboard is small. It might show two or three business outcomes, adoption, actual cost, one important service measure and the largest open risk. More metrics do not automatically create more insight.
Put risk into the decision
Forecasts should not hide uncertainty. Show an expected case together with realistic lower and upper cases. Record dependencies such as data quality, supplier delivery, user adoption and another project completing on time.
The U.S. GAO describes technology investment management as a cycle of selecting, controlling and evaluating investments. That is the important habit: value is managed throughout the investment, not calculated once to win approval.
The takeaway
IT spending pays off when the organisation can connect cost to a real outcome, measure the change and act when the evidence is different from the plan. ROI can support that work, but the strongest decision combines financial return, service results, strategic fit and risk.
Key takeaways
- Define the business outcome and baseline first
- Include the full lifetime cost
- Keep measured, estimated and qualitative benefits separate
- Use ROI with other financial and operational measures
- Review actual value after launch
- Change or stop investments that no longer justify their cost and risk