The Coordination Tax Most Business Owners Don't See

When several providers each handle a slice of a small business's back office, somebody has to make them work together — and that somebody is almost always the owner. The hours never appear on an invoice, and rarely on the owner's own calendar, because each individual moment feels too small to count. Added together, they are frequently the largest unbilled expense in the business.

Invisible by design

Ask an owner with a fragmented back office what they do all day, and "coordinate my providers" will not make the list. They will say they are running the business, seeing clients, handling the operational things that have to happen. But sit alongside them for a week and tally just the coordination — the relay between bookkeeper and accountant, the email translating an HR question into payroll-system language, the support ticket that needed several exchanges before anyone agreed what the problem was — and the total surprises everyone in the room, the owner included.

The tax is invisible because of its shape. It arrives as brief replies, short calls and quick clarifications, each one plausibly trivial. Nothing about any single moment says "expense". The expense is the aggregate, and nobody is adding it up.

Why small interruptions carry a big price

The dollar cost of the minutes is only half the story. Each coordination moment is a context switch, and context switches are the most expensive interruptions in an owner's day: they break a thread of strategic thinking that takes far longer to re-form than the interruption itself lasted. A morning peppered with quick provider questions can leave no single block of time long enough for the pricing decision, the hiring plan or the difficult customer call — the work the owner is actually irreplaceable for. The coordination tax is paid twice: once in the minutes, and again in the quality of everything squeezed between them.

What a week of it looks like

The pattern is remarkably consistent across industries. Early in the week, the bookkeeper queries an unfamiliar card charge and the owner digs out the context. The payroll provider needs a decision about a public-holiday rate, which means first checking with the HR retainer, which means a three-way email chain that outlives the pay run it was meant to serve. Midweek, the IT firm and the accountant need each other's input on a software renewal, and neither has the other's details, so the owner brokers the introduction — again. By Friday there is a document the tax agent needs from the bookkeeper that the owner ends up forwarding personally, because that is faster than explaining who should have sent it. None of these items was a task. All of them consumed the owner.

Why it lands on the owner specifically

Each provider optimises for their own scope, so cross-boundary questions belong to nobody. The owner is the only person who holds the full context, has authority over every relationship, and cares about the joined-up answer — so the integration work flows to them by default, without anyone ever deciding it should. That default has a second cost beyond the hours: a business whose functions only connect through its owner cannot run without that owner, which is the heart of the founder dependency problem.

Measuring your own tax

You cannot manage what you have never counted, and counting it is easy. For one ordinary week, keep a note on your phone and log every provider-related touch with a rough duration: every relay, chase, translation and re-explanation. Do not filter out the small ones; the small ones are the tax. At the end of the week, total the time, multiply out to a year, and value the hours at what your attention is genuinely worth to the business. Most owners who do this once never see their provider structure the same way again.

Shrinking it

• Collapse the densest joins. Wherever two providers exchange information constantly, ask whether those functions should sit with one provider, or at least in one shared system.
• Give cross-boundary questions an owner who isn't you. Someone, internal or external, should be explicitly accountable for the whole, with standing access to every provider so questions stop routing through your inbox.
• Replace relays with shared context. A large share of coordination is re-transmitting information one party already wrote down. Shared systems and standing information flows, of the kind a connected back office is built around, remove the relay rather than speeding it up.

The goal is not to eliminate every provider conversation. It is to stop being the switchboard, because the switchboard role is the one job in the business that pays the owner nothing and costs the business the most.