A meeting cost calculator turns calendar time into a visible operating expense. This guide provides a reusable formula, spreadsheet layout, worked examples, and an optimization checklist for deciding which recurring meetings to keep, change, shorten, or replace with asynchronous updates.
Overview
Meetings have a direct cost: the time that attendees could otherwise spend on engineering, support, sales, operations, or focused project work. That cost is easy to overlook when a recurring meeting is only 30 minutes long. The impact becomes clearer when you multiply the meeting length by the number of attendees and its monthly frequency.
A meeting cost calculator should answer four questions:
- What does one occurrence cost in team time?
- What does the recurring meeting cost per month or year?
- What outcome is the meeting expected to produce?
- Would a shorter meeting, smaller attendee list, lower frequency, or asynchronous workflow deliver a similar result?
Cost is not a reason to eliminate every meeting. A planning session that resolves dependencies or enables a timely decision may create more value than it consumes. The purpose of the calculation is to make that trade-off explicit and support better decisions.
How to estimate meeting cost
Use this basic formula:
Meeting cost per occurrence = meeting length in hours × total attendee hourly cost
For a recurring meeting:
Monthly meeting cost = cost per occurrence × meetings per month
Annual meeting cost = cost per occurrence × meetings per year
To build a spreadsheet, create one row per recurring meeting and add these columns:
- Meeting name
- Purpose or decision supported
- Meeting length in minutes
- Meetings per month
- Number of attendees
- Average hourly pay or loaded hourly cost by attendee group
- Burden rate, if you are converting direct pay into a broader employment cost
- Cost per occurrence
- Monthly cost
- Annual cost
- Outcome or success measure
If every attendee has the same loaded hourly cost, the spreadsheet formula is straightforward:
=(Duration_Minutes/60) × Attendee_Count × Loaded_Hourly_Cost
For mixed teams, calculate each attendee group separately. For example, a meeting with two engineers and one product manager can use:
=(Duration_Minutes/60) × ((Engineer_Count × Engineer_Rate) + (Product_Count × Product_Rate))
Then multiply the result by the monthly meeting frequency. This approach is more useful than assigning one broad company-wide rate when the meeting includes people with materially different costs or responsibilities.
Inputs and assumptions
Attendee hourly cost
Choose a consistent basis. You can use salary converted to an hourly amount, an internal loaded labor rate, or a planning rate used for budgeting. The important point is consistency across the audit. If you use salary, document the working hours and pay period used in the conversion.
Burden rate
A burden rate accounts for employer costs and other labor overhead that are not included in base pay. If your hourly figure excludes these costs, apply the rate as follows:
Loaded hourly cost = base hourly cost × (1 + burden rate)
For example, a base rate of 40 with a 25% burden assumption becomes 50 per hour. Treat the burden rate as an internal planning assumption, not a universal benchmark. Update it when compensation structures, benefits, or budgeting conventions change.
Meeting frequency
Record the actual cadence rather than relying on the calendar label. A weekly meeting may occur four or five times in a month, while a daily weekday meeting may occur roughly 20 times. For annual planning, use the number of expected occurrences and account for known holidays or company shutdowns if those affect the schedule.
Value and outcomes
Cost alone cannot determine whether a meeting is worthwhile. Add a measurable or observable outcome, such as a decision made, dependency cleared, incident reviewed, customer issue resolved, or action owner assigned. If the meeting has no clear output, that is a useful audit finding.
| Meeting type | Typical purpose | Cost-control questions | Expected output |
|---|---|---|---|
| Standup | Surface blockers and coordinate near-term work | Can status be posted asynchronously? Who needs to attend live? | Blockers, owners, and immediate dependencies |
| Status review | Share progress across a team or project | Can a written update replace part of the meeting? | Shared understanding and escalations |
| Brainstorming | Generate or evaluate options | Are participants prepared, and is the decision scope narrow enough? | Prioritized ideas or next-step experiments |
| Sprint planning | Agree on scope, capacity, and commitments | Can pre-reading reduce live explanation time? | Selected work, owners, and assumptions |
Worked examples
These examples use illustrative assumptions so you can replace them with your own inputs.
Example 1: Weekly status meeting
Assume a 60-minute meeting with six attendees. The average loaded hourly cost is 55, and the meeting occurs four times per month.
- Cost per occurrence: 1 hour × 6 attendees × 55 = 330
- Monthly cost: 330 × 4 = 1,320
- Annual planning cost: 330 × 48 occurrences = 15,840
If the same outcome can be achieved with a 30-minute meeting attended by four people, the revised cost is 110 per occurrence. At four meetings per month, that is 440 monthly. The potential difference is 880 per month, before considering whether the smaller format changes the quality or speed of decisions.
Example 2: Daily standup
Assume a 15-minute standup with eight attendees, a loaded hourly cost of 60, and 20 occurrences per month.
- Cost per occurrence: 0.25 hours × 8 × 60 = 120
- Monthly cost: 120 × 20 = 2,400
A practical experiment might be to keep two live coordination sessions each week and move routine updates to a shared channel or tracker. Measure blockers resolved, response time, missed dependencies, and delivery impact before making the change permanent.
Calculating meeting ROI
A simple meeting ROI comparison is:
Meeting ROI percentage = ((estimated value created − meeting cost) ÷ meeting cost) × 100
Value may be difficult to express precisely, so use a decision-quality score, avoided delay, resolved incident, or other documented outcome when a financial estimate would be speculative. Do not assign a precise monetary value merely to make a meeting appear justified.
Meeting optimization checklist
Audit recurring meetings in this order:
- Inventory: Export or review recurring calendar events. Include internal, cross-functional, and customer-facing meetings that consume team capacity.
- Calculate: Apply attendee rates, burden assumptions, duration, and frequency. Sort the list by annual cost and by total attendee-hours.
- Define purpose: Write one sentence describing the decision, coordination need, or output that justifies the meeting.
- Set a KPI: Choose an observable measure, such as decisions completed, blockers cleared, action completion, or time to resolve an issue.
- Test a change: Try reducing duration, frequency, or attendees. Add an agenda and pre-reading so live time is reserved for discussion and decisions.
- Measure the result: Compare the selected KPI with the previous format. Keep the change only if the outcome remains acceptable.
- Document the decision: Record the new cadence, attendee rule, owner, and review date.
For teams working across time zones, an agenda, decision log, and action tracker can replace some live coordination. See the Async Team Communication Bundle for a structured starting point. If the audit reveals overlapping tools or unused subscriptions, pair it with a SaaS stack audit.
When to recalculate
Run the meeting cost calculator before creating any new recurring meeting. A one-time meeting may become recurring by habit, so estimate its cost before adding a repeating calendar series.
Perform a broader audit quarterly or before annual budgeting. Recalculate when team composition changes, compensation assumptions are updated, meeting frequency shifts, a project enters a new phase, or a recurring meeting loses its original purpose. Update burden-rate and internal planning assumptions at the start of each fiscal year or whenever finance revises them. Review recommended meeting durations and collaboration tooling annually rather than treating them as permanent defaults.
Save the spreadsheet with a dated version and retain the previous assumptions. That makes savings claims easier to verify and prevents a change in rates from being confused with a genuine reduction in meeting time. A useful recurring task is to compare current annual cost with the last audit, list the meetings changed, and record whether their outcomes held steady. This turns a meeting cost calculator from a one-off exercise into a practical team operating control.
