A tool for the next conversation
What is coordination costing your team?
Estimate the paid capacity your team allocates to meetings, status updates, and chasing context. Change the assumptions and take a transparent summary with you.
The starting values are a sample, not a benchmark. Replace them with your team's estimates. No email is needed to calculate or copy your summary.
Sample estimate
Annual coordination capacity
$325K
of modeled pay allocated to keeping work in sync
20 people × 6.5 hours/week × 48 weeks
16.25% of modeled payroll
- Team hours / week
- 130
- Capacity value / month
- $27.1K
- 40-hour workweeks / year
- 156
- Full-time equivalents
- 3.25
Coordination includes useful work. This is a capacity allocation, not all waste, cash savings, or a product ROI estimate. Displayed results are rounded.
Your inputs stay in this page. Copying is optional.
How the estimate works
Add the time
Hours per person per week = meeting hours + reporting hours + chasing hours.
Use a typical week and three non-overlapping categories. Their total must fit within the modeled 40-hour week.
Value the allocated capacity
Hourly loaded pay = annual loaded pay ÷ (48 weeks × 40 hours). Annual coordination hours = people × weekly coordination hours per person × 48. Annual capacity allocation = annual coordination hours × hourly loaded pay.
The model uses 1,920 working hours per person each year. Monthly allocation is the annual figure divided by 12. Forty-hour workweeks and full-time equivalents describe time, not roles to remove.
Explore a change, if you want
Scenario hours = annual coordination hours × your assumed reduction percentage. Scenario capacity value = annual capacity allocation × that same percentage.
The optional scenario starts off. Choose your own assumption after identifying a specific change, then compare it with observed time. No reduction is predicted by this calculator.
What this number can and cannot tell you
Coordination includes useful work. This estimate allocates paid capacity; it does not show that all of that time is waste or that changing it creates cash savings.
The calculation assumes one average pay rate, a representative week, 48 working weeks per year, and a 40-hour week. It excludes the value of delayed decisions, context switching, implementation effort, and software costs.
A recovery scenario is a user-selected hypothesis. It is not a Zeke performance claim, a product ROI estimate, or a staffing recommendation. Confirm any change with your own before-and-after observations.
Questions about the estimate
What should I put in each time category?
Start with a recent typical week. Separate attending meetings, preparing or reporting updates, and chasing answers or rebuilding context. Average the hours over the entire group entered. Count any hour in only one category, even when a task involves several kinds of coordination.
Is the result money we could save?
It is the share of modeled pay allocated to these activities. Recovered time could support other work, but payroll may stay the same. Useful coordination should remain. The calculator does not estimate cash savings or product ROI.
Why does the calculator stop at 40 hours?
The pay conversion assumes a 40-hour working week. More than 40 hours of coordination per person would allocate more than the modeled payroll. Check for overlapping categories or an unrepresentative week; this model does not cover overtime schedules.
Do I have to share my inputs?
No. Calculation happens in this page, with no email gate. Inputs and results are not saved to the URL, browser storage, or a backend. Copy summary writes them to your clipboard only when you choose it. Reset restores the sample and clears your scenario and workflow selection.