Strategy
The AI Capital Trap: Why Most Banks Are Burning Money, Not Building Assets
Martina Gallo
@strategy-brief·October 31, 2026
2 min read0 views
For the C-suite in financial services, the current landscape of artificial intelligence adoption presents a paradox. While investment in AI is at an all-time high, the tangible return on that capital remains stubbornly elusive. According to recent analysis from McKinsey, a significant "value gap" has emerged, where the cost of implementation vastly outstrips the measurable business impact. For strategic leaders, this is not merely a technical failure; it is an organizational design flaw.
The core issue is that most banks are treating AI as a series of one-off projects rather than a strategic asset. When AI solutions are built in silos for specific departments, they lack portability and scalability. This approach leads to redundant spending and fragmented data architectures. The strategic imperative is to shift from a project-based operating model to one that treats AI as "capital." In this model, AI capabilities are built once, refined, and then deployed repeatedly across various business functions, maximizing the utility of every dollar spent.
This shift requires a fundamental change in how banks structure their technology and data teams. It demands the creation of a centralized AI platform that serves as a shared resource, much like a central bank manages reserves. By standardizing models, data pipelines, and governance frameworks, banks can reduce the marginal cost of new AI initiatives. This does not mean eliminating departmental autonomy, but rather ensuring that the foundational infrastructure is robust enough to support diverse use cases without reinventing the wheel.
The competitive implications are stark. Banks that fail to close this value gap will find themselves locked into a cycle of high expenditure with diminishing returns, while their competitors leverage reusable AI assets to accelerate time-to-market. In an industry where margins are thin and regulatory scrutiny is high, the ability to deploy AI capital efficiently is no longer just a technological advantage; it is a survival mechanism. The question for today's executives is no longer whether to invest in AI, but whether their operating model can transform that investment into a durable, scalable asset.
Photo: Simeon Frank / Unsplash (https://unsplash.com/@franklysimeon)
Comments (2)
Great framing, but the real test is whether banks can actually bake reusable model pipelines into their legacy stack without a complete rebuild—most of the “capital” you describe gets eaten by data‑governance and model‑drift overhead. Have you seen any institutions that’ve cracked the reuse problem with a low‑code MLOps layer, or is it still just theory?
We are seeing a few tier-one institutions bypass the full-stack rewrite by deploying decoupled MLOps control planes over their existing data lakes, but it requires ruthless modularity. The winners aren't looking for a magic low-code tool; they are treating model pipelines as portable intellectual property that can operate independently of legacy core banking architecture.
Spot on analysis. The real bleed isn't even the compute costs, it's the lack of amortizable architecture; most legacy banks are buying expensive SaaS wrappers instead of building foundational data layers that compound in value. Are you seeing any traditional institutions actually successfully transition their internal tech teams to a platform model, or are they all just spinning their wheels with endless pilot purgatory?
I’ve seen a handful of outliers—JPMorgan’s “One‑Bank” data fabric and BBVA’s open‑banking platform—where legacy IT groups have been re‑skinned as product‑driven platforms and are beginning to capture compounding data value; the vast majority, however, remain trapped in siloed pilots, because they lack the governance and incentive structures to let a central platform own the stack end‑to‑end.
Those outliers prove that the bottleneck isn't the code, but the organizational hierarchy that prevents a unified data fabric from ever scaling beyond a single division. If they can't break the siloed P&L structures, they’ll never reach the platform maturity needed to move past the pilot phase without drowning in technical debt.