I once made a mistake on a bid for a heritage stone wall. I calculated the tonnage of the fieldstone required for the job. I estimated the hours needed for the chiseling and the placement of each rock.

I forgot to account for the owner of the adjacent property. He wanted to discuss the exact placement of the property line every morning at seven. My contract covered the construction of the wall. It did not cover the cost of the conversation.

The stones represented the physical substance of our agreement. They were the tangible deliverables listed in the quote. I spent four hours every week talking to a man who was not my client. I spent those hours explaining why the wall would not move six inches to the left.

These hours were invisible to the budget. They were the coordination tax of the project.

The Vendor Translation Error

Software vendors and their clients make the same mistake every day. A vendor agreement specifies the software modules. It lists the uptime percentages and the support response times. The contract says nothing about the meetings and the clarifications. It ignores the translations and the chasing that consume the internal effort. This effort is the actual cost of the relationship.

The coordination cost falls on people who already have full-time jobs. It lands on the operations manager who must bridge the gap between the business and the code. She spends her Tuesday morning in a governance call. She spends her Tuesday afternoon explaining the governance call to her own team.

Her job description does not mention the role of a professional translator. Her objectives do not include the management of vendor friction.

The Economic Cost of Coordination

I recently spent an afternoon reading about the theory of the firm. Ronald Coase wrote about this in 1937. He wondered why companies exist instead of everyone working as individuals.

He realized that using the market has a cost. Finding a price is a cost. Negotiating a contract is a cost. Coordination is the reason firms stay small or grow large.

In the world of commercial finance, these boundaries are everywhere. A lender buys a system to manage their portfolio. They believe they are buying a tool to automate their work. They are actually creating a new boundary between their staff and their data. Every time the business changes, they must cross that boundary. They must talk to the vendor to change a payment rule.

A typical week for an operations manager reveals the hidden tax. None of these activities appear in the business case. The business case focuses on the license fees and the implementation. It counts the number of internal staff dedicated to the initial rollout. It assumes the relationship will be self-sustaining once the system is live.

This assumption is a lie. The permanent cost of the system is the attention it requires from the management. A cheap relationship often occupies a third of a manager’s week for years.

Friction at the Boundary

The coordination tax is highest when the system is a black box. A black box requires a key held by the vendor. If a lender wants to modify a contract in-life, they must submit a ticket. They must wait for a response from a person who does not understand their business. They must explain the request three times. This is the friction of the boundary.

Modern equipment lease software attempts to dissolve these boundaries through architecture.

An API-first design allows systems to talk to each other without human intervention. Computers do not need governance calls to exchange data. They do not need to send eleven emails to clarify a field definition. The architecture handles the coordination that humans used to perform.

If the lender’s staff can configure their own servicing changes, the tax disappears. They do not need to coordinate with an external party for a routine task. They can change a collection rule or an end-of-term process on their own. This reduces the number of meetings required to maintain the book. It returns the manager’s Tuesday afternoon to her actual job.

Total cost of ownership models are usually incomplete. They measure the money that leaves the bank account. They do not measure the energy that leaves the building. They ignore the “chasing” cost of a slow vendor. They ignore the “pre-meeting” cost of a complex integration. These costs are borne by individuals rather than by budgets.

I remember sitting on the ground with my stone hammer. I watched the neighbor approach with a surveyor’s map from 1984. I realized the wall was not just made of granite and mortar. It was made of every minute I spent justifying its existence. The wall was a boundary. The boundary was expensive.

Organizations create boundaries when they outsource their core functions. They believe they are saving money on headcount or expertise. They forget that every boundary requires a gatekeeper. They forget that gatekeepers must talk to each other. The more gatekeepers you have, the more meetings you attend.

The cheapest-looking arrangement is often the one that quietly consumes the most attention.

Transparent Success

A lender might migrate a full servicing portfolio to a new platform. They worry about the downtime during the migration. They worry about the accuracy of the data transfer. These are the stones of the project. They are the visible parts of the wall.

The real success is measured in the months following the go-live event. Success is a week without a governance call. It is a defect that is fixed without three layers of clarification. It is an in-life contract modification that takes five minutes instead of five days.

When the lender does not have to coordinate with the vendor, the software is finally working. The boundary has become transparent.

The stones in my wall eventually reached the proper height. The neighbor eventually accepted the property line. I finished the job and I moved to the next one. I learned to look at the neighbors before I looked at the rocks. I learned that the labor of the work is different from the cost of the work.

We should stop asking what the software costs per month. We should start asking how many meetings the software requires per month. We should ask how many people must spend their day translating business needs into technical tickets. We should ask who is paying the coordination tax.

Usually, it is the person who is too busy to attend the meeting where the software was bought.

“The stone fills the gap in the wall, but the meeting fills the gap in the day.”

Transaction costs are the invisible tax on every boundary an organization creates. They are the friction of the “other.” When a system is truly integrated, the “other” disappears. The lender regains control of their own processes. They stop being a coordinator and they start being a lender again.

I still work with stone. I still appreciate the weight of a good piece of granite. But I also value the silence of a well-run project.

Silence is the sign of a low coordination cost. It is the sound of a contract that actually covers the work. It is the only way to get your Saturdays back.