New — onFlow: your most critical process, automated with AILearn more
Perspective

The hidden cost of legacy systems

  • November 19, 2026
  • By Germán Middi
The hidden cost of legacy systems

A system that works fine has a cost too, even if nobody measures it

Many of the companies we talk to have a legacy system that works fine. They have used it for years, it doesn't go down and the team knows it by heart. When the question of replacing it comes up, the answer is almost always the same: not now, there are more urgent things.

It's a reasonable answer. Changing systems takes time, money and a few weeks in which everyone works more slowly while they learn. On the other side there is nothing pushing: no outage, no angry customer forcing a decision. The cost of staying the same is real, but it doesn't show up anywhere.

Where the cost shows up

It rarely shows up as a failure. It shows up in tasks that have become normal:

  • Slow lookups: answering something simple means pulling a report, searching by hand or asking someone.
  • Decisions that depend on one person's memory, the one who knows where everything is.
  • Spreadsheets outside the system to cover what the system doesn't.
  • More people for the same tasks when the work grows.

None of these makes noise on its own. Together, they take up a large part of the day.

The Delta case

Delta rents out skip bins and, until 2022, ran its whole operation on a DOS application. Orders were entered without problems and the system did its job. But to know which bins were out on the street, or which ones had to be picked up that week, someone had to go through printouts or ask whoever remembered.

We built them a web system organised around the three movements a skip bin has: delivery, swap and pickup. All of the day's orders are on one screen, with a map showing where every bin is in real time. Each bin's colour tells you whether it needs to be delivered, swapped or picked up. Drivers see their jobs on their phone and mark delivery and payment right there.

Since they started using it, they spend 40% less time on admin tasks. That number didn't appear anywhere before it was measured: the time went into tasks nobody recorded as a cost.

How to tell

A few questions that help you see whether a legacy system is costing more than it seems:

  • How long does someone on the team take to answer a usual customer question?
  • What happens if the person who knows the system best takes two weeks off?
  • Are there spreadsheets or notebooks for things the system should handle?
  • If the work grew by 30% tomorrow, would the same team be enough?

If several answers are uncomfortable, it's worth measuring. You don't have to change everything at once either: it often makes sense to start with the part that takes the most time and leave the rest as it is until it makes sense.

If you have a system like this and want to review it with someone from outside, get in touch.

Germán Middi
Written byGermán MiddiFounder at onMedia — Software engineer, automation & applied AI.

I build digital systems that help businesses run better. From Argentina to Australia, I work with companies turning complex operations into scalable platforms. 🚀 Laravel • Vue • AI workflows • Digital transformation Let’s connect if you’re building something meaningful.

You Might Also Like

Would you like to share your thoughts?

Your email address will not be published. Required fields are marked *