The 11 a.m. team sync had been on the calendar for so long that nobody questioned it. Eleven attendees, every Tuesday, half an hour. Sometimes it ran over. Most weeks, three people did most of the talking and the rest watched. When a new manager added up the numbers, including salary, preparation, and the thing none of them did right after, the recurring meeting was costing the team more than $50,000 a year. The meeting itself was not necessarily bad. The cost was simply invisible.
This is a guide for making that invisibility go away, without pretending every meeting should be cancelled.
Why the cost stays hidden
Most calendars treat a meeting as free until proven otherwise. There is no line on a credit card statement and no monthly invoice to compare. The expense is paid in salaried time, which is already on the books regardless. Logically, accountants and managers know the salary is being spent; emotionally, the meeting feels like it costs nothing, because nobody writes a cheque for it.
The trap is that "already paid" is not the same as "free." A team's hours are finite. Every meeting hour is an hour not spent on the work the salary was meant to produce. Once a few hours per week add up across a team, the gap becomes visible, usually as missed deadlines, growing backlogs, and the quiet feeling that nobody can find time to think.
The basic meeting cost formula
The simplest model is the one a Meeting Cost Tracker implements directly: multiply the number of attendees by their average hourly cost by the duration of the meeting.
Cost = attendees × average hourly cost × hours
For a 30-minute meeting with 8 attendees at an average loaded hourly cost of $80, that is 8 × 80 × 0.5 = $320. Over a year of weekly sessions, the same line item runs $320 × 52 = $16,640.
That number is already enough to start filtering recurring meetings, but it is the floor of the cost, not the ceiling. There are at least three more honest categories to add.
How to get an hourly cost from a salary
If you are starting from annual salary, the rough conversion is salary divided by working hours in a year. A common assumption is 2,080 hours (40 hours × 52 weeks), which corresponds to a full-time work year before vacations and holidays.
For a $90,000 annual salary, that gives roughly $43/hour. But the cost to the employer is higher than the salary alone. Benefits, payroll taxes, equipment, software, office overhead, and management overhead are all real costs of employing the person. A common rule of thumb is to multiply base salary by 1.25 to 1.4 to estimate fully loaded cost; senior or specialized roles can land higher. A $90,000 salary at a 1.35 multiplier yields a loaded cost near $122,000, or about $59/hour.
The exact multiplier depends on the company, the country, and the role. The point is not to nail the figure down to the penny; it is to stop pretending an hour of someone's time is the same as their stated wage. The Hourly to Salary Calculator and the Salary Calculator help translate between these views quickly when planning.
Attendee count is the variable that compounds
Cutting a meeting in half saves half the cost. Removing one of ten attendees saves a tenth. Those feel symmetric, but they are not, because the value of each attendee is rarely equal.
A meeting needs decision-makers, contributors, and information-providers in the room. The fourth, fifth, and sixth people of the same role are usually present "for context" or "in case it comes up." Their marginal information value is low, and their marginal cost, both the cost of their time and the cost of the meeting being slower because more people are speaking, is high.
The most useful question a meeting organizer can ask is who actually needs to be here for this to succeed? That is the lever with the biggest multiplier in the formula, and the only one most teams can pull without political cost. Send notes to the people who only needed to be informed; bring back the ones who genuinely needed to debate.
Preparation and follow-up are part of the cost
A 30-minute meeting is rarely 30 minutes of time spent. Someone wrote the agenda. Someone prepared a short deck or a doc. Two attendees re-read the relevant Slack thread. After the meeting, somebody wrote up notes and assigned action items. Someone else followed up the next day.
If the meeting costs an hour of in-room time across the team, the real cost may be 1.5 or 2 hours when preparation and follow-up are counted honestly. For a well-prepared meeting, the prep is doing useful work, and the meeting itself is shorter because of it. For a poorly prepared meeting, both the prep and the meeting are partial.
A reasonable rule is to budget a third of the meeting's in-room time for preparation among the active participants, and a quarter for follow-up. Two questions can sharpen this. Was there an agenda? Were there written action items at the end? The presence of both is closely correlated with a meeting that actually accomplished something proportional to its cost.
Opportunity cost: the work that didn't happen
The hardest line to estimate is the work the attendees would have produced if the meeting had not run. Salaries are sunk; opportunity is not.
A senior engineer's 90 minutes might have shipped a fix that unblocks four other engineers. A salesperson's two hours might have been a call that closed a $40,000 contract. A designer's morning might have produced a prototype that resolves a debate the next meeting was scheduled to have. None of that is on the invite, but all of it is the actual price of the slot.
Opportunity cost is genuinely impossible to forecast with precision. It is still useful to gesture at, because it pushes meetings into a sharper question: was this the highest-leverage hour these people had today? For meetings that recur weekly with the same attendees and the same purpose, the answer eventually drifts toward no, and that is the signal to renegotiate.
A worked example: the recurring sync
Picture a Tuesday product sync. 9 attendees, 45 minutes, weekly. The team is a mix of engineers, designers, and a manager; the blended fully-loaded cost averages $95/hour.
- Base cost per session: 9 × $95 × 0.75 hours = $641.25
- Preparation (10 minutes per active attendee, 6 active attendees): 6 × $95 × (10/60) = $95
- Follow-up (15 minutes for the manager, 10 minutes for two leads): ($95 × 0.25) + (2 × $95 × 10/60) = $55.42
- Per-session total: about $792
Over 50 working weeks, that is $39,600 per year. If the meeting consistently produces decisions worth at least that much, it is a fine investment. If it has been running on momentum for two quarters without anyone able to point at a decision it drove, it is a candidate for a 25-minute version with five attendees, or replacement with an async written update.
To translate raw minutes into the decimal hours the formula needs, the Time to Decimal tool is the quickest helper: fifteen minutes is 0.25 hours, not 0.15, and the conversion error is the most common arithmetic mistake people make when they try to do this in their head.
When a meeting is the right tool
It is worth saying plainly: some meetings are worth far more than their cost. Real-time conversation is the right format when a decision needs everyone in the same context within the same minute, when the conversation is genuinely creative, when trust needs to be built between unfamiliar people, or when the topic is sensitive enough that written communication will misread. These are exactly the kinds of meetings whose value is much higher than the salary math implies.
Anti-meeting advice that ignores this lands badly in real teams, where over-correcting toward async creates other problems: drift, confusion, conflict avoidance. The goal is not fewer meetings; it is meetings whose cost the organizer is willing to defend out loud.
Patterns that show a meeting is too expensive
A meeting with no decision criteria. If you cannot name what would count as a successful outcome, the meeting will run to time and produce a feeling of progress without measurable change.
A meeting where most attendees do not speak. Most calendars have at least one of these, and they are the easiest to trim. Send notes; remove from invite.
A meeting that grew. Adding "just one more person" to a recurring meeting is the calendar equivalent of credit card minimum payments: easy at the time, expensive cumulatively.
A meeting whose preparation time exceeds its in-room time. Sometimes this is right. Often it indicates a written artefact (a decision doc, a proposal) was the actual deliverable, and the meeting is a ceremony around it that adds little.
A meeting whose follow-up never happens. If decisions evaporate the day after, the cost was paid for nothing.
Common mistakes when estimating meeting cost
Using base salary rather than loaded cost. Loaded cost is the honest number for organizational decision-making.
Including only the people in the room. Preparation and follow-up are part of the meeting's footprint. So is context-switching back to focused work, which research suggests can cost real minutes per interruption.
Treating all 30-minute meetings as equal. A 30-minute meeting with three peers and a 30-minute meeting with twelve mixed-seniority attendees are radically different costs. Attendee count is more important than length, in most cases.
Forgetting the meeting was the third this week on the same topic. Cost compounds across the topic, not just the slot.
Pricing a meeting that produced a real decision the same as one that did not. The metric to evaluate is value-per-cost, not cost in isolation.
Common mistakes worth fixing first
A few low-effort changes do most of the work. Tighten the standard meeting length from 30 to 25 minutes, or 60 to 50, to recover transition time. Default to async-first for status updates, with synchronous meetings reserved for decisions. Add an explicit decision section to every recurring meeting's agenda. Make the cost number visible. A single line in the meeting notes that reads "estimated cost of this meeting: $X" changes the conversation more than any policy.
FAQ
How do I calculate the cost of a meeting? Multiply the number of attendees by their average loaded hourly cost by the meeting duration in hours. Add preparation and follow-up time for an honest figure.
Do salaried employees actually cost the company per hour? Their salary is fixed, but every working hour has an implied hourly value. Treating that value as zero leads to too many meetings, because the cost feels invisible even though it is real.
Are short meetings always better than long ones? Not always. A 60-minute meeting that produces a decision is cheaper than three 30-minute meetings that do not. Optimize for outcomes per minute, not minutes themselves.
Is the cost just salaries, or more than that? At minimum it is loaded salary cost. Preparation, follow-up, and the opportunity cost of work not done are all reasonable additions, even if estimated roughly.
Should we cancel recurring meetings to save money? Some, perhaps. The cleaner move is to audit them: cancel ones with no decision criteria, shrink the attendee list on those that survive, and convert status-only meetings to async updates.
What is opportunity cost in the context of meetings? The value of the work the attendees would have done if the meeting had not happened. It is hard to estimate precisely but worth keeping in mind, particularly for senior or high-leverage roles.
What this changes in practice
Meetings will not, and should not, disappear. They are the medium that decisions, alignment, and trust often genuinely need. What changes when the cost becomes visible is the threshold for calling one and the seriousness with which the organizer prepares. A meeting that survived that test will tend to be shorter, smaller, and more useful, which is the only thing the math is really trying to push toward.