
A North American bank we worked with through 2025 and 2026 had been a customer of Adobe Real-Time Customer Data Platform and Adobe Experience Platform for nearly two years before anyone outside the marketing technology team really used the licenses.
The platforms were fully procured, integrated to a meaningful degree, and largely sitting idle. The marketing team, frustrated, decided to stop waiting for executive air cover and run a small experiment on their own subscription. They picked a single customer journey, a digital banking sign-up flow that had been losing prospects at the same step for years, and used the existing Adobe stack to instrument it properly. Real-time event capture. Behavioral segmentation. A next-best-action engine that adapted in seconds rather than days.
The pilot moved the conversion number on that single flow by a margin that, scaled across the bank's volumes, was a multi-million-dollar outcome. The team presented the results at an internal town hall.
The next twelve weeks did not go the way the marketing technology team expected. They did not get a polite congratulations and an invitation to do more of the same. They got a queue of internal demand they had no infrastructure to handle. Wealth wanted the same instrumentation on advisor handoffs. Cards wanted it on activation. The line of business running small business lending wanted it on origination. The contact centre wanted it on the inbound call routing flow. Every team had been waiting for someone to demonstrate that the platforms the bank had already paid for could actually move a number, and once someone did, the demand was immediate and unmanageable.
That story is the better entry point into the Customer 360 conversation than any architectural diagram is. The bank did not have a platform problem in 2024. It had an activation problem. The architecture had been bought, the integrations had been built, and the work was sitting on a shelf because nobody had connected it to a number a senior leader cared about.
This piece is about why that pattern is so common in BFSI, why it matters more in the agent era than it ever has before, and what happens once you stop treating Customer 360 as a procurement problem and start treating it as the data layer every agentic surface in the institution will run on.

Unlock the Future
Continue reading in the FinScale Magazine
This insight was originally published in the third issue of FinScale Magazine by TrialScale. Download the magazine to keep reading.
