Insights

Why banks build digital facades instead of real digital platforms

Most regional banks have invested in digitalization over the past 5-7 years and got a pretty mobile app on top of old architecture, not a real digital platform. This text covers why this happened and what distinguishes banks moving correctly.

Discuss Your Challenge

Authorial position: most Central Asian banks built a digital facade on top of old architecture over the last 5-7 years. This is a visible result the board welcomes, but not real digital transformation. The right path is invisible work on the data layer and integration architecture.

How this shows up in real life

A bank has a modern mobile app with good design, mobile identification, ability to apply for products online. At board presentations and conferences, they speak of digital transformation. But behind the facade — the same manual account opening processes, the same paper approvals on corporate deals, the same customer data fragmentation across core, CRM, and product systems. Any non-standard customer action sends them to a branch or contact center. Any internal task requires email and Excel approvals.

Why the bank ended up here

Bank digital transformation in Central Asia was built as a product improvement program, not as an architectural modernization program. Budget went to the visible part — mobile app, website, individual digital products. The invisible part — data layer, integration architecture, operational processes — remained almost untouched. This produced quick visible results for the board but created systemic debt. After 5-7 years, the facade looks modern, but inside the bank — exactly the same process as 10 years ago.

What teams usually try — and why it does not fix it

Yet another mobile app iteration — new products added, design refreshed, but the foundation is the same
Launch of a separate digital bank — isolated project with own team and infrastructure, but no migration of the main base
Partnership with fintech — bank provides the license, fintech does the front. But this is not bank transformation, it is its license usage
Procurement of a digital platform from a vendor — implemented as a parallel contour, not integrated with the main architecture
Appointment of a CDO without architectural mandate — CDO owns 'the digital program' but real systems remain in the CIO zone

What type of solution is actually needed

Real bank digital transformation is work on the invisible part. The customer data layer that unites core, CRM, and product systems. Integration architecture with event bus and API gateway. Unified AML process with case management. Anti-fraud around the customer, not around the channel. Biometric contour as part of the unified profile. This is not advantageous for presentations — invisible work does not show on slides. But it is exactly what determines whether the bank will be competitive in 5-7 years.

What to check before starting

Which share of digital program budget goes to the visible part (front, mobile app) and which to the invisible (data layer, integrations, processes)
How long does it take to launch a new product direction — if more than 6-9 months, the foundation is not working
How many systems must be updated to add a new field to the customer profile — if more than 3, there is no unified layer
What share of customer mobile app actions leads to manual process in the bank — if more than 20%, facade without foundation
How many times in the last year the integration between core and product system was changed — if regularly, there is no proper integration layer

How to move step by step

Acknowledge that a digital facade does not equal a digital platform — first and most difficult
Diagnose the invisible part — data layer, integration architecture, operational processes
Form a target architectural vision with priority on platform investments, not new products
Reallocate budget — increase platform share, reduce visible product improvements for 12-18 months
Launch the platform investment program — customer data layer, integration architecture, unified AML process
After 18-24 months — verify whether new product launch accelerated, whether operations cost decreased

→

What else is worth exploring

Topics from the same area we usually explore together

Solution

These are not just articles

I do not just write about this. I can come in, examine your situation and design a solution for your specific landscape.

Discuss applying this →

← Back

Ready to discuss your challenge?

Tell me what's not working or what needs to be built. First conversation — no obligations.

Discuss Your Challenge Write on Telegram

Usually respond within a few hours