Anna Totterdell
Projects Director
Count the number of software platforms your business pays for. Not the ones on the official list. The actual number - including the tools that individuals signed up for, the free tiers that became essential, the trial accounts that never got cancelled, and the subscriptions that finance does not know about.
In most mid-market businesses, that number is somewhere between fifteen and forty. CRM. ERP. Finance. HR. Project management. Email marketing. Document storage. Communication. Reporting. Scheduling. Time tracking. Invoicing. And that is before you count the industry-specific platforms.
Each one was bought to solve a problem. Each one did solve that problem - in isolation. And that is precisely where things went wrong.
The tool accumulation problem
Nobody plans to build an operation on disconnected tools. It happens one purchase at a time, over years, with each decision making perfect sense in the moment.
Sales needed a CRM. Marketing needed an email platform. Finance needed accounting software. Operations needed a project tracker. HR needed a people system. Each department evaluated their options, chose a product, implemented it, and moved on.
The problem is that nobody was responsible for how these tools would work together. There was no IT and process strategy that said "when this happens here, this should happen there." Each tool became a silo - a self-contained system that does its own job well and communicates with nothing else.
The result is an operation that looks well-tooled on paper but runs on manual handoffs in practice. Someone exports a CSV from the CRM and imports it into the reporting tool. Someone copies order data from the ERP into a spreadsheet for the finance team. Someone emails a status update because the project tracker and the client system do not share information.
You have invested in technology. You have not invested in a system.
The difference between tools and systems
A tool is a piece of software that performs a function. A system is a connected set of tools, data, and workflows that performs an operation.
The distinction matters because tools alone do not create operational improvement. They create operational islands. Each one works, but the space between them - the handoffs, the data transfers, the process transitions - is where all the time, cost, and error lives.
Think about your client onboarding process. It probably touches at least four platforms: CRM for the deal, a project system for delivery, HR or resource management for staffing, and finance for the initial invoice. How much of the movement between those platforms is automated? How much is someone copying details from one screen into another? How many times does the same client name, address, or contract term get typed in?
That gap between tools is your real operational cost. It is a data and systems integration problem, and no amount of new software will fix it, because the problem is not what the tools do - it is how they connect.
Why buying more tools makes this worse
There is a natural instinct, when a process is painful, to look for a tool that fixes it. This instinct is actively encouraged by a software industry that creates a product for every conceivable problem.
But adding a new tool to an already disconnected stack just adds another silo. It might solve the immediate pain, but it creates a new integration gap, a new data source that does not reconcile with the others, and a new handoff that someone has to manage manually.
The worst version of this is the "platform consolidation" play - where a business decides to replace five tools with one platform that claims to do everything. This sounds rational but rarely works in practice, because all-in-one platforms make compromises. They do ten things adequately instead of one thing well. And the migration cost, retraining burden, and feature gaps usually leave the business worse off than before - just with fewer vendor logos on the invoice.
What a system looks like
A system does not require you to replace your tools. It requires you to connect them.
That means three things:
First, a shared data model. Agree on what constitutes a customer, a product, an order, a transaction - and ensure those definitions are consistent across platforms. When the CRM says "customer," it should mean the same thing as when the ERP says "customer."
Second, automated data flows. When information is created or updated in one system, it should propagate to every other system that needs it - without someone manually transferring it. This is integration at the process level, not the API level. It is not enough to connect two platforms technically. The connection needs to reflect how the operation actually works.
Third, workflow orchestration. The process that spans multiple tools needs to be managed as a single end-to-end workflow, with clear triggers, handoffs, rules, and exceptions. Not "the CRM does its bit and then someone tells the ERP" - a defined, automated, auditable sequence that runs from start to finish.
When those three elements are in place, your tools stop being islands and start being components of a coherent operation. The data is consistent. The handoffs are automated. The process is visible from end to end. And you can finally see how your business actually runs - in real time, without someone spending a day building a report.
Where to start
You do not need to connect everything at once. Start with the process that costs you the most in manual effort, errors, or delays.
Map it end to end. Identify every tool it touches. Find the manual handoffs - the points where someone is copying, emailing, or re-entering data between systems. Those are your integration points.
Then build the connections. Normalise the data. Automate the handoffs through business automation that replaces the fragmented, manual workflow with a single, visible one.
Do that once, prove the value, and the rest of the business will understand what a system looks like - because they will see the difference between the connected process and the disconnected ones.
The tools are fine. Most of them are doing their jobs. The problem is the space between them. Fix that, and everything starts working.
