“But does it handle the skip-payments for the citrus guys in Florida?”

“We’ll get to the lifecycle management module in a moment,” the presenter says, his voice as smooth as a polished ball bearing (which, incidentally, was a design patent held by Leonardo da Vinci in the 15th century). The screen transitions to a dashboard so vibrant it looks like it belongs in a flight simulator rather than a back-office financial suite.

Tom, the VP of Operations, watches the cursor glide across a series of “Opportunity Stages.” He has a legal pad in front of him with one word written in the center: “Restructures?” He has circled it twice, the ink bleeding through to the next three pages. He wants to know what happens when a drought hits the Everglades and six different multi-generational farming families need to push their June payments to November. It is a messy, granular, deeply un-sexy question that involves recalculating interest accruals-the process of accounting for interest earned but not yet paid-on the fly.

The Social Gravity of Silence

Instead of asking, Tom looks at his CFO, who is nodding rhythmically at the “Pipeline Velocity” chart. Tom realizes that asking about the citrus guys right now would be like complaining about the upholstery of a lifeboat while everyone else is admiring the engine’s horsepower. It feels small. It feels like a “me” problem rather than a “system” problem.

We often treat software demos like high-stakes theater where the goal is to reach the final curtain without anyone tripping over the props (and interestingly, the word “prestige” originally referred to a magician’s trick, or an illusion). Because the status gradient in the room is steep, the most important questions are often the ones that stay in the pen.

The demo continues into “Automated Origination,” a phase of the process that Tom’s team hasn’t struggled with since 2014. The software is showing him how easy it is to onboard a new customer, which is the software equivalent of showing a prospective homeowner how easy it is to walk through the front door (though most residential doors are standard at 80 inches tall to accommodate the average human height).

The real problem isn’t getting people into the house; it’s what happens three years later when the roof leaks and the plumbing is backed up. In the world of equipment finance, the “leaky roof” is the mid-contract amendment. It is the borrower who needs to extend their lease by 14 months because their new equipment is stuck in a port in Long Beach.

Beneath the Neon Glow

Finley E., a veteran neon sign technician who spends his days bending glass tubes over open flames, once told me something that stuck. He said, “If the vacuum pump is cheap, the sign will flicker in six months, no matter how pretty you bent the glass.” (Argon gas, which creates that distinct blue glow, requires a near-perfect vacuum to stay stable).

“If the vacuum pump is cheap, the sign will flicker in six months, no matter how pretty you bent the glass.”

– Finley E., Neon Sign Technician

Software is no different. The front-end “glass”-the dashboards, the drag-and-drop interfaces, the colorful reporting-is what gets the budget approved. But the “vacuum pump” is the servicing engine. It’s the ability to handle a partial payoff-paying down a portion of the principal before the scheduled end date-without the entire ledger collapsing into a pile of manual spreadsheets.

Last week, I accidentally sent a text meant for my wife to a senior partner at a firm I’m consulting for. It was a grocery list that included “the weird yogurt with the little hats” (referring to the plastic lids on certain probiotic brands). For three minutes, I felt that specific, cold-water-down-the-spine panic of having exposed the messy, domestic reality of my life to a person who only knows me in a suit.

That is exactly how operators feel during a software demo. To ask about a “weird” edge case is to admit that your business is messy. It’s an admission that your data isn’t clean, your customers are unpredictable, and your current process involves a person named Brenda who knows exactly which Excel cell to “fudge” to make the monthly report balance.

Growth vs. Protected Profit

The irony is that every single person in that conference room knows the business is messy. The CFO knows it. The vendor knows it. But the social contract of the demo requires us all to pretend we are buying a “solution” that will eliminate the mess, rather than a tool that will help us manage it.

We buy the “Pipeline” because it represents growth, but we live in the “Servicing” because that is where the profit is actually protected. When you are evaluating equipment financing software, the shiny origination tools are the lure, but the contract modification engine is the hook. If the system can’t handle a simple change in payment frequency from monthly to quarterly without a support ticket, you haven’t bought a solution; you’ve bought a 2,140-day headache.

The presenter moves to the “End of Term” slides. He shows a clean, automated workflow for residual buyouts-the price a lessee pays to own the equipment at the end of the lease-which looks incredibly efficient on a slide. In reality, end-of-term is a chaotic period of negotiations, inspections, and partial returns.

(A standard shipping container can hold about 3,500 shoe boxes, yet somehow, equipment returns never seem to fit the space allocated for them). If the platform doesn’t allow for “pro-rating”-calculating a cost based on the proportion of time used-then every one of those negotiations becomes a manual entry. This is how “digital transformation” ends up being just a more expensive way to move numbers from one screen to another.

Eighty Minutes of Fatigue

Tom’s thumb hovers over his phone. He thinks about the 42 different times last month his team had to manually adjust a schedule because a client’s credit rating shifted. He looks at the “Full Lifecycle Management” slide, which is the industry’s way of saying “we do everything” (even though the term “lifecycle” was originally a biological concept used to describe the development of insects).

He wants to ask if the system can handle “non-accrual status”-where the lender stops recording interest income because the borrower is unlikely to pay-but the presenter is already talking about the AI-driven “Sentiment Analysis” for new leads.

The room is silent except for the hum of the HVAC system, which is likely moving about 400 cubic feet of air per minute per person. The silence isn’t because everyone is impressed; it’s because everyone is tired. They have been in this room for eighty minutes, and they have seen forty-five slides, none of which showed the screen they will actually have to look at when a customer calls in a panic.

The “servicing” part of the demo is usually squeezed into the last ten minutes, right before the Q&A, because vendors know that servicing isn’t what wins the heart-even though it’s what breaks the back.

We tend to overestimate the importance of the “moment of sale” and underestimate the “duration of service.” (The average lifespan of a modern commercial lease is roughly 1,825 days). For 1,824 of those days, the origination features that looked so good in the demo will be irrelevant. The only thing that will matter is whether the operations team can respond to a change request without having to perform digital gymnastics.

The Price of Reporting Flash

The software evaluation process is a series of trade-offs, but we often trade the wrong things. We trade “servicing depth” for “reporting flash.” We trade “configurability” for “user interface.”

We do this because it is easier to show a board of directors a beautiful graph than it is to explain why the way the system handles “interim rent”-the daily rent charged between the delivery of equipment and the start of the first full billing cycle-is a competitive advantage.

At the end of the meeting, the presenter asks if there are any final questions. Tom looks at his pad. He looks at the word “Restructures?” circled until the paper is thin. He looks at the CFO, who is checking his watch.

“Great presentation,” Tom says, sliding his pen into his pocket. “The dashboard looks really clean.”

He will regret those five words in approximately fourteen months, on a Tuesday, when the citrus guys call. He will realize then that the cost of a software platform isn’t the license fee; it’s the “friction tax” paid every time the system forces a human to do what the machine was supposed to handle. (The first tax in recorded history was levied in Sumeria, where citizens paid in livestock and labor).

The dashboard is a mirror for a future where every manual adjustment is a quiet confession of a failed demo.

Tom leaves the room and realizes he still hasn’t replied to that accidental text. He sends a quick follow-up: “Wrong person, obviously. But I do actually need that yogurt.” It’s a small, honest admission of a mess. If only he could have done the same in the conference room, he might have saved his team from 862 hours of future manual data entry. But in the theater of the corporate demo, the script is king, and the “weird” problems of the people who actually do the work are just unwritten stage directions.

The Cycle Continues

The vendor packs up his laptop, satisfied. He has shown the features. He has stayed on schedule. He has avoided the mess. He doesn’t know about the Florida citrus farmers, and he won’t have to deal with the 31% increase in “exception processing” that will plague the operations department by next Christmas.

He’s already thinking about the next demo, where he will show the same beautiful, empty dashboards to another room full of people who are too polite to ask about the leaks in their own roofs.