ROI (Return on Investment)
ROI (Return on Investment) is a profitability metric that relates the profit or benefit of an investment to its cost. Expressed as a percentage, ROI shows how much a sum spent – for example on an ERP system – brings back, making investments comparable.
ROI (Return on Investment) is a financial profitability metric that relates the return on an investment to the capital deployed. In a single percentage figure it answers the question: how much does the money invested bring back? The basic formula is ROI = (profit ÷ investment cost) × 100. An ROI of 50 percent means an investment has earned half of its outlay as net return over the period considered. Because ROI condenses returns and costs into a dimensionless figure, it puts very different projects – a new machine, a marketing campaign or the rollout of an ERP system – onto a common yardstick.
In the ERP and digitalisation context, ROI is the central argument for justifying a system decision on economic grounds. An ERP incurs clearly quantifiable costs – licence or subscription, rollout, interfaces, migration, training, operation. Against these costs stand benefit items: saved working time, fewer errors, faster processing, lower inventory. ROI relates the two sides to each other and shows whether and to what extent the project pays off. It is thus the bridge between a pure cost view and a sound investment decision.
At a glance
- ROI = (profit ÷ investment cost) × 100 – profitability as a percentage
- Makes different investments comparable on a common yardstick
- In ERP: benefit (time, errors, inventory) against cost (licence, rollout, operation)
- Positive ROI = the investment pays for itself; the figure shows the profitability
- Complements TCO (the cost side) and payback period (when the outlay is recovered)
How ROI is calculated
In its basic form, ROI divides the profit achieved by the investment cost deployed and multiplies the result by 100 to obtain a percentage. "Profit" here means the net return, that is the benefit minus the ongoing costs. If a project costs 40,000 euros and delivers 60,000 euros of benefit over the period considered, the profit is 20,000 euros and the ROI is (20,000 ÷ 40,000) × 100 = 50 percent. The decisive point is that profit and costs must refer to the same period – otherwise the figure is meaningless.
In classic metric systems – such as the DuPont scheme – ROI is broken down more finely into return on sales multiplied by capital turnover. This breakdown shows whether profitability stems mainly from high margins or from a fast capital turnover. For investment decisions in mid-sized companies the simple form usually suffices; the analytical breakdown is used above all in controlling and balance-sheet analysis.
Quantifying the benefit – the real challenge
The cost side of an ERP project can be quantified relatively cleanly. More difficult and at the same time decisive is the benefit side. Saved working time can be valued via hourly rates, avoided error costs via complaint and rework rates, lower tied-up capital via reduced inventory levels. Anyone who wants to report ROI seriously makes the underlying assumptions explicit – such as "three person-days saved per week" – instead of calculating with round wishful figures.
Why ROI (Return on Investment) matters
ROI (Return on Investment) condenses a complex investment decision into a single, easily communicated figure. That makes it the preferred argument towards management, shareholders or the bank: instead of a long list of pros and cons, it delivers a clear statement about profitability. At the same time it allows competing projects to be prioritised – with a limited budget, the project with the higher ROI tends to be favoured.
The benefit lies, however, not only in the resulting figure but in the process of arriving at it. Anyone who sets up an ROI seriously has to think through costs and expected benefit in a structured way. It is precisely this discipline that prevents bad investments made on gut feeling alone or on an attractive entry price. ROI forces you to name the value contribution of an investment and to make it verifiable after the fact.
Calculating and measuring ROI in an ERP system
For an ERP project, the ROI is composed of the comparison of total cost and quantified benefit over a fixed period, usually three to five years. On the cost side sits essentially the total cost of ownership: licence or subscription, rollout, customising, interfaces, data migration, training as well as ongoing operation and support. On the benefit side sit efficiency gains through automation of manual processes, fewer media breaks, lower error rates in order processing and inventory management, faster throughput times and lower tied-up capital through better planning.
A modern advantage: the ERP system supplies the data for later ROI measurement itself. Via metrics and dashboards, throughput times, error rates, inventory turnover or processing times can be compared before and after the rollout. This turns ROI from a mere upfront forecast into a verifiable figure – you can prove whether the expected savings actually materialised, and adjust the calculation if needed.
Calculate realistically instead of flattering the numbers
The most common weakness of an ERP ROI calculation is an overstated benefit combined with understated costs. Anyone who omits the internal project effort, productivity losses during the transition or later extensions and generously estimates the time saved obtains a figure that does not hold up in practice. A sound calculation is honest in both directions: complete costs, conservatively estimated benefit. Only then does ROI support a decision that lasts for years.
Distinguishing ROI, payback and TCO
ROI, payback period and total cost of ownership illuminate the same investment from three angles and are often confused. TCO looks solely at the cost side – it sums all expenditure over the lifecycle and says nothing about the benefit. ROI relates benefit and cost and expresses profitability as a percentage. The payback period, finally, answers the question of timing: after what span of time have the savings recovered the investment?
In practice the three metrics interlock. TCO provides the cost base against which ROI weighs the benefit; the payback period makes clear how quickly the project pays for itself. A high ROI with a long payback period can be less favourable for a capital-constrained company than a moderate ROI that materialises quickly. A complete economic assessment therefore uses all three figures together rather than relying on a single one.
Limits of ROI and DACH specifics
As practical as ROI is, it has limits. It ignores the time value of money: a euro today is worth more than a euro in five years. For long-term or large investments, dynamic methods such as net present value or the internal rate of return, which discount future returns, are therefore used in addition. Moreover, ROI captures only what can be expressed in money; qualitative effects such as higher data quality, better responsiveness towards customers or compliance certainty slip through the net, even though they may be decisive.
In the DACH region there is the added factor that many ERP investments are also driven by legal requirements – such as GoBD conformity, the mandatory e-invoice or audit-proof archiving. Such projects can hardly be fully justified via a classic ROI, because their "benefit" lies primarily in avoiding sanctions and in legal certainty. Here a cost-benefit analysis complements the ROI: the question is then not "what return does it bring?" but "what does the cheapest way of meeting the obligation cost?". ROI remains the standard instrument for optional efficiency investments, but is sensibly flanked by other criteria for mandatory topics.
Example
Example: ROI of an ERP rollout in retail
A retail company with 25 employees introduces an ERP system. The total cost over five years – subscription, rollout, interfaces to the shop and shipping, migration and support – amounts to 90,000 euros. Before the rollout, manual order entry, retyping of orders and inventory corrections tie up around two full-time positions in routine effort. After go-live, the ERP automates order import, inventory synchronisation and invoicing.
Calculated conservatively, the company saves about 1.2 full-time positions of routine work – at around 45,000 euros full cost per position, that is a good 54,000 euros of benefit per year, and 270,000 euros over five years. Added to this are avoided error costs and a 15 percent lower tied-up capital in the warehouse. The net profit over five years is around 180,000 euros (270,000 minus 90,000). The ROI is thus (180,000 ÷ 90,000) × 100 = 200 percent over five years – the investment therefore pays back twice, and payback is reached after just under two years.
Frequently asked questions
Related services
Questions about ROI (Return on Investment) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.