Modernisation 7 min read

Signs Your System Is Costing More Than It's Saving

How to recognise when a legacy system has become a liability, with a framework for calculating the true cost. Perth, Melbourne, Sydney and Brisbane.

Best for: Business owners, finance leaders Practical guide for business decision-makers

Who this is for

Business owners and finance leaders who suspect a legacy system is costing more than it's worth but need a framework to confirm it.

Question this answers

How do I calculate whether our old system costs more to maintain than it would cost to replace?

What you'll leave with

  • The hidden costs most businesses don't track
  • A framework for calculating true total cost of ownership
  • Clear warning signs that a system has become a net liability
  • How to build the case for replacement

The hidden costs of legacy systems

When asked "how much does this system cost?" most businesses answer with the direct costs: licensing, hosting, support contract. But those are typically only 30-40% of the real figure.

The rest is hidden across the business:

  • Workaround time: Staff exporting to Excel, manually reformatting data, re-keying information between systems
  • Integration friction: Custom middleware, manual data transfers, scripts that nobody fully understands
  • Training overhead: New staff take longer to learn clunky systems; institutional knowledge is needed for basic tasks
  • Opportunity cost: Features you can't build, integrations you can't make, customers you can't serve
  • Risk cost: What would a system failure actually cost? What about a security breach through unpatched vulnerabilities?
  • Morale cost: Hard to quantify, but real, team frustration with tools affects retention and productivity

Calculating the true cost

Use this framework to estimate the total annual cost of your legacy system:

  1. Direct costs: Licensing + hosting + support contracts + maintenance developer time
  2. Indirect labour costs: Hours per week spent on workarounds × hourly cost × 48 weeks
  3. Integration costs: Cost of maintaining custom connections, middleware, manual data transfers
  4. Error costs: Estimate the cost of errors caused by the system per year (rework, customer impact, compliance issues)
  5. Opportunity cost: Estimate revenue or efficiency lost because the system can't support new requirements (this is the hardest to quantify, use conservative estimates)

Total annual legacy cost = Direct + Indirect labour + Integration + Error + Opportunity

Warning signs

Signs your system costs more than it saves

  • Maintenance costs have increased year-on-year for 3+ years
  • Staff regularly export data to Excel to do their actual work
  • You've turned down business because the system couldn't support it
  • New staff complain about the system within their first month
  • The one person who understands it is a single point of failure
  • You're paying for custom middleware just to connect it to other systems
  • Security updates are no longer available from the vendor

The break-even analysis

Once you have the total annual legacy cost, compare it to replacement cost:

  • Replacement cost: Get a ballpark estimate for building or buying a replacement (including data migration, training, and transition costs)
  • Break-even period: Replacement cost ÷ (Annual legacy cost – Annual new system cost) = years to break even

If the break-even period is under 3 years, replacement is almost always the right financial decision. Under 2 years, it's urgent.

What to do about it

  1. Run the numbers: Use the framework above to calculate your true legacy cost. Be honest about the hidden costs.
  2. Get replacement estimates: Talk to development partners about ballpark replacement costs.
  3. Present the case: Frame it as a financial decision, not a technology decision. "This system costs us $105K/year. Replacing it costs $80K. Break-even is 14 months."
  4. Start small: If the full replacement is too large, identify the highest-cost component and modernise that first.

Key takeaways

  • Direct licensing and hosting costs are only 30-40% of the true cost, the rest is hidden in workarounds, lost time, and missed opportunities
  • If staff spend more than 2 hours per week working around the system, those hours are a direct legacy cost
  • Opportunity cost is real: business you can't win because the system can't support it
  • When annual total cost exceeds 25-30% of replacement cost, replacement usually makes financial sense
  • The decision should be quantitative, not emotional, use the framework, run the numbers
Legacy SystemsCost AnalysisModernisation

Meet the person

Written by the person who does the work

This guide comes from real projects. If it raises a question about your own system, you can ask the founder directly.

HELLO PEOPLE designs, builds and looks after AI, software, app and data solutions for Australian businesses, with senior expertise on every project and a scope agreed before work starts. For an older system, that means learning what it really does first, so nothing your business relies on is lost.

Since 2007, HELLO PEOPLE has delivered more than 100 projects from Perth for small and medium businesses across Australia: custom software and apps, system integrations, data migrations, reporting and dashboards, and AI that works inside the systems a business already runs.

I lead every engagement myself. I trained in accounting before moving into IT, hold accounting and IT professional qualifications and an MBA, and bring more than 20 years of experience across sales, service delivery, inventory and compliance. I am also a PhD candidate in AI at Curtin University, researching retrieval-augmented generation (RAG), so the technology is always judged by what it does for the business.

  • An old-fashioned service

    Small and boutique. The person who scopes the work is the person who does it, and the same person is there when the old system is switched off.

  • Quick responses

    No ticket queue and no account manager in between. You hear back within one business day, usually sooner.

  • A long-term partner

    The upgrade is the start, not the end. When you need the next system, integration or report, you call the same person, who already knows your business.

Related guides

Modernisation 10 min read

Rebuild vs Modernise vs Patch

What to do once you know the cost.

Read guide
Software Planning 8 min read

When to Rebuild and When to Keep

Making the final decision.

Read guide

Ask the author

Still have a question?

Ask it here and it comes straight to the founder. No sales call, no obligation, and a real answer even if the answer is that you do not need us.

Kasun Wijayamanna, Founder Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.