The hour on your calendar is the receipt, not the bill. Here is how to price a recurring meeting properly, and which one to retire this week.
The Hour Is the Smallest Line Item
A founder I work with runs a $7M research and strategy firm. Twenty-four people, remote-first, four time zones. She keeps a clean P&L. She knows her gross margin to a decimal and can tell you what a billable hour costs to produce.
She had never once asked what her meetings cost.
That is normal, and it is not a discipline failure. Payroll gets planned. Software gets audited. Client hours get tracked to the quarter hour. Meetings simply happen, and everyone absorbs the cost quietly because it never appears on a single line.
Underneath the hour sit four costs nobody counts:
The eight minutes before, when nobody starts real work because the meeting is coming.
The twenty minutes after, when a dropped thread has to be picked back up from the beginning.
The five other people who were mid-task and are now mid-task again, so their next block starts with remembering.
The decision that got scheduled instead of made, and so did not get made this week.
That last one is where the money is, and it shows up nowhere.
What One Recurring Meeting Actually Costs
Use your own numbers, but here is the shape of it. Six attendees. Fifty minutes, scheduled for an hour. A blended loaded cost of $105 an hour, including salary, benefits, and overhead.
Six people times 0.83 hours times $105 is roughly $525 each time that room convenes. Weekly across 46 working weeks is $24,150. Add ten minutes of prep each and you are near $29,000 a year for one recurring meeting.
That is not an argument to cancel it. It is an argument to know what you are buying. $29,000 is a delivery coordinator, a chunk of a sales hire, or a month of a senior contractor. If the meeting produces a decision every week, it may be the cheapest thing in the building. If it produces a status update, you are paying senior salaries to read a document aloud.
Remote-first firms pay a premium here. In an office, a ten minute standup interrupted almost nothing, because everything nearby was already interruptible. Remotely, it lands in the middle of someone's best thinking. Two meetings on a Tuesday morning do not cost an hour. They cost the morning, because the ninety minute block that would have produced the client deck is now two fragments.
And the hidden one. A meeting that ends with "let's take this offline," where the offline routes to next week's meeting, has not consumed fifty minutes. It installed a seven day delay into your operating system, and will do it again next Tuesday. Ten decisions a year waiting an extra week is not a time management problem. It is why your launch slipped a month and nobody could say where the month went.
This Week's Test: The Meeting Ledger
One week. Twenty minutes a day. No new software.
List every meeting, recurring and one-off, including the fifteen minute ones. Short meetings hide because they feel free.
For each, record attendees, actual minutes (not scheduled), and one line on what came out. Name the artifact or decision. If nothing came out, leave it blank. Blank is data.
Compute cost: attendees, times minutes, divided by sixty, times your blended rate. Use $100 if you do not know it.
Label each meeting: Decision, Coordination, Information, or Relationship.
On Friday, sort by annualized cost (cost per occurrence, times frequency, times 46) and circle the top three.
Then apply the rules.
Information meetings become a written post at the same time, with a named author. Test for two weeks. If nobody notices, it was information.
Coordination meetings become a shared board or a five minute async check-in. Keep the slot only if a handoff actually failed without it.
Decision meetings survive, with two additions. The decider is named in the invite, and the outcome is recorded within 24 hours. A decision meeting with no written output will happen again.
Relationship meetings are real, and usually the ones founders protect for good reason. Keep them, shorten them, review them quarterly.
Then run the swap. Take the most expensive of your top three that is not a Decision meeting. Convert it for two weeks: same slot, written update instead of a call, one named owner. Put the review on the calendar before you cancel the invite, then follow through.
When the Meeting Is the Work
Some things cannot be written, and pretending otherwise makes a firm brittle. A hard conversation with a delivery lead who is three weeks from leaving. A kickoff with a client who needs to see how you handle a difficult room. A planning session where the argument produces the plan.
So the test is not "could this have been an email." Almost anything technically could. The test is whether presence changes the outcome. If two people in a room produce something a document and a deadline would not, that meeting is doing work. If they would produce the same thing apart, you are paying for a distribution mechanism.
What Are We Optimizing FOR?
The tempting answer is an emptier calendar. That is a vanity metric with a pleasant feeling attached, and firms that chase it end up with a leadership team that stopped coordinating and started guessing.
What you are after is the rate at which questions turn into owned answers. A meeting is one instrument for that. So is a document, a decision log, a standing owner, a threshold written into a policy. When you measure the calendar instead of the commitment, you cut the meetings that worked and keep the ones that did not, because the bad ones feel more productive.
So the question underneath the audit is not how do we meet less. It is what is this hour for, and is it still doing that.
The Control Question
Pick one meeting. Not three. Which recurring meeting will you convert to a written artifact for two weeks, starting Monday, review already on the calendar?
Before you do it, write one sentence: what would have to break for me to bring this back. That sentence tells you what the meeting is for. If you cannot write it, you have your answer, and you did not need the two weeks.
