There is a conversation that happens in boardrooms everywhere. The business is growing. Ambitions are high. And then the question: why is everything taking so long?
The development team says it is complex. Management says they need more people. Both are telling the truth. And both are missing the bigger picture.
Because the answer usually sits in a place that rarely makes it onto the agenda: the quality of the software itself, and the architecture behind it.
The invisible bottleneck
In some organisations, developers spend up to 80% of their time on maintenance. Not building new things. Not innovating. Fixing incidents and keeping the existing system from falling apart. For every five developers on the payroll, four are running to stand still.
That number does not appear on any balance sheet. There is no line item for ‘innovation lost to technical debt’. No quarterly report on the maintainability of your core systems. The cost is there, but it is invisible. It shows up as slower time to market. As missed opportunities. As the nagging feeling that something is holding you back.
A CTO we spoke with described it as flying without instruments: ‘I know something is off. I can feel it. But I cannot put a number on it. And without a number, I cannot take it to the board.’
Why this matters more now than ever
Software projects have always been unpredictable. Requirements change. Markets shift. New regulations appear. That is not new.
What is new is the pace. Technology is evolving faster than most organisations can adapt. AI is changing the way code is written. Business models are being disrupted in months, not years. The window for responding to change is getting smaller.
In that world, the organisations that will thrive are the ones that can move fast. And you can only move fast if your software allows it. If the foundation is healthy, you can adapt. If it is not, every change becomes a project in itself, and you fall behind while the world moves on.
One founder put it in words that stuck with us: ‘I know that the moment we hit our sweet spot in the market, we need our software to keep up. If it cannot, we lose the window. That is the one thing I refuse to let happen.’
A question worth asking
Every leadership team reviews financials monthly. Revenue, margins, burn rate. The numbers are scrutinised, debated, and acted upon. That is considered normal.
Now consider: when was the last time someone independently assessed the health of the software that generates those numbers? Not a status update from the team. Not a demo of the latest feature. An actual look at the code. At the structure. At the foundation.
Most organisations have never done this. Not because they do not care, but because it never occurred to them. Software runs, so it must be fine.
We believe that is changing. We see more leaders starting to ask the question: what is actually going on underneath? Not out of suspicion, but out of responsibility. Because they understand that you cannot steer what you cannot see.
And once you see it, everything changes. You know where the risks are. You know what to invest in. You can make decisions based on facts instead of assumptions.
That is not a luxury. In a world that is moving this fast, and that runs on software, it might be the most important thing you do.
