Most small businesses in the UK run on more than one piece of software. There is the accounting package. The spreadsheet for jobs or orders. The email system. Perhaps a booking tool or an invoicing app bolted on later. Each one works. None of them speak to each other.
That gap is where things go wrong.
This article sets out exactly what breaks — in plain terms — so you can see whether the friction your business is feeling has a name.
The double-entry problem
When two systems do not share data, someone has to enter the same information twice. An order goes into the order management system; someone then types the same values into the accounts package. A customer record is updated in one place; it stays out of date everywhere else.
Every re-keying step introduces a chance of a mistake. More importantly, it costs time. A few minutes per transaction, multiplied across a week, adds up to hours of staff effort that produces no value — it simply keeps two systems consistent with each other.
Decisions made on yesterday's numbers
When systems are disconnected, a report is only as current as the last manual export. If someone pulled figures from the accounts package on Monday morning, the analysis you are using on Wednesday afternoon reflects the position four working days ago.
For a business where cash flow matters — and for most small businesses it does — that lag can cause a genuine problem. You are making decisions on a picture of your business that no longer exists.
The version problem
A spreadsheet exported from System A and imported into System B becomes a separate copy the moment it leaves. If the original changes, the copy does not. Within a few days there are two versions of the same data: the one people are working from and the one that is actually current. Nobody is certain which is which.
This is not a discipline problem or a process problem. It is a structural problem. It will keep happening until the systems are connected.
The staff time that disappears into the gap
Consider the tasks that exist only because systems do not connect:
- Downloading a report from one system and uploading it to another.
- Chasing a colleague for a figure that should be visible in the software.
- Cross-referencing two spreadsheets to find a discrepancy.
- Reconciling an invoice in accounts against an order in the job system.
Each task is short on its own. Together they can absorb a significant proportion of a member of staff's working week — time that could be spent on the business rather than on the administration of the business.
What integration actually fixes
When systems share data directly — either through a purpose-built connection or through a managed integration — a record entered once appears everywhere it needs to appear. An order raised in the CRM updates the accounts. A contact updated in one place is current in every system.
The result is fewer errors, faster reporting, and less staff time spent on manual reconciliation.
That is not a technical benefit. It is a business benefit.
In short
Disconnected systems do not announce themselves. They show up as time nobody has budgeted for, numbers nobody quite trusts, and mistakes that reach the customer before they reach you. None of those look like a software problem on any given day, which is why businesses live with them for years.
The fix is not always integration. Sometimes it is dropping a system, or agreeing which one is authoritative and making everyone use it. But you cannot make that judgement until you know what the gap is costing, and that is a measurement anyone can take in a week.
How to measure how bad it is in your business
Before deciding whether to fix this, it is worth knowing what it is costing. Three measurements, none of which need a consultant.
Count the re-keys. Over one normal week, note every time somebody types information into one system that already exists in another. Not an estimate — an actual count. Most businesses are surprised by the number, because each individual instance takes a minute and nobody thinks of it as work.
Time the reconciliation. How long does it take, each week or month, to establish what is true — matching the shop's orders against the accounts, checking the stock figure, working out which address is current? Include the checking, not just the correcting. This is usually the largest number of the three and the one nobody has ever measured.
Count the escapes. Over the last quarter, how many times did something reach a customer wrong because two systems disagreed? A duplicate invoice, a delivery to an old address, a chase for a payment already made. Each of those has a cost in refunds, credits or goodwill, and each was avoidable.
Those three numbers together are the honest size of the problem. If they are small, you do not have an integration problem and nobody should sell you one.
Why it gets worse rather than levelling off
The reason to deal with this sooner rather than later is that the cost does not stay flat.
Manual reconciliation scales with volume. Twice the orders is roughly twice the checking, and the errors rise faster than that, because the more transactions there are, the more chances two systems have to drift apart before anyone notices. A process that is irritating at fifty orders a week becomes a part-time job at two hundred.
It also gets more expensive to fix. Every month you run on disconnected systems is another month of history that will eventually need reconciling, deduplicating or migrating. The cheapest time to connect two systems is before either of them has accumulated years of divergence.
How to know whether integration is right for your business
Integration is worth considering when at least one of the following is true:
- Staff regularly enter the same information in more than one place.
- Reports are routinely delayed because data has to be exported or compiled manually.
- You are not confident that the numbers in different systems match each other.
- A mistake caused by a data entry error has cost the business money or a customer.
If none of those apply, your systems may already work well enough for your current scale.
If you recognise any of these problems in your business, speak to us — we work with UK small businesses to connect the software they already use, or to replace it with something that fits together from the start.