The Hidden Tax of Fragmented Systems — why IFAs need one platform to scale

Your CRM doesn't talk to your portfolio system. Your proposal tool lives in a separate universe from your client management platform. And the back-office system that holds the fees disagrees with the platform on what last month's valuation actually was.

You're spending eight hours a week copying data between systems. Or your paraplanner is. Sound familiar?

I've sat in 30-something of these conversations in the last year. The pattern is identical every time. Your firm is paying what we call the fragmentation tax: the hidden cost of running multiple disconnected systems that each promise efficiency and collectively deliver the opposite.

The IFA tech stack: five to eight systems doing one job

Most UK IFA firms run between five and eight pieces of software to deliver one service. The full menu usually looks like this:

• A CRM (Intelligent Office, Curo, Salesforce, Microsoft Dynamics, or a sector specialist)
• A back-office or client-management system (often the CRM, but not always)
• A research and portfolio-analytics tool (FE, Morningstar, FinaMetrica or similar)
• A cashflow and financial-planning tool (Voyant, Truth, CashCalc, Prestwood)
• A risk-profiling tool (Dynamic Planner, A2Risk, FinaMetrica)
• A suitability-report and proposal builder (Genovo, Plannr, or in-house templates)
• A platform-aggregator or platform feed (often two or three platforms, each with its own portal)
• A compliance and file-checking system (ATEB, Worksmart, in-house)

Each tool is good at its job. Collectively, they make the job harder.

The original pitch was simple: best of breed. Pick the strongest tool in each category, connect them, and you'll have something more powerful than any single vendor could build. That isn't how it plays out in practice. The data formats don't match. The API breaks on the next vendor release. And the time it takes to keep the chain consistent eats the gain.

Look at the numbers we see in our customer base. The median number of systems an RI touches in a single client onboarding is six. The median number of places a client's address gets typed in is four. The median lag between a platform valuation refresh and that valuation arriving in the proposal builder is two working days.

None of those numbers shocks on its own. Add them up across 200 clients and they become the firm's biggest variable cost.

What the fragmentation tax actually costs

There are two ways to measure it. One is the time. The other is the second-order cost: errors, compliance gaps, slower growth, capacity lost.

The time

Honestly, the time number is the easiest part. In our customer base and in pre-sales conversations over the past 18 months, the consistent observation has been the same. An RI in a fragmented-stack firm loses 8 to 12 hours a week to system work that adds nothing to client value. The rough split, week by week, looks like this:

• Rekeying between systems: three to four hours.
• Switching between portals or hunting for information: two to three hours.
• Reconciling discrepancies between systems: one to two hours.
• Building reports by pulling data from multiple sources: two hours.
• Maintenance and connector breakages: one hour, smoothed across the year.

Different firms report different splits. A firm with a strong CRM-to-back-office integration loses less on rekeying. A firm with multiple platforms loses more on switching. The total tends to land in that 8 to 12 range.

The notional cost depends on how you price RI time. At a £250 hourly cost (a defensible mid-point for UK IFAs), a 10-hour-per-week tax on a six-RI firm runs roughly £780,000 a year in lost capacity. Your firm doesn't see it in the P&L. It's not a cash cost. The firm just sees it in the head count it has to carry to deliver the service.

I asked a paraplanner at one of our customer firms last quarter what really ate her week. Three things, in order. Rekeying. Chasing platforms for valuations. And then building the same client report in three different formats for three different stakeholders inside the firm. The detail varied from the next paraplanner I asked. The shape was identical.

The second-order cost

The time is the visible bit. The harder cost is what fragmentation does to the work itself. There are four places it shows up:

• Errors.Every hand-off between systems is a re-entry. Industry studies of clerical re-entry put error rates around 2 to 4%. Two percent might sound low in the abstract, but in a financial services firm, a 2% error rate on suitability documentation is the kind of thing the FCA puts in a Section 165 letter.
• Compliance exposure. Consumer Duty's distribution-chain rules and the outcomes-monitoring obligation both assume your firm can produce consistent data across the client book inside a reasonable window. A fragmented stack makes that a project rather than a query. (We've written separately on what year-2 outcomes monitoring expects.) The short version: if your firm can't pull a vulnerable-client cohort and the adaptations made for it inside a working week, you have a Section 165 problem waiting to happen.
• Slower growth.Capacity is set by adviser hours minus rekeying. Recover the hours, recover the capacity. Firms running on an integrated end-to-end platform onboard new clients in days, not weeks. That compounds into a higher new-client rate at the same staffing.
• Capacity lost.Everything above, compounding. The firm that should be running 240 clients per RI is running 180. The firm that should be onboarding two new clients a week is onboarding one. The firm that should be at 35% AUM growth is sitting at 18%. None of those gaps are caused by the people. They're caused by the systems.

"But we have integrations" — why best-of-breed plus middleware isn't the fix

Most firms know all this. They've tried to fix it by buying more software. Middleware, integration platforms, Zapier-style connectors, custom API wiring. The pitch is identical to the original "best of breed" pitch, just with a different word in the middle.

Three reasons it doesn't work:

• The connections are fragile.A vendor ships a new version. The connector breaks. The data sync stops. Your firm doesn't notice until a client report shows last month's valuation, the IT support call goes out, and a working day later the connection is back. Multiply by every connector in the chain. None of these breakages is catastrophic on any given day. They're just constant.
• The transfer is shallow.Most APIs move the standard fields fine. What they don't move is the custom fields, the file notes, the risk-profiling rationale, the suitability commentary, the "we discussed this with the client and they prefer X" text. The exact information that makes the client relationship personal is the information that stays behind. Manual intervention fills the gap. The tax doesn't go away.
• The chain has a tax of its own.Middleware costs money. So does the IT support to maintain it. So does the time you spend explaining your connector setup to a new paraplanner. By the time you've added everything up, the integrated chain costs about what a unified platform would cost. Without doing the job.

What "unified" actually means

Unified isn't the same as integrated. An integrated stack is several systems pretending to be one. A unified platform is one system, end to end, with one underlying record for each client.

The features overlap with what an integrated stack tries to do. The mechanism is different. Three differences matter:

• One record per client.The address is stored once. The risk profile is stored once. The fee structure is stored once. When any of them changes, every part of the platform (proposal builder, suitability report, back-office, ongoing review) sees the change immediately. There's no sync delay. Because there's no sync.
• Workflow that crosses functions.Prospect, fact-find, research, proposal, suitability, onboarding, ongoing review. In a unified platform, that's one workflow. In a fragmented stack, it's seven hand-offs. And every hand-off is where rekeying happens.
• One audit trail.The compliance question (show me everything the firm did for this client in the last 18 months, in order) has one answer in a unified platform. In a fragmented one, it has seven partial answers.

The trade-off everyone worries about with unified platforms is the loss of best-in-class depth in any one function. That trade-off used to be real. In 2026 it's mostly not. A modern unified platform built for UK IFAs hits parity on the depth that matters (research, suitability, planning, portfolio analytics) and collapses the chain while it's at it.

The Wealth Analytica wedge against the legacy stack here is FE Analytics. We've written a fuller side-by-side of WA versus FEif you want the head-to-head on portfolio research depth versus end-to-end coverage. The short version: FE remains strong on its specific research depth, and weak everywhere else.

What changes when you collapse the stack

Three numbers we see consistently across firms moving from a fragmented stack to a unified platform:

• 8 to 12 hours a week per RIrecovered from the categories above.
• 60% faster client onboarding(from initial fact-find to first review), driven mostly by the elimination of rekeying and the workflow being one process rather than seven.
• Client capacity per RIrising 25 to 40% over 12 to 18 months, as the hours recovered flow into client meetings rather than admin.

Here's the thing. The pattern compounds. Every hour an RI gets back is an hour available to a client. Every hour spent with a client is a stronger relationship, a higher retention rate, a higher referral rate. The firms running on a unified platform aren't growing faster because the software is magic. They're growing faster because they've stopped paying the tax.

How to start the conversation inside your firm

If you're a CFO or an MD reading this and wondering what your firm's fragmentation tax actually looks like, there are three exercises to run. None of them is expensive.

Start with a week of honest time-tracking. Pick two or three of your RIs and categorise every 15-minute block. Look at what falls into rekeying, switching between systems, reconciling, and building reports manually. That number is your fragmentation tax. Multiply it by 50 weeks and by your hourly RI cost. It'll be bigger than you expect.

Next, count the systems. Not the vendors. The actual screens an RI opens during a typical client onboarding. If the answer is four or more, your firm is paying the tax.

Finally, ask whether the firm could produce, inside a working day, an outcomes-monitoring extract for a single client segment across the last 12 months. If the answer is no, that isn't a compliance problem. It's a systems problem.

The fragmentation tax is the largest single cost in most UK IFA firms. It's also the only one nobody puts on the P&L. The firms that thrive over the next five years will be the ones that decide to stop paying it.