Buying situation
Growth that spends itself on coordination.
A complexity tax is when administrative cost, coordination, management layers, and software complexity rise as fast as — or faster than — revenue. You are busier. You are not necessarily more profitable.
Recognition
Signs the operating model is taxing growth.
The tax rarely appears as one line item. It appears as a business that grew and got harder.
Revenue is up, but contribution margin or cash after ops costs is flat or worse.
Every new hire seems to need a coordinator, a tool seat, and a meeting.
The same information lives in three systems and still requires a spreadsheet glue layer.
Managers spend more time reconciling status than improving the work.
Software spend and “process improvements” keep stacking without anything being retired.
Stakes
Margin compression is the quiet outcome.
When every dollar of growth needs another seat, another app, and another meeting, you are financing inefficiency.
Operating leverage is the opposite of a complexity tax: additional revenue should produce proportionally more contribution and more control. If it produces proportionally more coordination instead, the model is working against you at exactly the moment you are trying to scale it.
Tool sprawl usually follows unresolved handoffs. Buying the next platform without retiring steps embeds the tax in contract form — monthly, automatic, and hard to see on a busy dashboard.
What to measure
Put the tax next to the revenue line.
The tax is only arguable when it sits beside output. Measure per unit — per job, per order, per closed case — not in totals.
Admin and coordination hours per unit of output
Hours spent chasing, re-entering, reconciling, and reporting per job, order, or closed unit — not total payroll alone.
Systems and handoffs on the critical path
Count tools and person-to-person handoffs from demand to cash. Growth that multiplies handoffs multiplies tax.
Duplicate entry and reconciliation loops
Where the same fact is typed or checked more than once. Each loop is complexity you pay for every week.
Management layers added for visibility
Roles created mainly to “keep track” because the work is not observable. That is a design cost, not destiny.
What not to buy yet
Do not add a layer to fix a layer.
Every fix that adds a step, a seat, or a subscription raises the tax it was bought to lower.
Add a dashboard, PM tool, or automation on top of unresolved ownership.
A layer added to see a layer is more tax, billed monthly. Settle who owns the handoff before you buy visibility into it.
Renew the stack or green-light the integration project.
Map one economically important workflow end to end and mark every re-entry, approval, and status chase. Decide what to remove or combine before you decide what to automate.
Create a role to keep track.
Make the work observable where it happens. A coordinator hired because nobody can see the board is a permanent cost covering a temporary design gap.
Map one economically important workflow and mark the re-entry, approvals, and status chase driving the tax. Open the Operational Leverage Map.
References
Outside sources, not Mission results
- BLS Occupational Employment and Wage Statistics — fully loaded hourly cost for the admin and coordination hours you are counting.
Find where the tax concentrates.
Thirty minutes on the workflow that costs the most to coordinate, and you leave knowing what to retire first.