Every professional services firm I've spent time with has a tool stack story. It starts small, a CRM to track deals, a project management tool because the CRM isn't good at delivery, an invoicing tool because the PM tool isn't good at money. Five years and three leadership changes later, you're holding fourteen subscriptions together with a Zapier account and a shared inbox nobody reads.
The subscriptions themselves aren't the problem. The integration tax is.
The true cost of a disconnected stack isn't the line-item price of each tool. It's the re-entry, the reconciliation, the shadow processes that exist purely to hold the seams together.
That's what I want to unpack in this piece. Not the part of the conversation that gets to quote a per-seat saving — the part that gets to the question the finance director actually cares about:
what is this costing me in margin that I can't see?
The 3 costs your finance system cannot see
When a firm does a tool-stack rationalisation exercise, they almost always end up looking at the same three numbers: licences, admins, and implementation. Those are the numbers the procurement team can pull cleanly. They're also the wrong numbers to lead with.
The costs that really hurt sit elsewhere. They hurt for two reasons: they don't land in one budget, and they show up as "how we do things" rather than as line items. Here are the three I see consistently bleed the most margin:
Re-Keying
Every time a deal closes in the CRM and a project gets set up in the PM tool, somebody types the same information twice. Sometimes it's an account manager doing it as part of their kick-off checklist. Sometimes it's a project coordinator doing it because the account manager forgot. Either way, a £350/day resource just spent 45 minutes re-keying data that already existed in another system.
Multiply that across closed deals per month, across engagement types that each need different configuration in different tools, across the inevitable "we missed a step, let's go back and fix it later" remediation, and you're looking at meaningful six-figure numbers in a mid-sized firm. None of that time is billable. None of it shows up as a line item in your tool-stack TCO spreadsheet.
Reconciliation
This is the one CFOs quietly pay for but rarely see. When your finance system says revenue was £X and your pipeline tool says it should have been £X + £Y, somebody needs to explain the difference. That somebody is normally an experienced finance hire spending a day a week reconciling between systems that think slightly different things are true.
The reconciliation test: Ask your finance lead what percentage of their time goes into reconciling between systems vs. doing actual financial analysis. In fragmented stacks, I've seen this run as high as 40%. In integrated ones, it rarely cracks 10%.
Shadow Processes
This is the subtle one. Every fragmented stack grows workflows that exist purely to hold the seams together. The weekly "sync meeting" between sales and delivery that exists because neither team can trust the other's system. The spreadsheet that somebody maintains to make sure renewals don't get dropped on the floor. The Slack channel that has become the de-facto CRM because it's the only place the customer conversation actually gets logged. None of these are in anyone's process documentation. All of them are real work. Most of them employ at least one person full-time equivalent, when you add them up honestly.
How to see the integration tax in your own numbers
Here's a rough audit I've run with several services firms. It takes about two hours and doesn't require any special tooling.
- Pick five deals that closed and went to delivery in the last quarter. Sample them across engagement types if possible.
- Walk each deal from first enquiry to invoiced outcome. Write down every system it touched and every handoff.
- At each handoff, ask two questions: (a) Was any data typed twice? (b) Did anyone have to email, call, or meet to get the next person unblocked?
- Sum the handoff friction Across the five deals and extrapolate to annual volume.
What "integrated" actually needs to mean
The easy mistake when you see the numbers is to buy another integration tool. Another iPaaS, another middleware, another "write-once-sync-everywhere" promise. These can be fine. They are never free, and they almost always end up being the next thing you need to maintain.
The harder path — and the one I'd argue is genuinely cheaper over three years — is to consolidate onto a platform where the integration doesn't exist because the data is the same data. Same contact record, same deal, same project, same invoice. Not synced — the same.
This is the pitch we make for Avaro-One™, and I'll be honest that I'm biased. But the broader point is true regardless of which platform you land on: the integration tax goes to zero only when you stop having integrations at all. Anything short of that is optimisation of a problem you don't need to have.
What to do this week
If this post made you nod once or twice, three concrete things you can do in the next seven days:
- Run the 5-deal audit described above with your COO or ops lead. Don't try to be precise, try to be honest.
- Count your shadow processes. Weekly sync meetings, maintained spreadsheets, Slack channels that do real work. Name them. Estimate the FTE cost.
- Pull up your TCO calculator numbers and ask whether they include the three costs above. If not, the stack is costing more than you think.
I'll write next about the reverse: when consolidation is the wrong answer. There are cases, usually around specialist tools for regulated work, where a focused point solution beats a platform. The craft is knowing which is which.
Thanks for reading.
Rich Morgan is Founder of Avaro Technologies Ltd and has spent the last fifteen years building and operating professional services firms. If you want to talk, he'd love to hear from you — get in touch.