Your Most Expensive Employee Doesn’t Exist on Payroll
There’s a line item hiding in every company’s P&L. It doesn’t show up as salary. It doesn’t appear in your SaaS spend. But it costs more than both combined.
It’s the coordination tax — the time and money your team spends routing information between tools, chasing updates, maintaining context across systems, and doing the administrative glue work that holds your operations together.
McKinsey found that the average employee spends 1.8 hours per day searching for information and coordinating work between tools. That’s 22.5% of their working day. For a 15-person company paying an average loaded salary of $80,000, that’s:
15 employees × 1.8 hours × 250 days × $38.46/hr = $259,615 per year
A quarter of a million dollars. Not on tools. Not on output. On coordination.
What Coordination Tax Actually Looks Like
Coordination tax isn’t one big expense. It’s thousands of small ones that are invisible until you add them up.
The Morning Email Triage
Your operations lead spends 45 minutes every morning scanning email, Slack, and Asana to figure out what needs attention. They’re not doing work — they’re building context. They’re reading the same information in three different places, cross-referencing updates, and mentally assembling the picture of “where things stand.”
This is coordination.
The Status Update Loop
A client asks: “Where’s the proposal?” Your PM checks Asana (it says “in progress”), Slacks the account manager (they’re in a meeting), scans email for the latest draft, finds it attached to a thread from Tuesday, realizes it was sent to the wrong client name, and spends 20 minutes untangling the situation.
The answer took 25 minutes. The actual information transfer took 5 seconds.
The Knowledge Walkout
Your senior account manager leaves. With them goes every client preference, every relationship nuance, every “oh, they hate morning meetings” detail that lived only in their head. The replacement spends 3-6 months rebuilding that context — and some of it is lost permanently.
This isn’t a personnel problem. It’s an architecture problem. The knowledge was never stored. It was cached in human memory.
The Dashboard Graveyard
Your company pays for 22 SaaS tools. Each has its own dashboard. The 2025 Luzmo survey found that 72% of dashboard users abandon them within six months — not because the data is bad, but because checking 15 dashboards is work in itself.
So your team builds workarounds: spreadsheet summaries, Slack channels that duplicate tool notifications, Monday morning “alignment meetings” that exist solely to sync information between systems.
All coordination. All tax.
Why Coordination Tax Compounds
The dangerous thing about coordination tax isn’t its size. It’s that it scales linearly with complexity.
More People = More Coordination
Every new hire adds coordination load. They need context. They produce updates that others need to consume. They use tools that generate data that needs to be routed somewhere.
A 10-person team has 45 possible communication pairs. A 20-person team has 190. A 50-person team has 1,225. The coordination overhead doesn’t just grow — it compounds geometrically.
More Tools = More Bridges
The average company uses 106 SaaS applications (Productiv 2025). Each tool is an island. Between every pair of islands, someone has to build and maintain a bridge — whether that’s a Zapier workflow, a manual copy-paste, or a human who checks one tool and updates another.
Those bridges are fragile. When they break (and they do), people become the fallback. The coordination tax spikes.
More Clients = More Context
Agencies and service businesses feel this acutely. Client #1 is easy. Client #15 is manageable. Client #30 is when things start breaking — not because the work is harder, but because the context overhead becomes unmanageable.
“Wait, does Acme prefer the blue template or the green one?” “Did we already send Johnson Corp their invoice?” “Who’s the primary contact at that new account?”
Every client multiplies the context load. Without a system to store and retrieve that context, your team becomes the database.
The Five Forms of Coordination Tax
To eliminate it, you need to name it. Coordination tax shows up in five specific forms:
1. Information Routing ($$$)
Moving data from where it’s generated to where it’s needed. Copying a client request from email into your project tool. Forwarding a Slack message to someone who “needs to see this.” Updating a CRM after a meeting.
Cost: 30-45 minutes per person per day.
2. Context Assembly ($$)
Building the full picture by pulling information from multiple sources. Preparing for a client call by checking email, CRM, project tool, and Slack history. Figuring out what happened while you were on PTO.
Cost: 20-30 minutes per person per day.
3. Status Synchronization ($$)
Keeping everyone aligned on where things stand. Stand-up meetings. Status update emails. The “just checking in” Slack messages.
Cost: 15-30 minutes per person per day.
4. Knowledge Recovery ($$$)
Recreating context that was lost — because someone left, because it was never documented, because it lived in a tool nobody checks anymore.
Cost: Sporadic but severe. 3-6 months of reduced capacity per key departure.
5. Tool Bridging ($)
Maintaining the connections between tools. Fixing broken Zapier workflows. Updating API integrations. Rebuilding spreadsheet formulas when someone changes the source data.
Cost: 10-15 minutes per person per day, plus sporadic crises.
How to Calculate Your Coordination Tax
Here’s a simple formula:
Annual Coordination Tax = (Employees × Avg Loaded Salary × 0.25)
The 0.25 multiplier is conservative — it represents the low end of the 20-40% range found across multiple studies. For most companies, the actual number is higher.
For a quick calculation:
| Team Size | Avg Salary | Estimated Annual Tax |
|---|---|---|
| 10 | $70,000 | $175,000 |
| 25 | $80,000 | $500,000 |
| 50 | $85,000 | $1,062,500 |
| 100 | $90,000 | $2,250,000 |
These numbers feel high because they are. But track your team’s day for one week and count the minutes spent on routing, syncing, searching, and context-switching. The math holds.
Or use our Coordination Tax Calculator for a more detailed breakdown based on your specific team size, salary, and tool complexity.
Why Automation Doesn’t Fix It
The instinct is to “automate” the coordination away. Set up Zapier rules. Build Slack bots. Create auto-forwarding filters.
This helps at the margins. But it misses the core problem: coordination requires context, and most automation tools are stateless.
A Zapier workflow can move data from tool A to tool B. It can’t decide whether to move it based on what happened in yesterday’s client call. It can’t remember that Client X changed their preferences last week. It can’t understand that the “urgent” flag from your EA means something different than the “urgent” flag from your intern.
Stateless automation handles the 20% of coordination that follows predictable rules. The other 80% requires memory, reasoning, and judgment — the exact things that make coordination expensive in the first place.
What Actually Eliminates Coordination Tax
The coordination tax exists because of an architecture problem: information is fragmented across tools, and humans are the integration layer.
The solution is an orchestration layer — a system that:
-
Connects to your existing tools rather than replacing them. Your CRM, email, project management, and chat stay where they are. The orchestration layer bridges them.
-
Builds persistent memory. Not just moving data, but understanding relationships. “John at Acme prefers Tuesday calls” is remembered once and applied everywhere — across email scheduling, project timelines, and meeting prep.
-
Routes information intelligently. Instead of broadcasting everything to everyone, the orchestration layer delivers the right context to the right person at the right moment. Your morning brief contains exactly what you need — assembled automatically.
-
Executes coordination work autonomously. Triaging email. Updating project statuses. Preparing meeting agendas with relevant context. Sending follow-ups. The glue work that consumed 20-40% of your team’s day is handled by the system.
-
Operates through your existing communication layer. No new dashboard to check. The orchestration happens inside Slack, where your team already works.
The ROI Math
If an orchestration platform eliminates 60-80% of coordination tax (a conservative estimate — the remaining 20-40% involves truly novel situations requiring human judgment), the math looks like this:
25-person company:
- Annual coordination tax: ~$500,000
- 70% reduction: $350,000 saved
- Orchestration platform cost: $36,000/year
- Net annual savings: $314,000
- ROI: 872%
And that’s just the direct labor savings. It doesn’t count:
- Faster lead response (24/7 vs business hours)
- Reduced knowledge loss from turnover
- Fewer dropped balls and missed follow-ups
- Time redirected from coordination to revenue-generating work
Start With One Workflow
You don’t need to orchestrate everything at once. Start with the highest-friction workflow — the one your team complains about most.
Common starting points:
- Lead processing: Inbound lead → enrichment → routing → follow-up, all handled autonomously
- Email triage: AI reads, classifies, drafts responses for approval, and routes action items
- Daily operations digest: Automated morning brief pulling from all tools, personalized per role
- Client onboarding: Checklist execution across tools with status tracking and stakeholder updates
Deploy one workflow. Measure the time saved. Then expand.
Calculate your coordination tax to see the specific numbers for your team. Or book a 30-minute demo to see how Alacritous eliminates coordination work for teams like yours.