You Optimized Your Software Stack and Ignored the Meeting Eating It Alive

Here's a thing I've noticed talking to founders and team leads: they can tell you, to the dollar, what they spend on software every month. They know which tools are underused. They've read the subscription audits. They've killed the zombie apps.

And then they'll sit through the same weekly status meeting they've held since the company was four people, in a conference room that no longer fits the problem, and call it culture.

We've built an entire discipline around auditing our tools — and none around auditing our time. That's backwards, because your calendar is the most expensive subscription you have.

The Meeting Is a Subscription. Treat It Like One.

Run the numbers. A recurring one-hour meeting with six attendees, at a blended rate of $75 an hour, costs about $23,000 a year. You would never approve a $23K line item without an owner, a purpose, and a review date. But meetings don't come with invoices, so they don't get scrutinized. They just renew.

Every recurring meeting on your calendar is effectively a SaaS subscription: it has a cost, an owner, a set of features, and — crucially — a reason it was created. The difference is that software subscriptions at least send a receipt. Meetings just quietly compound.

So borrow the playbook. Give every recurring meeting three things it almost certainly doesn't have:

An owner. One person whose name is on it, responsible for deciding whether it still earns its keep. Not "the team." A human.

A renewal date. Every quarter, the owner has to actively justify the meeting's existence — what decision did it drive, what would have happened without it? If the answer is "nothing, really," the renewal fails.

Kill criteria. Written down at creation. This meeting ends when the product ships, when the pipeline exceeds X, when the new hire is ramped. Meetings without a defined end become furniture. Nobody remembers why the couch is there, but nobody moves it either.

The 3 PM Problem

There's a specific species of meeting that deserves special contempt: the 3 PM recurring sync that lands squarely in the middle of your team's deepest work window. Nobody chose 3 PM for focus reasons. It was chosen because it was empty when the invite went out two years ago.

For a small team, the cost isn't just the hour itself. It's the fragmentation. A 3 PM meeting means nobody starts anything ambitious after lunch, because why get into flow for 90 minutes of runway? The meeting doesn't cost one hour — it costs the whole afternoon on both sides of it.

And here's the part that stings for readers of a site like this one: many of us automated our workflows specifically to buy back time, and then immediately gave that time back to meetings. You built the Zap, cut the manual report, saved four hours a week — and filled them with syncs. The automation was a raise. The calendar spent it.

A Modest Proposal for Your Next Quarter

Try this instead of another productivity app trial: declare a one-quarter renewal cycle for every recurring meeting. Each owner gets 15 minutes to make the case in writing — purpose, attendees, cost, and what success looks like. Anything that can't make the case gets demoted to an async thread, a Loom video, or a doc comment. Nothing is permanent; anything worth doing can win its slot back.

Two things tend to happen. First, you'll find that a third of your recurring meetings were solving a problem that stopped existing months ago. Second, the meetings that survive get sharper, because their owners now have skin in the game.

Your software stack is lean. Your automations are humming. Now audit the thing that's actually consuming your team's hours. The calendar is not a junk drawer — it's your most expensive product decision, renewed every single week whether you're paying attention or not.