You are sitting in a medium-sized conference room on the eleventh floor of a glass-fronted building in a city where it has rained for three consecutive days. On the table before you is a printed copy of a vendor’s annual report, a stack of three-ring binders containing software specifications, and a cold cup of black coffee.

You are looking at a specific page in the financial summary-a table labeled “Revenue by Segment.” The numbers are clear. Subscription and license revenue accounts for $12.4 million. Professional services and implementation revenue accounts for $18.7 million. The second number is not only larger but is growing at a rate of 14% year-over-year, while the license revenue has remained relatively flat at 3%.

In your other hand, you hold a glossy brochure from the same company’s marketing department. It features a high-resolution photograph of a smiling woman in a neutral-toned office, looking at a clean dashboard. The headline, printed in a bold, sans-serif font, says: “The Fully Configurable Platform: Put the Power Back in the Hands of the Business User.” Underneath, a bulleted list promises a “no-code environment,” “seamless in-life changes,” and “zero reliance on vendor support for day-to-day operations.”

You have spent the last four hours trying to reconcile these two documents. One document describes a business that makes the majority of its money when its customers cannot do things themselves. The other document describes a product that supposedly eliminates the need for that very assistance.

You are looking for the lie. You are looking for the person who sat in a room and decided to deceive you. But as you trace the flow of capital from the services invoice to the marketing budget, you realize that there is no liar. There is only a loop.

I spent twenty-two minutes yesterday testing every ballpoint pen in the supply closet to find one that didn’t skip on the vertical stroke. It was a waste of time, but I wanted to know the failure rate. I have spent a career looking at traffic patterns and data packet flows, and I have learned that the tension between the services revenue and the “configurable” marketing is not a sign of a failing company; it is the source of its stability.

The Expert “Wrapper” Economy

The implementation team for a legacy software provider usually arrives with three laptops, a rolling whiteboard, and a spreadsheet containing 1,412 open issues from the legacy migration. These individuals are highly skilled. They are experts in database schema adjustments, custom reporting triggers, API mapping for legacy ERPs, and UI localization for specific tax jurisdictions.

They spend their days in windowless rooms writing “wrappers” around old code to make it look like new code. They are not villains. They are hard-working professionals who are solving the immediate problems that the software, in its “out-of-the-box” state, cannot solve.

The cost of their time is significant. A single change request-perhaps a modification to how the system handles grace periods for late payments on a fleet of five hundred delivery vans-can take three weeks to scope, two weeks to develop, and another month to test. The invoice for this work is added to the professional services segment of the annual report. This revenue is predictable. It is reliable. It is the steady heartbeat of the vendor’s financial health.

The Roadmap of Belief

Meanwhile, three floors up or perhaps in a different city entirely, the marketing team is tasked with growth. They look at the market and see that buyers are tired of high service costs. They see that the “no-code” movement is the primary driver of new leads. They write a campaign based on the vision of the product. They believe in the roadmap.

They are told that the next version of the software will finally include the configuration engine that will make the services team obsolete. They write the brochures based on that belief. The salesperson is not lying about what the software could be, and the services lead is not lying about what the software currently is.

The loop completes itself when the revenue from the services team-the money paid by customers who are currently stuck in a cycle of change requests-is used to fund the marketing campaign that promises a world without change requests. This is a self-financing mechanism. It is stable. It is explicable without any individual acting in bad faith.

I once miscalculated the throughput of a major shipping port because I assumed the cranes were slow due to poor maintenance. I was wrong. The cranes were slow because the terminal operators were paid by the hour, and the shipping lines were willing to pay the premium for “priority” docking which only became necessary when the cranes were slow.

The bottleneck was the profit center.

In the world of commercial finance, the bottlenecks are often found in “in-life changes.” Consider the life of a lease for a piece of industrial equipment-a laser cutter or a fleet of heavy-duty stamping presses. Over the course of five years, the customer may need to substitute collateral, extend the term by three months to bridge a budget gap, or restructure the payment schedule due to a seasonal downturn in their industry.

The Architecture of Freedom

When you are evaluating equipment finance software, you have to look past the “no-code” label and look at where the change button actually lives.

If the change button lives on the vendor’s side of the firewall, you are looking at a services business disguised as a software business. If the change button lives on the lender’s dashboard-if the person who manages the portfolio can adjust a late fee, add a grace period, or re-calculate a residual value without opening a ticket-the loop is broken.

The reason most vendors cannot break the loop is that they cannot afford to. If they made the software truly configurable by the end-user, they would lose 40% of their revenue overnight. They would have to fire the implementation teams that are currently keeping the lights on. They would have to stop the marketing campaigns because the budget would vanish.

To move from a services-heavy model to a truly configurable servicing platform requires a different architectural starting point. It requires an API-first approach where the core engine is separated from the user interface, allowing the lender to build their own workflows and make their own changes without touching the underlying source code.

The architectural choice is also a business model choice. A company like Lendscape, which focuses on portfolio servicing rather than the entire origination-to-end-of-term lifecycle, can afford to be truly configurable because their success is measured by the scale of the portfolio, not the number of hours billed by a consultant.

When the software handles finance leases, operating leases, and equipment loans on a single platform, and the architecture allows for “in-life” changes to be executed by the lender’s own staff, the vendor-client relationship shifts. It moves from a relationship of dependency to a relationship of utility.

I have seen similar patterns in city planning. We build roads that are too narrow, which creates congestion, which justifies the budget for a new highway, which is funded by the taxes of the people sitting in the congestion. We call it “infrastructure growth,” but it is really just the monetization of a self-inflicted wound.

The stable loop of the software vendor is comfortable for everyone involved except the customer. The sales team gets their commissions. The services team gets their billable hours. The executives get their growing “total revenue” figures to show to the board. The customer is the only one who feels the friction, and because the friction is presented as “customization” or “high-touch support,” the customer often feels that they are getting a premium experience.

The Psychology of Complexity

They are told that their business is “unique” and “complex,” and therefore requires the special attention of the services team. This is the most effective part of the loop: it flattens the customer’s ego. It convinces the lender that their inability to change a payment date is a sign of their own sophisticated requirements rather than a sign of the software’s rigid architecture.

Breaking this cycle requires a moment of clarity. It requires looking at the “Services” line of a proposal not as a necessary evil of implementation, but as a diagnostic indicator of the software’s limitations.

The rain is still hitting the window of the glass-fronted building. You close the annual report. You realize that the search for a villain was a distraction. The system is working exactly as it was intended to work.

The only question left is whether you want to continue being the fuel for someone else’s loop, or if you want to find a platform where the configuration is a reality you can touch, rather than a promise you have to pay for twice.

When the lender can handle the late fees, the tax adjustments, and the collateral substitutions without picking up the phone, the vendor loses a billable hour but gains a partner. Most vendors are not yet ready to make that trade. They are still too busy buying pens that don’t skip and writing brochures for a future they can’t afford to build.