Intro
ROI is one of the most widely used metrics in business. It’s quick, simple, and part of the language leaders use to compare options and justify initiatives.
Yet ROI is often misused—calculated inconsistently, stretched to “prove” a case, or applied where it doesn’t fit. Used in isolation, it can distort priorities and lead to poor choices.
At TransparentChoice, we see ROI as an important tool—but only one piece of the puzzle. Factors such as strategic alignment, risk, feasibility, and capacity are just as critical to sound decisions.
This guide explains what ROI is (and isn’t), when to use it, when not to, how to calculate it credibly, and how to apply it responsibly in real-world decisions.
What ROI Is (and Isn’t)
ROI expresses an investment’s net financial gain relative to its cost. Financial benefits might include additional contribution (extra revenue minus the variable costs of earning it) or genuinely avoided expenditure; gross revenue or time saved is not automatically a financial benefit.
For the simple, undiscounted calculation used here:
ROI = (Total financial benefits − Total investment costs) ÷ Total investment costs
Multiply the ratio by 100 to express it as a percentage. State the investment costs included and the period covered: a cumulative return over two years is not an annual return. If £1 invested generates £1.50 in total financial benefits, the net ROI is 50%, not 150%.
Where ROI is expected
- Projects: Sponsors must show expected ROI to secure approval.
- Products & services: Vendors are expected to evidence ROI for buyers.
- Initiatives: Leaders are asked to defend ROI when allocating resources.
In most organisations, ROI is a default question—success depends on how clearly you explain and support it.
Why ROI is widely used
- Clear language: ROI is widely understood across functions and industries.
- Flexible: Applies to most investments with costs and benefits.
- Quick signal: Positive ROI = gain; negative ROI = loss.
- Benchmarking tool: Many organisations use ROI “hurdle rates” to compare options consistently.
Limits of ROI
ROI can oversimplify an investment when benefits are non-financial, cash flows arrive at different times or risks differ substantially. Net Present Value (NPV) discounts dated cash flows; Internal Rate of Return (IRR) is the discount rate at which NPV equals zero; it can mislead when comparing projects of different size or timing. The Analytic Hierarchy Process (AHP) helps structure judgement across multiple criteria, including considerations that are not well represented by financial return. These methods answer different questions rather than serving as interchangeable ROI replacements.
At TransparentChoice, we treat ROI as one lens in a broader model—balanced with strategic fit, risk, and capacity—so financials inform decisions without dominating them.
How to Calculate ROI
For this simple, undiscounted method, use financial benefits and investment costs for the same time period:
ROI = ((Total financial benefits − Total investment costs) ÷ Total investment costs) × 100%
Quick example (first year only):
- Annual heating cost before insulation = £1,000.
- Insulation cuts that cost by 20%, saving £200 in year one.
- Insulation costs £100 upfront; assume no other first-year costs.
ROI = ((£200 − £100) ÷ £100) × 100% = 100%
This is a one-year simple ROI, not a lifetime or annualised return. Over a longer period, count the costs and benefits for that period; when their timing matters, use dated cash flows and consider Net Present Value (NPV).
Building an ROI model
A credible model starts with the financial change the investment could cause, compared with what would happen without it. Build and check the estimate in four moves:
- Set the boundary: define the alternative being compared, whose finances count and the appraisal period.
- Trace financial benefits: show how higher volume, improved productivity or reduced usage creates incremental contribution or expenditure that can actually be avoided. Saved hours or gross new revenue are not automatically cash benefits.
- Count relevant costs: include implementation, internal effort, transition, recurring expenses and dependencies; avoid double-counted benefits. For a new choice, separate future costs from sunk spend.
- Expose assumptions: record key input values, their sources, the cash-conversion condition and who can check them. Keep cash flows by period even if presenting a single ROI percentage.
Compact illustration: Suppose a process change avoids an externally paid £10 fee on 60% of 10,000 eligible transactions each year. Over two years, with £60,000 implementation cost and £10,000 extra annual operating cost: benefits = 10,000 × 60% × £10 × 2 = £120,000; costs = £60,000 + (2 × £10,000) = £80,000; two-year simple ROI = 50%.
This only works as a financial estimate if the external fee really disappears and the new process's costs are included. The numbers are illustrative, not typical investment results.
Examples of ROI models
- Accounting software: Simple time-savings calculation. See example.
- Training: Requires assumptions about performance improvement. See example.
- Projects: Broader scope with multiple inputs. See example.
- Risk reduction: Value comes from avoided losses. See example.
Sensitivity and uncertainty
An ROI result changes when its inputs change. One-factor sensitivity varies one assumption while holding the others fixed; scenarios combine plausible changes in several assumptions. Neither establishes how likely an outcome is.
For the compact two-year model above, the base-case ROI is 50%. The following one-factor results are calculated from that model, not independent guesses:
| Driver (downside / base / upside) | ROI downside | ROI base | ROI upside | Change from base (pts) |
|---|---|---|---|---|
| Transactions changing process: 40% / 60% / 80% | 0% | 50% | 100% | −50 / +50 |
| Avoidable fee per transaction: £8 / £10 / £12 | 20% | 50% | 80% | −30 / +30 |
| Implementation cost: £70k / £60k / £50k | 33.3% | 50% | 71.4% | −16.7 / +21.4 |
At 40% of eligible transactions changing process, for example, total benefits fall to £80,000, equalling the model's £80,000 costs: simple ROI reaches 0%. This is a break-even point for this calculation, not an approval rule. A hurdle or discounted cash-flow assessment may require a stronger result.
Sort each driver's changes from largest to smallest to create a tornado diagram. It communicates exposure in ROI percentage points, not probability:
Look beyond the widest bars: identify which uncertain input could overturn the financial case, what evidence could resolve it, and whether delays would change the result. Sensitivity shows consequences of assumptions, not forecasts.
Using Excel for ROI models
A useful spreadsheet links inputs (such as adoption, avoidable cost, horizon and implementation expense) to calculated benefits and costs, then to an ROI output. Keep the time-phased cash-flow view and record input sources. Do not type scenario ROI figures independently of their drivers.
Illustrative combined scenarios: Several inputs change together below, unlike the one-factor table. The annual transaction volume (10,000), two-year period and additional annual operating cost (£10,000) remain fixed.
| Input / output | Pessimistic | Base | Optimistic |
|---|---|---|---|
| Transactions changing process | 40% | 60% | 80% |
| Avoidable fee per transaction | £8 | £10 | £12 |
| Implementation cost | £70,000 | £60,000 | £50,000 |
| Operating costs, two years | £20,000 | £20,000 | £20,000 |
| Total financial benefits | £64,000 | £120,000 | £192,000 |
| Total investment costs | £90,000 | £80,000 | £70,000 |
| Two-year simple ROI | −28.9% | 50% | 174.3% |
These are arithmetic illustrations, not probabilities or evidence that the combined extremes are plausible. Check how the inputs depend on each other before using them for a decision.
Excel tips:
- Colour-code editable inputs; separate assumptions from formulas and outputs.
- Use Data Validation and a Data Table or Scenario Manager to reproduce the tests.
- Flag a missing or zero cost denominator rather than masking it as a valid ROI.
- Build tornado bars from calculated changes against the same base case.
The aim is a model another person can understand and challenge, not simply a persuasive percentage.
ROI calculators
Vendors often publish ROI calculators. They can provide a quick sense-check, but many are sales tools and operate as black boxes. Use them for ideas, then build a transparent model you can explain to stakeholders. For guidance, see Tips for building an ROI calculator.
Examples
Even if you don’t use them directly, reviewing calculators can suggest useful inputs:
- HubSpot ROI calculator – marketing and lead generation
- Red Tomato ROI calculator – promotional products
- Birdview PSA ROI calculator – project management
Common ROI Mistakes
ROI is useful—when applied correctly. The two big pitfalls are using ROI in the wrong situations and miscalculating ROI.
When not to use ROI
ROI describes simple financial return; it should not carry the full investment judgement. Each limit below points to a different method, such as discounting for timing or the Analytic Hierarchy Process (AHP) for structuring non-financial criteria.
- Delayed payback: ROI ignores the time value of money. If benefits arrive years later, use NPV or IRR.
- Non-financial benefits: ROI misses outcomes like safety or customer satisfaction. AHP lets you weigh these alongside financial return.
- Different risk levels: Comparing a low-risk efficiency project with a high-risk product launch on ROI alone is misleading. Factor risk in explicitly.
Bottom line: use ROI when financial return is the main driver. When timing, non-financial outcomes, or risk matter as much, combine methods.
Common errors in ROI calculation
Even when ROI is the right tool, calculation mistakes can skew results. Watch for:
- Overestimated benefits / underestimated costs: Optimism bias. Fix with independent review.
- Making all benefits financial: Not all benefits are reliably quantifiable. Forcing “hours saved” estimates can create spurious precision, turning ROI into fiction with decimal places.
- Ignoring dependencies: Overlaps can cause double-counting or missed costs.
- Treating internal resources as “free”: Ignoring people’s time misses opportunity cost and encourages weak planning. It also hides viable alternatives in the typical “build vs buy” decision.
- Treating ROI as static: Costs and benefits change. Revisit regularly.
- Omitting cost avoidance: Excluding avoided costs (e.g. deferred upgrades) understates ROI.
- Ignoring opportunity cost: Resources used here can’t be used elsewhere.
- Hidden costs: Staff time, compliance, integration, and change management.
- Working in isolation: Cross-functional input reduces blind spots.
- Ignoring uncertainty: A single number reduces credibility. Use ranges, scenarios, or tornado diagrams.
- “Pet projects” in disguise: Massaging assumptions to “make the numbers work” (e.g. unexplained margin jumps) creates a false case. Use independent review and lock assumption changes.
- No measurement plan: Without a commitment to measure, ROI becomes a tick-box exercise. Build validation into delivery:
- Identify existing data that is “good enough” to track impact.
- Run pilots while a credible control group still exists.
- Include measurement costs (panels, dashboards) in the business case.
Takeaway: ROI is a decision aid, not proof. Use it to inform choices—not to force them.
Project ROI
ROI isn’t a single calculation; it’s a thread that runs from proposal to completion. The challenge is to take a headline number and turn it into a credible case, a feasible plan, and realised benefits—and to keep testing whether the value still stands up as reality unfolds.
Proposal: build a credible business case
Many organisations set minimum ROI thresholds to shape decisions. Sources such as Epicflow describe 10%+ as a common floor, while Monograph discusses higher figures typical in engineering (e.g. 25%+ seen as healthy and 40%+ signalling tight scope control, above 100% often deserve extra scrutiny for missing costs). These are directional signals only—calibrate to your context and governance.
At proposal stage, ROI is a value hypothesis. State the headline ROI and payback plainly, then make the scaffolding visible: what must be true about adoption, volumes, pricing, or unit costs; where the data comes from; how sensitive the outcome is to a few pivotal assumptions.
A simple range (best/base/worst) or a tornado view helps people see uncertainty without getting lost in detail. Note any dependencies—projects, vendors, regulatory steps—that could shift timing or magnitude, and explain how benefits will be measured later so today’s promise can be tested tomorrow.
Approval: validate and de-bias the case
Approval is where optimism meets governance. The question isn’t “is the ROI big?” but “is it believable and deliverable?” Sense-check the assumptions against benchmarks and past results, and look for scope or timing mismatches between costs and benefits.
Consider feasibility and capacity: even a strong ROI can unwind if the organisation can’t staff and sequence the work. Balance the financial view with strategic fit, risk and feasibility (methods like AHP can help) so the decision isn’t driven by the ROI figure alone.
Execution: protect the return
Good economics can evaporate through delays, multitasking, or scope creep. Plan with capacity in mind and sequence work to avoid needless switching. Treat change control as an economic decision—if scope shifts, show the impact on the forecast, and prefer deferring low-value items over stretching teams thin.
Track the leading indicators behind the ROI (for example, user adoption or cycle time) so you see erosion early. Replace assumptions with observed data as you go, and keep a living forecast; if the expected return sinks below your hurdle, be ready to re-scope or pause.
Completion: measure and learn
ROI is proven only when it is measured. Revisit the original baseline and compare realised benefits to the forecast, including any timing effects. Attribute variance deliberately: what came from assumption error (the world was different), what from delivery variance (we executed differently), and what from external change (market, regulation, shocks).
Record the realised ROI and payback, publish a short benefits realisation note, and feed the lessons into your value library so future proposals start smarter.
Portfolio ROI
Many projects are evaluated using forecast ROI, but not every important investment has a credible financial-return percentage. Looking only at the ROI of a single initiative can be misleading. A saving in one project can create delays, bottlenecks, or lost opportunities elsewhere.
The challenge is to make portfolio choices that reflect financial return alongside strategic value, necessary operations, mandatory commitments, risk and scarce capacity. Leaders must decide what to fund, continue, change or defer. Essential operational work can protect service reliability and enable future change even when its value is difficult to capture in a conventional ROI calculation.
This broader view is difficult because projects interact. Cutting spend on one initiative might free budget but slow down delivery of a strategic programme. Approving multiple high-ROI projects at once can overwhelm scarce resources, pushing all of them out and eroding their benefits. Portfolio ROI depends as much on selection, sequencing, and capacity as on the arithmetic inside any one spreadsheet.
Using ROI responsibly across a portfolio is not a single calculation. Four practices help:
- Challenge weaker commitments: Revisit work whose expected contribution no longer justifies its cost, risk, opportunity cost or resource requirements.
- Balance demand with capacity: Make resource constraints and competing demands visible before treating a proposed portfolio as deliverable.
- Sequence realistically: Avoid starting everything at once; stagger work to reduce multitasking and gridlock.
- Balance essential work and change: Account for operational needs, mandatory commitments and transformation in the same resource-allocation discussion.
TransparentChoice supports this portfolio decision process. Organisations can assess initiative contributions to priorities, model funding and capacity constraints, and compare feasible portfolio choices. For the fuller decision process, see Project Prioritization: The Ultimate Guide.
Conclusion
Return on Investment (ROI) is a widely used tool in decision-making. It offers a simple way to compare investments and a common language for communicating value.
But ROI has limits—especially when benefits are non-financial, paybacks are long or uncertain, or projects carry different risk profiles. In these cases, combine ROI with NPV, IRR, or the Analytic Hierarchy Process (AHP).
Crucially, building an ROI model surfaces assumptions, tests sensitivities, and encourages collaboration. Even if the final number is imperfect, the exercise improves decisions.
Used well, ROI is a powerful lens. Used poorly, it can distort priorities. Develop the discipline to apply ROI correctly—and in balance with other criteria.
Glossary
- ROI (Return on Investment): (Gain − Cost) ÷ Cost, usually expressed as a percentage.
- NPV (Net Present Value): Discounts future cash flows to reflect the time value of money.
- IRR (Internal Rate of Return): The discount rate at which the present value of inflows equals outflows.
- AHP (Analytic Hierarchy Process): A structured method that compares options against multiple weighted criteria.
- Hurdle rate: The minimum acceptable return required before approving an investment.
- Tornado diagram: A chart that shows which variables most affect ROI by displaying sensitivity ranges.
