What Does Your Meeting Actually Cost?
Enter the average salary, number of attendees, and meeting duration. Instantly see how much each meeting burns in work hours and real cost.
Meeting Cost Calculator
Finance & Daily Life
This is an estimate based on 220 working days × 8 hours/day. Actual cost varies by salary, taxes, and geography.
Based on 220 working days × 8h/day
* Affiliate link – As an Amazon Associate we earn from qualifying purchases.
* Affiliate link – As an Amazon Associate we earn from qualifying purchases.
* Affiliate link – As an Amazon Associate we earn from qualifying purchases.
* Affiliate link – As an Amazon Associate we earn from qualifying purchases.
The short answer: most meetings cost more than people think
A 60-minute meeting with 10 mid-level employees burns roughly 10 work hours — more than one full workday — every single time it runs. If that meeting is weekly, it eats over 500 work hours per year. The cost isn't the room or the coffee. The cost is the salary your company keeps paying while everyone sits and listens instead of doing the work they were hired for. This calculator turns that invisible cost into a number you can actually look at before sending the next invite.
Real meetings, real numbers
Below are the kinds of meetings most teams run every week. The numbers are calculated using gross salary divided by 1,760 work hours per year (220 days × 8 hours) — a baseline used by the OECD for working time statistics. Add 25–40% on top if you want fully-loaded employer cost including taxes and benefits.
| Scenario | People | Length | Avg salary | Cost | What usually goes wrong |
|---|---|---|---|---|---|
| Monday morning standup | 6 | 15 min | 60,000 | 43 | Half the team is barely awake. Status reads as a checklist instead of surfacing blockers. |
| Weekly engineering sync | 10 | 60 min | 90,000 | 511 | Three people talk. Seven mute themselves and answer emails. Same agenda as last week. |
| Quarterly all-hands | 80 | 60 min | 75,000 | 3,409 | Slides are read out loud. The Q&A everyone wanted gets cut for time. |
| Sprint planning | 8 | 120 min | 85,000 | 773 | Estimation arguments eat the first 40 minutes. Backlog grooming never happens. |
| Vendor pitch with leadership | 5 | 45 min | 140,000 | 298 | Director joins 8 minutes late. Vendor restarts the pitch. Real questions arrive in the last 5 minutes. |
| Weekly 1:1 (manager + report) | 2 | 30 min | 95,000 | 54 | Usually worth it. Cancelled when the calendar gets crowded — which is exactly when it matters most. |
| Recurring "sync that should be a doc" | 7 | 30 min | 70,000 | 139 | Same updates every week. Nobody ends it because nobody scheduled it — it was inherited from someone who left. |
Notice the recurring sync at the bottom. 139 once a week is forgettable. Run it for a year and it's over 7,000 — for a meeting that was supposed to be a Slack update. Recurring meetings are where most of the real money disappears.
Mistakes people make when they think about meeting cost
They count the meeting and forget the cost of switching into it. Engineers and writers lose roughly 15–25 minutes of deep focus every time they have to context-switch into a meeting, even a short one. A 30-minute meeting can effectively wipe out an hour of productive work per person. The American Psychological Association has documented this multitasking cost for years — meetings are a form of forced context-switching.
They forget recurring meetings compound. A 30-minute weekly meeting with 8 people at 80,000 salary costs about 182 per occurrence. That's nothing. But it runs 50 times a year. That's 9,100 — for a single recurring slot. Most teams have 5–10 of these. The math is uncomfortable.
They treat everyone's hour as equal. A director making 180,000 costs roughly 102 per hour. A junior making 50,000 costs about 28. If you can keep the director out of a 90-minute meeting, you save more than three junior-hours of budget — for just one fewer attendee. The cheapest way to cut meeting cost is usually to cut the most expensive attendees, not shorten the meeting.
They forget the meeting starts before the meeting. Slides, prep notes, "let me dig up that link" — 1-hour meetings often have 20–40 minutes of prep behind them, and another 15–30 minutes of follow-ups (writing the recap, chasing decisions, updating the doc). The "1-hour meeting" is often a 2-hour job per organizer.
They confuse cost with value. The expensive meeting isn't automatically the bad one. A 60-minute debate between three founders that prevents a wrong hire is worth tens of thousands. A 15-minute standup that puts 8 disengaged people to sleep five times a week is worth nothing — and still costs money. Cost tells you the price tag, not whether the meeting earned it.
When the meeting is worth the money
There are exactly four situations where pulling people into a room reliably beats a written update:
- Decisions with real disagreement. Async loops drag. When two reasonable people disagree and the decision matters, 30 minutes face-to-face usually beats two days of back-and-forth Slack threads.
- Brainstorming and creative divergence. Genuinely creative work benefits from interruption and overlap — but only if the group is small (4–6 max) and the facilitator is willing to cut tangents.
- Conflict resolution and sensitive feedback. Tone doesn't survive written channels. Anything emotionally charged should be a call, ideally with video on.
- Onboarding and relationship-building. New hires, new clients, new partnerships — there's no async substitute for the first 30 minutes of "let me tell you how I think about this."
Almost everything else — status updates, FYIs, "let me walk you through this deck," weekly check-ins where nothing is blocked — can be a Loom, a doc comment, or a single Slack message.
How to cut meeting cost without becoming the no-meeting weirdo
Make the default 25 minutes, not 60. Google, Shopify, and several large teams have shifted to 25- and 50-minute defaults explicitly to leave buffer between meetings. The shorter slot forces tighter agendas. If 25 minutes isn't enough, you didn't need a meeting — you needed a workshop, which is a different thing entirely.
Audit recurring meetings every quarter. Most teams collect meetings the way old hard drives collect files — nothing ever gets deleted. Once per quarter, cancel every recurring meeting on the team calendar. The ones people miss come back within two weeks; the others were already dead. Shopify ran this exact exercise in 2023 and reportedly eliminated about 12,000 hours of meetings per year.
Cut the "optional" attendees, especially senior ones. If someone is invited to "stay in the loop," they shouldn't be in the meeting. Send them the recap. The director's hour is 3–4× more expensive than the junior IC's hour — protecting it is the highest-leverage cost-cutting move you can make.
Require a written agenda 24 hours in advance. No agenda, no meeting. The agenda forces the organizer to actually think about whether the meeting needs to happen. About a third of meetings die quietly at this step, which is the point.
End with written decisions and owners, not "great chat." If the meeting produces no decisions and no action items, the meeting did not happen — you just spent money on a group conversation. The recap should fit in 5 lines: what was decided, who owns the follow-up, when it's due.
Edge cases worth knowing about
External attendees. If a customer, vendor, or partner is in the meeting, the cost calculation breaks. Their time is also expensive, and a wasted external meeting can cost the relationship — which is much more than the labor cost on paper. Treat external meetings with more discipline, not less.
Remote and async-first teams. A 60-minute video call with people in 5 time zones often means at least one person is attending at a bad hour. The "cost" includes their evening or early morning — and the next day's output is usually worse. Async tools like Loom and shared docs aren't just nice-to-have for distributed teams; they're the difference between sustainable and unsustainable.
The "we just need to sync" instinct. When you feel the urge to call a meeting to "sync," ask yourself: what specifically am I trying to find out? If the answer is a single sentence, send a message. If the answer requires back-and-forth, do a 15-minute call. The full 60-minute hold is almost always overkill.
Founders and small teams. Below ~8 people, the math changes. The whole company is in the meeting, decisions move fast, and the overhead of writing things up may actually exceed the meeting cost. The "fewer meetings" rule applies more strongly the larger the company gets.
Once you start looking at the per-meeting cost, you stop calling them by reflex. That's the whole point of the tool. The number on the screen isn't there to make you feel bad about your calendar — it's there to make you ask one question before you click "send": is this conversation worth what it costs? Roughly half the time, the answer is no, and a written update goes out instead. That's the win.
For people thinking about how time and money compound differently, the compound interest calculator shows the same principle from the opposite direction — small recurring amounts add up to surprisingly large totals over time, whether you're saving them or burning them.
Frequently asked questions
It's actually on the low side. We use gross salary divided by 1,760 work hours per year. Fully-loaded employer cost — taxes, benefits, equipment, office overhead — is typically 25–40% higher in most countries. So if the tool shows 500, the company is probably paying closer to 650 to keep those people in that room. The discomfort you feel looking at the number is the point. Most teams stop running half-pointless meetings within two weeks of seeing real numbers attached to them.
1,760 comes from 220 working days × 8 hours, which is a rough cross-country average after weekends, public holidays, and standard vacation. Germany and France actually run lower (around 1,500–1,600 hours due to more vacation), the US slightly higher. The number isn't meant to be payroll-accurate — it's a defensible baseline so the per-meeting comparison stays consistent. If your team works 35-hour weeks, the real per-hour cost is roughly 14% higher than what we show.
Inviting people defensively. The reflex is "better invite them in case they want to be in the loop" — and suddenly you have 12 people in a room where 4 were needed. The fix is just-in-time inviting: start with the smallest possible group, add people only when you genuinely need their input, and send a recap to everyone else. The people who actually wanted to be there will speak up. The rest are quietly relieved.
Three signals: nobody remembers who originally scheduled it, the last three meetings could have been emails, or the agenda hasn't meaningfully changed in two months. The clean way to kill it is a 30-day trial — announce it's paused, see who notices. If more than two people independently ask "where did the meeting go?" within four weeks, bring it back. Fewer than a third usually come back. The rest were running on calendar inertia.
Two reasons. First, real discussion doesn't start until people warm up — usually 5–10 minutes of context-setting and small talk. Second, the most important topic almost always lands last, when people are watching the clock instead of the issue. The fix: put the hardest decision first, set a hard stop at 50 minutes instead of the hour, and leave the last 10 minutes specifically for action items. Meetings feel shorter and produce more.
Almost never. A 30-minute weekly 1:1 between manager and report is usually one of the highest-leverage meetings on the calendar. The cost is around 50, and it prevents much more expensive failures — bad performance reviews, surprise resignations, projects quietly going sideways. The mistake managers make is cancelling 1:1s when their calendar gets crowded. That's exactly when the report needs the slot most.
Initially, maybe. After about two months, the team starts defending you. Time is the one resource everyone notices when it disappears but nobody thanks you for protecting. The reframe: you're not anti-meeting, you're pro-decision. Cancel the ones that don't produce decisions. Keep the ones that do. Send written recaps so visibility stays high. The pattern people remember isn't "this manager has no meetings" — it's "this team ships more."
Don't cancel it. Propose a downgrade: "Could we try moving this to an async update for the next two weeks and see how it goes? Happy to write it up." Most managers say yes because it shifts work from them to you, which is a hard offer to refuse. After two weeks, the meeting usually doesn't come back — or it comes back shorter, because the async version made everyone realize what was actually needed.