How to reduce recurring meeting waste in a growing team
A practical framework for auditing your recurring meeting stack and replacing low-value meetings with async workflows.
As SaaS teams grow, meetings multiply faster than headcount. A company with 20 people has no shortage of recurring syncs, standups, pipeline reviews, and all-hands. The problem is rarely that meetings are bad in principle — it is that the recurring meeting stack accumulates without any systematic review. Meetings that were useful at 10 people are still running at 40.
The real cost of a recurring meeting
A 60-minute weekly meeting with six people does not cost one hour — it costs six hours, every week, plus preparation time and context-switching overhead. For a team where individual contributors earn $80,000–$120,000 per year, a single weekly meeting with six people costs approximately $9,600–$14,400 per year in direct salary cost, before you account for the work that does not get done during that time.
Note
Meeting cost = (sum of attendee salaries / 2,080 working hours per year) × meeting duration × frequency × 52. A 30-minute biweekly meeting with four people at $100,000 average salary costs approximately $5,800 per year.
Step 1: Audit your recurring meeting stack
Start by listing every recurring meeting in your calendar, its attendee count, duration, and frequency. For each one, answer:
- 1What decision or output does this meeting produce?
- 2Could the same output be produced asynchronously (a shared doc, a Loom, a status update)?
- 3Who actually needs to be in this meeting versus who is informed out of habit?
- 4When did this meeting last produce a decision that required real-time discussion?
Step 2: Classify each meeting
| Type | Keep synchronous? | Async alternative |
|---|---|---|
| Decision meetings | Yes — if decisions require real-time input | Decision doc with async comments |
| Status updates | No — almost always async | Shared status doc or async video update |
| Pipeline reviews | Depends — if forecasting requires discussion | CRM dashboard with async notes |
| All-hands | Yes — for culture and alignment | Consider reducing frequency |
| 1:1s | Yes — relationship-dependent | Supplemented by async check-ins |
Step 3: Redesign high-cost recurring meetings
For meetings you decide to keep, apply a simple redesign framework:
- Cut the duration by 30% — most 60-minute meetings work equally well at 40 minutes
- Reduce the attendee list to decision-makers only — others receive the output async
- Require a pre-read or agenda at least 24 hours before the meeting
- End every meeting with explicit next steps assigned to specific people
- Review each recurring meeting quarterly — ask whether it still needs to exist
Step 4: Build the async infrastructure
Replacing meetings with async workflows requires investing in the infrastructure that makes async reliable:
- A shared status doc (Notion, Confluence, or a simple Google Doc) updated by each team member weekly
- A consistent format for async video updates (Loom or similar) with a standard structure
- Agreed response-time norms for async communication — not 24/7, but defined
- A clear protocol for when something must be escalated to a synchronous meeting
Tip
The most effective async transition is not eliminating meetings — it is raising the bar for what justifies a meeting. If a decision can wait 24 hours for async input, it probably should.
Still calculating commissions in spreadsheets?
Join the waitlist for early access to the Toolsmith Commission Tracker plus free tools.