Why Meetings Cost $37 Billion a Year

$37 billion. That's what U.S. companies waste annually on unnecessary meetings. Not all meetings. Just the ones that didn't need to happen. I spent three years managing a 12-person engineering team before I understood where that number comes from, and once you see the math, you can't unsee it.

The $37 Billion Number

That figure comes from a combination of Bureau of Labor Statistics salary data and Atlassian's research on meeting frequency in knowledge-work companies. The average U.S. knowledge worker spends 11.5 hours per week in meetings. Managers spend closer to 15. About 55-70% of those meetings fail to produce an actionable outcome. When you scale that across 35 million knowledge workers, you hit the $37 billion mark fast.

The number feels abstract until you zoom into your own company. The average organization spends roughly $29,000 per employee per year on meeting time alone. That's not a metaphor. That's salary plus benefits paid to people sitting in rooms where nothing gets decided.

Breaking Down the Math

Cost per meeting

Here's the formula I use. Take the average fully loaded cost per employee in your company. "Fully loaded" means salary plus 30% for benefits, office space, equipment, and overhead. For a U.S. knowledge worker earning $85,000 base, the loaded cost is roughly $110,500 per year. That breaks down to about $57 per hour.

Now multiply. A typical meeting has 6 attendees. Six people at $57/hour for one hour costs $342. That meeting where your team discussed a Jira ticket that could've been a Slack message? $342. The 30-minute "quick sync" that ran to 48 minutes? About $275.

This math changes your thinking fast. Every meeting has a price tag. You just never see it on a receipt.

Recurring meeting trap

Recurring meetings are where the real money burns. That $342 meeting happens every week? That's $17,784 per year for one recurring calendar event. Most teams have 5-8 recurring meetings. Do that math and you'll feel slightly sick.

Five weekly meetings with 6 people each: $88,920 per year. For one team. And I've worked at companies where teams had 12+ recurring meetings per week. Nobody ever deleted them. They just accumulated like barnacles on a ship hull, slowing everything down while nobody thought to scrape them off.

Here's what makes it worse. People stop paying attention in recurring meetings by week three. They show up, mute themselves, check email, and mark it as attended. You're paying $342 per session for 6 people to sit there thinking about other things.

The Hidden Cost Nobody Calculates

The dollar cost of meeting time is only half the story. The other half is what meetings do to the time between them.

Researchers at the University of California, Irvine found that it takes 23 minutes and 15 seconds on average to return to full focus on a task after being interrupted. A meeting isn't just an interruption. It's a scheduled destruction of whatever focus state you built up before it started.

Think about what that means practically. You sit down at 9:00am to write code or design a feature or draft a proposal. You're hitting your stride by 9:45. Then you remember you have a 10:00 meeting. So you stop at 9:50 because there's no point starting something new. The meeting runs 10:00 to 10:47. You get back to your desk at 10:52 after a bathroom break and refilling coffee. You open your files. You stare at where you left off. You re-read your notes. By 11:15, you're back in the zone. Then your 11:30 meeting reminder pops up.

That morning had two hours of meetings but produced maybe 45 minutes of real work. The rest was transition time, ramp-up time, and dead zones too small to start anything meaningful. This is why so many engineers say they only get real work done before 9am or after 5pm. Their actual workday is consumed by meeting-adjacent dead time.

When you add context switching costs, a one-hour meeting actually consumes about 1 hour and 23 minutes of productive capacity. Four meetings in a day doesn't cost you 4 hours. It costs you roughly 5.5 hours and fragments the remaining 2.5 hours into unusable scraps.

The "Could This Be an Email?" Test

Before scheduling any meeting, I ask three questions. If the answer to any of them is "yes," I cancel the meeting and send a message instead.

Question 1: Am I sharing information in one direction? If people just need to know something, write it down. A Notion doc, a Slack post, a Loom video. One-directional information transfer is what email was invented for.

Question 2: Can this decision wait 24 hours for async input? Most decisions can. If you're not choosing between two options that expire today, give people time to think and respond in writing. Async responses are almost always more thoughtful than put-on-the-spot verbal answers in a meeting room.

Question 3: Are more than 3 people needed for the actual discussion? If you're inviting 8 people but only 3 will talk, you've got 5 expensive audience members. Meetings are for discussion, not presentation. Present async, then meet with the 3 people who have input.

These three questions killed about 40% of my meetings within the first month of applying them. Forty percent. Gone. Nobody complained. Two people said they preferred the written updates because they could read them when it suited their schedule.

Calculate YOUR Meeting Costs

I built a Meeting Cost Calculator that does this math for you. Plug in your team size, average salary, number of recurring meetings, and average meeting length. It shows you the annual cost and the context-switching overhead.

Most people who use it are surprised by how quickly the numbers add up. A 15-person team with typical meeting loads often burns $200,000-400,000 per year just in meeting time. That's the salary of 2-3 additional engineers you could hire instead.

The calculator also breaks down cost per minute, which is useful for setting meeting-length defaults. When you know your team's meetings cost $5.70 per minute, you start questioning whether that "quick 15-minute check-in" that always runs to 35 minutes is really worth $200 every time.

What to Cut First

Status updates

Status meetings are the lowest-hanging fruit. They exist because someone, at some point, didn't trust written communication to keep everyone aligned. But tools like Slack, Notion, Monday.com, and even email handle status updates better than synchronous meetings ever will.

Replace them with a daily async check-in. I use a simple Slack template: what I did yesterday, what I'm doing today, anything blocking me. Takes 90 seconds to write. Everyone reads it when they want. Total cost: basically zero versus the $342 per meeting version.

Bloated brainstorms

Brainstorm meetings with 8+ people don't work. Research on group dynamics shows that groups larger than 4-5 people produce fewer ideas per person because of social loafing and production blocking (waiting for your turn to speak). The loud people dominate, the quiet people disengage, and you leave with the same ideas the loud people would've had alone.

Cap brainstorms at 4 people maximum. If you need input from 8, split into two groups of 4, brainstorm separately, then merge the results async. You'll get better ideas and spend half the person-hours.

Zombie recurring meetings

Every quarter, audit your recurring meetings. For each one, ask: "If this meeting didn't exist already, would I create it today?" If the answer is no, delete it. Don't "pause" it. Don't reduce the frequency. Delete it. You can always recreate it if something breaks, but I promise you, 80% of deleted recurring meetings are never missed.

I've done this audit four times now. Each time I delete 3-5 meetings and nobody says a word. They just get that time back and do something productive with it.

My 2-Meeting Rule After 6 Months

Six months ago I set a hard limit: maximum 2 meetings per day, each capped at 25 minutes. Not 30. Not "roughly half an hour." Twenty-five minutes with a hard stop.

The 25-minute cap works because it forces an agenda. When people know the clock is real, they skip the 5-minute small talk and get to the point. I set a visible countdown timer on screen share. People adapt instantly.

Results after 6 months: I recovered roughly 8 hours per week. My deep work blocks went from scattered 45-minute fragments to consistent 2-3 hour stretches. I shipped two side projects that had stalled for months. My team's velocity actually increased because they had the same uninterrupted time.

The pushback was minimal. Two people said they missed the social aspect of longer meetings. I started a weekly 15-minute optional coffee chat with no agenda for them. It's the only meeting I run that has no purpose, and it's the one people actually enjoy.

Not every team can do this. Client-facing roles need more meetings. But for internal teams building products? Two meetings, 25 minutes each, and everything else goes async. The math works, the output improves, and nobody misses the meetings that disappeared.