You Don't Replace Excel by Being Better Than Excel

A bank was running its loan operations in Excel. Deals worth millions of dollars. No audit trail, no validation, no way to tell who changed what or when.

Your first reaction is that this is madness. The better question is why it survived, because it survived against every enterprise system that bank already owned.

Excel Wins on the Thing People Feel

A spreadsheet does exactly what you tell it, immediately, with no ceremony. Add a column. Paste a block. Restructure the whole thing on a phone call. Nothing asks you to file a change request.

Enterprise software loses that fight on purpose — structure is the point — but it usually loses it without offering enough in return. So people export to Excel, do the actual work there, and paste the result back. The system becomes a filing cabinet for decisions made somewhere else.

Win on What Excel Cannot Do at All

You won't out-flexible a spreadsheet. What a spreadsheet genuinely can't do is tell you who changed the rate at 4pm on Thursday, or stop someone typing a number that can't be true, or show the same deal to two people without one of them holding a stale copy.

Those aren't features you sell on a slide. They are the things that turn a spreadsheet into a liability the moment a deal goes wrong — and in lending, deals go wrong.

Keep the Workflow, Change the Substrate

The mistake I've watched teams make is treating migration as an opportunity to fix how people work. It's not. The people doing the work built that process against real constraints, and most of it's load-bearing.

Match the shape of what they do now, then add the things only real software can give them. Ask them to change one thing at a time, and let the audit trail be the argument.

How that mapped onto the actual screens is in the Investor Loan Platform case study.