Blog

Diagnosing Flat Growth: When Your Banking Platform Becomes the Ceiling

A rising line that flattens against a ceiling, illustrating growth blocked by platform capacity
Leonid Goriev, Co-founder of Alty

Leonid Goriev

Co-founder of Alty

July 23, 2026

When growth flattens, the first suspects are always on the demand side. Marketing gets asked for more campaigns. Sales gets a new funnel review. Someone proposes revisiting the pricing. A quarter later the spend has gone up, the curve has stayed flat, and the conversation starts again with a bigger budget. The instinct is understandable. In Celent's 2025 Dimensions survey, 53 percent of banks said winning and retaining customers has become harder than it was a year earlier, and that kind of pressure naturally pushes budgets toward the visible end of the funnel.


I have watched this cycle run inside banks for years, and the pattern behind it is consistent. Flat growth has two possible roots. One is a demand problem: people don't know you, don't trust you, or don't want what you offer. The other is a capability ceiling: people arrive, try to make you their bank, and the platform quietly turns them away. Marketing can fix the first. No amount of marketing can fix the second, because the constraint sits below everything marketing touches.


Most banks never separate the two. That is the diagnostic gap this article is about.

The symptoms of a ceiling

A capability ceiling rarely announces itself. Nothing is formally broken. The app works, releases still happen, the roadmap still exists. The signals are quieter, and they usually show up in four places.


Feature delivery stretches from weeks into quarters. A payments improvement that a neobank ships in a sprint takes your teams two release cycles, and everyone has stopped finding that strange.


Campaigns bring people in and the product lets them leave. Acquisition metrics look healthy while activation and primary-account usage stay flat, which means you are paying to introduce customers to their next disappointment. And that loss is not neutral. A customer who tried you and left is the most expensive customer you will ever face again: in our experience, winning back a churned user costs three to four times the original acquisition, when it is possible at all. Under a ceiling, marketing budgets don't just underperform. They finance churn.


The roadmap fills up with maintenance. Inside a ceiling, the backlog exists to protect the platform, and growth work waits behind it, quarter after quarter.


And teams start avoiding the core. Engineers propose workarounds instead of changes. Product managers scope features around the platform rather than through it. When your best people quietly route around the foundation, they have already diagnosed the ceiling. They just haven't put it in a deck.


None of this makes your bank unusual. In Publicis Sapient's Global Banking Benchmark, a survey of 600 retail banking executives across 13 countries, 70 percent said legacy infrastructure is holding back the digital experiences their customers expect. The ceiling is close to the industry's default condition. What varies is whether a bank has diagnosed its own.


If two or more of these symptoms sound familiar, spending more on demand will produce exactly what it has produced so far.

The growth diagnostic: check the layers bottom-up

The reason the misdiagnosis is so common is the order in which banks investigate. Growth reviews start at the top of the funnel, with awareness and acquisition, because that is where the dashboards are. The diagnostic works better upside down. Three layers, checked from the bottom.


Layer one: capability. Can the platform actually deliver what retention requires? Not in principle, in practice: at what speed can you ship a meaningful product change, and at what risk? If the honest answer is "slowly and nervously", stop here. Nothing above this layer will move until it does.


Layer two: experience. For the customers who already arrive, does the product convert them into primary users? Look at activation, at how many everyday financial actions your app can fully complete, at where people fall back to a branch, a call centre or a competitor. Flat growth with healthy traffic almost always lives here or below.


Layer three: demand. Only now does it make sense to look at awareness, acquisition and pricing. If layers one and two are sound and growth is still flat, you genuinely have a marketing problem, and it is worth solving with marketing money.


The sequence matters because investment flows to the layer you diagnose. A bank that starts at the top will fund campaigns for years while the real constraint compounds at the bottom.

What removing the ceiling looks like

The clearest evidence I can offer comes from one engagement that ran through all three layers, with one of the largest banks in Nigeria, an institution serving more than 30 million customers.


When we started, the ceiling was not primarily technical, which is what makes the case instructive. Innovation was happening, in the sense that attractive ideas kept shipping. But they shipped without validation, often without the expertise the decisions required, and without any fundamental view of how the platform should evolve as a system. The structural and technical limits surfaced gradually, feature by feature, as it became clear that what had been built could not keep working the way it worked. By the time we engaged, teams were afraid to touch core functionality, and growth work had become structurally impossible. We rebuilt the product and technical foundations together with decision ownership, and the app rating moved from 3.4 to 4.7. The full story is in the mobile ecosystem case study.


What happened next is the part that matters for this article, because it shows what a removed ceiling converts into.


With the foundation stable, the bank embedded investments directly into its core banking app, with a unified wealth layer and KYC that could be reused across products. The result was ₦6B in subscriptions within two months of launch. Then pensions, a product that had lived offline with chronically low adoption, was brought into the same mobile ecosystem and became a digital growth driver instead of a dormant line on the balance sheet.


Neither of those growth results came from a campaign. The demand for investments and pensions had existed the whole time. What changed is that the platform became able to receive it.


We saw a different facet of the same logic at Oschadbank. The bank had millions of existing customers, so demand was never in question. But its mobile app had spent a decade as a limited extension of branch systems, and customers kept coming to branches for anything meaningful. Once the app was redesigned as a full primary channel around everyday actions, the rating rose from 3.2 to 4.2 and more than 4 million customers became active mobile users. The detail is in the Oschadbank case study. And the reason our longest client relationship, with PrivatBank, goes back to 2011 and now serves 24M+ users is that the ceiling there is treated as something you raise continuously, rather than discover in a crisis.

If the diagnostic points at the platform

The uncomfortable conclusion, when layer one fails the test, is that flat growth stops being a marketing question and becomes an operating-model question: who owns platform decisions, how release risk is governed, and in what sequence the foundation gets rebuilt without halting the business. Those decisions sit across multiple executive roles rather than with any single owner, and that dispersion is itself part of the problem: a decision that belongs to everyone stalls on everyone's agenda, and inside large institutions that is exactly what happens. Why they stall, and which underestimations set the stall up before kickoff, is a subject of its own; we cover it in why bank digital transformations stall.

What I would ask of any leadership team looking at a flat curve is only the discipline of order. Run the diagnostic bottom-up before approving the next demand budget. If the platform passes, spend on growth with confidence. If it doesn't, you have just saved several quarters of marketing money and found the real project. Structuring that project is the work we do; you can see how in how we work, or simply start a conversation.

Most newsletters aren't worth the inbox space.

This one goes out when we have something worth saying, usually a pattern we've hit building products for regulated banks. Skip it any time.

Frequently asked questions

How do I know if my banking platform is limiting growth?


Look at four signals: meaningful product changes take quarters rather than weeks; acquisition grows while activation and primary usage stay flat; the majority of the roadmap is maintenance; and teams design workarounds to avoid touching the core. Two or more of these together suggest the constraint is the platform, and further demand spending will underperform until it is addressed.

Why is our banking app not growing despite marketing spend?


Because marketing can only fix demand-side problems. If customers arrive but the product cannot complete their everyday financial actions, they revert to branches or competitors, and paid acquisition converts into churn. That churn is the most expensive kind of loss a bank can buy. A customer who tried the product and left disappointed is close to impossible to bring back: in our experience, reacquisition runs at three to four times the original customer acquisition cost, and often fails regardless of spend. Check activation and primary-account usage before increasing budgets. Flat growth with healthy traffic points at the experience and capability layers, and both sit below marketing's reach.

Is it worth rebuilding a banking platform to restart growth?


When the diagnostic shows a genuine capability ceiling, the rebuild tends to pay for itself through the products it unlocks rather than the platform itself. In one engagement, a leading Nigerian bank launched embedded investments within months of stabilising its foundations and took ₦6B in subscriptions in the first two months. The right comparison is never rebuild cost against zero. It is rebuild cost against years of demand spending that cannot convert. One caution: a rebuild only pays if it breaks the cycle that made it necessary. Many banks rebuild, leave the platform largely untouched for seven to ten years, then rebuild again from scratch because everything has aged at once, effectively paying for the same transformation twice. Companies like Revolut avoid this by running a continuous innovation cycle, where the platform evolves every year and never needs rescuing. The rebuild is the entry ticket; the operating rhythm afterwards is what protects the investment.

Leonid Goriev is Co-founder of Alty, a digital product partner working with banks, fintechs, and regulated platforms across the UK and CEMEA.

Most newsletters aren't worth the inbox space.

This one goes out when we have something worth saying, usually a pattern we've hit building products for regulated banks. Skip it any time.