I once spent trying to dismantle a masterpiece because I didn’t have the password to the file. At the time, I was managing a small operations team for a mid-market lessor, and I had become obsessed with the idea of “process purity.” I believed that if a task wasn’t documented in the official SOP, it shouldn’t be happening.
One of my analysts, a quiet man named Elias, was processing three times the volume of anyone else. When I asked him how, he told me he was just “getting into a rhythm.” I didn’t believe him. I spent a weekend trying to reverse-engineer his spreadsheets, looking for the hidden gears. I eventually found a series of nested macros that were so sophisticated they essentially did his job for him.
Instead of celebrating, I panicked. I told him to delete them because they weren’t “vetted by IT.” I pushed a door that said Pull, and in doing so, I watched my team’s most efficient engine stall and eventually quit.
The mistake wasn’t in wanting stability; the mistake was in failing to recognize that when the official tools provided by the institution are too blunt for the precision of the work, the worker will always find a way to sharpen the edge in secret.
In a modern equipment finance office, this plays out every single day. There is almost always one person-let’s call her Sarah-who is the undisputed champion of the monthly close. Her manager, a well-meaning person who likely worries about “delinquency roll rates” and “cost per contract,” looks at Sarah’s numbers and sees a paragon of focus.
Team Average
814
Sarah’s Output
1,168
Active contracts managed per analyst: Sarah maintains a 43% productivity advantage through “unmanaged” automation.
Sarah manages 1,168 active contracts while the team average is closer to 814. She never seems stressed. She never stays late. Her billing accuracy is nearly 100%. To the leadership, Sarah is a cultural victory. To Sarah, she is a person who got tired of copy-pasting the same twenty-four fields from a legacy green-screen terminal into an Excel sheet.
The Labyrinth of Workarounds
On her second monitor, hidden behind a browser window displaying the corporate intranet, Sarah has a small executable file running. It isn’t malicious software. It’s a script she wrote in her on the job, back when she realized the company’s servicing system was a labyrinth of manual workarounds.
The script pulls data from the contract records, matches the collateral IDs, and produces the final allocations for her to review. She spent of her own time building it. She has never told anyone about it because the last person who mentioned a custom automation in a department meeting was told by a compliance officer that “unmanaged code is a security breach.”
This is the quiet tragedy of shadow innovation. The very thing that makes the business profitable is technically a violation of the rules.
Because the architecture of a spreadsheet mimics the architecture of a mind, we assume we can see the logic of our business through its rows. Which is also how we mistake the map for the territory when a lender scales.
A lease is not a row; it is a promise of cash flow tied to a physical object, a piece of metal that exists in the dirt while the data sits in the cloud, and if the data is wrong, the metal might as well be invisible. The analyst who builds a secret script is simply trying to bridge the gap between the metal and the cloud, trying to make the map look more like the actual world. They are building the infrastructure they were promised but never given.
When you look at a portfolio that has grown beyond 10,000 contracts, the cracks in the manual approach start to look like canyons. In the context of equipment finance, the rules are designed to ensure data integrity, yet by making it so difficult to update a system or automate a repetitive task, the organization forces the analyst to choose between “following the rules” and “getting the work done.”
If Sarah follows the rules, she processes 800 contracts and the backlog grows. If she gets the work done, she uses her script, and the company stays profitable, but the “capability” belongs to Sarah’s local hard drive, not to the company. If Sarah leaves for a competitor tomorrow, her 43% productivity advantage leaves with her.
Bridging the Capability Gap
This is why the architecture of the servicing platform matters more than the training of the analyst. If a lender is running on a system that treats every contract as a static artifact, they are essentially asking their staff to act as human bridges. They are paying for brains but using them for thumbs.
A modern approach to equipment finance software flips this dynamic. Instead of forcing the analyst to build a “shadow” bridge, the platform itself provides the API-first connectivity that makes the automation part of the official record.
When the servicing capability belongs to the platform rather than the individual’s secret folder, the innovation is no longer a risk-it is an asset.
I remember a specific Tuesday when I finally realized how deep the rot of “secret efficiency” went. I was sitting with a collections manager who was miraculously keeping his delinquency rates under 3%. He was a wizard. He knew exactly when to call, who to talk to, and how to structure a workout.
“When I asked him for his secret, he pulled a tattered notebook from his desk. It was filled with handwritten notes on ‘informal’ grace periods and personal cell phone numbers for fleet managers that were never entered into the main CRM.”
– The Wizard’s Notebook
He was terrified I’d take the notebook away. He saw his expertise as a form of contraband. That is the signal that your technology has failed. When your most talented people feel like they are “cheating” just to be good at their jobs, you aren’t running an efficient operation; you are running a hostage situation.
The Cheapest R&D Department
The irony is that shadow automation is the cheapest R&D department you will ever have. These analysts are identifying the exact friction points in your business and solving them with zero budget. They are showing you precisely where your system is broken. Instead of shutting them down, the goal should be to provide a system that is flexible enough to absorb their improvements.
When a lender moves to a system that handles the entire lifecycle-from finance leases to operating leases to conditional sales-on a single, API-enabled platform, the need for Sarah’s secret script evaporates. Not because she’s been told she can’t use it, but because the system is finally doing what she was trying to make it do.
I often think about Elias and his macros. If I had been smarter, I wouldn’t have told him to delete them. I would have asked him to help me build a system where those macros weren’t necessary. I would have realized that his “rebellious” code was actually a cry for help from a person who wanted to be more than a data-entry clerk.
We tend to value the “servicing book” as a collection of assets, but the real asset is the ability to service that book without it becoming a weight around the organization’s neck. As soon as you scale, the manual workarounds that were “fine” at contracts become a terminal illness at .
You cannot hire your way out of a broken process, and you certainly cannot “rule” your way into efficiency. The next time you see someone who is significantly more productive than their peers, don’t just congratulate them on their focus. Ask them what they’ve built. Ask them what they’re hiding.
If they trust you enough to show you the script running in the background, don’t call compliance. Call your software vendor.
The transition from a “shadow-powered” office to a platform-powered one isn’t just about technology; it’s about a shift in the psychology of permission. It’s about moving from a world where innovation is a secret to a world where capability is a feature.
When the servicing platform is built to handle the complexity of in-life changes, billing, and asset tracking through a single, governed source of truth, the “Sarahs” of the world can finally stop being programmers and start being analysts again. They can focus on the strategy of the portfolio rather than the syntax of a macro.
We have to stop pushing the doors that say Pull. We have to stop trying to force people into rigid, manual processes and instead give them systems that are as dynamic as the markets they serve. Only then can we move the innovation out of the shadows and into the ledger where it belongs.