Meetings That Exist Because They Always Have

Somewhere in your company calendar, a weekly meeting has run for 14 months straight. Nobody remembers why it started. Eleven people attend. Two of them speak. The meeting produces no documented decision — but canceling it feels riskier than keeping it.

Recurring meetings are the most visible form of coordination cost in a services firm, and the least examined. The Cost-Per-Workflow framework puts coordination cost at 30-50% of total workflow cost in firms between 30 and 100 people. A significant share of that cost sits inside standing calendar blocks that nobody has questioned since they were created.

The Eliminate-Before-Automate framework applies here with one adaptation. The original framework asks: has this step caught a real problem in the last 12 months? For meetings, the question sharpens: what specific decision does this meeting produce? If the answer is unclear — “alignment,” “visibility,” “staying on the same page” — the meeting is a candidate for elimination or replacement with something cheaper.

How much recurring meetings actually cost

At a 50-person services firm, recurring meetings consume 15-25 hours of collective staff time per week. The math becomes specific quickly.

Cendia mapped meeting cost at a 48-person marketing agency running $7.5M in annual revenue. The firm had 22 recurring meetings on the weekly calendar. We measured three things for each: who attended, how long it ran, and what decision it produced.

The bottom two categories — 14 meetings totaling 45 hours per week — cost $328,160 per year in staff time. Nobody in the firm had summed this number before. Each meeting felt small. In aggregate, the firm was spending more on meetings without clear decisions than on any single operational function except delivery itself.

Why bad meetings persist

Recurring meetings survive elimination for three structural reasons, all of which are diagnosable.

Missing decision rules. A weekly project status meeting exists because leadership wants to know which projects are at risk. The meeting runs 90 minutes every Monday with 8 attendees because no documented threshold defines “at risk.” If the firm documented the rule — flag any project more than 15% over budget or 5+ days behind schedule — the information could flow through a dashboard or a Slack alert. The meeting exists as a human substitute for a rule that was never written.

Missing ownership. A weekly cross-functional sync exists because two teams need to coordinate on shared clients. Both teams attend in full because nobody is assigned as the single point of contact between them. The meeting compensates for a missing role definition. Assign one person as the coordination point and the 8-person meeting becomes a 2-person check-in — or disappears entirely.

Institutional inertia. A biweekly all-hands started when the firm was 15 people and the CEO wanted everyone aligned on priorities. At 48 people, the meeting still runs. The CEO still presents. The content has shifted from decision-making to announcements that could be a 3-paragraph email. Nobody cancels it because the meeting has become part of the firm’s identity. Questioning it feels like questioning culture.

Each of these causes has a structural fix. Missing decision rules get documented. Missing ownership gets assigned. Institutional inertia gets addressed by measuring the cost and presenting it to leadership — most CEOs cancel a $50,000/year meeting when they see the number.

The elimination test

Eliminate-Before-Automate provides a clean protocol. For each recurring meeting on the calendar, ask four questions in order:

Question 1: What specific decision does this meeting produce? Write it in one sentence. “This meeting decides which client deliverables ship this week” passes. “This meeting keeps everyone aligned” does not. If you can’t name the decision, the meeting is an elimination candidate.

Question 2: Does the decision require real-time, synchronous conversation? Some decisions require debate — trade-offs between competing priorities, resource allocation with dependencies, client escalation responses where context changes fast. These decisions benefit from a meeting. Most status updates, progress reports, and information-sharing do not. If the meeting’s output could be a written document reviewed asynchronously, the meeting is replaceable.

Question 3: Does every attendee need to be there for the decision to happen? Most recurring meetings have 2-3 people who actively participate and 5-8 people who listen. The listeners are there “for visibility” — which means the meeting is doing double duty as a decision forum and an information broadcast. Split those functions. Make the decision with the 2-3 people who matter. Send the outcome to everyone else.

Question 4: Has this meeting caught a real problem in the last 3 months? The Eliminate-Before-Automate threshold is 12 months for workflow steps. For meetings, 3 months is more appropriate because meeting cadence is weekly or biweekly. If a recurring meeting hasn’t surfaced an issue that changed a decision in the last 3 months, it’s running on habit.

Any meeting that fails Questions 1 and 4 should be canceled. Any meeting that passes Question 1 but fails Questions 2 or 3 should be restructured — made async, reduced in scope, or reduced in attendance.

What the 48-person agency changed

After the elimination test, the agency made three categories of changes:

Canceled outright (5 meetings, 14 hours/week recovered): These were the meetings where nobody could name the decision. A weekly “creative sync,” two biweekly “team check-ins,” a monthly “operations review” that had become a status readout, and a Friday “wrap-up” that had devolved into casual conversation. Total annual cost eliminated: $102,480.

Replaced with async alternatives (6 meetings, 18 hours/week recovered): These meetings had identifiable decisions, but the decisions didn’t require real-time conversation. Project status updates moved to a Monday written summary in a shared channel. Client pipeline reviews moved to a shared dashboard with a flagging threshold. Resource allocation meetings moved to a weekly form submission. Total annual cost eliminated: $131,040.

Restructured (3 meetings, 13 hours/week reduced to 5): The weekly leadership meeting stayed but dropped from 90 minutes to 30, with a written agenda and a documented decision log. Two cross-functional meetings stayed but attendance dropped from 8-10 people to 3-4 decision-makers, with outcomes sent to the broader team afterward. Annual cost reduced by $58,240.

Total impact: $291,760 in annual coordination cost recovered. Meeting hours on the calendar dropped from 45 per week to 12. The firm redeployed the equivalent of 1.5 full-time employees’ worth of hours — without hiring anyone.

Each meeting felt small. In aggregate, the firm was spending more on meetings without clear decisions than on any single operational function except delivery itself.

What this isn’t

Scope notes:

• This isn’t an anti-meeting argument. Some meetings are the most efficient way to make complex decisions. The elimination test preserves those meetings and removes the ones that have outlived their purpose. The goal is fewer, sharper meetings — not zero meetings.
• This isn’t about meeting hygiene. “Start on time, have an agenda, end with action items” is useful advice. It also optimizes meetings that shouldn’t exist. The Eliminate-Before-Automate framework asks whether the meeting should exist at all before asking whether it runs well.
• This isn’t limited to large teams. A 30-person firm with 12 recurring meetings faces the same structural pattern. The dollar amounts scale down, but the per-person impact is often larger because smaller firms have less slack in their calendars.

FAQ

How many recurring meetings should a 50-person services firm have?

Cendia’s benchmark: 8-12 recurring meetings per week, each tied to a specific, documentable decision. Most firms start with 18-25 and can eliminate or restructure 30-40% through the four-question test.

What’s the fastest way to audit our meeting load?

Pull a list of every recurring meeting from your calendar system. For each one, write one sentence describing the decision it produces. Meetings where you can’t write that sentence in under 30 seconds are your first elimination candidates. The full audit takes 2-3 hours with your operations lead.

Won’t people resist canceling meetings they’re used to attending?

Resistance is common and usually lasts 2-3 weeks. The pattern Cendia sees: initial discomfort, followed by relief when people realize they have 5-8 hours per week back on their calendar. Framing matters — “we’re replacing this meeting with a faster way to make the same decision” generates less resistance than “we’re cutting meetings.”

How do we prevent new unnecessary meetings from accumulating?

Add a 90-day sunset to every new recurring meeting. When the 90 days arrive, the meeting owner must restate the decision the meeting produces and confirm it still requires synchronous time. If they can’t, the meeting expires. Most firms that implement sunset clauses see their recurring meeting count stabilize within two quarters.

This article is part of Cendia’s Hidden Costs series. Companion pieces cover Coordination Cost, the CEO Bottleneck, and the drowning ops manager — the operational patterns that compound as services firms grow past 30 people.