Why Lending Organizations Are Splitting Into Two AI Camps

I keep having the same conversation with lending executives, and I think it deserves a direct article because of how stark the divide has become. I am not talking about a divide between organizations that are ahead on technology and organizations that are behind. That gap has always existed and always will. What I am hearing now is something different — a genuine philosophical split about whether AI belongs in a lending organization at all, and that split is showing up in real strategic planning conversations, sometimes between people sitting on the same board.

Two Positions, Same Room

Here is what I keep hearing. One organization says AI is a company mandate. We are going all in. We are looking at every workflow, every process, every role, and asking how AI can make it faster, cheaper, and more consistent. Underwriting, document review, servicing, collections, reporting — nothing is off the table. The other organization says AI has no presence here. Full stop. We looked at it, we explored it, and we decided it is not ready and not appropriate for what we do. We will keep watching, but we are not moving.

Both of these positions are held by sophisticated people who have thought carefully about their organizations. Neither camp is being careless or naive. And in my conversations, I have come to believe both of them are partially right and both are missing something important. That is the more useful way to think about this divide — not as a contest to determine who is correct, but as two incomplete answers to the same question.

What the All-In Camp Gets Right

The organizations going all in are right about one fundamental thing: AI is not optional over a long horizon. The competitive dynamics of lending are shifting quickly enough, and the productivity gains from applying AI to the right workflows are real enough, that an organization ignoring AI entirely is taking on real competitive risk over a five to ten year window. Document-heavy processes, data extraction, portfolio monitoring, and pattern recognition across large volumes of loan data are exactly the kind of work AI is suited for, and lenders who build capability in these areas now will have a structural advantage over lenders who wait.

Where the all-in camp runs into trouble is governance. Moving fast across every workflow at once, without a clear framework for what data is going into these tools, how outputs are validated, and who is accountable for decisions influenced by AI, creates real exposure. In a regulated lending environment, that exposure is not abstract. It shows up as data handling questions from examiners, as compliance gaps in underwriting documentation, and as operational dependence on tools that were adopted faster than they were vetted. I have seen organizations get most of the way through an ambitious AI rollout only to discover that nobody had mapped which processes actually touch protected borrower data or how a decision made with AI assistance would be defended in an audit. That is not a reason to stop. It is a reason to slow down the parts of the rollout that deserve more scrutiny while continuing to move on the parts that do not.

What the Hold-Back Camp Gets Right

The organizations holding back are right about something too, and it is worth taking seriously rather than dismissing as fear of change. Most AI implementations in lending today are overpromised and underdelivered. The underlying tools are real and improving quickly, but the number of use cases that work reliably, consistently, and defensibly in a regulated lending environment is narrower than most vendor pitches suggest. A model that performs well on a demo data set is not the same as a model that performs well on your actual loan portfolio, with your actual document formats, your actual borrower population, and your actual exception cases. Lenders who have looked closely at specific tools and concluded that the reliability is not there yet for their use case are making a defensible judgment, not an outdated one.

The risk on this side of the divide is different but just as real. Waiting for perfect clarity before doing anything creates a window during which competitors are building operational advantages that become harder to close the longer the window stays open. AI adoption in lending is not just about the tool itself. It is about the organizational learning that happens while using it — the data cleanup, the process documentation, the internal expertise in evaluating vendor claims, the muscle memory of running a structured pilot. Organizations that wait for the technology to be perfect before starting also delay the organizational learning that has to happen before any technology can be used well. That learning curve does not compress just because an organization decides to move quickly once it finally commits.

The Question Neither Camp Is Asking

What I keep seeing in the organizations navigating this best is that they are not trying to answer either version of the big question. They are not asking should we adopt AI, and they are not asking should we avoid it. They are asking a narrower, more operational question: which specific workflows in our lending operation would benefit from AI augmentation right now, what is the data governance framework that makes that adoption responsible, and how do we build the organizational capability to evaluate new AI use cases systematically as the technology matures.

That reframing matters more than it sounds like it should, because it turns an all-or-nothing cultural debate into an operational planning question. A cultural debate about whether an organization is an AI company or not tends to produce a stalemate, because it is really a debate about identity and risk tolerance, and those debates rarely resolve cleanly in a single meeting. An operational planning question about which three workflows would benefit from augmentation in the next twelve months produces a list, an owner, a timeline, and a way to measure whether it worked. For a COO or Head of Lending at a community lender or specialty finance company, that second kind of question is exactly the kind they are equipped to answer, because it looks like every other operational decision they have made — evaluate the workflow, understand the constraint, pilot the change, measure the result, scale what works.

Why This Maps Onto Digital Transformation More Broadly

I would go a step further and say this pattern is not unique to AI. It is the same pattern I have seen play out with every wave of digital transformation in lending over the past decade, including the shift away from spreadsheet-driven origination and the move toward platforms like Salesforce-native loan origination and servicing systems. Organizations that treated the decision as should we modernize or not tended to get stuck in the same kind of stalemate. Organizations that asked which specific processes are creating the most manual work, the most reconciliation burden, or the most reporting risk right now, and started there, tended to build momentum and organizational trust in the process. AI adoption is following the same script, just compressed into a faster timeline because the underlying technology is moving faster than core lending infrastructure typically does.

This is also why governance and platform architecture matter more than the AI conversation alone suggests. An organization running loan origination and servicing on a fragmented set of disconnected tools is going to have a much harder time applying AI responsibly than an organization running on a unified platform with clear data lineage. If you do not know where your data lives, how it flows between systems, or who has access to it at each stage of the loan lifecycle, you are not in a position to answer the governance half of the operational question, no matter how promising a specific AI use case looks. That is not an argument for adopting any particular platform. It is an observation that the lenders who are navigating the AI divide most calmly tend to be the ones who already have their operational and data foundation in reasonable shape, because they are not trying to solve a data governance problem and an AI adoption problem at the same time.

The Practical Takeaway

If your organization is heading into a strategic planning conversation about AI, the most productive frame is not how do we feel about AI as a company. That question invites a philosophical debate that tends to split a room rather than move it forward. The more productive frame is three specific questions. Which three workflows would benefit most from AI augmentation in the next twelve months. What does responsible adoption look like for a regulated lender, specifically around data handling, documentation, and audit defensibility. And who owns that decision going forward, so that the organization is not relitigating the same debate every quarter as the technology continues to change.

Those three questions produce an action plan with an owner and a timeline. The all-or-nothing debate produces a stalemate that gets revisited at every board meeting without ever quite resolving. I have watched both versions of this conversation play out across enough lending organizations now to be confident that the operational framing wins, not because it is more sophisticated, but because it is the only version of the conversation that actually produces a decision. The organizations that figure this out are not the ones with the boldest AI mandate or the most cautious AI ban. They are the ones who stopped arguing about identity and started arguing about workflows instead.