The real cost of separate tools is re-entry
Separate applications are attractive because each one is usually better at its own job and cheaper to start. The cost appears later, and it is rarely on an invoice: the same customer exists in the billing tool and the sales sheet, the same employee exists in payroll and attendance, the same item exists in the shop system and the stock file.
Every one of those overlaps is a place where two records drift apart, and someone spends time each month deciding which one is right.
A simple test
Count how many times the same entity has to be created or updated in more than one system today. Customers, employees, students, items, suppliers.
One or two overlaps is manageable with discipline. Beyond that, the reconciliation work usually exceeds whatever you saved by buying separately — and it grows with your size, while the licence saving does not.
When separate tools are the right answer
Connected is not always better. Separate tools make sense when a function is genuinely specialised and barely touches the rest of the business, when a department needs depth no suite offers, or when you need something working in days rather than months.
They also make sense as a starting point. Adopting one strong application and connecting others later is a legitimate strategy, provided you choose the first one knowing what it will need to connect to.
The middle path most organisations actually take
In practice, few organisations replace everything at once, and few stay fully separate. The common pattern is a shared core — one system holding the organisation, its people and its access — with specialist applications connected to it as each is adopted.
That keeps one authoritative version of shared records while still allowing depth where a department genuinely needs it.
