When the Software Is the Boss's Baby: What's a System Worth If It Isn't Future-Proof?
"Oh, that software can't be replaced. It was built 12 years ago at the boss's request. It's like his baby, he won't let anyone touch it."
That was the answer I got during the assessment for a digitalization project. My first thought: well, we're starting from a long way back. But an old system isn't a problem in itself. If it's continuously developed and maintained, you can build on it.
Three questions that decide everything
So I asked a few small but very telling questions:
Do you have the source code? No. Can it connect to external software? No. Can you extract or export the data? No.
That's it. No more questions.
A system like that isn't a tool, it's a dead end. You can't develop it further because there's nothing to work with. You can't connect it to an ERP, CRM or shop-floor system because it doesn't talk to anything. And you can't migrate the data, which means the company's own knowledge is locked in a box.
It's not about technology, it's about mindset
Over my morning coffee I was reading the September issue of Forbes Hungary, where Tom Kürti wrote a great piece on generational change and mindset. It confirmed what we see in the field: for family businesses, the systems many SMEs still lack (ERP, CRM, innovation methods, the use of AI, and the integrations between them) form the infrastructure of trust that underpins their competitiveness.
The real problem is rarely the old software itself. It's when a leader holds on to it for emotional or ego reasons and won't let it evolve. At that point the system isn't protecting the company; the company is protecting the system, at the cost of its own growth.
What makes software future-proof?
Not being new. Being:
accessible: you have the code, or at least control over how it works, able to integrate with other systems (API, export, data connections), clear on ownership: your data stays yours and you can take it with you, scalable as your company grows.
If any of these is missing, that's not stability, it's risk.
What can you do?
You don't have to replace everything at once. Step one is an honest assessment: what genuinely works, and what has stayed only out of habit. From there, you can build step by step, modularly, a system that doesn't tie your hands but takes the load off your team.
If you have an "untouchable" piece of software too, let's talk. We'll help you decide what should stay and what's already standing in the way of growth: digitalizaltmukodes.hu