Legacy systems don’t usually crash and force your hand. They do something more dangerous: they work just well enough to keep, while quietly costing you deals, staff and customers every single day. Here are the seven signs we look for — if three or more feel familiar, the “if it isn’t broken” logic is already costing you money.
1. New hires need weeks to learn it
If onboarding someone onto your core system takes weeks and a tribal-knowledge mentor, the software has become a liability. Modern tools are learnable in days. Every extra week of ramp-up is salary spent fighting your own tools.
2. “That’ll take our IT team a while”
When simple changes — a new field, a new report, a small rule — turn into multi-week projects, the system has stopped serving the business and started dictating to it. Speed of change is competitiveness.
3. Your team keeps a spreadsheet on the side
The unofficial spreadsheet is the clearest symptom of all. When staff route around the official system to get real work done, the system is no longer the source of truth — it’s an obstacle they tolerate.
Every workaround your team invents is a feature your software should have had. Count the workarounds and you’ve measured the gap.
4. It can’t talk to anything modern
If your system can’t integrate with the tools customers now expect — WhatsApp, modern payments, e-invoicing, a mobile app — you’re not just behind on features. You’re actively turning away customers who assume those things are standard.
5. It’s slow, and everyone’s stopped noticing
Teams normalise slowness. But a screen that takes eight seconds to load, times a hundred staff, times every day, is a staggering hidden tax — and if customers touch that system too, slowness reads as untrustworthiness.
6. One person is the system
If there’s a single developer or vendor who alone understands how it works, you don’t own a system — you own a risk. The day they leave, raise their price, or simply stop answering, the business is exposed.
7. Security and compliance are “probably fine”
Unsupported platforms stop getting security patches. If you can’t confidently say your legacy system meets current data-protection and compliance standards, you’re carrying a risk that a single breach could turn into an existential cost.
We rarely recommend the “big rewrite” — it’s risky and slow. On stalled platforms we modernise incrementally, replacing the worst-performing pieces first while the business keeps running. Customers feel the improvement long before the project is “done.” Modernise in motion, not in a shutdown.
What to do about it
- Quantify the leak. Add up the wasted hours, the lost deals, the ramp-up time. Modernisation competes against that number — and usually wins easily.
- Modernise incrementally. Replace the highest-pain component first. Each step should pay for itself before the next begins.
- Protect the business while you do it. A good partner keeps you running throughout — no “system down for two weeks” gamble.
The takeaway
Legacy systems fail quietly, which is exactly why they’re dangerous — the cost is real but invisible until you add it up. If these signs feel familiar, you don’t need a dramatic rip-and-replace. You need a clear-eyed count of what the old system is really costing you, and a partner who can modernise it piece by piece without stopping the business.
Recognise your systems here? Let’s map a modernisation plan that fixes the worst of it first — without the rewrite trap.