How much is
this meeting costing?

Field guide

The hidden cost of “just a quick meeting.”

According to research by Atlassian, the average employee attends 62 meetings per month — and considers more than half of them a waste of time. A Microsoft study found that time spent in meetings has tripled since 2020. Yet most teams never attach a dollar figure to this time. The formula is deceptively simple:

A 10-person meeting at a $75/hr average rate lasting 90 minutes costs $1,125. Run that every week and you’re spending $58,500 per year on that single recurring slot — before you factor in benefits (typically 25–30% on top of salary) or office overhead.

Salary-to-hourly conversion

The calculator converts annual salaries to an hourly equivalent using the standard US full-time benchmark of 2,080 hours per year (52 weeks × 40 hours). A $100,000 annual salary works out to approximately $48.08/hr. This is a labor-cost figure — it measures the opportunity cost of an employee’s time, not their take-home pay.

What the cost actually represents

The calculated figure is a floor, not a ceiling. It captures only the direct salary cost of the time spent. The true cost is higher when you add:

• Employer benefits burden — typically 25–35% on top of salary (health insurance, payroll taxes, retirement match, paid leave). A $50/hr worker costs the company roughly $65–68/hr all-in.
• Overhead and facilities — rent, utilities, and software licenses allocated to the attendees’ time. For office-based companies, this adds 20–40% more.
• Opportunity cost — what work is not getting done while these people are in the room. For senior ICs and makers, an interrupted two-hour block of deep work can represent far more lost value than the salary cost alone.

Recurring meetings: where the real waste hides

One-off meetings are easy to justify. The quiet budget drain is the recurring slot that nobody ever cancels. A weekly 30-minute standup with 8 people at $60/hr costs:

• $240 per occurrence
• $12,480 per year
• $62,400 over a five-year period

Run a quick audit on your team’s recurring calendar and total the annualized costs. Most teams are surprised to find they’re spending hundreds of thousands of dollars per year on meetings alone.

The maker’s schedule problem

Paul Graham’s essay “Maker’s Schedule, Manager’s Schedule” explains a critical asymmetry: for managers, a meeting is just one block in a day of blocks. For engineers, designers, and writers — people who do deep work — a single meeting in the middle of the afternoon can destroy an entire productive day. The “cost” is not just the 60 minutes in the room but the surrounding 2–3 hours of lost flow state.

This is why many high-performance teams adopt meeting-free mornings, no-meeting Wednesdays, or strict async-first cultures for anything that doesn’t require real-time collaboration.

When a meeting is worth it

Not all meetings are waste. Some decisions genuinely require synchronous discussion and cannot be made asynchronously without significant risk. A meeting earns its cost when:

1. The output would have taken longer to produce via email or doc than the meeting itself
2. Real-time debate is needed to surface conflicting assumptions that documents would miss
3. The relationship or alignment value justifies the time cost (e.g., a quarterly all-hands or onboarding session)

A useful heuristic: if you can write a clear decision doc and get async approval within 24 hours, the meeting is probably not necessary.

How to reduce meeting costs

• Shrink the invite list. Each additional person adds their full hourly cost. Only invite people who are strictly necessary — not everyone who “might find it useful.”
• Default to 25/50 minutes. Calendar tools default to 30/60. Setting 25- and 50-minute defaults forces meetings to end on time and creates buffer for transitions.
• Require an agenda. If a meeting cannot be described in a one-line agenda, it’s not ready to happen.
• Cancel recurring meetings that drift. A recurring meeting that runs out of agenda items is pure waste. Build in a quarterly review of all standing meetings.
• Use async for status updates. Standups, progress reports, and FYI announcements are better handled via Loom, Slack, or a shared doc — no synchronous cost at all.