Published on
New Requirements, Old Software: Does It Always Take a New Tool?
“New wine in old bottles” was my first thought when someone recently recommended investing once more in our six-year-old CRM system instead of buying a new one.
The same thought comes up in many conversations with controlling and finance leaders. When requirements shift, or planning and forecasting processes need modernising: does the answer always have to be new software?
I do not think so. There is often considerable potential in making a proven system fit for new tasks. It protects budgets, uses the skills the team already has, and makes change management easier, because only the process is new and not the technology underneath. Costly steps like vendor selection and basic training fall away, and the interfaces to other systems usually exist already.
In almost 20 years around software for controlling and finance I have seen both: the big move to a new solution, and the smart extension of what is already there. Either can be right.
Which is why I find it interesting that we are currently taking the second route more often with long-standing customers. Their established simulation models get adapted to new requirements flexibly and with manageable effort.
The real question is rarely which tool is best. It is where the bottleneck actually sits.