Are you missing the bigger, bigger picture?.
The end-of-life date for your aging corporate financial management system is still some distance away. No reason to worry about a replacement just yet, then. Or is there?
Keeping legacy software for as long as possible might feel like a relatively safe option - "it's far from optimal but everyone's familiar with it, and we're busy with other projects". This approach brings with it significant costs and risks, however. Some obvious, others less so.
With any big technology investment, the decision on if and when to make your move requires a look beyond direct vendor costs. It should be guided by Total Cost of Ownership (TCO) analysis, but even this can miss critical indirect value factors. As EY’s experts explained in our ‘Cost of doing nothing’ Q&A session, when it comes to assessing the true total cost, it’s essential to look at the complete business perspective.
What costs should you be factoring in, then? How might doing nothing for too long lead to unforeseen risks and a blunter competitive edge? Here are the elements to perform a comprehensive TCO analysis.
Analyzing software end-of-life from a business perspective
At first glance, the latest notification from your current software vendor looks like good news. The system you’ve been using for years is to receive vendor support for longer than previously promised.
However, extend your focus a little, and you may find this announcement gives little cause for excitement. The decision to postpone end-of-life is normally driven by commercial strategy reasons. An overly aggressive approach might push customers into the arms of competitors. And if customers seem content to stick with the status quo, why give up the revenue that stems from those licenses?
If your vendor announces an end-of-life extension, this shouldn’t be seen as a cue to hold back a replacement project. There are two good reasons for this:
For a start, there’s functionality. Look at more recent, cloud-based offerings, and you notice a wide range of tools - AI-driven, super-quick consolidation, real-time reporting and self-service analytics capabilities - that your system simply does not include. In fact, it’s been years since anything resembling a major functionality upgrade was added. In terms of product development, the vendor has moved on. The ‘good stuff’ is reserved for newer products, and the end-of-life extension they are promising amounts to little more than technical life support.
Alongside this, there’s your business. Think about the changes that have happened since you first deployed your system. Headcount growth, market expansion, M&A activity, changes to the supply chain, compliance obligations. Think about how these have impacted Office of Finance operations. Does the solution align with today’s needs?
Considerations:
- Remember; ‘end-of-life’ means end-of-life from a technical support perspective - not a business one.
- Outdated software, or a spreadsheet-based process, is likely to reach the end of its optimal life significantly earlier than the point when technical support is withdrawn.
- Your TCO analysis should reflect this. It requires consideration not just of upfront, direct costs, but also indirect and hidden costs.