Why Lending Leaders Shouldn’t Start With AI Tools

I have had a version of the same conversation with a dozen different lending operations leaders over the past year. It usually starts the same way. Someone on the executive team, often a COO or a Head of Lending, says something like “we need to figure out our AI strategy.” And within a few minutes, the conversation drifts toward a list of AI vendors, feature comparisons, and demos scheduled for next month.

I want to push back on that starting point, because I think it is the single most common mistake lending organizations make when they approach AI. Nobody wakes up in the morning and decides they need AI. That is not how lending executives actually think about their day. What they say, when you ask them directly, is something much more specific. We need to reduce clicks. We need our underwriters to stop manually copying information from one system into another. We need to stop losing files in someone’s email inbox. We need our credit team spending their time reviewing credit, not assembling packages and chasing down documents.

Those are the real problems. AI is one way to solve them. But the order in which you approach that problem determines whether your AI investment actually changes how your organization operates, or whether it becomes a pilot program that quietly disappears from the roadmap a year from now.

The Wrong Question Leads to the Wrong Evaluation

When a lending organization opens its AI evaluation by asking “which AI tools should we buy,” it almost always ends up in the wrong conversation. The team starts comparing platforms on the basis of how sophisticated the underlying technology looks in a demo. They get excited about capabilities that sound impressive in a sales presentation. They ask about model architecture, about accuracy benchmarks, about whether a vendor uses one large language model or another.

None of that is irrelevant, exactly. But it is downstream of the actual question that matters, and starting there almost guarantees that the technology never fully connects to a specific operational pain point. And when AI tooling does not connect to a pain point that your team feels every single day, it gets adopted slowly, used inconsistently across the organization, and eventually deprioritized the moment something more urgent shows up on someone’s desk. I have watched this happen at lenders with real budget and real intent. The tool was not bad. The starting question was.

This is not a small distinction. It is the difference between technology adoption and technology novelty. A novel tool gets a few champions inside an organization who use it enthusiastically for a few months. An adopted tool becomes part of how the whole operation runs, because it eliminates something painful that everyone in that role has to deal with regardless of how they feel about new technology.

Starting From the Workflow Instead of the Technology

The lending organizations that are getting AI adoption right are starting from a completely different place, and it is a place any operations leader already knows how to think about. They are asking where their team spends the most time on work that does not require human judgment. What do people click on repeatedly throughout the day. What information gets manually re-keyed from one system into another. What causes a loan file to sit in a pending status while someone tracks down a missing document or waits on a callback. What slows underwriting down before a credit decision ever gets made.

Those questions do not sound like an AI strategy conversation. They sound like an operations review. And that is exactly the point. Workflow problems have specific, identifiable AI solutions attached to them, but you can only find the right solution if you have correctly identified the problem first. Skipping that step and jumping straight to evaluating AI platforms is a little like hiring a contractor before you have decided what room needs to be renovated. You might end up with a beautiful result, but it is unlikely to be the result you actually needed.

I want to be specific here, because this is where the abstraction usually breaks down in these conversations. Document extraction is a useful example, because it is one of the clearest cases where the framing genuinely changes the outcome. No lending executive has ever called me and said “we need AI document extraction.” But every single lending operations leader I have talked to has felt the specific pain of a processor spending forty-five minutes manually entering data from a bank statement, a tax return, or a financial statement into their loan origination system. That is a real, measurable, felt problem. When you frame the AI solution as eliminating that forty-five minutes per document, the conversation changes immediately. It stops being about AI as a category and starts being about giving a processor back three or four hours a day that they were spending on data entry instead of on the parts of their job that actually require judgment.

That reframing matters because it changes who signs off on the project, how success gets measured, and how quickly the organization actually uses the tool once it is live. A project framed around “reducing manual document entry time by X hours per week” gets measured against a number operations leadership already tracks. A project framed around “implementing AI” gets measured against enthusiasm, which fades.

The Same Logic Applies Beyond Document Extraction

Document extraction is the easiest example because it is so visible and so universally painful, but the same logic applies to a wider set of workflow problems that show up across origination and servicing. Missing document detection is another good case. Loan processors spend a meaningful amount of time simply checking whether a file is complete, chasing down a signature page or a missing insurance certificate, and following up with borrowers or brokers to close the gap. That is rule-based, repetitive work. It does not require years of underwriting experience. It requires consistency and speed, which is exactly what AI-driven workflow tools are good at providing.

Underwriting preparation follows the same pattern. Long before a credit decision gets made, someone has to assemble the file, verify that the numbers tie together, flag inconsistencies, and get the package into a reviewable state. That preparation work is where a lot of underwriting time actually goes, and it is largely mechanical. Portfolio monitoring is similar at the servicing end. Someone has to track covenant compliance, watch for early warning signs across a portfolio, and flag accounts that need attention before they become a real problem. That is exactly the kind of ongoing, pattern-based monitoring that benefits from automation, because it does not rely on judgment until an exception actually gets flagged for a human to review.

In every one of these cases, the underlying technology is AI. But the value proposition that actually gets budget approved and actually gets adopted by the team doing the work is operational, not technological. Nobody in operations cares what model is running underneath the tool. They care whether their week got easier and whether their team is spending time on the parts of the job that matter.

Leading With Operational Value Changes the Adoption Curve

I have started paying close attention to which lenders successfully scale an AI tool past the pilot stage and which ones stall out after an initial rollout, and the pattern is remarkably consistent. The lenders who lead with operational value rather than technology novelty are the ones who get genuine adoption. The lenders who lead with the technology itself tend to get a proof of concept that never becomes part of daily operations.

Part of the reason is straightforward change management. If you tell your credit team “we are implementing an AI underwriting tool,” you have told them almost nothing about how their day changes, and you have introduced a category of technology that a fair number of experienced underwriters are skeptical of, often for good reason given how much AI hype they have already absorbed from outside the industry. If you tell that same team “we are eliminating the manual data entry step that currently delays every file by half a day,” you have told them exactly what changes, and you have framed it around a problem they already want solved. The second framing gets buy-in. The first framing gets questions and hesitation.

The other reason is measurement. Operational framing gives you a baseline and a target. You know how many hours per week your team currently spends on manual entry, how many files sit in a pending state waiting on documents, how long underwriting preparation currently takes from submission to a reviewable package. You can measure whether the AI tool actually moved those numbers. Technology framing does not give you that baseline, because “how is the AI going” is not a metric. Operations leaders who cannot measure the impact of a new tool struggle to defend continued investment in it when budget conversations come around, and that is often exactly when a promising pilot quietly disappears.

The Practical Question Every Lending Executive Should Be Asking

If you are a COO, a Head of Lending, or a digital transformation leader at a specialty lender thinking about AI right now, the practical question is not “what AI should we implement.” It is a more familiar and more useful question: where does our team spend the most time on repetitive, rule-based work that does not require experienced human judgment. Walk through origination and servicing end to end and answer that question honestly, department by department. Talk to the people doing the work, not just the managers overseeing it, because the person entering data from a bank statement into your loan origination system every day has a much clearer view of where the time goes than a dashboard does.

The answer to that question is your AI roadmap. It will be more specific than anything a vendor’s feature list will hand you, because it is built from your own operation rather than from a generic sales pitch. It will also be easier to get approved and easier to defend later, because it is framed in terms your organization already uses to measure operational performance rather than in terms of a technology category that means something slightly different to everyone in the room.

This is not an argument against AI. It is an argument for sequencing. Identify the workflow problem first, with real specificity about where time and accuracy are being lost. Then let that problem point you toward the right AI capability to solve it, whether that is document extraction, missing document detection, underwriting preparation, or portfolio monitoring. The lending organizations getting this right are not the ones with the most advanced AI. They are the ones who correctly diagnosed the operational problem before they went shopping for a solution.