Seven suppliers. Twelve platforms. One expensive mess.

Ask most business owners how many suppliers touch their technology and they can usually give you a number. Ask them to draw how those suppliers connect, and the pen tends to stop moving somewhere around minute three.

There is a website agency. A hosting company, sometimes two, because the last migration went badly and nobody trusted the new lot with the old lot's mistakes. A CRM vendor, an ERP that predates most of the current staff, and a marketing agency sending paid traffic into a funnel nobody has audited since it was built. Perhaps a developer who did "a bit of custom work" three years ago and has since gone quiet, taking the only useful knowledge of the system with him.

Each decision probably made sense when it was taken. Put together, they look less like a technology strategy and more like an accumulation of reasonable decisions that were never designed to coexist.

The business pays for every part separately. The cost of the gaps between them appears elsewhere.

It appears when a sales rep re-enters information the CRM already contains. When finance builds another spreadsheet because the reporting platform cannot reconcile with the system that takes the orders. When marketing performance looks healthy until somebody asks which campaigns produced revenue rather than leads.

Most companies in this position do not have one large technology problem. They have several smaller problems that have each been solved in isolation.

The suppliers are rarely the problem

The agency built the site it was briefed to build. The CRM does what the CRM was bought to do. The hosting company keeps the server running. Each supplier can fulfil its contract while the business as a whole remains disjointed, because nobody was ever briefed on the complete operation. Nobody owned it.

A managing director should not be expected to understand why the checkout platform and the stock system disagree about how many units are available. Nor should a sales director have to determine whether the CRM, quoting software and email platform are passing the correct data between them. They're the consequences of a role nobody ever filled.

For a business turning over a few million pounds, a full-time CTO can be difficult to justify. There may not be a technology department to manage, a product engineering team to lead or enough strategic work to occupy a senior executive every day.

There are still important decisions to make. They simply arrive in bursts: a platform renewal, a failed integration, a reporting problem, an acquisition, a security concern or a supplier recommending another rebuild.

Without someone responsible for the whole picture, the gap remains. Another supplier is appointed to solve the latest visible problem, and another system is added to a setup nobody has been asked to examine from end to end.

What changes when somebody owns the whole picture

Before anything else, someone has to understand what already exists.

That means going through the supplier list, contracts, platforms, integrations and internal workarounds. It means finding out where data is entered twice, where reporting becomes unreliable, where two systems overlap and where a supposedly minor manual task is consuming several days of staff time each month.

The answer is not always a rebuild. Sometimes several tools can be consolidated. More often, a modest integration quietly removes hours of repetitive work each month, and only occasionally does a platform actually need replacing because the workaround has outlived its usefulness.

Occasionally the sensible decision is to leave an imperfect system alone. Not every inconvenience justifies the cost and disruption of fixing it, and businesses have already been sold enough transformation programmes built around replacing everything that came before them.

A useful technical review should be closer to an accountant reading a balance sheet than an agency presenting a redesign. The aim is to find where the real cost sits, not merely where the invoices happen to appear.

The AI complication

This problem is becoming easier to create.

AI tools can now produce an internal application, reporting interface or customer workflow in an afternoon. Some of them work surprisingly well. They can remove a bottleneck quickly and cheaply, which makes them attractive to any business tired of waiting for a supplier or an internal development queue.

The difficulty tends to arrive later. The person who prompted the system into existence may not understand its architecture, dependencies or security model, and there may be no documentation beyond the original conversation. When the system fails, changes or becomes important enough to need proper maintenance, nobody can confidently explain how it works.

The tool that generated it does not hold responsibility for the outcome. It will not answer the telephone when a critical process stops running. In practical terms, it becomes another supplier: one with no contract and no institutional memory.

A system nobody understands may still be useful. It should not become business-critical by accident.

The number most businesses have never calculated

Before appointing another supplier or buying another platform, it is worth establishing what the existing arrangement actually costs.

Licence fees are only the obvious part. There is also the time spent copying data between systems, correcting inconsistencies, producing manual reports and checking whether figures can be trusted. There are sales opportunities lost between disconnected platforms, and decisions made using partial information because nothing agrees with anything else.

Then there is the cost of dependency: the employee who alone knows how the spreadsheet works, the former developer whose code nobody wants to touch, the agency that controls a system the business cannot easily move elsewhere.

Most companies have never seen those costs added together. When they are, the number is usually larger than expected, and often more fixable than expected too.

Bringing in a fractional CTO to review the whole technology setup gives the business something its individual suppliers cannot provide: one person responsible for understanding how the parts fit together, where the waste sits and which changes are worth making.

The business may still have seven suppliers and twelve platforms afterwards. The difference is that somebody will know why.