The gap nobody can explain
A growing mid-market company closes its year with revenue up twenty-two percent. The owner pulls the financials expecting to see margin expand in the same direction. It does not. EBITDA holds flat. In some cases it compresses. Headcount is up twenty-eight percent. The team is working harder than ever. The business looks like it is winning on the top line and losing somewhere in the middle.
The CFO flags it. The leadership team debates it. The usual explanations get trotted out. Wage pressure. Input costs. Timing of a few large jobs. Some of that is real. Most of it is not the actual answer.
The actual answer is that the business is paying a tax it never agreed to and cannot see on any invoice. Every growing mid-market company pays it. The ones that figure out what it is get ahead. The ones that do not spend the next five years hiring to outrun it and wondering why the math never catches up.
Revenue climbs. Margin does not.
Typical pattern in a growing mid-market company, indexed to year one.
What the coordination tax actually is
Coordination tax is the cumulative labour cost of moving information, decisions, and work between people and systems inside an organization. It is the time your team spends not doing the job, but coordinating the doing of the job. Status updates. Handoff confirmations. Manual reconciliation between platforms. Meetings held because nobody trusts the dashboard. Rework caused by a detail that did not make it from one function to the next.
At a ten-person company this tax is near zero. Everyone sits in the same room. Information moves by conversation. Decisions get made in the hallway. The business runs on shared context and tribal knowledge, and for a while that is enough.
By the time that same business is fifty people across two locations, the context has fragmented. Information that used to move for free now requires a meeting. Decisions that used to happen in minutes now wait for three people to respond. Handoffs that used to be invisible now leak detail and require follow-up. Nothing obvious broke. The structure outgrew the way it was being run.
By the time the business is 150 people, the coordination layer is a department. Coordinators, project admins, operations managers, dispatchers. A growing portion of headcount exists not to produce output but to move information between the people who do. Margin is being paid out to the tax, and nobody is naming it.
How the tax scales with headcount
Stage 1
10 people
Near-zero tax
Shared context. Information moves by conversation. Decisions made in the hallway.
Stage 2
50 people
Context fragments
Meetings replace conversation. Handoffs leak detail. Structure outgrows the run.
Stage 3
150 people
Tax is a department
Coordinators, admins, ops managers. A layer that moves information instead of producing.
The four forms it takes
The coordination tax does not show up as a line item. It shows up in four specific patterns, and every mid-market operator we talk to recognizes at least two of them inside their own business.
Form 1
Manual handoffs between systems
Four people touching the same information four times because the tools do not talk.
Form 2
Status updates and meeting overhead
Standing meetings exist because nobody trusts the data to reflect what is actually happening.
Form 3
Rework from miscommunication
Wrong size ordered, wrong scope priced, wrong crew dispatched. Visible cost plus invisible cost.
Form 4
Single-person knowledge bottlenecks
The one person who knows where everyone is. Key-person risk disguised as reliability.
Manual handoffs between systems
A construction estimator finishes a bid in one tool. The PM picks it up and rebuilds the budget inside a project management platform. Procurement pulls the same materials list into a third system to issue POs. Accounting eventually imports the whole thing for invoicing. Four people touch the same information four times because the tools do not talk. That is not workflow. That is the business paying four people to keep four systems in sync, and calling it operations.
Status updates and meeting overhead
Standing meetings exist because nobody trusts the data to reflect the truth. Weekly ops reviews get scheduled to confirm what the system was supposed to show automatically. Senior people spend four hours a week answering variations of the same question: where are we on this. Time that should be going toward decisions gets spent manufacturing the inputs to the decisions. The calendar fills up and nothing gets built.
Rework from miscommunication
A detail gets missed in a handoff. Wrong size ordered. Wrong scope priced. Wrong crew dispatched. The work gets redone. The cost of the rework itself is visible. The cost of the follow-up, the damage control, the trust erosion between functions is not. Over twelve months, the quiet cost of rework is often double the visible cost, and the root cause is almost always the same: information that was supposed to move did not, or moved incompletely.
Single-person knowledge bottlenecks
Every mid-market operation has one. The dispatcher who knows which crews work well together. The scheduler who knows which clients need a heads-up before invoicing. The long-tenured admin who is the only person who understands the old ERP. When that person takes a week off, the operation slows. When that person leaves, a visible portion of the business falls over. That is not institutional knowledge. That is key-person risk disguised as reliability, and every year it goes unaddressed the exposure grows.
Why the default fixes make it worse
When leaders feel the weight of coordination tax, they reach for the tools they know. All four of them treat the symptom. None of them fix the structure.
Hiring. The instinct is that the team is underwater, so more hands should help. But if coordination overhead is already scaling faster than output, every new hire creates more handoffs, more status updates, more sync meetings. A thirty-person team that hires five more people does not get thirty-five people worth of output. It gets thirty-three, and the other two are absorbed into the coordination layer. The business pays for five and receives the capacity of two or three.
New software. The second reflex. Buy the ERP, the CRM, the project management tool, the AI assistant. Within twelve months the team is running two operational layers in parallel. The official one in the new system, and the real one in the spreadsheets and email threads where the actual decisions still get made. The invoice is paid. The overhead stays.
Process documents. The third reflex. Someone runs a project to map the workflows, publishes a set of SOPs, and declares the problem solved. The documents get filed. The team keeps working the way they were working. The structure that was producing the tax in the first place never changed.
Off-sites and culture work. The fourth reflex. Bring the leaders together. Align on the vision. Clarify the values. These efforts are not wasted, but they do not move coordination tax. The tax is structural, not motivational. Energized people coordinating badly still coordinate badly.
What actually works
The coordination tax comes down when the coordination work stops being done by humans. That does not mean replacing the team. It means redesigning the operation so that information moves without a human relay, decisions have the data they need without a meeting to manufacture it, and handoffs happen inside the system rather than on top of it.
In practice that looks like a connective layer across the tools you already own. Workflows that fire on events rather than on someone remembering to check. Data that flows from the field to the back office automatically and arrives in the shape the next person actually needs. Reports that are live rather than assembled weekly from four spreadsheets. Single-person knowledge captured into the system so the business is not one resignation away from a bad quarter.
This is not a platform decision. It is an operating model decision. The companies that get this right do it in a specific order. They measure the tax first. They identify the two or three workflows costing the most. They build the automation and data flow to eliminate the manual relay on those workflows. Then they repeat. Over twelve to eighteen months the operation quietly rebuilds itself into something that scales without the overhead scaling with it.
What you lose by leaving it alone
Coordination tax compounds. Every year it goes unaddressed, the overhead layer grows a little larger, the decisions get a little slower, and the margin gap between you and the competitor who is fixing this widens. The operators who rebuild their coordination layer in the next two to three years will set the new cost baseline for their sector. The ones who do not will find themselves losing bids they used to win and wondering why their pricing no longer works.
The business will still grow. Revenue will still go up. But the owner will stay the bottleneck. Key-person risk will keep rising. The team will keep saying they need more people. And the financials will keep telling the same story: revenue growing, margin flat, and nobody in the room able to say exactly why.
What changes when you fix it
An operation that has rebuilt its coordination layer feels different from the inside. Handoffs happen without follow-up. Status is visible without a meeting to confirm it. Decisions that used to wait for information now have the information waiting for them. The team still works hard, but the work is output, not overhead. Headcount stops being the lever every time the business needs more capacity. Margin starts moving with revenue instead of chasing it.
From the owner's chair, the shift is quieter than it sounds. Fewer fires. Fewer emergency calls on a Friday afternoon. More of the week spent on the decisions that actually matter. That is what growing without growing overhead looks like, and it is not reserved for tech companies. Every mid-market operator can build toward it. Most just need someone to name what is in the way.
Two companies. Same starting point. Different decisions.
Illustrative EBITDA trajectory over three years for a $50M mid-market operation.
Year 1
Identical starting point
Both at $50M revenue, $6M EBITDA, 12% margin.
Year 2
The divergence begins
Company A: 10.5% margin. Company B: 14.0% margin. The gap is $2.01M.
Year 3
The gap compounds
Company A: 9.5% margin. Company B: 16.0% margin. The gap is $4.23M annually.
Both businesses grow revenue at the same rate. Same sector, same size, same team composition on paper. The difference is not in what they do. It is in how information moves between the people doing it. By year three, Company B is keeping an additional $4.23M of EBITDA every year on identical revenue. That gap is what the coordination layer is worth in real dollars, and it widens every year the decision is deferred.
Where to start
The first step is not a platform decision. It is a measurement decision. Before any tool, any hire, any process initiative, the question to answer is: how much is coordination actually costing us right now, and where is the biggest portion of it sitting.
That is what the LVRGWRKS Leverage Audit does in sixty minutes. Not a technology audit. An operational one. Where is data moving manually. Where are decisions slowing down because information is not available or not trusted. Where is the team spending time on coordination instead of execution. What is the actual labour cost of the friction.
Once the tax is named and quantified, every decision that follows gets clearer. The platform question, the hiring question, the automation question, all of it. The operators who move first on this get a margin advantage that is difficult to reverse. The ones who do not keep paying the tax and keep wondering where the money went.