The Cost of Delaying Digitalisation, in Financial Terms

No investment committee would approve a loan at 38% annual interest.

Yet many companies are signing one without realising it. Every time they postpone the decision to modernise their management system, they are taking on exactly that debt. Implicit, undocumented, and with interest charges that appear on no line of the income statement.

It is called technical debt. It works exactly like financial debt: it has principal, annual interest, and a maturity date. The difference is that financial debt appears on the balance sheet. This kind does not.

The Implicit Cost of Inaction

Consider a distribution company. Thirty-five million in revenue. A management system installed twelve years ago. It works, more or less. Estimated cost of modernising it: €220,000.

The first step is to calculate the net annual cost of not doing it. The word ‘net’ matters: the maintenance expense on the current system does not disappear with the transformation — it is replaced by the OPEX of the new system. If the new system costs €30,000 per year in licences and cloud support, the real saving on that line is €18,000, not €48,000 — like trading an expensive car for a cheaper one to run: the saving is the difference, not the full cost of the old one.

€83,640 per year to maintain the problem, already net of the new system’s cost.

Divide that annual cost by what it would take to solve the problem once and for all: 83,640 / 220,000 = 38%. That is the implicit interest rate — the percentage it costs the company each year to continue without acting, expressed against the capital it would need to invest to close the debt.

No committee would approve it if they saw it written down like this.

Compound Interest: Why Waiting Costs More Than Expected

Each year that passes, the data gets dirtier, the integrations more fragile, the manual processes more entrenched. The transformation that costs €220,000 today will cost more in two years, because the project that needs to be done has become more complex. A conservative estimate, consistent with the deviation data documented by Panorama Consulting (ERP Report 2024): costs grow at 6% per year due to cumulative deterioration in data quality, integrations, and the functional gap.

In three years, the total cumulative cost — what you have paid plus what it will cost to fix — exceeds €512,000. More than twice what it would cost to solve the problem today.

The NPV of Waiting: What Inaction Costs in Today’s Euros

That compounding effect becomes even clearer when both decisions are compared in today’s euros.

NPV — Net Present Value — answers exactly that question: if you bring all future cash flows back to today’s euros, how much is the decision worth? To calculate it, you need a discount rate: the percentage by which you adjust future euros, because a euro today is worth more than a euro in three years. That rate is the WACC — the weighted average cost of capital, the minimum return the company must demand from any investment to avoid destroying value. For most mid-sized companies it sits between 8% and 12%, according to sector data published by Damodaran (NYU). We use 8%, the conservative end of the range.

Before looking at the table, one important clarification. The €83,640 above represents the direct costs of maintaining the current system. The €480,000 below is something different: the net operational value the new system generates — process automation, better planning, real-time data, error reduction — beyond simply eliminating current costs. For a €35M distribution company with significant manual processes, €480,000 represents 1.4% of revenue, in line with the ranges documented by Panorama Consulting for implementations of this profile.

The structure of each scenario is as follows. In scenario A the company acts now: it pays for the project in year 0, implements during year 1 with no savings yet, and from year 2 onwards the system generates €480,000 per year. In scenario B it waits two years: nothing happens in years 0 and 1, the project is paid for in year 2 — now more expensive because it has grown at 6% per year — implementation runs through year 3, and savings begin in year 4. In both cases there is exactly one implementation year with no return. The difference is when the clock starts.

In scenario B the year-2 CAPEX is €247,192 because the project has grown at 6% per year for two years. Savings begin in year 4 because implementation is also delayed.

Difference: €785,000 of NPV destroyed by waiting two years. That is not the cost of implementing. It is the cost of not implementing.

The Forced Refinancing

There is one more factor: technical debt has a maturity date, but you do not choose it.

Management systems have lifecycles. When one reaches its limit — technically, regulatorily, operationally — the transformation is no longer optional; it becomes urgent. And urgency is expensive. No time to evaluate, no room to negotiate, with vendors knowing you have no alternative.

It is exactly like renewing a loan when the bank knows you cannot go to another bank.

How to Calculate It for Your Company

The calculation is replicable for any company. Add up the net annual costs of maintaining the problem — real saving in maintenance versus the new system, staff time on manual processes, shadow IT, manual regulatory compliance, late decisions. Divide by the estimated cost of modernisation. Compare that percentage to your WACC.

If it exceeds your WACC, inaction is destroying value. Not as a metaphor. Mathematically.

The question is not whether you can afford to invest. It is at what interest rate you are financing the decision not to.