Industry POV · 2026

Financial Institutions Do Not Have an AI Problem.
They Have a Decision-Making Problem.

After 14 years inside cards, payments, credit unions, and fintech platforms, I have watched institutions spend confidently on tools they understand and stall on tools that would make the business smarter. The problem is not that leaders are irrational. It is that AI has exposed a deeper weakness: many institutions do not yet know how to evaluate, defend, and scale decisions when the payoff is not immediately visible.

THE TECHNOLOGY ISN'T THE PROBLEM — What a failed AI launch taught me about financial services. By Danny Del Toro.

The reason everyone cites. And the real one.

Ask anyone in financial services why AI adoption is slow and you will get the same answers: compliance risk, data privacy, legacy infrastructure, regulatory uncertainty. Those are real constraints. They are also not the full story.

The deeper issue is more uncomfortable: many institutions are not evaluating AI on its actual potential. They are evaluating whether the person approving it can defend the decision if the outcome is messy, delayed, or hard to explain.

When a credit union or regional bank approves a media buy, the executive team does not need to understand Meta's ad auction or Google's attribution logic. They understand the dashboard. They understand the vocabulary. They know what number will appear in the board deck, even when that number is incomplete or the quality of the outcome is questionable.

AI does not have that advantage yet. AI asks leaders to approve something they may not fully understand, measure something that does not behave like a traditional funnel, and defend a tool whose value may show up first as better decisions, faster workflows, or fewer hours wasted. Those are real business outcomes. They do not look like a conversion dashboard.

That is why familiar but inferior investments keep winning. They are easier to approve. Easier to explain. Easier to survive politically if they underperform.

"The problem is not that leaders do not trust AI. The problem is that they do not yet trust themselves to explain why they trusted AI."

The lesson institutions learned too well.

I once tried to get approval for Mastercard Business Intelligence, a portfolio analytics tool that would have let me analyze cardholder behavior in ways our internal systems never could. The tool was effectively already funded through existing program economics. The resistance was not about cost. It was about trust and confidence in the decision.

The executive instinct was to build something in-house because it felt safer, more controllable, and easier to explain. That instinct was not irrational. The organization had already been burned by a trusted vendor in a very visible and expensive way. Every subsequent conversation about external tools inherited that damage.

That is the real adoption barrier. Financial institutions are not simply conservative because they lack imagination. Many are conservative because they have paid real money for sophisticated tools that failed in production, then had to explain the failure internally.

Financial institutions are applying the right lesson in the wrong direction. They learned that vendor promises can fail. But instead of becoming better at evaluating new tools, many became better at avoiding them.

A trusted AI tool can do more damage than an unknown one.

I was part of the launch of an AI-powered decisioning platform from one of the most trusted data vendors in financial services. Not a startup. A household name. The kind of partner a credit union board approves without extensive debate because the relationship is already decades old.

The platform promised AI and machine learning to accelerate acquisition decisions: faster approvals, smarter risk scoring, better conversion. On paper, it was exactly what a modern card portfolio needs. In practice, it failed in the three places that matter most.

How institutional trust gets permanently damaged
The tool was too hard to operate. Implementation was technically painful, the initial configuration lacked enough capability to do what was promised, and more money had to be spent before the product could even launch properly.
The decisioning was wrong. Once live, the platform produced poor credit decisions that required human review and correction to every output. The AI that was supposed to speed up the process created more manual work than the process it replaced.
The vendor did not fully understand their own product. The platform had not been pressure-tested in real financial institution environments. The promises made in the sales process did not match the reality of the product in production.

This is not a story about one bad vendor. It is a story about what happens after trust breaks. Every future AI conversation now has to climb over that memory. Every new tool inherits the skepticism created by the last one, even when the product, use case, risk profile, and vendor are completely different.

This is the real adoption barrier: not fear of AI in the abstract, but the accumulated weight of tools that sounded strategic, consumed resources, and failed to deliver confidence.

The uncomfortable truth

"Financial services institutions are not only behind on AI tooling. They are behind on the operating muscle required to evaluate unfamiliar technology before the ROI is obvious."

That is not a technology gap. It is a decision-making gap. Better model demos will not close it. Better adoption design, vendor evaluation, internal champions, and executive translation will.

What AI vendors need to understand about this market.

Most AI vendors are selling the wrong thing to the wrong person using the wrong metric. That is a GTM problem, not a product problem, and it is fixable.

A financial institution buyer is not only asking, "Does this work?" They are asking, "Can I defend this if it works slowly? Can I explain it if the first pilot is messy? Can I get compliance, legal, product, operations, and the board comfortable enough to let this survive long enough to prove itself?"

That is why mediocre but familiar solutions keep beating better but unfamiliar ones. The winning move is not proving the model is powerful. It is selling decision confidence.

What the GTM motion needs to change
01
Lead with specific workflows, not general capability. "Claude can reason across complex documents" means nothing to a BSA analyst. "Here is what your Tuesday morning SAR review looks like before and after" means everything. The use case is the message. The capability is the footnote.
02
Build the compliance materials before the buyer asks for them. The compliance review kit, the vendor risk assessment template, the data handling brief. These need to be ready at the first demo. If a financial institution has to ask for them, you are already behind.
03
Price the pilot to remove the procurement event. A 30-day, department-scoped pilot at low or no cost removes the SOW approval process from the initial conversation. The goal of the pilot is not revenue. It is a before/after ROI story the internal champion can take to their board.
04
Find the champion and equip them, not the executive. The person who will actually decide whether AI survives inside a financial institution is not the CRO or the COO. It is the VP of Product or Director of Operations who is already frustrated and willing to fight for something better.

This is why product marketing matters so much in AI. Not because AI needs better adjectives. Because AI needs someone who can translate capability into institutional confidence, and that translation requires understanding both the technology and the organizational dynamics of the buyer.

The top-down approach is too slow. Here is what works instead.

If I had five minutes with a fintech CEO about AI, I would not tell them they need to understand every tool themselves. They do not. That expectation is part of the problem.

The people who understand the practical value of AI are not usually at the top of the org chart. They are the product owners, analysts, marketers, and directors closest to the work, buried in manual workflows, knowing exactly where time is wasted. They do not need unlimited budgets. They need a narrow mandate, clear guardrails, and permission to run real experiments.

What slows adoption

Waiting for every executive to understand the technology. Defaulting to in-house builds because they feel controllable. Measuring AI on legacy dashboards that were never designed to capture workflow value or decision quality.

What actually works

Trust the domain experts closest to the problem. Give them a specific workflow, a contained pilot, a success metric, and the authority to prove whether the tool deserves more investment.

The cost of building it ourselves is almost always higher than buying the right tool. But that math is impossible to accept when the organization has been trained to associate external innovation with implementation risk.

What commitment looks like when it actually works.

I spend time in Sweden. My partner is Swedish, her kids are 19 and 13, and they both use Swish, Sweden's mobile payments platform, to split lunch, pay for boba with friends, and settle up for everything. Not because it is mandated. Because it is simply better and everyone uses it.

The Swish standard

Sweden did not gradually wander into digital payments. The country made a cultural and institutional commitment to them. The result is a payment behavior that feels completely natural across every age group, a 13-year-old and a grandparent use the same system with equal ease because it is simple enough, trusted enough, and universal enough to become part of daily life.

Cash in Sweden is now seen as unusual. It carries a connotation of opacity rather than convenience. That is a complete inversion of default behavior, and it did not happen by accident. It happened because institutions coordinated, committed, and created the conditions for adoption rather than waiting for it.

AI is going to face the same question inside companies. The technology can exist, the vendors can be credible, and the use cases can be real. But until organizations create the conditions for usage to feel safe, normal, and supported, adoption will stay trapped in pilots and side projects indefinitely.

Fintechs are not immune. They are next.

Everything I have described about traditional financial institutions: the hesitation, the committee calculus, the preference for internal solutions. It is starting to appear inside fintechs too. The companies founded on being faster and more innovative are now becoming mid-size organizations with procurement processes, SVP approval chains, and risk committees.

There is a moment when AI can become part of how the company works. After that moment passes, AI becomes another procurement category. Another committee item. Another tool that needs fourteen approvals before anyone can learn from it.

"The question for fintechs is not whether to use AI. It is whether to embed it in the culture before the culture turns it into a procurement event."

One: trust domain experts earlier. The people closest to the workflow see the AI opportunity before leadership can translate it into a board narrative. Give them tools, boundaries, and ownership before the committee instinct kicks in.

Two: evaluate vendors more rigorously, not more fearfully. A failed AI implementation should teach the institution to demand better pilots, clearer workflow baselines, and production evidence before signing a larger contract, not to avoid AI altogether.

Three: build a measurement framework for AI before buying the tool. If the organization cannot measure workflow efficiency, decision quality, and time saved, it will keep killing useful tools because the value never shows up on a dashboard anyone understands.

Final thought

"The companies that win at AI adoption will not be the ones that moved first. They will be the ones that moved with conviction, trusted their domain experts, evaluated tools rigorously, and built the organizational muscle to measure what actually matters."

I have spent 14 years watching financial institutions spend on what they understand instead of investing in what they need. AI is not a different problem. It is the same problem, with higher stakes and a shorter window to get it right.

DD
Danny Del Toro
Fintech Product Marketing Leader · San Francisco, CA

14 years building go-to-market systems, lifecycle programs, and growth engines for fintech and payments companies across cards, embedded finance, and API-driven payments infrastructure. I have launched card products inside regional financial institutions, built a GTM function from zero at a global B2B payments platform, and watched expensive AI implementations fail from the inside. This piece is not a vendor pitch. It is what I have actually seen, and what I think the industry needs to say out loud.

Create a free website with Framer, the website builder loved by startups, designers and agencies.