Modernize or Fossilize: Why AI Can’t Save Legacy Wealth Tech

For decades, wealth management firms viewed proprietary, custom-built software as the ultimate competitive edge—a badge of honor proving their technology was as tailored as their client advice. Today, that legacy infrastructure is rapidly becoming an anchor. Nimble, off-the-shelf vendor platforms now deliver superior functionality, faster deployment, and lower total cost of ownership than costly home-grown systems. In a bid to protect these legacy investments, some firms are bolting AI tools onto aging architecture, hoping a modern layer will justify keeping outdated systems alive.

According to Joe Nestlerode, Partner at Alpha FMC and a 28-year wealth technology veteran, this approach is little more than putting “lipstick on a pig.” Drawing on decades of leadership—including overseeing platform strategy at Wells Fargo—Nestlerode discusses why firms must stop defending software the market has already passed by and how they can execute true, core-level tech stack modernization.

CM: Wealth management firms once saw their in-house systems as a real competitive advantage. When did that stop being true, and what changed in the vendor market to make it happen?

JN: For a long time, a proprietary platform really was a competitive advantage. When I moved over to support Wells Fargo’s independent channels around 2008 to 2010, the firm had recently built a fully proprietary advisor platform. At the time, it was well regarded across the industry, and it helped Wells Fargo recruit advisors.

That advantage disappeared quickly. I’d put the turning point at roughly 2013 to 2016. Fintech had already produced strong point solutions like eMoney, MoneyGuidePro and Salesforce. In that window, though, firms like Black Diamond and Orion began delivering all-in-one platforms that brought those capabilities together and removed much of the friction between them. At the same time, cloud, mobile and APIs made it possible, albeit expensive, to curate and build a custom tech stack of vendor point solutions.

After that, it became nearly impossible for an enterprise to compete on capabilities outside of core custodial functions like onboarding and cashiering. Vendors were spending every day on a single problem, such as how to build the best CRM, the best planning workflow or the best performance reporting. Most large firms didn’t have the specialized skill set to keep up, and their legacy platforms stopped being a differentiator.

CM: Why do you think so many firms continue to defend legacy platforms even when off-the-shelf options can do the same work faster and cheaper?

JN: It varies by firm, but four reasons come up again and again.

The first is career risk. Replacing a major part of an enterprise tech stack is a huge undertaking. If it goes sideways or advisors don’t accept the new platform, it can end the career of the leader who made the call.

The second is deep entanglement. Legacy platforms have had capabilities bolted on for years, and they’re woven into everything else the firm does. When I did analysis on retiring systems, swapping out the tool itself was rarely the hard part. The real work was untangling and re-integrating all the connections to other legacy platforms.

The third is skill set. Many large firms built their technology teams in the mainframe era. They didn’t always have the people in place to move to modern, API-driven architecture.

The fourth is resistance from the field. Many advisors, particularly in the affiliated model, have used the same tools for 10 or 15 years. They know exactly how those tools work, and their clients know what to expect. They don’t want their cheese moved.

CM: You’ve compared adding AI to legacy systems to putting lipstick on a pig. What specifically goes wrong when firms try to modernize this way?

JN: Right now, every point solution feels it needs AI in some form or it will become irrelevant. In many cases, adding it doesn’t address the root cause. A tool can have AI built in, but if the data layer underneath is a mess and governance is weak, the AI doesn’t matter.

The second problem is architecture. Many of the fintech tools from that 2012 to 2015 wave are still in use, and they’ve aged. They aren’t AI-native, so vendors add an AI orchestration layer on top. Each new layer is another point of failure and potentially introducing latency to real-time trading, rebalancing and portfolio updates, while sitting on architecture that isn’t modern to begin with

Compare that with the AI-native solutions that have emerged over the last 12 to 18 months. They don’t have monolithic code holding them back, so they can build and change much faster. I think that gives them a real competitive advantage.

CM: Are there any situations where layering AI onto an existing system makes sense, or is it almost always a stopgap?

JN: AI is most valuable when it sits across a unified data footprint that brings all of a firm or advisors’ data together. That’s where you get the deepest insights and can automate workflows end to end. But there are two exceptions where adding AI to an existing system makes sense.

The first is CRM. Even on a legacy platform, AI is already delivering real value there. Meeting prep and note-taking tools like TIFIN.AI, Zocks and Jump are good examples. AI can also mine an advisor’s book, contact frequency or other client dimesions for insights. If a firm can’t get to a unified data layer yet, CRM is where I’d make an exception in the near-term.

The second is with an orchestration layer. Emerging providers like Avantos, Backbase and OneVest aren’t trying to be a CRM or a single capability. They’re an orchestration layer that offers that unified data footprint and delivers a frictionless experience through integration. Because they pull data from all of a firm’s point solutions into one unified data layer, adding AI there makes sense even if the platform wasn’t built AI-native. We see these orchestration tools growing in popularity very quickly in our industry.

CM: How much of the resistance to replacing custom systems is about technology, and how much is about sunk costs, internal politics, or organizational identity?

JN: It varies by firm. In my current role I work with many firms evaluating their legacy systems. Some fully understand that replacing them is what it takes to stay competitive for years to come. Among the firms that are still reluctant, most of the resistance comes down to internal politics and cost.

Much of it is about prioritization. Large firms often have a few massive initiatives underway, such as modernizing the advisor platform or launching a new RIA offering, and those consume most of the technology budget and staff. With that much going on, it’s hard to also take on something like replacing an internal model management solution with a TAMP and moving away from rep-as-PM.

Then there’s the risk to the person making the decision. In a large enterprise, if you botch a platform change and start losing advisors, you’re going to lose your job. That makes people cautious.

CM: From your time leading platforms at Wells Fargo, what lessons did you learn about when to build, when to buy, and when to walk away from a system?

JN: For a long time, “buy” wasn’t even part of the vocabulary at the big wirehouses. Before 2015, and in some cases until 2018, the assumption was that proprietary platforms were a competitive differentiator. Firms held on to that belief well beyond the point where it was true.

The biggest lesson is that most individual capabilities are commodities now. Planning, CRM and reporting tools are used so widely that they no longer differentiate anyone. Wells eventually replaced its in-house planning tool with eMoney, which reflected a broader shift from building to buying. The firm recognized it couldn’t keep up with companies that work on that problem every day.

I think of it as pebbles and sand. The pebbles are the individual capabilities, and those are commodities you should generally buy. The sand is what goes between them: how you integrate systems, reduce friction and surface insights for advisors. That’s where the real competitive differentiation is today, and that’s where it can make sense to invest your own resources.

Firms should walk away from a system when it starts costing them advisors or when the cost to support and maintain it begins to outpace the ability to innovate.

CM: What are the warning signs that a firm’s technology has become a liability rather than an asset?

JN: The most obvious warning sign is when things break. Severity incidents and outages that disrupt advisors’ day-to-day work carry financial and reputational risk, and they can force a firm’s hand.

The second is advisors leaving because of technology. You have to be careful here, because technology is an easy thing to blame when the real reason is compensation or succession. Use exit interviews to find out exactly what in the stack kept them from running their business the way they wanted. When advisors really are leaving over technology, take it seriously. The flight to independence over the last decade has largely been driven by advisors who want to choose their own tools, or who see a better stack at an RIA or IBD and believe they can run their business more efficiently there. That’s what pushed many large firms to start modernizing and using vendors.

The third is when “run the bank” outpaces “change the bank.” If more than half the people supporting a system are just keeping the lights on and working through Tier 1, 2 and 3 tickets, the platform has become too much of a monolith to maintain. When maintenance consistently crowds out innovation, the system has become a liability.

CM: If a wealth manager can fund only one major technology change this year, how should it choose where to start?

JN: It comes down to an ROI business case, measured on three dimensions. Will it generate more revenue? Will it help you retain or recruit advisors? Will it make your advisors more productive? Any major investment should clearly deliver on at least one of those. If you’re losing advisors because your planning tool is outdated, for example, the decision makes itself.

Firms are investing most heavily in three areas right now. The first is data. Building a unified data layer isn’t an advisor-facing capability, but it’s a huge part of most firms’ technology investment, and it makes everything else more valuable.

The second is product. Rep-as-PM is on its way out, and outsourcing investment management is growing fast. Firms want their advisors spending more time as relationship managers and less time trading, building models and picking stocks. That’s why many larger players are bringing in TAMPs, with guardrails, to build out their product shelf.

The third is trading. Many firms have relied on their back-office provider’s capabilities or a proprietary trading tool for years. With alternatives and newer asset classes on the shelf, and clients demanding more personalization, many firms are moving to institutional-grade trading platforms.