The real cost of a meeting is the salary bill plus the focus time it destroys — and the second number is usually larger. Eight people in a weekly hour on $120k salaries costs roughly $75,000 a year in wages alone. The fragmentation it causes around that hour typically costs more, and never appears in anyone's budget.
Meetings feel free to whoever schedules them and expensive to everyone attending. That asymmetry is the whole problem, and pricing is the fix.
The direct cost — do this maths once
Fully-loaded hourly cost is roughly:
(annual salary × 1.3) ÷ 1,800 working hours
The 1.3 covers employer taxes, benefits and overhead; 1,800 is a working year after leave and holidays. For a $120,000 salary that's about $87/hour.
Now the recurring multiplier, which is where the number gets uncomfortable:
| Meeting | Attendees | Per occurrence | Per year |
|---|---|---|---|
| Weekly 1-hour team sync | 8 | ~$696 | ~$36,000 |
| Weekly 1-hour, senior team | 8 @ $180k | ~$1,040 | ~$54,000 |
| Daily 15-min standup | 6 | ~$130 | ~$34,000 |
| Fortnightly 2-hour planning | 12 | ~$2,088 | ~$54,000 |
A daily standup costing $34,000 a year is the one that surprises people. Fifteen minutes feels like nothing; 250 occurrences × 6 people is not nothing.
Run your own numbers in the meeting cost calculator — it also finds workable time-zone overlap if your team is distributed.
The bigger cost nobody prices
Salary is the visible line. The larger one is what the meeting does to the hours around it.
Deep work needs uninterrupted blocks. A meeting at 11:00 doesn't consume one hour — it can consume the whole morning, because the 90 minutes before it aren't long enough to get properly into a hard problem and the reattachment cost afterwards eats into what's left. This is the fragmentation tax, and it's why focus time matters more than active hours.
Two meetings placed badly can eliminate a day's deep work while consuming only two hours of calendar. Two meetings placed back-to-back at the start or end of the day might cost almost nothing extra.
Which meetings to cut first
Not all expensive meetings are wasteful. Rank by cost-per-decision, not by cost:
- Status meetings — the classic cut. If the meeting exists so people can report what they did, a written update does it for a fraction of the cost and creates a searchable record. Highest saving, lowest risk.
- Meetings with passive attendees — if half the room hasn't spoken in a month, they're paying attention tax on someone else's decision. Shrink the invite list before cancelling the meeting.
- Recurring meetings nobody chose — most recurring series were created for a reason that expired. A standing rule that every recurring meeting is cancelled every six months unless someone re-justifies it kills these automatically.
- Meetings that exist because trust is low — a check-in that exists so a manager feels informed is a management problem wearing a calendar invite. Fixing the underlying reporting is cheaper than the meeting.
Keep the ones that make genuine decisions, resolve real disagreement, or do work that needs bandwidth — design reviews, incident response, hard prioritisation calls. Those are cheap at almost any price.
Make the cost visible
The single most effective intervention is showing the number. Teams that put the annual cost in the calendar invite title — "Weekly sync (~$36k/yr)" — cancel meetings without anyone mandating it, because the asymmetry disappears. The organiser now sees what the attendees have been paying.
Three practices that follow from that:
- Price every recurring meeting once a quarter. Not to cancel them all — to make the trade-off explicit.
- Default recurring series to a six-month expiry. Re-justify or it lapses.
- Report meeting load alongside output. If meeting hours rose and shipped work didn't, that's a decision-ready signal. For distributed teams, pair it with the time-zone playbook, where meetings cost extra in unsociable hours.
Measuring it honestly
You can price meetings from calendar data alone, but calendar data lies in both directions: it misses ad-hoc calls and it counts meetings people declined or half-attended. Activity data closes the gap by showing actual meeting-app time and, more usefully, what happened to focus blocks around it.
The signal worth tracking is the ratio: meeting hours versus sustained focus hours, per team, over a month. A team at 12 meeting hours and 6 focus hours a week has a structural problem no amount of individual discipline fixes. See how to track employee productivity for the wider method, and remote monitoring if your team is distributed.
Where ProdView fits
ProdView shows meeting load and focus time side by side from activity metadata — never screen content, screenshots off by default, and employees see the same dashboard managers do. That pairing is the point: meeting hours alone tell you volume, but meeting hours against focus hours tell you whether your calendar is costing you the work. Native Windows, macOS and Linux, SOC 2 Type II, $4.99/user/month (₹399 in India), free for 3 seats.
When not to pick us: you want per-meeting attribution to specific calendar events with attendee-level billing — that's a calendar-analytics product, not what we build.
Start with the number
Price your three most expensive recurring meetings before changing anything. Most teams find one that nobody would defend once the annual figure is visible.