How we went from 11 tools to 1 platform (without losing a feature)

Meridian Advisory Services — a composite case study based on real firms — was a successful 25-person accounting practice with a stable client base, strong margins, and a genuinely chaotic technology stack. Not chaotic in the way that makes for dramatic stories: no data breaches, no major failures. Chaotic in the ordinary, grinding way that most professional services firms accumulate over time — one tool added to solve one problem, another added six months later for a slightly different problem, integrations built between them, some of those integrations breaking, workarounds created for the broken integrations.

Eleven tools. Thirty-one user accounts per staff member on average. Four separate file storage locations that had all accumulated important client documents in different versions. Three different ways to send a client a document to sign. Two internal messaging channels — a Slack workspace and a Google Chat that nobody admitted to using but several people relied on. And a monthly software bill of £3,840 that the managing partner had never looked at as a single number, because it arrived on four different credit cards from nine different vendors.

The trigger for change was not a crisis. It was a compliance audit. A new corporate client — a financial services firm with its own compliance function — asked for a copy of Meridian’s data processing register and a list of sub-processors before signing an engagement letter. It took the practice manager two and a half days to assemble something that approximated an answer. The managing partner decided that was unacceptable and asked for a review.

The audit: what 11 tools actually looked like

The first step was a complete inventory. Not the tools the partners thought the firm used — the tools the firm actually used, verified against payment records, Google Workspace OAuth grants, and a staff survey. The survey produced three additions that nobody in management knew about: a free-tier project coordination tool one team had started using for internal work, a transcription service connected to Zoom that had been recording client calls, and a browser extension that had been granted access to staff Gmail accounts.

The audit produced several immediate findings. Five former employees had active accounts across Slack and Dropbox — two at Slack and three at Dropbox. Both are Tier 1 data processors: Slack contains client correspondence and project discussions, Dropbox contains client financial documents. Former employee access to these systems is a live GDPR exposure. The practice manager revoked all five accounts the day the audit was completed.

Four tools had no signed DPA: Monday, LastPass, Calendly, and Mailchimp. Monday and Mailchimp process client data — Monday contains project notes referencing client matters; Mailchimp holds client email addresses and communication preferences. LastPass holds credential data for all practice systems. Calendly collects client names, email addresses, and appointment preferences. All four are data processors under GDPR and require a DPA. Three of the four have standard DPAs available on their websites — getting them signed took less than a day once someone was assigned to do it. Mailchimp required a formal review by the practice’s legal adviser because their standard DPA contained data transfer clauses that required a Standard Contractual Clause addendum for EU clients.

The cost analysis, when assembled for the first time as a single number, produced the sharpest reaction. £3,840 per month for 11 tools — £46,080 annualised — for a 25-person firm. That is £1,843 per head per year in software costs, before internal IT time, integration maintenance, training, and the time spent managing 11 separate vendor relationships.

The decision: consolidate rather than remediate

The partners’ initial instinct was to remediate: get the missing DPAs signed, clean up the access lists, and continue with the existing stack. The practice manager pushed back with a calculation. The ongoing cost of maintaining 11 separate tools — 11 access reviews per quarter, 11 DPAs to keep current, 11 breach notification chains to manage, 11 integration points to maintain — would continue consuming time that the firm was not accounting for. The integrations between tools were the worst offenders: the Zapier automations connecting HubSpot to Monday to Slack had broken three times in the past year, requiring manual data reconciliation each time.

The consolidation case was made on three dimensions: compliance simplification (one DPA, one audit trail, one access review), cost reduction (fewer licences, fewer integrations, fewer vendor relationships), and operational reliability (native integrations instead of fragile third-party automations). The partners approved a migration with an 8-week timeline and a constraint: no disruption to active client work.

The migration: 8 weeks, no client disruption

Results: what changed after consolidation

The cost reduction was the most immediately visible result. Monthly software spend fell from £3,840 to £1,490 — a saving of £2,350 per month, or £28,200 annualised. The saving came from eliminating 8 of the 11 tool subscriptions entirely (Google Workspace and Xero were retained; Zoom was retained initially and later phased out). The new platform’s per-seat cost was higher than any individual tool, but substantially lower than the aggregate of the tools it replaced.

The compliance improvement was harder to quantify but more strategically significant. The practice now operates under a single DPA with a single data processor. The complete audit trail of every client interaction — every document viewed, every message sent, every signature collected — lives in one place and is exportable on demand. The next time a prospective client asks for the data processing register, the practice manager can produce it in under an hour.

New staff onboarding dropped from an average of three days to half a day. Under the 11-tool stack, onboarding required accounts created across 11 systems, training on each, and an explanation of how they connected. Under the consolidated platform, there is one account and one interface. The half-day onboarding is now primarily spent on the firm’s own processes — how to handle client matters, how to manage engagements — rather than which tool to use for which task.

What did not change — and why that matters

The concern most firms express when considering consolidation is feature loss. The migration revealed this concern to be largely unfounded for two reasons. First, the 11-tool stack was not actually using the full feature set of each tool — most tools were being used for one or two core functions. Monday was used for task lists. Calendly was used for one type of appointment booking. Mailchimp was used to send a monthly newsletter. The advanced features of each were largely unused.

Second, where genuine capability differences existed, the migration timeline allowed time to verify before cutover. No capability gap was discovered after migration — all gaps were identified and addressed during the pre-migration testing phase. This is the argument for a phased migration over a hard cutover: the time between “new platform provisioned” and “old tools cancelled” is when you discover whether anything is actually missing. If you cancel first and migrate second, you do not have that time.

One year after the migration, the managing partner’s assessment was direct: “We should have done this three years earlier. The cost saving was meaningful but not the main thing. The main thing is that I no longer have to think about whether we are compliant. I know we are, because there’s one system and one audit trail. Before, I could not have told you with confidence where all our client data was. Now I can answer that question in five minutes.”