Modernization

The system gap: Why fragmentation blocks advisory at scale

10 June 2026
4 min read
mins read

This article examines what fragmented systems actually cost advisory firms - not just in productivity, but in the relationships that determine whether AUM stays.

Advisors already know what their clients need. Their systems just won't surface it in time.

A client mentions, almost in passing at the end of a routine call, that they are planning to retire in 18 months. The advisor congratulates them and makes a mental note. To act on it properly means checking the financial planning tool for their retirement projections, then the portfolio system for current allocation, then the CRM for any prior conversations about retirement goals, then the compliance queue for suitability implications. By the time the full picture is assembled, two weeks have passed. The client has already started researching retirement income strategies on their own. They've formed the impression that their advisor, for all their expertise, isn't quite on top of things.

The architecture is what makes proactive advisory structurally impossible. The advisor did everything right.

Attention decides how many relationships an advisor can serve well

Every wealth management firm eventually hits the same problem: advisors carrying a full book start missing things. The cause sits in the systems around them, which make it too slow to act on what advisors already know about their clients.

What actually degrades is the quality and depth of the relationships an advisor already has.

Kitces Research finds that advisors spend more than a third of their time on meeting prep, data-gathering, and client servicing follow-up. Advisors become less present, not just less productive. They arrive at client meetings having spent the morning in five different systems, trying to reconstruct a picture that should already exist. They miss the retirement conversation because the signal never reached them. They find out about portfolio drift at the quarterly review, weeks after it would have mattered.

The architecture decides, every time, that advisors find out last.

The knowledge is already there. The systems just won't surface it.

The information to act proactively almost always exists somewhere in the wealth firm's technology stack. The retirement goal is in the financial planning tool. The portfolio risk is in the portfolio management system. The recent life event is in the CRM. The compliance flag is in the back office.

None of it connects. The advisor ends up doing the connecting instead - manually bridging systems that were never designed to talk to each other. Their expertise, their judgment, and their time are consumed by the act of assembly rather than the act of advising.

Fragmentation's real cost is the relationship itself. The advisor who should be calling first, with the right insight, at the right moment, is instead piecing together context that should have been surfaced automatically.

Why AI does not fix a fragmented foundation

Many wealth firms have invested in AI pilots and seen limited returns. The diagnosis is usually framed as an AI problem: the model isn't quite right, the use case is too narrow, the data isn't clean enough. The real diagnosis is structural.

AI agents cannot coordinate across systems that do not share a common data model. An agent that can only see the CRM will surface CRM-level insights. An agent that operates on the portfolio system will surface portfolio-level recommendations. Neither knows what the other knows. Neither can reason about the full client picture, because that picture does not exist in one place.

On a fragmented foundation, AI does not close the gap. It amplifies it, producing more output, faster, from an incomplete view of the client.

The system gap has to close before AI can deliver on its promise. Closing it and building AI capability are one investment, on one timeline.

The operating model question that matters

The competitive question for wealth firms has shifted to something more fundamental than portal design or AI feature counts. It's whether the operating model can surface what advisors already know, and put it in front of them at the moment it matters.

Firms that answer that question well will have advisors who call before clients have to ask, and who show up to the retirement conversation before the client has started researching alternatives. Those same advisors serve every relationship at a higher standard, because the system finally works with them.

The firms that do not answer it will keep funding the same fragmented foundation, and keep wondering why their advisors, for all their expertise, always seem one step behind.

Next: The Advisor Workspace - what it looks like when the system works for the advisor, not against them.

About the author
Backbase
Backbase pioneered the Unified Frontline category for banks.

Backbase built the AI-native Banking OS - the operating system that turns fragmented banking operations into a Unified Frontline. Customers, employees, and AI agents work as one across digital channels, front-office, and operations.

Backbase was founded in 2003 by Jouk Pleiter and is headquartered in Amsterdam, with teams across North America, Europe, the Middle East, Asia-Pacific, Africa and Latin America. 120+ leading banks run on Backbase across Retail, SMB & Commercial, Private Banking, and Wealth Management.

Table of contents
Vietnam's AI moment is here
From digital access to the AI "factory"
The missing nervous system: data that can keep up with AI
CLV as the north star metric
Augmented, not automated: keeping humans in the loop