What is the cost per hour of a meeting?

To calculate meeting cost per hour, multiply the number of attendees by their average hourly rate. For engineers, use their "fully loaded" cost (salary + benefits + overhead), which is typically 1.3-1.5x base salary. A $150k engineer costs about $72/hour. Eight engineers in a meeting costs $576/hour. Add context-switching costs (typically 30-60 minutes of lost productivity before and after), and the true cost per hour can exceed $800.

What is the optimal meeting frequency for engineering teams?

Limiting recurring meetings and protecting "maker time" works for engineers. Best practices include: standups no longer than 15 minutes, sprint planning capped at 2 hours max, and ensuring at least 2-3 meeting-free half-days per week. High-performing teams typically spend less than 20% of their work week in meetings. See our Working Agreements Guide for more on setting these norms.

Should engineering teams have meeting-free days?

Yes. Meeting-free days (or half-days) significantly improve developer productivity. Cal Newport's research on "deep work" shows that context switching can cost 23 minutes of recovery time per interruption. Shopify famously removed 12,000 meetings after calculating their cost. Many successful engineering organizations implement "No Meeting Wednesdays" or similar policies to protect focused coding time.

How can I reduce meeting costs without losing alignment?

Start by auditing existing meetings: Does every recurring meeting still serve its purpose? Could it be async? Key strategies include: (1) Require agendas for all meetings, (2) Set default meeting length to 25 or 50 minutes instead of 30/60, (3) Implement "office hours" instead of individual sync meetings, (4) Use async standups via Slack or tools like Geekbot, and (5) Record and summarize important meetings for those who don't need to attend live.

All Free Tools

For Engineering Managers2 min

Meeting Cost Calculator

See the true cost of meetings for your engineering team. Calculate how much engineering time and money is spent in meetings.

Most teams know meetings cost money, but few ever put a number on a single recurring slot. A weekly sync that feels harmless on the calendar can quietly burn through tens of thousands of dollars a year once you account for everyone in the room and their fully loaded cost.

This calculator turns a meeting into a dollar figure. Enter how many engineers attend, their average salary, how long the meeting runs, and how often it repeats. You get the cost per session, the monthly and annual totals, and the engineering hours that time represents.

It is built for engineering leaders and team leads who want a concrete way to challenge a packed calendar - not to ban meetings, but to make the trade-off visible before agreeing to yet another standing invite.

Enter Meeting Details

Number of EngineersHow many people attend?

Average Engineer SalaryFully loaded cost (salary + benefits + overhead)

Tip: Fully loaded cost is typically 1.3-1.5x base salary (includes benefits, equipment, overhead).

Meeting DurationIn minutes

Meeting FrequencyHow often does this meeting occur?

Enter meeting details above to calculate the true cost.

Tip: A $150k salary with 1.3x overhead is ~$200k fully-loaded cost.

Why Meeting Costs Matter

Meetings are often the largest hidden cost in engineering organizations. A 2022 study found that the average employee spends 31 hours per month in unproductive meetings. For engineering teams with high hourly costs, this translates to massive opportunity costs.

The "Plus One" Problem

Each additional attendee adds linear cost but rarely linear value

Context Switching

A 30-min meeting can cost 2+ hours of deep work due to ramp-up time

Meeting Creep

Recurring meetings rarely get shorter or canceled when no longer needed

Maker vs Manager Time

Engineers need long blocks of uninterrupted time for complex work

Get actionable insights from your data with CodePulse

How it’s calculated

The cost is the combined salary value of everyone in the room for the time they spend there. The tool converts salary to an hourly rate, multiplies by attendees and meeting length, then scales by how often the meeting repeats.

Inputs

Number of engineers attending.
Average salary, entered as either an annual figure or an hourly rate.
Meeting duration in minutes.
Frequency: one-time, daily, weekly, bi-weekly, or monthly.

Formula

Cost per meeting = attendees x hourly rate x (duration in minutes / 60). An annual salary converts to an hourly rate by dividing by 2,080 working hours per year. Monthly and annual totals apply frequency multipliers: daily is 22 sessions a month and 260 a year, weekly is 4.33 and 52, bi-weekly is 2.17 and 26, monthly is 1 and 12.

Assumptions

Use fully loaded salary - base pay plus benefits, equipment, and overhead, usually 1.3 to 1.5x base. The dollar figure understates the true cost if you enter base salary alone.
The 2,080-hour year assumes 40 hours a week over 52 weeks with no adjustment for holidays or leave.
The hours-lost figure counts time in the room only. It does not include the context-switching tax of stopping and restarting focused work.
The opportunity-cost estimate of small features delivered uses a rough rule of roughly 8 engineering hours per small feature or PR.

Worked example

Take a weekly engineering sync with 8 attendees, an average fully loaded salary of $200,000, running 60 minutes.

Hourly rate: $200,000 / 2,080 = about $96 per hour.
Cost per meeting: 8 x $96 x 1 hour = about $769.
Annual cost: $769 x 52 weeks = roughly $40,000.
Hours lost: 8 hours per session x 52 = 416 engineering hours a year, or about 52 features at 8 hours each.

The read: one recurring hour-long sync costs this team the equivalent of a junior hire's annual budget and over 400 hours of build time. That does not make the meeting wrong, but it sets a clear bar. If the meeting cannot point to decisions worth $40,000 a year, it is a candidate to shorten, shrink the invite list, or move async.

Our Take

The real cost of meetings isn't the meeting itself - it's the context switching before and after that destroys 2+ hours of focused work.

A 30-minute meeting doesn't cost 30 minutes. Research shows it takes an average of 23 minutes to refocus after an interruption. Factor in preparation time and post-meeting follow-ups, and a single 30-minute meeting can consume 2+ hours of productive time. That's why high-performing teams protect 'maker time' blocks of 4+ uninterrupted hours.

"Engineers in 31+ hours of weekly meetings produce 50% less code than those in fewer than 10 hours."
— Atlassian State of Teams Report

Key terms

Fully Loaded Cost: An employee's total cost to the company, not just salary. It adds benefits, payroll taxes, equipment, software, and overhead, typically landing at 1.3 to 1.5 times base pay.
Cost Per Meeting: The combined salary value of every attendee for the duration of one session. It is the headline number this calculator produces.
Frequency Multiplier: The factor that turns a single meeting's cost into a monthly or annual total. A weekly meeting uses 4.33 for the month and 52 for the year.
Opportunity Cost: What the meeting time could have produced instead - here expressed as engineering hours and a rough count of small features or PRs that time could have covered.
Context Switching: The productivity lost when an engineer stops focused work for a meeting and has to ramp back up afterward. Research puts recovery at around 23 minutes per interruption, which this calculator does not add to the in-room cost.

Frequently Asked Questions

Meeting costs depend on attendee salaries, duration, and frequency. A typical 1-hour meeting with 8 engineers at $100k salary (fully loaded to ~$150k) costs approximately $577. If that meeting happens weekly, it costs $30,000 annually. The average company spends roughly 15% of its total personnel costs on meetings - for a 50-person engineering team earning $150k average, that's over $1.1 million per year in meeting time.