Every tool your team uses has a price tag. Most of it doesn't appear on any invoice.
I've spent a lot of time in the last few years helping organizations figure out why their teams feel busy but not productive.
The answer, almost always, involves counting tools.
Not because tools are bad. Tools are useful. But there's a cost to using tools — a coordination cost — that scales with the number of tools in use, and it almost never shows up in any budget line or productivity metric.
When that cost gets large enough, it becomes the most significant drag on organizational throughput. And because it's invisible, it usually grows to that point before anyone does anything about it.
What Coordination Cost Actually Is
Coordination cost is the time and cognitive overhead required to work across multiple systems, formats, and contexts.
It includes:
Context switching overhead. Every time someone moves from one tool to another, there's a cognitive reset — reorienting to the new interface, remembering where things are, loading the mental context for that tool's workspace. Research on cognitive switching puts this overhead at 10-20 minutes of reduced cognitive efficiency after each switch.
Information assembly time. When the information needed to make a decision or complete a task lives in multiple tools, someone has to gather it manually. The project status is in Monday. The relevant conversation is in Slack. The background document is in Notion. The customer record is in HubSpot. A 20-minute meeting requires 15 minutes of preparation to assemble context from four different systems.
Communication overhead about where things are. In organizations with fragmented tools, a significant portion of team communication is meta-communication: "where did you put that document," "which Slack channel is the right one for this," "did you update the task in Monday or just send the Slack message." This overhead is real, measurable, and completely unproductive.
Duplicate updates. When the same information needs to exist in multiple systems — task status in the project tool, context in the document, update in the communication channel — someone has to maintain that duplication. Or nobody does, and the systems fall out of sync, which creates its own overhead.
How to Measure What You're Currently Spending
Most organizations have never measured their coordination cost. Here's how to get a rough number quickly.
Meeting preparation time. Ask your team how much time they spend gathering information before a typical meeting. Multiply by the average number of meetings per week, per person. This captures information assembly cost.
Context switch frequency. Ask team members to count how many different tools they open in a typical workday. For a 200-person company, it's common to find people working across 7-10 different applications. At 10-20 minutes of switching overhead per transition, a person switching between 8 tools experiences 80-160 minutes of reduced effectiveness per day.
Duplicate update volume. Pick a specific workflow — sales opportunity update, project status report, customer support resolution — and count how many systems need to be updated to reflect that one event. Each additional system is coordination overhead with no output value.
The aggregate number is usually striking enough to change how leadership thinks about the tool stack.
The Tool Acquisition Pattern That Creates This Problem
Organizations don't start with 10 tools. They start with 3 and accumulate the rest gradually.
Each addition is locally rational. Sales wants a better CRM, so HubSpot gets added. Engineering wants better project visibility, so Jira joins the stack. Marketing wants async video, so Loom arrives. Customer support wants a dedicated ticketing system, so Zendesk appears.
Each addition solves a real problem for the team that requested it. None of the additions is evaluated against the coordination cost it adds for everyone else.
Over three years, the 3-tool stack becomes a 12-tool stack. The per-seat licensing cost is visible and gets reviewed. The coordination cost — the 80-160 minutes per person per day of switching overhead, the meeting preparation time, the duplicate updates — is invisible.
This is why coordination cost tends to grow until it becomes the dominant operational problem. It's never on any dashboard.
The Evaluation That's Usually Missing
Before any new tool gets added to the stack, the right evaluation question is not "does this tool solve the problem it was acquired for." It's:
"Does this tool's contribution to solving this specific problem exceed the coordination cost it adds to everyone who now has to interact with one more system?"
That's a harder calculation. It requires estimating both the benefit (which is often overstated in the business case) and the cost (which is rarely calculated at all).
For tools that consolidate rather than add — a single platform that replaces three existing tools — the calculus is different. Consolidation has an upfront transition cost but a reduction in ongoing coordination cost. The tool that replaces three tools is adding less overhead than the three tools it eliminates, and the licensing comparison isn't the right one.
This is why integrated platforms tend to look underpriced on a feature-by-feature comparison and overpriced on a per-module basis. The value isn't in any individual capability — it's in the coordination cost saved by having everything in one place.
A Practical Audit
If you're not sure how much coordination cost your organization is carrying, run this audit for one week:
Ask three to five team members across different functions to log every tool they use, every context switch, and every time they spend time assembling information from multiple sources rather than doing the work itself.
Aggregate the results. Calculate the hours per week per person. Multiply by headcount and hourly cost.
That number — total weekly coordination cost — is usually a significant fraction of your total payroll. Organizations that have run this calculation with honesty have found coordination cost in the range of $500,000-2,000,000 per year for mid-market companies, most of it invisible in any financial report.
Once you've measured it, the operational case for consolidation tends to become obvious.
Top comments (0)