How to Calculate the Cost of Unproductive Meetings for Your Team

I once sat through a 90-minute "alignment sync" with 14 people where nothing was decided. On the way out I did the rough math in my head: 21 person-hours, and every single one of them was somebody's most productive afternoon slot. That meeting probably cost more than my monthly rent. Nobody in the room had ever priced it out, because nobody prices out meetings. That is exactly the problem.

Calculating the cost of unproductive meetings is not about shaming anyone. It is about giving a number to something your team already feels. When you can say "this recurring meeting costs us $74,000 a year," the conversation about fixing it gets a lot easier.

The core formula

Strip it down and a meeting costs one thing: attendees × hourly cost × hours. The trick is in what "hourly cost" really means. If you use base salary alone, you will understate the cost by roughly a third, and your number will lose credibility with anyone who has read a budget.

An employee costs more than their paycheck. Benefits, payroll taxes, equipment, and office space typically add 25 to 40 percent on top of base pay. Finance people call this the fully-loaded cost, and 1.3x is the standard shortcut. So the real formula is:

The three things most estimates miss

1. Preparation and follow-up time. One analysis of meeting culture found that an hour in a meeting often consumes close to three hours of employee time once you count prep, context-switching, and recovery. A 2015 poll found people spent about 4.5 hours a week in progress meetings and another 4.6 hours preparing for them. The meeting itself is only half the bill.
2. The unproductive share. Not every minute of a meeting is waste. Research from Microsoft and Atlassian has found that participants themselves describe 30 to 50 percent of meeting time as unnecessary or unproductive. For a cost-of-waste estimate, multiply total meeting cost by a reasonable share, maybe 40 percent, and state your assumption.
3. Opportunity cost for billable or revenue roles. For consultants, agencies, and anyone client-facing, an hour in a meeting is an hour not billed. If a partner bills at $300 an hour, that is the right number to use, not their salary equivalent.

A worked example: the marketing team

Let me borrow a concrete case. A marketing team of 8 people each spends about 20 hours a week in meetings. Their average loaded cost is $75 an hour.

That number is deliberately ugly, and you should argue with my inputs. Maybe your team's loaded rate is $55. Maybe only 30 percent is waste. The point of the exercise is that even the conservative version lands in the six figures. Change the assumptions and the number stays big.

A simpler version for one meeting

For a single meeting, skip the annual projection. I like the "lunch test": price the meeting, then ask whether it was worth more than the nice team lunch it could have bought.

The per-minute figure is the one that changes behavior. When a team knows the meter runs at $7.50 a minute, agendas get tighter all by themselves.

What to do with the number

A cost estimate is ammunition, not a verdict. I have seen three fixes work reliably:

• Cut the invite list. Invite the deciders, send notes to the informed. Every person you remove from a weekly hour-long meeting at $75 an hour saves roughly $4,875 a year.
• Default to 25 or 50 minutes. Calendar defaults of 30 and 60 minutes create overflow. Shorter defaults force prioritization and the per-minute meter does the rest.
• Replace the status round with a written update. If the meeting's only output is "everyone knows what everyone is doing," a shared doc does that for free.

The honest truth is that most of the savings come from deleting meetings, not optimizing them. Price them, pick the most expensive recurring ones, and ask the uncomfortable question: what would break if this one just stopped existing? Usually the answer is nothing.

Frequently asked questions

Related reading: What a One-Hour Meeting Actually Costs: Worked Examples by Team Size