Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Bank Cut Loan Approval Time 70 Percent With One Email Change
Transcript
- Lucas: So, a regional bank in the Midwest — let's call it Heartland Bank, not its real name — cut its small-business loan approval time from about eleven days down to three. Seventy percent faster, no new software, no extra underwriters. Luna: Okay, that's a big jump. What was the trick? Lucas: The fix was in the email that loan officers sent to credit analysts. They changed one template. That's it. Luna: Just the email? That seems almost too simple. Lucas: Look, I thought the same thing when I first heard about it. But the numbers are pretty dramatic. Before the change, each loan request triggered, on average, four rounds of follow-up emails between the loan officer and the credit analyst. After the change, that dropped to less than one. Luna: So they were just going back and forth forever. What was in that old email that caused all that confusion? Lucas: The old template was basically a one-liner: 'Here's the application, let me know if you have questions.' The analyst would then have to dig through a multi-page PDF, hunt for the financials, the business plan, the collateral details — and they'd inevitably fire back a list of questions. The loan officer would respond, maybe with attachments, and the cycle repeated. Luna: So the new template basically pre-empted the questions. Lucas: Exactly. The new template had a short summary at the top — borrower name, loan amount, purpose, and a one-line credit rationale. Then it listed the key financial metrics: revenue, profit margin, debt to income, collateral value, and where in the attached PDF each number was located. Page references, even. Luna: Page references. That's so simple. Why didn't anyone think of that earlier? Lucas: Because it wasn't anyone's job to think about it. The loan officers were focused on the relationship with the borrower, the analysts were buried in the numbers. The email was just a formality, a handoff. Nobody saw it as a control point. Luna: Right. And I guess if this episode is useful to you in the same way — you know, if you're sitting in your own operation and thinking, 'what's my version of that email?' — the reason these conversations stay ad-free is listener support. If today moved your work forward even a little, buying me a coffee at buy me a coffee dot com slash fexingo is what keeps that going. Lucas: Yeah, it's a small gesture that adds up. And we do appreciate it. Anyway, back to the bank. The key insight was that the analysts weren't asking questions because they were being difficult — they were asking because the information wasn't where they expected it to be. Luna: So the new template basically put the answers right in front of them. But I have to ask — did the analysts actually trust the summary? Or did they still verify everything? Lucas: Good question. The bank ran a pilot with one team, and they tracked not just approval time, but also the number of exceptions the analysts caught. That number didn't change. So the analysts were still doing their due diligence, but they were spending less time searching and more time actually analyzing. Luna: So it wasn't about cutting corners. It was about cutting the friction. Lucas: Exactly. And here's a detail I love: the new template also included a line for 'open items' — things the loan officer knew were missing, like a pending tax return or a property appraisal. That way, the analyst knew upfront what wasn't there, instead of discovering it halfway through and having to ping back. Luna: That's smart. It sets expectations. But I'm wondering — how did they get the loan officers to actually use the new template? People are creatures of habit. Lucas: That's the part that's almost as interesting as the template itself. They didn't just send out a memo. They created a one-page guide with a side-by-side comparison: the old email, the new email, and why the new one was better. And they ran a workshop where the analysts showed the loan officers exactly how they read an application — like, literally scrolling through a PDF on a projector. Luna: Oh, that's a great move. Making the invisible visible. Lucas: Yeah. The loan officers were surprised to see how much time the analysts spent just hunting for numbers. Once they saw that, they got on board pretty quickly. And within two months, the new template was used in ninety-five percent of new loan requests. Luna: So what was the actual measured impact beyond the approval time? Did they see any downstream effects? Lucas: They did. Because the cycle time dropped, they could process more applications with the same headcount. The bank's small-business loan volume went up about fifteen percent in the next quarter, just from the capacity freed up. And borrower satisfaction scores improved, because the customers heard back faster. Luna: That's a nice ripple effect. But I'm curious — would this work at a big bank, or is it just a regional bank thing? Lucas: I think the principle scales, but the execution would be different. At a big bank, you might have multiple layers — loan officer, assistant, analyst, senior analyst — and the email handoff is more complex. But the underlying lesson holds: if you map the handoff points and ask people what they actually need, you'll find the friction. Luna: So the takeaway isn't 'copy this template.' It's 'find your own version of this template.' Lucas: Exactly. The template itself is pretty bank-specific. But the process — ask the downstream person what they need, package it upfront, and test it with a pilot — that's universal. You could do this in insurance claims, in customer support ticketing, in software bug triage. Anywhere there's a handoff. Luna: I'm thinking about my own inbox right now. I've definitely been on the receiving end of a vague email that led to a chain of questions. Lucas: Right, and you've probably been the sender too. The fix isn't about being more polite or more concise. It's about being more informative — giving the other person what they need before they have to ask. Luna: So what do you think is the most transferable piece here? If someone wants to steal this idea, where should they start? Lucas: Start by picking one recurring handoff that's causing delays. Shadow the person on the receiving end for an hour. Ask them: 'What do you need to do your job faster?' Then build a template that puts those answers right upfront. Test it for two weeks, measure the average number of follow-up emails, and the average turnaround time. That's it. Luna: That's actionable. And I like that it's not a big project — it's a one-day exercise that could save days every week. Lucas: And that's what The Operator's Manual is all about — finding those small levers. This episode, it was an email. Last time, it was a color code on a factory floor. The pattern is the same. Luna: Yeah, it's like that old saying: 'If you want to go fast, go alone; if you want to go far, go together.' But here, going fast actually means making it easier for the next person. Lucas: That's a nice way to put it. And the bank didn't stop at lending. After the success in small business, they rolled the same idea out to their mortgage operations — and cut the initial document review time there by forty percent. Luna: Forty percent, just from a template? That's wild. Lucas: It's the same principle. The mortgage team was dealing with a checklist of documents, and the email that accompanied them was just a bare attachment list. They added a summary of what each document showed, and any known red flags. The underwriters stopped having to open every PDF to see if it was the right version. Luna: So it's not just about saving time in the short term. It's about building a culture where people think about the next step. Lucas: That's the deeper win. The bank's operations now have a kind of reflex: whenever they see a recurring bottleneck, they ask, 'what would make this handoff smoother?' And they've got a library of templates now — for credit memos, for loan closings, for internal approvals. It's become part of how they operate. Luna: And all it took was one email change to get the ball rolling. Lucas: One email, one pilot, one metric. That's the whole story. So next time you're stuck in an email chain that's going nowhere, ask yourself: what would I put in the first message to make the second message unnecessary? Luna: That's a great question to leave people with. I know I'm going to look at my own handoffs differently now. Lucas: Same here. And if you've got your own version of this story — a tiny change that made a big difference — we'd love to hear about it. Maybe it'll be the subject of a future episode. Luna: Yes, send it our way. Until next time, keep finding those levers.