Return on investment (ROI) compares net financial benefits with the cost of an investment. It cannot answer the investment decision on its own. An attractive percentage may hide delayed benefits, a shortage of operating cash or weak assumptions. A useful comparison starts with what you will spend, what you expect to earn or save, over what period, and the evidence supporting those estimates.
Start with the decision and baseline
Define the problem and alternatives before calculating ROI. You might buy a system, improve the current process or run a limited trial. The baseline is what would happen without the investment, including its costs and risks. Do not assume that continuing as you are is free or that current performance will remain unchanged.
Record the comparison period, currency and scope, and whether the figures represent the organization or a particular project. Compare alternatives over the same period and using consistent rules. Counting 3 years of benefits for one option against only 1 year of costs for another does not produce a fair comparison. Keep forecasts made before implementation distinct from actual results measured afterwards.
Identify costs and benefits without overstating them
Total costs include purchase, implementation, integration, training, staff time, operation, maintenance and exit where relevant. Document material items and the source of each estimate rather than relying only on the supplier price. If staff time is included as an economic cost, explain that it may not be an additional cash payment and maintain that distinction throughout the comparison.
Incremental benefits are gains attributable to the investment compared with the baseline. They might include avoided expenditure or additional contribution from new sales. Do not count all sales revenue as a net benefit if production or service costs have not been deducted. Avoid counting fewer errors and saved rework twice when they describe the same effect.
Saving 200 staff hours does not automatically save payroll cash. Salaries may remain unchanged while the team can complete more work. In that case, show released time as additional capacity and explain how it will be used. Record a cash saving only when there is evidence of an actual spending reduction, such as paid overtime or an external service.
Calculate and interpret simple ROI
Net benefit equals financial benefits minus the costs included within the calculation. Simple ROI is that net benefit divided by those costs, multiplied by 100. The denominator must be greater than zero, and benefits and costs must use the same currency, period and scope.
ROI = (Benefits − Costs) ÷ Costs × 100
With benefits of 130,000 and costs of 100,000, net benefit is 30,000 and ROI is 30%. Each 1 of cost corresponds to 0.30 of net benefit over the defined period. This is not a sales profit margin or an annual return unless the period is a year. Simple ROI also does not account for the timing of cash flows within that period.
(130,000 − 100,000) ÷ 100,000 × 100 = 30%Illustrative amounts in the same monetary units and period, not ATMACSS results. Simple ROI does not account for the timing of cash flows.
Worked example: reducing order-processing errors
This example is entirely hypothetical. The figures are not ATMACSS results or industry benchmarks. A company considers a system to reduce order-processing errors over 12 months. It compares the project with continuing the current process and uses AED for all amounts. To simplify the illustration, figures are before tax and financing, with no residual project value at the end of the period.
Estimated costs are 60,000 for purchase and integration, 15,000 for training and team time, and 25,000 for operation and support: 100,000 in total. Expected benefits are 80,000 from lower rework and compensation expenditure and 50,000 from eliminating a paid external processing service: 130,000 in total. Check that these benefits do not overlap and that the savings will actually occur against the baseline.
The finance owner reviews expenditure records and the supplier quotation; the operations manager checks the error volume and the feasibility of reducing it. The team identifies whether costs fall upfront or throughout the year and prepares a separate cash schedule that distinguishes staff-time value. It then calculates the expected 30% ROI and presents the assumptions alongside it, without presenting the return as guaranteed.
If benefits alone fall to 110,000 while costs remain 100,000, ROI becomes 10%. If costs alone rise to 120,000 while benefits remain 130,000, ROI becomes approximately 8.3%. If both changes occur, net benefit becomes a loss of 10,000 and ROI approximately −8.3%. These are calculation scenarios, not statements about statistical probabilities.
Test assumptions and the source of improvement
Sensitivity analysis changes one assumption, such as cost or usage, while holding others constant. A scenario combines related changes, such as delayed implementation, lower adoption and higher support costs. Present evidence-based estimated ranges. Do not call them statistical confidence intervals unless they were calculated using an appropriate statistical method.
Also ask how much improvement comes from the investment itself. Errors might fall because there are fewer orders or because another process changed. Compare similar conditions and record changes in volume, order mix and prices. A limited trial or comparison between similar units can help, but improvement after implementation alone does not establish that the project caused it.

Understand timing, cash availability and scale
The payback period is the time needed to recover the investment through net cash inflows. It helps explain how quickly cash is recovered, but simple payback ignores the time value of money and benefits arriving after payback. You cannot determine it from the 30% ROI alone without knowing when the cash flows occur.
Net present value (NPV) converts future cash flows to their value today using a suitable discount rate, then adds the inflows and outflows. It is useful for decisions spanning several years. Explain the basis of the rate and its consistency with inflation, tax and risk. Do not copy a rate from an example or public-sector guide into a commercial investment without justification.
Scale matters too. A net benefit of 6,000 on a cost of 10,000 gives a 60% ROI, while a net benefit of 200,000 on a cost of 1,000,000 gives a 20% ROI. The higher percentage is not automatically the better choice. Compare total value, available cash, potential loss and implementation capacity over a consistent period.
Present non-financial effects clearly
Safety, compliance, customer trust, resilience and environmental effects may be decisive even when they are difficult to monetize. Present them alongside the calculation using clear criteria and suitable evidence. Do not invent monetary values to improve the ratio. If an action is necessary to meet an applicable obligation, the practical question is how to meet it effectively, not whether to ignore it because financial ROI is low.
Review benefits after implementation
Assign each benefit an owner, data source and measurement date. In the example, the finance owner reviews actual expenditure monthly, while the operations manager monitors errors, order volume and service quality. Compare results with the approved forecast and explain differences before expanding. Evidence and obligations may support continuing, adjusting implementation or stopping an unproductive component.
Match review timing to the benefit: expenditure savings may appear monthly, while capability effects can take longer. When scope, prices or usage change, update the forecast while retaining the original case and reasons for the revision. Do not silently replace the original figures or allow two departments to claim the same benefit.
Check before approving the decision
- A baseline, alternatives and a consistent period and currency.
- Documented costs and benefits without double counting.
- Cash savings distinguished from released staff time.
- A transparent calculation, downside scenario and cash-flow schedule.
- Non-financial effects, owners and review dates.
Your next step
Choose one investment under consideration and put its costs and benefits in a table showing the source and owner of each figure. Calculate the base case, then test an assumption that could change the decision. Link the comparison to your business growth strategy and define the performance indicators you will use to verify results after implementation.

