Anna Totterdell
Projects Director
There is a tax your business pays every month that does not appear on any invoice, any P&L line, or any budget report. It is paid in hours - hundreds of them - by people across your organisation who spend their time moving data between systems that should be connected but are not.
You have never been billed for it. You have never approved it. But you pay it every month, without fail, and the amount has been growing for years.
This is the cost of disconnection. And most businesses have never calculated it.
Where the hours go
Pick any process that spans more than one system and follow the data. You will find the tax immediately.
A customer places an order. The details are entered into the CRM. Then someone re-enters the same details into the ERP - because the two systems do not share data. Then someone enters the relevant billing information into the finance platform - because it is not part of any data and systems integration.
That single order has now been entered three times, by up to three different people, into three different systems. Each entry takes time. Each entry introduces the possibility of error. Each error, when caught, requires investigation and correction - which takes more time.
Now multiply that by every order, every day, every month. Then add the same pattern for supplier management, stock updates, employee data, project information, and client communications. The total is staggering.
In most mid-market businesses, the disconnection tax runs between fifty and two hundred hours per month. That is one to five full-time employees' worth of capacity - consumed entirely by work that exists only because the systems do not exchange data automatically.
Why nobody measures it
The disconnection tax is invisible because it is distributed. It is not one person spending two hundred hours. It is dozens of people, each spending a few minutes here and a few minutes there, spread across every department, every day.
The individual moments feel trivial. A two-minute copy-and-paste. A five-minute reconciliation. A ten-minute email chase to confirm a figure. Nobody escalates these because they seem too small to matter.
But aggregated across the business, they add up to a significant portion of your operational capacity - capacity that is consumed by moving data from place to place instead of doing the work that actually creates value.
The finance team does not think of their monthly reconciliation as a disconnection cost. They think of it as part of the job. The operations team does not think of their daily data re-entry as a system failure. They think of it as their workflow. Nobody has named the problem, so nobody has measured it.
The compounding effect
The disconnection tax does not stay constant. It grows.
Every time the business adds a new system without an IT and process strategy view of how it fits - a marketing platform, a project tool, a reporting dashboard - the number of integration gaps increases. Each new platform that does not connect to the existing stack creates new manual handoffs, new data transfers, and new reconciliation requirements.
Every time the business grows - more customers, more orders, more products - the volume flowing through each disconnected process increases. The same manual steps take longer because there is more data to move.
And every time an employee leaves and is replaced, the new person inherits the manual processes and learns to accept them as normal. The institutional memory of "this should be better" fades, and the disconnection tax becomes embedded in the culture.
What the real cost looks like
Let me be specific.
If your business has ten people who each spend an average of one hour per day on tasks that exist purely because systems are not connected - data re-entry, reconciliation, copy-paste, email-based data transfer - that is fifty hours per week. At a blended cost of £30 per hour, that is £1,500 per week. £78,000 per year.
But the labour cost is only the beginning.
Add the cost of errors. Manual data entry has a typical error rate of one to three percent. In a business processing a thousand transactions per month, that is ten to thirty errors - each requiring investigation, correction, and sometimes client communication. The cost per error varies, but in most businesses it is somewhere between £50 and £500 when you account for the time and the downstream impact.
Add the cost of delay. Every manual handoff adds time to a process. A process that could complete in hours takes days because it waits for someone to extract data, someone to approve it, and someone to re-enter it. The delay costs money - in slower cash collection, later delivery, and missed opportunities.
Add the cost of poor decisions. When leadership cannot get timely, consistent data, they make decisions on instinct or stale information. The cost of a wrong pricing decision, a missed risk signal, or a delayed investment cannot always be quantified - but it is real.
The total cost of disconnection in a typical mid-market business is not £78,000 per year. It is multiples of that - when you account for errors, delays, and decision quality.
What connected looks like
The opposite of disconnection is not a single, all-in-one platform. It is an integration layer that connects the platforms you already have.
When a customer places an order in the CRM, the data flows automatically to the ERP and the finance system - with the right fields, in the right format, subject to the right business rules. Nobody re-enters anything. Nobody reconciles anything. Nobody emails anything.
When a supplier delivers goods, the receipt is recorded once and every downstream system updates - stock levels, committed costs, project progress, reporting dashboards. The data moves at the speed of the event, not the speed of a person typing.
When finance closes the month, the numbers agree because they have been flowing from a single source of truth all month. The reconciliation that consumed three days is replaced by a ten-minute exception review - the dividend of proper business automation.
The disconnection tax drops to near zero. The capacity it consumed is returned to the business. And the team spends its time on the work it was hired to do - not on moving data between screens.
The question
How many hours per week does your business spend on tasks that exist only because your systems do not talk to each other?
If you do not know the answer, find out. The number will be higher than you expect. And every hour in that number is a cost you can eliminate - without replacing a single system.
