Enterprise Services · A budget item nobody has named
What is capacity costing your operation?
It's already in your P&L, spread across attrition, rework, and meetings-about-meetings. This calculator finds what it's actually costing you — the floor created when complex work is routed into states that can't carry it.
Start with the Work Demand Diagnostic →
Based on the Zones Framework™ by Emergent Skills · Built for the COO, CFO, Chief of Staff, and Ops directors.
Every operating budget already absorbs the cost of capacity drift. It's spread across people quitting and getting replaced, work getting redone, decisions that have to be unmade, and meetings-about-meetings that compensate for thinking that didn't happen the first time.
And that is only the visible half of the ledger.
The other half never arrives at all: the connection between two ideas nobody had the margin to make, the innovation that never shipped, the value a narrowed team stopped creating. Together they could be the largest unmanaged variable on most operating P&Ls — and the most expensive piece never even reaches the P&L. Nobody has owned it because nobody has named it.
This calculator does the math your operating dashboards don't.
The routing logic behind the calculator
Zones tell you what kind of work the system should route next.
The Zones Framework is not a personality model and not a wellness label. It is a routing system for work, decisions, conversations, and recovery. Most execution drag comes from routing the wrong work to the wrong state.
🟢 Green
Route strategy, creative work, complex decisions, and high-stakes communication here.
🟡 Yellow
Route defined execution, familiar work, fewer decisions, and load reduction.
🔴 Red
Route only what cannot wait. Hold strategy, nuance, and performance conversations.
⚫ Can't-Even
Route recovery only. Reduce the work to the smallest possible demand.
How this connects to cost: bad work-demand design routes too much complex work into Yellow, Red, and Can't-Even. That mismatch creates the Five Capacity Taxes. The calculator prices the floor of that loss.
Sound familiar? What this looks like before you have a name for it See all nine scenes →
Most leadership teams have already lived through several of these. Nobody filed them under "capacity." They got filed under whoever was in the room.
These look like performance problems, culture problems, hiring problems, or prioritization problems. Sometimes they are. But often, the work was routed as if everyone were in Green when the team was actually operating in Yellow or Red. That routing mistake rarely gets measured, which is why the same scenes keep replaying.
How the taxes and the zones fit. The Five Capacity Taxes are what bad routing costs; the Zones are how managers decide what should happen next. Route complex work to Green. Simplify and reduce decision load in Yellow. Stop adding demand in Red. Route recovery only in Can't-Even. The estimate below prices the floor created when work keeps getting routed as if everyone is in Green.
Which of the Five Capacity Taxes this estimate prices
The calculator prices a deliberately conservative floor: the output lost when capable people are present but work is being routed into states that cannot carry it well. Here is how each of the five taxes maps to that number — and which two it leaves for the Audit.
These three are not separate dollar lines. They are the patterns that create bad routing: too much coordination, too many decisions, and too much bottlenecked work landing in Yellow and Red. The calculator prices that degradation as the floor. The floor also adds two AI-era costs that sit outside the original five: workslop downstream cost and AI oversight amplification.
Left out on purpose. Excluding the two biggest, most data-hungry taxes is what makes the number below a floor you can defend, not a projection you have to argue for.
The estimate
Quantify the cost of bad work routing
Defaults model a high-demand professional team under normal operating strain. Adjust the inputs to estimate what it costs when complex work is routed into Yellow, Red, and Can't-Even instead of Green.
Cognitive workforce & fully loaded cost
Count only the cognitive workforce — people whose output is judgment, analysis, or decision-making. Not total headcount.
Base + benefits + taxes + overhead. Use the figure your CFO uses, typically base × 1.30–1.40.
Typical range: 46–48 after holidays and average PTO.
For salaried cognitive workers, 45–50 is closer to actual hours than the contracted 40.
Zone distribution (avg per person/day)
Estimate how much of the day your cognitive workforce spends in each routing state. Green is calculated automatically. This is not a diagnosis; it is a directional estimate.
Without a reset mechanism, Yellow and Red episodes often shape the rest of the day. The Capacity Audit calibrates these assumptions to your actual operating data.
Still functioning, but margin is gone. Route defined execution, familiar work, fewer decisions, and load reduction.
Overloaded. Route only what cannot wait. Hold strategy, nuance, and performance conversations.
Complex work is offline. Route recovery only and reduce to the smallest possible demand.
🟢 Green hours/day (avg)
Green is the residual: working-day hours minus Yellow, Red, and Can't-Even. Route strategy, hard decisions, creative work, and high-stakes communication here.
Output loss by routing state
15–25% typical. Quality drift in routine cognitive work.
25–45%. Higher in trading, clinical decisions, senior judgment, M&A, legal — anywhere one wrong call is expensive.
50–75%. Complex thinking has stopped.
AI-augmented demand overlay
AI doesn't just augment work — it changes the demand profile. Validation load on the producer and workslop downstream cost on receivers are not in the original Five Taxes. Both are now research-anchored.
BCG Henderson (HBR, Mar 2026, N=1,488) found productivity peaks at 3 concurrent tools and declines above 4. Above the cliff, oversight load amplifies Yellow and Red losses.
At BCG's productivity peak. No oversight penalty applied.
Stanford / BetterUp (HBR, Sep 2025, N=1,150) anchor: 41% of workers receive AI-generated work that needs decoding; ~$186/month per affected worker; ~$915/year averaged across full workforce. Default $600 is conservative — adjust upward for high-AI-adoption organizations.
Capacity Audit investment
The Work Demand Diagnostic is the lowest-commitment front door. The Audit is the deeper diagnostic: we pull your operating data, calculate what bad work routing is actually costing you, identify which of the Five Capacity Taxes is hitting hardest, and hand you a business case you can take to the board. 4–6 weeks. Findings, not a pitch.
Scales by scope: $15K for a team of 5, up to $65K for a team of 100, with custom pricing for multi-business-unit engagements. Final scope and investment confirmed on the intake call.
Note: Pilot and License engagements use different economics. See those pages for the corresponding investment models.
Operational capacity cost
What it does not yet include. Three of the Five Capacity Taxes shape this loss without being separate line items here: Meeting Tax, Decision Density, and Manager Load are the patterns that create the routing mismatch — the lenses that explain the number rather than add to it. Two further costs sit outside this floor and are quantified in the Capacity Audit from data this calculator does not collect: Recovery Debt (the replacement cost of regretted attrition, from your turnover data) and Forfeited Upside (the value left on the table, co-authored from your pipeline, usually the largest tax in innovation-dependent businesses). The floor is conservative on purpose. The audit produces the full figure.
Research basis — the studies behind this model
Three-year compounding (realistic scenario)
Capacity recovery is structural, not episodic. The benefit holds as long as the underlying changes hold. Year 2+ includes modest compounding from fewer people quitting and the system staying in place.
This cost is already in your P&L. It's just not on a dashboard.
It hides in line items your dashboards already track but don't connect. Attrition. Rework. Meeting overhead. Decisions made under load that have to be redone. AI-generated work that took an hour to decode. None of it currently attributes back to capacity, which is why it compounds unchecked.
This is operational risk infrastructure, not employee benefits. It belongs to the COO, the CFO, and the Chief of Staff. The Zones Framework supplies the routing logic inside Yellow and Red: reduce decision load, hold high-risk conversations, route only what can safely be carried, and reset before the next demand compounds the state. Recovery does not mean running people at 100% — a fully loaded team is how these costs got created. It means more of the existing day routed into Green work, where the best thinking happens. Same lineage as Lean, Agile, and OKRs: an operating discipline that gets piloted, then adopted.
The one number behind the floor
In plain terms: about 8.6¢ on every payroll dollar
The calculator doesn't invent a cost. It estimates how much of each paid day your people spend working in states that can't carry the work well — Yellow, Red, and Can't-Even — and prices that lost time at what you already pay for it.
Add those slices up and, at the default settings, it comes to about 8.6% of the working day. So for every dollar of fully loaded payroll, roughly 8.6 cents is the capacity-drift floor — before workslop is added on top.
0.78 ÷ 9-hr day = 8.6% of the working day
$135,000 loaded comp × 8.6% ≈ $11,600 + $600 workslop ≈ $12,225 / person
To apply it fast: multiply your fully loaded payroll by about 8.6% for a back-of-the-envelope floor — call it under a dime on the dollar.
Reclaim operating capacity. Reduce cognitive variance.
The calculator estimates the cost. The Work Demand Diagnostic tests whether the number is attached to a real operating pattern. The Audit prices it, the Pilot proves the delta, and the License keeps the routing discipline in place.
Start with the Work Demand Diagnostic →
Founder-led engagements. Audit: from 5 cognitive workers. Pilot: up to 25 per team. License: minimum 200 cognitive workers.