Here's a pattern we see in almost every Australian small business we work with. There's a CRM that sales lives in. An accounting package the bookkeeper guards. A job book or scheduling tool for the field team. A shared inbox that's become the de facto ticketing system. An e-sign tool for quotes and contracts. And underneath all of it, a pile of spreadsheets holding everything the other five can't.
Nobody planned this. Each system was bought — sensibly — to solve one specific problem at the time. Each one probably does its own job reasonably well. The problem isn't any single tool. The problem is the gaps between them, because none of them talk to each other, and your staff have quietly become the integration layer.
This post puts a number on what that actually costs, explains why the cost grows faster than your headcount, and walks through the realistic options for fixing it — honestly, including the option of doing nothing.
How a Business Ends Up With Six Disconnected Systems
Nobody sets out to build a fragmented tech stack. It accumulates in a completely rational sequence:
- Year one: You start with spreadsheets and email. It works, because you know every customer personally.
- Year two: The bookkeeper insists on proper accounting software. Fair enough — you buy Xero or MYOB.
- Year three: You're losing track of leads, so someone signs up for a CRM. It has a free tier. Why not.
- Year four: The ops team can't schedule jobs from a CRM built for sales pipelines, so they buy a job management tool.
- Year five: Support requests are getting lost in personal inboxes, so support@ becomes a shared mailbox. Quotes need signatures, so an e-sign subscription appears.
- Ongoing: Every gap between those systems gets patched with a spreadsheet. There are now eleven spreadsheets, and three of them are called “Master List — FINAL v2”.
Every individual decision was sound. The cumulative result is that the same customer now exists in five places — with a slightly different name, phone number or address in each one — and no single system knows the whole truth.
The Cost Nobody Budgets For: The Reconciliation Tax
When businesses tally up software costs, they add up the subscriptions. That number is almost never the real cost. The real cost is the human labour spent moving information between systems and working out which system is right when they disagree.
The reconciliation tax: every hour your staff spend re-keying a quote into the accounting package, copying job details from the CRM into the scheduler, chasing a signed contract across two inboxes, or arguing about which spreadsheet has the current price list — that's not admin. That's the ongoing interest payment on a systems decision nobody consciously made.
Here's an illustrative worked example for a 12-person services business. Your numbers will differ — the point is that when you actually write them down, they're never small. We've costed staff time at a conservative $45/hour fully loaded:
| Hidden Task | Typical Time | Cost per Year (at $45/hr) |
|---|---|---|
| Re-keying accepted quotes into the accounting package | 3 hrs/week | $7,020 |
| Copying customer & job details between CRM and job book | 4 hrs/week | $9,360 |
| Chasing signed documents and filing them in the right place | 2 hrs/week | $4,680 |
| Reconciling conflicting customer records (“which one is right?”) | 2 hrs/week | $4,680 |
| Maintaining the “glue” spreadsheets that bridge the gaps | 3 hrs/week | $7,020 |
| Building month-end reports by exporting from four systems | 8 hrs/month | $4,320 |
That's roughly $37,000 a year in this example — more than most of these businesses spend on their entire software stack and IT budget combined. And it doesn't include the harder-to-price costs: the invoice that never got raised because the job was finished in one system but never appeared in another, the customer who was quoted two different prices, or the double-booked technician.
There's also a risk dimension. Customer data scattered across six systems and a dozen spreadsheets is customer data with six different access-control models — or none, in the case of the spreadsheets. If you ever have to work out what was exposed after a data breach, “we're honestly not sure where all our customer data lives” is a very bad starting position under the Privacy Act's notifiable data breaches scheme.
Why the Cost Grows Faster Than Your Headcount
This is the part most owners underestimate. The reconciliation tax doesn't grow linearly with staff — it compounds, for three reasons.
1. The connections multiply, not the systems
Six systems have fifteen possible pairings. Add a seventh and you're at twenty-one. Every pairing is a place where the same fact can exist twice and disagree. You don't feel each new system as one more thing — you feel it as six more seams.
2. At five staff, one person holds the map. At twenty, nobody does
In a small team, there's usually one long-tenured person who knows that the CRM address is right but the accounting address is stale, and that the real price list is the spreadsheet, not the one in the quoting tool. That person is your integration layer. When they're on leave, mistakes happen. When they resign, the map leaves with them. Every new hire has to learn six systems plus the unwritten rules about which one to trust for what — which is a big part of why onboarding new employees in fragmented businesses takes weeks instead of days.
3. Disagreements get more expensive to resolve
When two systems disagree about a customer in a five-person business, someone shouts across the office and it's fixed in a minute. In a twenty-five person business with remote staff, the same disagreement becomes an email thread, a Teams call, and a decision nobody is confident making — because nobody owns the “source of truth”. The dispute takes twenty times longer to resolve, and there are more disputes.
If your team spends more time servicing the systems than the systems spend servicing the team, that's one of the clearest signs your business needs an IT strategy review.
Your Realistic Options, Honestly Compared
There are four broad paths, and the right one genuinely depends on your size, complexity and appetite for change. Here's the honest version of each:
| Option | Best For | The Honest Downside |
|---|---|---|
| Do nothing (formalise the manual process) | Under ~5 staff, simple workflows | The tax keeps compounding as you grow; key-person risk stays |
| Glue existing tools together (Zapier, Power Automate, native integrations) | Teams happy with their current tools, with someone technical to own it | Integrations break silently when a vendor changes their API; you now maintain plumbing as well as tools |
| Move to an off-the-shelf all-in-one suite | Businesses whose processes fit a standard mould | You reshape your business around the software; often per-seat pricing across your whole team; unused modules still cost money |
| Have a platform built around your actual workflow | 10–50 staff with processes that are a genuine competitive advantage | You depend on the builder; costs more upfront than a $30/month subscription |
A few honest notes on each. Doing nothing is a legitimate choice at small scale — if the reconciliation tax on your version of the table above is under a few thousand dollars a year, the disruption of changing may not be worth it yet. Write the number down and revisit it every six months.
Gluing tools together works well when the integrations are native and boring — Xero talking to a job management tool it officially supports, for example. It works badly when you're chaining together Zapier workflows nobody documents. We've written before about where automation genuinely saves small businesses time and where it just relocates the fragility.
Off-the-shelf suites are the right answer more often than custom-software people like to admit. If your business runs the way the suite assumes — standard sales pipeline, standard jobs, standard invoicing — the economics are hard to beat. The trouble starts when your workflow doesn't fit and staff route around the system, which quietly recreates the spreadsheet problem inside a more expensive subscription.
A platform built around your workflow is the option that used to be reserved for big companies, and it's the one where we should declare an interest. Alongside our managed IT and web development work, we build an operations platform called iTec HQ for exactly this situation: one system, shaped around how the business already works, replacing the separate CRM, job book, ticketing inbox, e-sign tool and spreadsheets. It has thirteen modules but you only run — and only pay for — the ones you need; it isn't priced per seat; it's hosted in Sydney; most builds are live in two to four weeks; and sign-in runs through your own Microsoft 365 tenant, so your existing MFA and conditional access policies apply. The full argument for it lives on its own page, so we won't repeat it here.
Wondering whether one built-around-you system beats six subscriptions for your business? Have a look at what it replaces and how it's priced — then decide for yourself.
See iTec HQ →Questions to Ask Before You Consolidate Anything
Whichever path you take — including a competitor's product, or none — these questions will keep you out of trouble:
- What is our actual reconciliation number? Build your own version of the table above before you talk to any vendor. It anchors every decision in dollars rather than feelings.
- Which system is the source of truth for each fact? Customer contact details, pricing, job status, signed documents. If two systems will still hold the same fact afterwards, you haven't solved the problem — you've moved it.
- What happens to the accounting package? In almost every consolidation, Xero or MYOB stays — your accountant lives there and it does its job. The question is whether everything else pushes into it cleanly, so nobody re-keys an invoice ever again.
- How does pricing scale as we hire? Per-seat pricing means every new employee makes the software more expensive before they've earned a dollar. Ask what the bill looks like at double your current headcount.
- Where does our data live, and who can get it out? Australian hosting matters to some businesses for latency and to others for principle. Either way, insist on a clear answer about data export before you sign — the exit matters more than the entrance.
- How does sign-in work? A new system with its own passwords is a new attack surface. Anything that authenticates through your existing Microsoft 365 identity — so your MFA and conditional access carry over — is one less thing to secure.
The Bottom Line
Six systems that don't talk to each other isn't a sign you made bad decisions — it's the natural result of making six good ones at six different times. But the reconciliation tax between them is real, it compounds with headcount, and it never appears on any invoice, which is precisely why it never gets fixed.
Start by writing down your number. If it's small, do nothing and check again in six months. If it's a part-time salary — and for most businesses over ten staff, it is — then the question isn't whether to consolidate. It's which of the four paths fits your business, and whether you'd rather bend your workflow to fit software, or have software built to fit your workflow.
If you'd like a second opinion on where your stack stands — with no obligation to change anything — we're happy to talk it through as part of a free IT assessment alongside our managed IT services. Call us on 0493 831 141 or get in touch through the site.