Coordination Cost: The Hidden Tax on Growing Services Firms

You grew from 35 people to 62 people in 18 months. Revenue went up 70%. Profit margin went down 4 points. The spreadsheet says you should be making more money. The workflows say otherwise.

This is the growth paradox that hits services firms hardest between roughly 30 and 100 people. More people should mean more capacity. More capacity should mean more revenue at the same margin. But every person added to the org chart also adds coordination cost — the time everyone spends making sure other people know what they need to know, when they need to know it.

Coordination cost is the second of three components in the Cost-Per-Workflow framework: direct labor cost, coordination cost, and failure cost. Most firms measure only the first. The second one is what’s eating your growth.

What coordination cost actually is

Coordination cost is the operational time spent on handoffs, status updates, meetings, context re-creation, and re-explaining work between people. It produces no deliverable. It generates no revenue. It exists solely to keep work moving between humans who each hold partial context about the same project.

In a 10-person firm, coordination cost is low because everyone sits in one room and knows what everyone else is doing. In a 60-person firm, coordination cost is substantial because the work has been divided into specialized roles, and each role transition requires explicit communication that used to happen implicitly.

The Cost-Per-Workflow framework breaks every workflow into three cost layers:

That middle row — 30-50% of total workflow cost — is what most operators cannot see because they only measure the first row. The third row shows up eventually in write-offs and client disputes. The second row never shows up at all unless you go looking for it.

Why coordination cost grows faster than headcount

When you add person number 36 to a 35-person firm, you don’t add one unit of coordination. You add coordination between that person and every team they interact with. The growth pattern is closer to quadratic than linear.

A concrete example: a 40-person IT consultancy added 15 people over 12 months to handle a growing project pipeline. Revenue grew 38%. The firm’s internal meeting load grew 74%. The average project manager’s non-billable hours went from 12 hours per week to 19 hours per week. Those 7 additional hours per PM per week, across 8 PMs, totaled 2,912 hours per year of added coordination cost — roughly $437,000 at the firm’s loaded rate of $150/hour.

The firm hired 15 people to increase capacity. The coordination cost of integrating those 15 people consumed approximately 40% of the capacity they added.

This is the pattern Cendia finds consistently: firms between 30 and 100 people where headcount grows 30-40% but effective capacity grows only 15-20%. The gap is coordination cost.

The five places coordination cost hides

Coordination cost doesn’t appear on any standard financial report. It lives inside these five operational patterns:

1. Meetings that exist to share context. Weekly status meetings where 8 people sit in a room so that 2 of them can exchange information. The other 6 are there because nobody knows which 2 need the information on any given week. In a 60-person firm, Cendia’s typical finding: 25-40% of recurring meetings can be replaced by a documented status artifact that takes 5 minutes to write and 2 minutes to read.

2. Re-explaining project context at handoffs. Every time a project moves between teams — sales to ops, ops to delivery, delivery to QA — someone spends 30-90 minutes re-creating context that already existed in someone else’s head. Across 14-22 handoffs per project (the range Cendia finds in most services firms), that’s 7-33 hours of context re-creation per project. The Handoff Cost Model quantifies this precisely, but even a rough estimate reveals the scale.

3. Status checks and chase-downs. A project manager emails a developer to ask when the deliverable will be ready. The developer checks with the designer. The designer checks with the client. Three people spend 20 minutes collectively on a question that a documented workflow with clear ownership would answer in zero minutes. Multiply by 10-15 similar chase-downs per week per PM.

4. Approval queues. Work sits in someone’s inbox waiting for sign-off. The sign-off takes 5 minutes. The waiting takes 2-3 days. The downstream team adjusts their schedule around the delay. One 5-minute approval, when it lacks a defined SLA, creates 2-4 hours of downstream schedule disruption.

5. Onboarding new team members. Each new hire consumes 40-80 hours of existing team members’ time in their first 90 days — not in formal training, but in answering questions, re-explaining processes, and correcting errors that happen because the process lives in people’s heads rather than in documents. At 10 new hires per year in a growing firm, that’s 400-800 hours of coordination cost for onboarding alone.

How to measure your own coordination cost

You can estimate coordination cost for a single workflow in about two hours. The Eliminate-Before-Automate framework is useful for the measurement step because it forces you to evaluate each activity before trying to fix it.

Step 1: Pick your most common project type. The one you deliver most often, not the largest or most complex.

Step 2: List every activity in the workflow. Include handoffs, meetings, emails, approvals, and waiting periods — not just the deliverable work. Most teams list 15-25 activities when they’re honest about including the coordination steps.

Step 3: Categorize each activity. Label each one as Direct Labor (produces the deliverable), Coordination (keeps work moving between people), or Failure Recovery (fixes something that went wrong). If you’re unsure, ask: “If one person did this entire project alone, would this activity still exist?” If the answer is no, it’s coordination.

Step 4: Estimate hours. For each coordination activity, estimate the time per instance and the frequency per project. Multiply. Sum across all coordination activities.

Step 5: Calculate the ratio. Divide total coordination hours by total workflow hours (all three categories). If coordination is above 35% of total workflow cost, you have a measurement problem that’s worth solving. If it’s above 45%, you have a structural problem that’s actively limiting your growth.

Most firms that run this exercise for the first time find their coordination cost ratio is 35-50%. The reaction is usually disbelief, followed by recognition — the numbers explain why growth hasn’t translated to proportional profit.

What actually reduces coordination cost

Three categories of intervention work. Listed in order of typical impact.

Documented decision rules at handoffs. When a project moves between teams, the receiving team shouldn’t need a meeting to understand what to do next. A documented trigger (“when the contract is signed and the deposit clears, the onboarding checklist auto-generates and assigns to the designated PM”) eliminates the handoff meeting entirely. Cendia’s finding: documenting decision rules at the top 5 handoff points in a workflow typically reduces coordination cost by 15-25% within 60 days.

Asynchronous status artifacts. Replace recurring status meetings with a written artifact — a shared document, a dashboard row, a Slack post with a defined format — that takes 5 minutes to produce and 2 minutes to consume. The meeting becomes a 15-minute exception-only discussion for the 10% of weeks where something requires live conversation. Typical time savings: 3-6 hours per team per week.

Defined ownership with SLAs. Every workflow step has an owner and a response time. When the designer finishes the mockup, the developer has 24 hours to begin implementation. No chase-down needed because the SLA is documented and visible. When the SLA breaks, the escalation path is documented too. This eliminates the 20-minute-per-chase-down pattern at scale.

Every person you add increases coordination cost. The firms that grow profitably are the ones that reduce coordination cost per person faster than they add people.

What this isn’t

A few honest scope notes:

• This isn’t an argument against meetings. Some meetings produce real decisions. The problem is meetings that exist to share information that a written artifact handles better. Cut the information-sharing meetings. Keep the decision-making ones.
• This isn’t about individual productivity. Coordination cost is structural, not personal. Telling your PMs to “be more efficient with their time” when the workflow requires 19 hours of non-billable coordination per week is blaming the person for the structure.
• This isn’t a small-firm problem. Firms under 20 people rarely have significant coordination cost because the implicit coordination of proximity handles it. The problem emerges between 30 and 60 people and compounds through 100.

Where to start this week

Two actions, both completable before Friday:

1. Audit one project manager’s calendar for last week. Count the hours spent in meetings, on status updates, and on chase-downs. Separate those hours from billable project work. The ratio is your first coordination cost data point.

2. Pick your most common recurring meeting. Ask: what information does this meeting share? Could that information be a written artifact instead? If yes, trial replacing the meeting with the artifact for 2 weeks and measure whether the 10% exception-only cadence holds.

If coordination cost is consuming more than 35% of your workflow time and you want a structured diagnostic — measured costs across all three Cost-Per-Workflow components, identified root causes, and a 30-day intervention plan — that’s what a Cendia engagement produces. The Three-to-One Rule applies: every recommendation must return 3x its implementation cost within 12 months, or it doesn’t make the list.

This article is part of Cendia’s Hidden Costs series. Companion pieces cover the Handoff Cost Model, the Margin Leak Map, and why your ops manager is drowning in coordination work that belongs in documented decision rules.