ROI Forecast Calculator

The basic formula and what it omits

ROI is net gain divided by cost, expressed as a percentage. Its virtue is simplicity and its flaw is that it ignores time entirely. A 50 percent return over one year and a 50 percent return over five years produce the same ROI and are completely different investments. Any comparison between options with different durations must be annualised before it means anything.

Annualising properly

Dividing total return by the number of years overstates the result, because it ignores compounding. The correct approach takes the nth root of the growth multiple, where n is the number of years, and subtracts one. A 50 percent total return over five years annualises to about 8.4 percent, not 10.

Count the costs people leave out

Direct purchase price is the easy part. Implementation, training, integration, ongoing maintenance, support contracts and the staff time consumed by all of it are routinely excluded, and they frequently exceed the licence fee. Opportunity cost belongs in the calculation too: capital spent here is capital not spent on the next best option, and the comparison is against that alternative rather than against doing nothing.

Payback period is the risk question

ROI asks how much you get back; payback asks how long until you are whole. A project returning 200 percent over seven years may be worse than one returning 60 percent over eighteen months if the environment is uncertain, because the shorter horizon carries less risk of the assumptions expiring. Payback also ignores everything after break-even, so the two measures answer different questions and should be read together.

Discount future cash flows for anything multi-year

Money arriving in year five is worth less than money today. Net present value discounts each future flow at a rate reflecting your cost of capital, and internal rate of return expresses the result as a percentage comparable to other opportunities. For any project spanning more than two or three years, undiscounted ROI systematically flatters the outcome.

Be honest about the benefit side

ROI forecasts fail on the numerator far more often than the denominator. Projected time savings assume the freed hours become productive work rather than absorbed slack. Projected revenue assumes adoption that has not happened yet. The discipline that makes a forecast useful is stating those assumptions explicitly and revisiting them after the fact — a forecast nobody ever checks is a story, not a calculation.

Related tools

• Incident Impact Calculator — Estimate the cost of a security incident from severity, affected users and downtime hours, with a compliance and trust rating and the response actions each severity level demands.
• Third-Party Risk Assessor — Assess vendor risk based on data access and type.
• Data Breach Cost Estimator — Estimate what a data breach would cost from records exposed, cost per record, days to detect and hours of downtime, split into direct and indirect costs.
• SaaS Risk Heatmap — Pick the SaaS apps your company runs, add your own, and get a heatmap ranking each by data criticality times access scope, with the risk each carries.