What's a realistic hourly rate to use for cost calculations?

Use the fully-loaded cost, not just salary. For US-based engineers, this typically means multiplying base salary by 1.25-1.4x to account for benefits, taxes, and overhead. A $150K/year engineer costs roughly $90-100/hour fully loaded.

Should I include optional attendees in the cost calculation?

Yes. If someone is on the invite and regularly attends, their time counts. Optional attendees who never attend can be excluded. The goal is to capture the actual time spent, not the theoretical minimum.

How do I get leadership to take meeting costs seriously?

Present the annual cost of your team's top 5 recurring meetings. When leaders see that a single weekly sync costs $40-50K per year, it reframes the conversation from 'just a meeting' to a significant budget item.

Meeting Cost Calculator: What Your Meetings Really Cost

Key Takeaways

✓A typical 8-person weekly meeting costs $31,200 per year in direct time alone
✓Context switching adds 50-100% to the true productivity cost of meetings
✓The opportunity cost of your best engineers in meetings extends far beyond their individual output
✓Most teams can eliminate 20-30% of recurring meetings without losing alignment

Take your team's average hourly cost. Multiply it by the number of people in your weekly status meeting. Multiply that by 52 weeks. That's the annual cost of a single recurring meeting.

For a typical 8-person engineering team meeting lasting one hour each week, at an average fully-loaded cost of $75/hour per engineer, that's $31,200 per year. For one meeting.

Now multiply that by every recurring meeting on your team's calendar.

The result is usually somewhere between horrifying and life-altering. (You can run your own numbers with our free meeting cost calculator tool — no signup required.)

The math behind meeting costs

Meeting costs go far beyond just salary. Here's how to calculate the real number:

Direct cost: time × people × rate

The basic formula is straightforward:

Meeting cost = Duration (hours) × Number of attendees × Average hourly rate

But "average hourly rate" needs to be the fully-loaded cost, not just base salary. For a software engineer in the US earning $150,000/year base, the fully-loaded cost (including benefits, taxes, equipment, office space) is typically 1.25x to 1.4x the salary. That works out to roughly $90-100/hour.

For a 30-minute standup with 6 engineers: 0.5 × 6 × $95 = $285 per standup. Five times a week, that's $1,425/week or $74,100/year.

Suddenly, "it's just a 30-minute meeting" looks different.

Indirect cost: context switching

The direct cost is just the beginning. Research by Gloria Mark at UC Irvine shows that it takes an average of 23 minutes and 15 seconds to regain deep focus after any interruption. A 30-minute meeting doesn't cost 30 minutes of productive time — it costs closer to 60 minutes when you include the ramp-up on both sides.

The true productivity cost of meetings is roughly 1.5x to 2x the actual meeting duration. We cover this in more detail in our article on meeting fatigue.

Opportunity cost: what wasn't built

This is the hardest cost to measure but often the largest. Every hour spent in a meeting is an hour not spent writing code, reviewing PRs, designing architecture, or solving customer problems.

When your best senior engineer — the one who unblocks the whole team — spends 15 hours per week in meetings, the opportunity cost extends far beyond their individual output. The entire team moves slower.

What the data says

The industry numbers paint a clear picture:

According to Harvard Business Review research, executives now spend an average of 23 hours per week in meetings — up from less than 10 hours in the 1960s. And 83% of managers in one survey reported that the meetings on their calendars were unproductive.

Across the US economy, unnecessary meetings cost businesses $37 billion per year in salary costs alone. That doesn't include the knock-on effects of lost productivity and delayed projects.

— Atlassian Research

The problem is getting worse. Meeting time has been increasing steadily for decades, and the shift to remote work accelerated this trend. Microsoft's data shows a 13.5% increase in the number of meetings workers attend, even as average meeting length decreased by 20% — more meetings, shorter but more frequent.

Real examples: what meetings actually cost

Let's look at three common engineering team meetings and their true annual cost.

The weekly "sync" that nobody needs

Setup: 10 people, 1 hour, weekly. Average rate $85/hour.

Direct cost: 10 × 1 × $85 × 52 = $44,200/year
Context switching cost (add 50%): $22,100
Total: ~$66,300/year

If this meeting could be replaced with a 5-minute async Slack update from each person, the team saves the equivalent of a junior engineer's salary.

The daily standup that runs long

Setup: 8 people, 25 minutes (supposed to be 15), daily. Average rate $90/hour.

Direct cost: 8 × 0.42 × $90 × 260 = $78,624/year
Context switching cost: $39,312
Total: ~$117,936/year

That daily standup, running just 10 minutes over every day, costs more than $100K annually. Switching to an async standup bot could reclaim most of that.

Sprint planning that takes half a day

Setup: 12 people, 3 hours, every two weeks. Average rate $85/hour.

Direct cost: 12 × 3 × $85 × 26 = $79,560/year
Context switching cost: $39,780
Total: ~$119,340/year

What if planning took 90 minutes instead of 3 hours, with pre-reading done async? You'd save ~$60,000 in productive time.

How to use this to make changes

The cost calculation isn't meant to eliminate all meetings. It's meant to force a question: is this meeting worth its cost?

Here's a simple exercise for your team:

List every recurring meeting on your team's calendar.
Calculate the annual cost of each one using: attendees × hours × rate × frequency.
For each meeting, ask: "If we had to pay cash for this meeting every week, would we still have it?"
Pick the worst offender and run an experiment: cancel it for two weeks, shorten it by half, or replace it with an async update.

Most teams find that 20-30% of their recurring meetings can be eliminated or shortened without any loss of alignment. (For a structured approach to this, see our meeting triage framework.) For meetings that survive the cut, a meeting agenda template makes sure every minute of that expensive meeting counts.

One meeting at a time

You don't have to fix everything at once. Start with your most expensive, least valuable meeting.

Kill One Meeting helps engineering teams do exactly this. It connects to your Google Calendar, collects anonymous feedback from your team on which meetings are working and which aren't, and then helps you run a structured experiment — cancel, shorten, or go async — with one meeting per month.

Teams typically save 10-20 hours of meeting time per month within the first 90 days.

The first step is knowing the real cost. Now you do.

Frequently asked questions

What's a realistic hourly rate to use for cost calculations?: Use the fully-loaded cost, not just salary. For US-based engineers, this typically means multiplying base salary by 1.25-1.4x to account for benefits, taxes, and overhead. A $150K/year engineer costs roughly $90-100/hour fully loaded.
Should I include optional attendees in the cost calculation?: Yes. If someone is on the invite and regularly attends, their time counts. Optional attendees who never attend can be excluded. The goal is to capture the actual time spent, not the theoretical minimum.
How do I get leadership to take meeting costs seriously?: Present the annual cost of your team's top 5 recurring meetings. When leaders see that a single weekly sync costs $40-50K per year, it reframes the conversation from 'just a meeting' to a significant budget item.