The Meeting Cost Calculator: What a Recurring All-Hands Actually Costs

A recurring meeting never generates an invoice, so it never gets scrutinized the way a $50,000 software line item does — even when it costs more than that over a year. The only reason meetings feel free is that their cost is paid in salary that was already being spent anyway. That doesn't make the cost zero. It makes it invisible.

The formula

Cost per occurrence = attendees × loaded hourly rate × meeting length (hours)

"Loaded hourly rate" means salary plus the overhead that comes with it — benefits, payroll tax, equipment, office or tooling costs — not just the number on an offer letter. A workable approximation without pulling real payroll data: divide annual salary by 2,000 (a standard work-year in hours) and multiply by 1.3 to account for that overhead.

A worked example

Take a 12-person weekly all-hands, 60 minutes, with an average salary of $130,000 across the room (a realistic blend of ICs, managers, and leadership on a mid-size distributed team):

One weekly hour, for one 12-person meeting, costs more than a full-time hire in most markets. That's not an argument that the meeting is worthless — some recurring meetings genuinely earn their keep. It's an argument that "let's just keep it as-is, it's only an hour" is not a neutral default; someone is deciding to spend $52,728 a year every time nobody re-evaluates it.

The formula still undercounts the real cost

Sixty minutes on the calendar rarely means sixty minutes of actual cost. Add prep time for anyone presenting, the few minutes everyone loses re-focusing afterward, and — on a distributed team specifically — the time spent writing up notes for whoever couldn't attend live because it fell in their rest hours. A reasonable rule of thumb is to load an extra 20–30% onto the raw calculation above for meetings with a fixed agenda owner or regular follow-up documentation; the $52,728 example is closer to $65,000–$68,000 once that's included, not because the math changed but because the original formula was only ever pricing the time visible on the invite.

The distributed-team surcharge this formula misses

The dollar formula treats an hour the same regardless of when it happens, but on a distributed team it isn't. A meeting that lands in someone's fringe or rest hours costs that person more than their hourly rate — there's a next-day fatigue cost, a context-switch cost from stepping away from family or sleep, and a resentment cost that compounds if it's always the same person paying it. The fair rotation formula gives this a number (working = 0, fringe = 1, rest = 3) — multiply that pain score onto the dollar cost for each attendee, and a meeting that looks identically priced on paper can be two or three times more expensive in practice depending on who's attending from where.

Which meetings to cut first

Plot every recurring meeting on two axes — dollar cost (headcount × rate × frequency) and time zone pain (summed pain score across attendees) — and the priority order falls out on its own:

• High cost, high pain: convert to async first. This is where a recorded update plus a written doc for comments replaces the live call with the least lost value.
• High cost, low pain: keep, but shrink the invite list. The cost is legitimate; the question is whether all 12 people need to be live for all 60 minutes.
• Low cost, high pain: keep the meeting, fix the time. This is exactly the case the fair-rotation formula is built for — a small group can usually find a rotation that spreads the pain evenly instead of eliminating the meeting.
• Low cost, low pain: leave it alone. Not everything needs to be optimized, and small, well-timed meetings are rarely where the real cost is hiding.

Running this on your own team

1. List every recurring meeting with a fixed attendee list, its length, and its frequency.
2. Estimate a loaded hourly rate per attendee, or use one blended average if exact salary data isn't available to whoever's running this exercise.
3. Multiply out the annual cost for each meeting — most teams find one or two numbers that are startlingly large.
4. Check each meeting's actual time against attendees' local hours on the SyncHours planner to add the pain-score dimension before deciding what to cut.

The goal isn't a spreadsheet nobody looks at again — it's having one real number to point to the next time someone proposes adding a new recurring meeting "just for 30 minutes a week." Thirty minutes a week, at the example rate above, is still over $26,000 a year.