Nobody sits down and designs their business's IT systems. They pile up one sensible decision at a time, and it helps to know where that pile is heading.
My own consultancy is a small example. The first tool I needed was a CRM, because I was losing track of conversations. Then a mailing list manager, because the CRM wasn't built for sending newsletters. Then a form module, because enquiries needed somewhere to land. Each one was the obvious answer at the time, and each one added a place where data lives.
Scale that up to a business with staff, sites and compliance obligations and you get a pattern I see over and over. Systems grow in layers, and at every layer there's a tension a business owner should expect before they run into it.
The layers
1. No layers. Everything runs on memory, paper, spreadsheets and the inbox. It's cheap and flexible, and it only works while the people who hold it in their heads are around. The tension: it feels fine until the day someone is sick, or leaves.
2. A simple software layer. A few tools cover a minority of the business, usually accounting first and then a booking system or CRM. The tension: the tools only cover the edges, so the core work still runs on copy-paste and good intentions.
3. A complex software layer. Many tools now cover most of the business. Five, six, ten SaaS subscriptions, each good at its own job. The tension: nothing talks to anything, so staff become the integration layer. The same family, customer or job gets typed into three systems, and the systems slowly drift apart.
3½. The spaghetti. This stage deserves its own name because almost everyone passes through it. System A pushes to System B through a Zapier step, B exports a CSV to C every Friday, and someone built a sync two years ago that nobody quite understands. It feels like integration. In practice it's a web of fragile one-off connections with no single place to see whether any of it is working.
The crossroads
Past the complex software layer, the path splits. It's a choice, not the next rung of a ladder.
Integrate. Keep the tools you have and add an integration layer that ties them together. Records move between systems through one managed hub, not dozens of one-off links. You keep the best tool for each job and you don't have to migrate anything.
Consolidate. Replace the collection with one system that covers most of the business, an ERP. One database, one login, one version of the truth. You pay for that in migration pain, licence costs, and a system that does most things adequately instead of each thing well.
A well-built integration layer can get surprisingly close to what an ERP gives you, without the migration. For a small or mid-sized business that isn't ready to fund an ERP, and may never need one, that's often the sensible path.
A client at the fork right now
One of my larger clients is standing at exactly this point. They're a multi-site childcare business with two centres open and two more due by the end of the year. In a few years they've come a long way, from ad hoc everything to around six SaaS platforms running different parts of the business. Their industry platform wants to be the whole system, and it covers a lot, but it doesn't cover the whole business. No vendor on the market today serves every workflow they run, and custom ERP development isn't on the table at their size.
They didn't come to me asking for "an integration layer." They came because the manual data entry had become unbearable and they knew there had to be something better. That's usually how the crossroads shows up: not as an architecture decision, but as staff re-typing the same record for the third time.
What to get right before you pick a road
Whichever way you go, two things decide whether it works, and neither of them is the software.
Decide which system is the source of truth for each thing. Integration moves data around, but it doesn't settle which copy is correct. If enrolment details live in the industry platform and the CRM, one of them has to be authoritative, and the other has to follow it. Without that, an integration layer just syncs the disagreements faster.
Decide who owns it when a sync fails. Once systems talk to each other automatically, failures become quiet. A record doesn't arrive, nobody notices, and three weeks later the invoice is wrong. Someone needs to own the alerts, the retries and the fix. In a regulated industry, a sync that fails silently isn't just an annoyance. It's a compliance problem.
And at any stage: agents
There's one more layer that doesn't fit the ladder at all, because you can add it at any stage: AI agents that work alongside your people, in and on the business. I'll come back to that in a later note, because it deserves one of its own. The short version is that you can start with agents at any stage. How safely and how far they can go depends on what's underneath them.
If your business is at the crossroads, or somewhere in the spaghetti on the way there, a Systems Health Check maps what you have, where the data actually lives, and which road makes sense before you spend anything on either.