What a Week of Meetings Actually Costs Your Team
Most teams track their sprint velocity, their budget burn rate, their customer acquisition costs. Very few track the weekly salary cost of their meeting calendar. That number is almost always larger than people expect, and it's fully calculable from public information.
The Meeting Cost Calculator shows the cost of any individual meeting in real time. This article looks at the full weekly picture — what a typical week of meetings costs per person and for the team — and where that cost is actually worth paying.
What Counts as a Meeting Cost
The basic formula is simple:
meeting cost = attendees × average hourly rate × duration in hours
The hourly rate is usually estimated from annual salary. A $100,000/year employee works roughly 2,000 hours per year, so their time costs about $50 per hour. At $80,000 it's $40/hour. At $120,000 it's $60/hour.
This calculation uses salary cost only — it doesn't include employer payroll taxes, benefits, office overhead, or equipment. In practice, the fully loaded cost of an employee is typically 1.25–1.5x their salary. If you want a more complete picture, multiplying the salary-based estimate by 1.3 is a reasonable approximation.
A Typical Engineering Team's Week
Take a 10-person engineering team where developers average $130,000/year (~$65/hour) and the engineering manager earns $160,000/year (~$80/hour). Here's what a standard week looks like:
Daily standup — 15 minutes, 10 people, 5 days a week
- Per standup: 10 × $65 × 0.25 = $162.50
- Weekly total: $162.50 × 5 = $812.50
Sprint planning — 2 hours, 10 people, bi-weekly (half-week cost)
- Per session: 10 × $65 × 2 = $1,300
- Weekly cost (amortized): $650
Sprint retrospective — 1 hour, 10 people, bi-weekly
- Per session: 10 × $65 × 1 = $650
- Weekly cost (amortized): $325
1:1s — manager with each of 9 reports, 30 minutes each
- Per 1:1: (1 × $80 + 1 × $65) × 0.5 = $72.50
- 9 reports × weekly: $652.50
Cross-team sync — 1 hour, 4 people from this team
- 4 × $65 × 1 = $260
Weekly total: roughly $2,700 in salary cost for this one team
Over a 50-week year, that's $135,000 in meeting cost — just for a single 10-person team. Not meetings that are obviously wasteful. The routine, scheduled meetings that everyone attends without question.
Where the Cost Compounds
The salary number above is just the starting point. Two compounding effects make the real cost higher.
Context-switching. Meetings that interrupt deep work don't just cost the time in the room. A 30-minute standup in the middle of a 3-hour coding session doesn't consume 30 minutes — it consumes the 30 minutes plus the 15–20 minutes it takes to get back into the previous train of thought. Research consistently puts the re-focus time after an interruption at 15–23 minutes. For knowledge workers, a badly placed meeting can effectively destroy two 90-minute focus blocks in a single morning.
Preparation and follow-up. A 1-hour meeting with 10 attendees often involves 15–30 minutes of preparation per person — reviewing prior notes, checking related documents, preparing inputs. Follow-up adds more: writing action items, updating tickets, sending summaries. A 1-hour meeting is rarely just 1 hour of total work.
If you apply a 2× multiplier to account for these effects, the effective weekly meeting cost for that 10-person team is closer to $5,000–5,500 in true productivity cost.
Where Meeting Cost Is Proportionally Higher
Not all teams have the same cost profile. Meeting cost as a proportion of total work time is higher in certain roles and contexts.
Senior and principal engineers. Engineers at this level often earn $180,000–$250,000 or more. An hour of their time costs $90–$125 in salary alone. When these engineers spend 15–20 hours per week in meetings — which is common in companies that don't protect focus time — the cost is substantial and often invisible.
Management layers. A director or VP who manages multiple teams often attends every team's major meetings plus executive-level syncs. A 60-hour meeting week at $120/hour in fully loaded cost is $7,200 per week, per person, just in meeting time.
Cross-functional product meetings. Product reviews, design reviews, and planning meetings often pull in engineers, designers, product managers, and QA — each with different hourly rates but similar time cost. A 2-hour product review with 15 attendees from multiple disciplines can easily cost $2,000–3,000 in salary before anyone has done anything with the decisions made in the room.
How to Audit Your Team's Weekly Meeting Cost
Pull the meeting calendar for a typical week and calculate each meeting's cost:
1. List all recurring meetings 2. Count actual attendees (not just invitees) 3. Note duration in hours 4. Apply each attendee's estimated hourly rate (salary ÷ 2,000) 5. Multiply: attendees × average rate × hours
Run this for every recurring meeting and sum the week. The Meeting Cost Calculator handles the per-meeting calculation quickly — use it for each meeting on the list.
What you're looking for is the meetings where the cost is high but the output is unclear. High cost on its own isn't the problem — a high-cost meeting that unblocks $500,000 of work is cheap. A high-cost meeting that recurs because no one has questioned it in 18 months is a problem.
Questions Worth Asking Per Meeting
For each meeting in your audit:
- What decision or output does this meeting produce?
- Could that output be achieved with an async update — a written summary, a shared doc, a Slack thread?
- Who attends that doesn't strictly need to? Would a meeting summary work for them instead?
- When did this meeting last get cancelled, and was anything missed?
- Does the meeting have an agenda that gets sent in advance?
A meeting that survives these questions honestly is probably earning its cost. One that can't answer the first question — what output does this produce? — is a candidate for cancellation or format change.
Reducing Cost Without Eliminating Collaboration
The goal isn't zero meetings. Real-time conversation produces things async communication doesn't: rapid iteration on a complex problem, visible team cohesion, difficult conversations that don't work in writing. The goal is making the cost visible so decisions about meetings are intentional rather than habitual.
A few changes that reduce cost without losing value:
Tighten durations. Most hour-long meetings can be 45 minutes. Most 30-minute meetings can be 20 minutes. Google and other large organizations have found that 25-minute and 50-minute defaults (leaving buffer between calendar blocks) reduce meeting time without reducing output quality.
Reduce attendee lists. For every person on a meeting invite, ask whether they need to be in the room or whether a summary would serve them equally well. Cutting 2 people from a 10-person meeting reduces cost by 20%.
Move status updates async. Daily standups in their traditional form — each person reports what they did yesterday and what they're doing today — are essentially oral status updates. A written async format (a Slack post or a shared doc) often captures the same information at a fraction of the time cost, particularly for distributed teams.
Set a review cadence. Recurring meetings accumulate. Put a quarterly review on your calendar to look at every recurring meeting and ask whether it still needs to exist.
The salary cost of meetings isn't abstract — it comes directly out of the productive hours available to your team each week. Making it visible is the first step to making it intentional.
