CampeloLabs
← Blog

AI for Banks: The Risk Lens Founders Miss

Cicero Campelo

Cicero Campelo, CISSP
July 17, 2026 · 8 min read

Part of our guide to AI for startups.

A single founder presenting an AI system to a cautious bank risk committee, trading screens and audit logs on the wall behind them
Table of contents

Lloyd Blankfein spent decades at Goldman Sachs learning to manage risk at scale. He watched the firm through the 1987 crash, the dot-com bust, and the 2008 financial crisis, then the regulatory overhaul that reshaped Wall Street afterward. So when the bank's senior chairman and former CEO says AI worries him, the interesting part is not that he is worried. It is what he is worried about.

It is not superintelligence turning us into pets. In a 2026 interview on Andreessen Horowitz's podcast, Blankfein described a much more mundane problem, and in his telling a more frightening one: an AI agent wired into a financial system could fire off tens of thousands of transactions before anyone noticed something was wrong. That single concern is the key to why banks adopt AI so differently from the way a startup does, and it is the thing a founder has to answer before a bank will buy anything.

Why finance adopts AI differently

A startup adopting AI is usually optimizing for speed. The downside of a bad output is a weak demo or a wrong answer you catch and redo. A bank lives on the other side of that trade. Its downside is a fine, a systemic loss, or a regulator, and it arrives at the scale and speed of software.

Two properties make finance a different game:

  • Leverage. In a bank, a single automated action does not happen once. It repeats across thousands of transactions, accounts, or positions, and it compounds. A bug is not one wrong answer. It is a thousand wrong trades before lunch.
  • Testability. You cannot fully test a system that behaves probabilistically. Blankfein's point is that the leverage of these tools is itself the problem: they can act faster and wider than any human sitting in the loop can check. A model that is right almost every time still fails often enough, and fast enough, to matter when each failure moves money.

So a bank does not lead with the question a startup leads with, which is roughly whether the AI is good enough to be useful. It leads with a different one: what happens when it is wrong, how fast that shows up, and whether anyone can catch it before it compounds. If you are building AI for finance, that reordering is the whole game. Understanding AI as operational infrastructure to be governed, not a gadget to be adopted, is the throughline of running an AI-first company, and in finance the governance question comes first, not last.

The risk that actually worries a bank

The useful thing about Blankfein's framing is what it rules out. The risk he names is not the science-fiction one. It is a fast, confident, wrong machine operating with leverage and without a way to test it fully in advance. His own example is a piece of software that goes out and does tens of thousands of transactions, any one of which could be a costly mistake, at a speed no human review can keep up with.

Put that next to 2008. The crisis Blankfein steered Goldman through was, at its core, a story about hidden leverage: risk that had built up where no one was watching in real time until it broke all at once. He has warned that the system is again inching toward that kind of danger. AI adds a new channel for exactly the same failure: automated decisions, taken at machine speed, that no human is watching as they happen. For a bank, an ungoverned agent is not an efficiency story. It is hidden leverage with a friendly interface.

That is why a bank's caution is not backwardness. It is memory. The institutions that survived the last crises are run by people who assume things will go wrong and plan for it, and a probabilistic system that acts on its own reads to them as a familiar risk in a new coat.

Risk management is contingency planning, not prediction

The deeper lesson from a career like Blankfein's is how finance actually thinks about risk. Most of the job is not predicting the future. It is contingency planning: assuming you will be wrong, and building the machinery that limits the damage and tells you early. As he puts it, once the present becomes the past, everyone looks like a genius. In the moment, you do not get to know, so you plan for the version where you are wrong.

Goldman's own discipline is a good model for founders. The firm marks its positions to market every day, not just as accounting but as an early-warning system: the number moves before the story does, so a problem shows up as a red mark long before it becomes a crisis. The point is not the specific practice. It is the mindset. A bank trusts a system it can watch degrade in real time far more than one that is excellent right up until it is catastrophically wrong with no warning.

For a founder, this is the reframe that wins deals. The bank's real question is never how good your model is on average. It is what your plan is for when the model is wrong, and how fast you will know. Answer that, and you are speaking their language. Lead with an accuracy benchmark, and you are answering a question they did not ask.

What founders selling AI to banks should build

Translate the risk lens into product decisions and a pattern falls out. The AI a bank will actually buy is built to be governed:

  • Observability and audit trails first. Every action the system takes should be logged, explainable, and reversible. In finance, a large share of the organization is compliance and audit for a reason. If your product cannot show its work, it cannot be adopted, no matter how good it is.
  • Human gates on anything with leverage. Separate the ability to read and draft from the ability to act. An agent that summarizes filings or drafts a memo is one risk level. An agent that can move money, trade, or message a customer is another. Gate the irreversible actions behind a human approval or a hard limit.
  • Bounded scope over autonomy. A narrow agent that owns one reviewable workflow is adoptable. A broad, autonomous one that acts across the business is not, because no one can test the full surface of what it might do.
  • Testability as the entry ticket. This is the moat and the price of admission at once. A bank cannot adopt what it cannot evaluate, so the ability to measure and prove behavior is not a nice-to-have. Building real evaluations for your AI is what turns "trust us" into something a risk committee can sign off on.

None of this is theoretical. It is already how AI ships into regulated finance today. In our video knowledge base, Variant builds purpose-built agents for fraud, identity, and compliance review, exactly the narrow, auditable lanes banks open first. And founders who deploy voice agents into large enterprises report that quality assurance, not raw capability, is what makes or breaks the rollout, because a compliance slip that did not matter for a human agent very much matters for a machine repeating it at scale.

Start narrow, auditable, and reversible

The wedge into a bank is not the flashiest agent. It is the one whose failure is cheap and visible. Pick the work that is high-volume, rules-heavy, and reviewable: document and filing review, know-your-customer and anti-money-laundering checks, fraud and identity screening, drafting, and summarizing research. In every one of those, the output is checkable and a human stays on the decisions that cannot be undone.

This is the same shape as selling into any cautious, regulated buyer. The playbook for AI in government is nearly identical: a brutally slow, compliance-heavy sale, won by starting with one narrow workflow and one internal champion, with a sticky, expanding contract as the reward once you are through the door. Finance is government's private-sector twin here. The institutions move slowly and demand proof, and the same discipline that makes them slow to buy makes them slow to leave.

It is worth noticing that the aggressive, AI-native end of finance is playing the same game from the other side. An AI-native hedge fund hands the trader's job to a swarm of agents, but the founders building them keep a human hand on the risk and log everything, for exactly the reason Blankfein names: the action moves money, so it has to be watched. Offense and defense in finance converge on the same rule. Let the machine do the work, but never let it act, at leverage, unwatched.

What to do this week

  1. Write down your worst case. For your AI product, name the worst thing it can do when it is wrong, and how fast someone would notice. If the answer is "a lot, and slowly," that gap is your roadmap.
  2. Separate read from act. Ship the read-and-draft version first. Gate every money-moving or customer-facing action behind a human approval before you let the system act on its own.
  3. Build the audit trail before the feature. Make every action logged, explainable, and reversible from day one, so a risk reviewer can watch the system work instead of taking your word for it.
  4. Lead with one narrow workflow. Choose a single high-volume, reviewable job to sell into, not a broad platform. Cheap, visible failure is what gets you the first yes.

The larger move is to treat AI the way a bank treats risk: as something you govern by design, not something you bolt on and hope holds. Building your company to run on AI that is observable, bounded, and testable from the start is exactly what the AI Operating System for Startups is built to teach.

Sources

Frequently asked questions

How is AI for banks different from AI for startups?

Banks adopt AI under a constraint startups do not feel: leverage. A wrong output from a startup's AI is a bad demo. A wrong output from a bank's AI can repeat across thousands of transactions or accounts before anyone notices, and land as a fine, a loss, or a regulator at the door. So banks judge an AI tool less by how smart it is on average and more by what happens when it fails: how fast the failure shows up, whether every action is logged and explainable, and whether a human can catch and reverse it. Founders who lead with raw accuracy lose. Founders who lead with observability, audit trails, and bounded scope get in the door.

What is Lloyd Blankfein's concern about AI in finance?

Blankfein, Goldman Sachs' senior chairman and former CEO, has said the risk that worries him is not superintelligence but a far more mundane problem: leverage and a lack of testability. An AI agent wired into a financial system can act faster and wider than any human check, firing off tens of thousands of transactions before someone catches a mistake. Having managed Goldman through the 1987 crash, the dot-com bust, and the 2008 financial crisis, his frame is that AI is a new source of the hidden leverage behind past crises, and that the job is contingency planning for when it goes wrong, not trusting that it will not.

What AI use cases are banks actually adopting?

The AI that lands in banks first is narrow, high-volume, and reviewable: document and filing review, know-your-customer and anti-money-laundering checks, fraud and identity screening, customer-service drafting, and summarizing research. These share a shape. The work is rules-heavy, the output is checkable, and a human stays on the irreversible decisions. Purpose-built compliance and fraud agents already run at scale in exactly these lanes. The pattern that does not get adopted is an autonomous agent with authority to move money on its own, because that is where leverage and untestability collide.

How should a founder sell AI to a bank?

Start where failure is cheap and visible, not where the demo is flashiest. Ship the read-and-draft version of your product before the act-on-its-own version, gate every money-moving or customer-facing action behind a human approval, and build the audit trail before the feature so every action is logged, explainable, and reversible. Treat evaluations and testability as the entry ticket, because a bank's real question is what your plan is for when the model is wrong. Expect a slow, compliance-heavy sale, much like selling AI to government, with the same upside: once you are in and trusted, the contract is sticky and it expands.

Build your AI Operating System

A practical course to grow with AI, build internal tools, and operate safely. v1.0 launches August 31, join the waitlist.