AI in banking

The retail AI ceiling: why your award-winning app can't save your frontline

20 April 2026
3
mins read

Most retail banks keep investing in better models. The real bottleneck is the fragmented foundation underneath them. Learn why the banks winning with AI fixed their architecture first.

In the retail banking boardroom, artificial intelligence is often treated as a standalone capability - as something that can be purchased, tuned, and added onto the bank's existing operations. 

There are consistent calls for better AI models, more data scientists, and cleaner training data. The assumption is that if you just spend a little more on the next generation of large language models, your retail bank will finally unlock the promised ROI of personalization and predictive banking.

That assumption is precisely what creates the problem. According to Gartner, 85% of AI projects fail to deliver on their intended business outcomes - and banking is no exception. Meanwhile, BCG found that only 1 in 4 banks worldwide uses AI to gain any real competitive advantage. 

The answer, however, is rarely the models. These projects stall because the architecture underneath is fundamentally fragmented. 

Each system in your stack holds its own version of the customer, updated on its own schedule, with no shared state across channels.The result is that your recommendation engine only sees mobile behavior; your fraud model cannot correlate data across channels in real time; and your personalization layer hits a ceiling every time it tries to understand the whole customer.

This is the retail AI ceiling. Even though it looks like an AI gap, it is in reality an architecture gap - and no amount of algorithm tuning will fix it.

The level 1 trap: the app illusion

Over the last decade, retail banks have poured billions into digital transformation. By most metrics, the industry has successfully conquered this level, which we will call level 1.

Banks today boast the best-looking mobile apps in the financial sector, with award-winning user interfaces, frictionless digital onboarding, and rising digital customer satisfaction scores. 

But a beautiful digital front door creates a dangerous illusion. It masks the reality that the house behind it is broken.

While the app looks modern, the frontline still runs on a fractured operating model. 

Consider a standard, high-value customer journey: 

The customer starts a mortgage application on their mobile app. When they go to the branch, the customer support agent cannot see the mobile application in progress, forcing the customer to restart the conversation when they walk in. Meanwhile, the call center has no context of the branch visit, escalating the frustration when the customer calls to check their status.

This is the reality of your operating model. Your bank likely operates on five separate channels running on five completely disconnected systems.

The whitespace problem: five systems, five data silos

Count the systems your retail frontline relies on today. There is mobile banking, online banking, branch operations, contact center, and the back-office processing. 

Each one of these systems was built in sequence, usually by different teams, relying on different technology stacks at different times. And each one holds a highly isolated slice of your customer data.

For years, this fragmentation was viewed as an IT headache and a normal cost of doing business. Today, it is a structural barrier to survival, because when it comes to deploying AI, each  system represents an impenetrable data silo.

The highest-value work in retail banking does not happen neatly inside a single system. It happens in the whitespace between them. In fact, nearly 50% of retail frontline work lives in this whitespace. It takes the form of manual re-entry, emails, exception handling, and swivel-chair operations for your customer service representatives.

Why AI dies in the whitespace

Banks keep trying to layer sophisticated AI on top of fragmented architecture and wonder why it doesn't ship at scale. The answer is that AI cannot personalize what it cannot see.

When you introduce AI to this fragmented operating model, the limitations of your architecture become glaringly obvious. AI requires complete, real-time context to be effective. If your bank's data is trapped in channel-specific silos, your AI can only be channel-specific.

Here is what happens when AI hits the ceiling:

1. The blind recommendation engine: Your data science team builds a brilliant next-best-action model, but because it is trained exclusively on mobile data, it doesn't know the customer just visited a branch to complain about an overdraft fee. The AI blindly recommends a new credit card on the app while the customer is furious, making it the worst possible offer at the worst possible moment.

2. The isolated fraud model: A security anomaly occurs, but because the fraud model cannot correlate behavioral data between the online portal, the mobile app, and the call center in real time, the context is lost. The threat goes undetected until the money has already left the institution.

3. The personalization paradox: You invest in a sophisticated personalization layer, but it cannot coordinate a consistent customer journey. It relies on batch-processed data from yesterday to predict what the customer needs today. The customer is forced to act as the integration layer between your departments, repeating their story to every new representative they speak with.

Moving on to level 2: architecture is destiny

"We built a recommendation engine, but it only sees mobile behavior. It will never ship at scale."

This is a version of the conversation happening between chief AI officers and CTOs across the industry right now. The architecture simply will not let the AI see the full customer state graph.

The banks that are successfully pushing AI to production and reaping the massive economic rewards of true personalization are not doing it by buying better models. They are doing it by fixing the root cause.

They are moving past level 1 (digital experience) and competing at level 2 (the unified frontline). They are unifying their architecture so that the mobile app, the branch, and the call center all work from a single, real-time picture of the customer.

Your AI isn't broken - but until you fix the fragmented architecture it sits on, your AI ceiling will remain intact, keeping millions of dollars of innovation stuck in the lab.

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 bank operations into a Unified Frontline. With the Banking OS, employees and AI agents share the same context, the same workflows, and the same customer truth - across every interaction.

120+ leading banks run on Backbase across Retail, SMB & Commercial, Private Banking, and Wealth Management.

Forrester, Gartner, and IDC recognize Backbase as a category leader (see some of their stories here). Founded in 2003 by Jouk Pleiter and headquartered in Amsterdam, with teams across North America, Europe, the Middle East, Asia-Pacific, and Latin America.

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