The real cost of your weekly recurring meeting
A 30-minute meeting feels free because nobody sees a bill for it. But a recurring meeting isn't one event — it's a standing budget line that just never shows up as one, because payroll already covers it quietly in the background.
Turning a single meeting into an annual number
Take the per-meeting cost (attendee hourly rates, with overhead, summed and multiplied by the meeting length) and multiply by how often it happens in a year:
- Weekly meeting → ×52
- Twice-weekly → ×104
- Biweekly → ×26
- Monthly → ×12
Worked example: a 6-person weekly status meeting
| Length | Attendees | Per-meeting cost | Annual cost |
|---|---|---|---|
| 30 min | 6 (avg $110k) | ~$198 | ~$10,300 |
| 60 min | 6 (avg $110k) | ~$396 | ~$20,600 |
| 60 min | 10 (avg $130k) | ~$780 | ~$40,600 |
That last row is a part-time salary spent entirely on one recurring status check-in. Nobody approved that as a budget line — it accumulated one calendar invite at a time.
Why this number changes behavior
"It's only 30 minutes" is how every low-value recurring meeting survives. The moment it's reframed as "$10,000 a year," it competes with every other line item a manager has to justify — a tool subscription, a contractor, a training budget. Most of those get scrutinized annually. The recurring meeting usually doesn't, simply because nobody ever converts it into the same unit.
What to do with the number
- Cut the attendee list first. Cost scales linearly with headcount — dropping four people from a ten-person meeting cuts the cost by 40% without touching the agenda.
- Shorten before you cancel. A 30-minute version of a 60-minute meeting halves the annual cost and is usually an easier sell than killing it outright.
- Replace status updates with async writing. If the meeting's only function is "tell each other what we did," a shared doc or Slack thread captures it for a fraction of the cost and a fraction of everyone's calendar.