If you restore a grandfather clock from 1794, you cannot simply fix the face and the hands and call the job done. The clock is a system of three trains: the going train that keeps time, the strike train that rings the hours, and the chime train that plays the tune.

If you find the chime gears are rusted or the pins on the cylinder are bent, you might feel tempted to leave them out. You want the clock back in the hallway for the owner’s birthday party. The hands will turn. The guest will see the time. But at midnight, the house will stay silent.

You have met the date, but you have broken the soul of the machine. The owner will spend the next twenty years looking at a mute box of wood and brass, knowing that it only does half the work it was built to do.

Software implementations in the world of commercial finance suffer from this same desire for a pretty face on a broken body. We sprint toward a go-live date as if it were a finish line. We treat the date like a god that demands a sacrifice. Usually, that sacrifice is the servicing team.

The Anatomy of a Failure

Week forty-one of the project is where the rot starts. I remember sitting in a room where the air had grown thin from too many hours of talk. The project manager stood at the front, pointing at a red box on a slide. He spoke about the “interim rent proration module.”

He said the build was behind. He said we had to protect the “Go-Live” date. I yawned while he spoke, not out of boredom, but from the kind of deep fatigue that comes when you see a mistake being made in slow motion.

That word “agreed” is a lie. It implies a fair trade. But in these rooms, the operations people have no real vote. They are told that if they do not “agree,” the whole project will fail. They are told that “Phase Two” will start the month after go-live.

Everyone in the room knows that Phase Two is a graveyard. It has no budget. It has no team. It has no date. By the time Phase Two is supposed to start, the consultants have moved to a new client and the internal project leads have taken their bonuses and their new titles.

Six years later, a team of four people still sits in an office on the second business day of every month. They open a spreadsheet. They pull data from the system. They calculate the proration by hand. They type the numbers back in. They have done this for 2,192 days. They will do it until they quit or the company dies.

The project manager who “saved” the date by cutting that scope is long gone. He is probably a Vice President somewhere now, telling stories about how he delivered a complex system on time and under budget. He didn’t deliver a system. He delivered a debt. He took a loan out against the life of the servicing team, and the interest rate is a thousand hours of manual labor every year.

This happens because project incentives are broken. We measure the success of a launch by the calendar and the bank account. We do not measure the success by the “servicing tax” we leave behind. If a project manager were forced to stay and do the manual work they created for the next five years, they would never cut a single piece of automation.

The Shiny Front vs. The Rusted Gears

When you look for equipment loan software, you are often sold on the “front end.” You see the shiny portals where customers can apply for a lease. You see the credit scorecards that blink green in three seconds. You see the digital signatures.

This is the “going train” of the clock. It looks good. It moves fast. But the life of a lease is not the thirty minutes it takes to sign the paper. The life of a lease is the seven years that follow. It is the thousands of days of billing, the mid-term changes, the tax updates, and the end-of-term processing.

If the servicing scope is cut, the “chime train” is missing. The system might keep time, but it cannot ring.

“If you don’t set the escapement right today, you’re just asking the owner to climb a ladder and shake the case once a week for the next thirty years.”

– Winter J.P., Clockmaker

Winter J.P. knew that the person who does the work today determines the pain of the person who lives with the machine tomorrow.

The Gravity of the Small

The manual work we “agree” to in week forty-one is almost always the “boring” stuff. It is the way the system handles a partial payoff. It is the way it tracks a piece of collateral that has been moved to a different state with different tax laws. It is the way it reconciles a payment that is five cents short.

These are small things in a steering committee meeting. They are huge things when you have 48,000 contracts and the system cannot handle them.

We must stop treating servicing as a “Phase Two” problem. In commercial finance, servicing is the business. It is where the profit is made or lost. If your system requires a human to touch a contract every time a customer changes their billing address, you do not have a system. You have a very expensive typewriter.

The cost of these manual steps is hidden. It does not show up on the project budget. It shows up in “headcount.” When the servicing team asks for more people, the executives wonder why. “We just spent millions on a new system,” they say. “Why do you need more staff?”

They need more staff because the “Phase Two” functionality that was supposed to automate their jobs is currently sitting in a digital drawer, gathering dust.

A Different Mindset

True automation requires a different mindset. It requires an architecture that is built for the “long now” of the lease. This is why API-first systems are changing the math.

When a system is built with APIs at its heart, like the ones used in modern portfolio management, you don’t have to wait for a vendor to build a “module” for your manual tasks. You can connect the system to your own tools. You can automate the proration yourself. You can fix the clock without waiting for the original clockmaker to come back from his vacation.

But even with the best tools, the human problem remains. We have to be brave enough to say “No” to a go-live date if the servicing train is not ready. We have to stop letting people who won’t be there in three years make decisions for the people who will be there in ten.

The next time you are in a meeting and someone suggests “deferring” a servicing requirement to protect a date, look at the people from the operations team. Look at their faces. They are the ones who will have to pay the bill you are about to sign. They are the ones who will be doing the manual proration on the second business day of the month in the year 2031.

And a silent clock is just a very heavy piece of furniture. We owe it to the people who run the business to deliver a machine that actually works, even if it means the birthday party has to wait a few more weeks.

Honesty about what is actually being delivered is the only way to stop the rot. We have to stop calling a permanent manual workaround a “Phase Two.” We have to call it what it is: a failure of will.

I think back to that decision log entry from six years ago. If I could go back, I would stop yawning. I would stand up. I would take the pen. I would strike out the word “agreed.” Because no one who has to do that math for six years would ever agree to it.

They were just outvoted by a calendar. And the calendar is a very poor judge of what a servicing team needs to survive.