There are seven distinct ways a passenger dummy’s head can rotate during an offset frontal collision. Natasha T.-M., who works as a car crash test coordinator in a sprawling hangar near the West Midlands, spent four hours last Tuesday explaining the rotational physics of the “neck-twist” to me over a lukewarm coffee.

Natasha has seen more shattered windscreens than a city-center rioter, but she doesn’t talk about the leather stitching or the haptic feedback on the dashboard. She cares about the kinetic energy that the infotainment system ignores.

“The impact isn’t the problem,” she told me while pointing at a crumpled front fender, “it’s the energy that has nowhere to go.”

– Natasha T.-M., Crash Test Coordinator

Structural Welds vs. Heated Seats

We buy cars for the infotainment and the heated seats, but we survive the crash because of the crumple zones and the structural welds that nobody sees until the metal starts folding. Most commercial lenders are currently driving a vehicle that is all infotainment and no chassis.

They have spent millions on a glossy front-end that makes the “yes” feel like a spa day, but the moment the deal is signed, the energy of that transaction hits a wall of 2009 legacy code and a master spreadsheet named “DO_NOT_DELETE_DEBT_RECON_V4.”

A Ritual of Modern Corporate Life

The application portfolio review is a ritual of modern corporate life that reveals the true hierarchy of our priorities. I sat in one recently where the contrast was so sharp it felt like a theatrical production. The Origination platform was a pristine, cloud-native SaaS wonder with a dedicated product owner, a sleek UI, and a roadmap that looked like a space agency’s flight plan.

It had been upgraded twice in eighteen months. Then, the slide deck shifted to Servicing.

The room grew colder. The Servicing “platform” was a Frankenstein’s monster consisting of an aging core from the late Bush administration, six internal builds that were essentially digital scar tissue, a purchased document tool that no longer received security patches, and the aforementioned spreadsheets.

This entire precarious tower was supported by a single analyst whose time was split between three other systems. This isn’t an accident or a simple case of “we’ll get to it later.” It is a structural byproduct of how capital is allocated in financial services.

Acquisition has a revenue case-it is a story of growth, of “more,” of capturing the market. Administration, the mundane work of managing a lease or a loan for the next five years, has a cost case. It is a story of “less”-less overhead, less friction, less headcount.

Because we treat growth as a generative force and administration as a tax, we industrialize the “yes” and MacGyver the “wait.”

Lasers at the Point of Sale, Chains in the Swamp

I spent half of yesterday in a Wikipedia rabbit hole reading about the Great Trigonometrical Survey of India, which was an nineteenth-century effort to map the entire subcontinent with scientific precision. They had the most advanced theodolites in the world at the top of the chain, but at the bottom, the actual work was done by thousands of people carrying heavy chains across swamps.

We haven’t changed much. We have the digital equivalent of a laser-guided theodolite at the point of sale, but we are still carrying heavy chains across the swamp of contract administration.

When a lender separates “bought” from “built” along the line of revenue vs. cost, they create a permanent drag on their own economics. If you buy a top-tier origination engine but build your servicing out of workarounds, you are effectively buying a Ferrari and then hiring a team of people to push it down the highway.

The friction is invisible at first. A few spreadsheets here, a manual ACH reconciliation there-it feels like “agility.” But as the portfolio grows, that friction scales faster than the revenue.

You find that you can’t modify a contract in-life without opening a vendor ticket that takes six weeks to resolve. You find that your asset records have drifted away from your contract records, like two tectonic plates grinding toward a massive audit failure.

In the world of commercial lending, this fragmentation often hides in plain sight until an auditor asks for a reconciliation report that requires three people and a week of work. This is the moment when the reality of the “cost case” finally breaks.

They need a dedicated equipment finance software that recognizes that the deal doesn’t end when the signature is dry; it only begins there.

The boundary between what we purchase and what we improvise usually follows the availability of a revenue argument rather than the actual difficulty of the work. It is infinitely easier to get a budget approved for a tool that promises a 10% increase in lead conversion than for a tool that promises to automate the end-of-term residual buyouts.

One feels like winning; the other feels like chores. Yet, the economics of an equipment finance portfolio are decided in those “chores.” The profitability of the deal is leaked or locked in during the five years of in-life changes, billing cycles, and delinquency management.

The Kinetic Energy of Finance

Natasha T.-M. would call this a “secondary impact.” In a car crash, the primary impact is the car hitting the wall. The secondary impact is the passenger hitting the interior of the car. In finance, the primary impact is the market volatility or the interest rate hike.

The secondary impact-the one that actually kills the firm-is the internal systems hitting each other because they aren’t synchronized. When your origination data doesn’t flow cleanly into your servicing engine, or when your servicing engine requires manual reconciliation of a wire payment, you are experiencing a secondary impact. The energy has nowhere to go, so it breaks the structure.

Beyond Spreadsheets and Prayers

We have reached a point where “servicing” can no longer be the dumping ground for technical debt. The complexity of modern assets-IoT-enabled tractors, modular medical imaging suites, renewable energy arrays-requires more than a spreadsheet and a prayer.

These assets move. They change. They are upgraded, liened, and returned. An API-first architecture isn’t a luxury in this environment; it is the only way to ensure that the “infotainment” at the front of the house is actually connected to the engine at the back.

I often wonder if we would treat our back offices differently if they were as visible as our storefronts. If a customer could see the “manual routines” that govern their five-year lease, they might feel like a passenger in a car where the steering wheel is connected to the wheels by a series of clotheslines and pulleys.

It works, until it doesn’t. It works, as long as the road is straight and the speed is low. But the moment the market turns-the moment there is a “crash”-those workarounds become the very things that cause the most damage.

The deeper meaning here is that the parts of an organization we describe as “growth” get industrialized because we believe in their future. The parts we describe as “cost” get improvised because we are ashamed of their past.

Industrializing Growth, MacGyvering Trust

We see servicing as a legacy of a deal already done, rather than the lifeblood of a relationship still in progress. This is why the portfolio economics of so many lenders are currently being eaten alive by headcount.

They are adding people to solve problems that should have been solved by code, because code requires an “investment” while people are just “operating expenses.” It is a bizarre inversion of logic.

We will spend millions to acquire a customer, and then refuse to spend thousands to ensure that customer’s experience for the next sixty months is seamless. We treat the wedding like a royal event and the marriage like a series of sticky notes on the fridge.

The Industry Wakes Up

But the industry is starting to wake up to the “servicing gap.” The most successful firms are the ones that have realized that the boundary between origination and administration is an artificial one.

They are looking for platforms that can handle the full lifecycle, not by replacing every single piece of their stack, but by plugging in a servicing engine that is as sophisticated as their acquisition tools. They are looking for a way to make sure that when the “energy” of a new deal hits the book, it doesn’t result in a crash.

Natasha told me that the most dangerous part of a car isn’t the engine; it’s the heavy, unsecured objects in the backseat. In a collision, those objects keep moving at the original speed of the car until they hit something-usually the back of the driver’s head.

They look harmless while you’re cruising at sixty miles per hour on a sunny day. But when you have to slam on the brakes, they are the things that will finish you.

We need to stop building our businesses out of workarounds. We need to stop pretending that the “cost case” is an excuse for improvisation. The next time you look at your application portfolio, don’t just look at the shiny SaaS tool at the top.

Where True Risk Lives

Look at the spreadsheets at the bottom. That is where your true risk lives. That is where the energy is going to go when the impact happens.

And if you haven’t built a structure that can handle it, no amount of heated seats or high-end infotainment is going to save you.