Your Calendar Is a Legacy System
There’s something that happens when you’re a founder right now. You have more cognitive leverage available than at any point in history. Research agents running, AI tools working in parallel, the kind of output that used to require a team is now possible in a single afternoon. Which makes it all the more maddening when you can’t get to it.
Two weeks ago, I’d blocked Tuesday. Not casually. Intentionally. For the first time in weeks I had real work I wanted to accomplish — things that had been stacking up for months, some of them longer. I finally had the tools and the space to actually attack them.
By 10 am, two quick syncs had claimed most of it.
By noon, a check-in materialized in the last open slot.
By 4pm, I’d attended six meetings and written maybe 200 words.
I headed out to dinner that evening, thinking: I didn’t get any of it done. Again.
But I stopped being annoyed at the people who booked the meetings. I started asking what each one was actually doing. And every single one had the same job: collecting information so someone could make a decision. A status check. A loop that needed to close before the next step could happen. Information moving from one person to another through thirty minutes of scheduled time.
That’s it. That’s all they were.
On Wednesday, I blocked the time again and intentionally ignored everyone. I went and built agents to do it instead. A status reporter. A decision router. A check-in replacement. A financial outlook. All of them run on Claude Cowork, integrated with the business’s existing tools via a set of connectors.
I don’t know yet if “Tuesday” is fixed. I’ll tell you when I find out.
But the diagnosis got clearer. Every meeting on my calendar stopped looking like coordination. It started looking like a system I hadn’t built yet.
Turns out that’s true of every calendar. It’s not a scheduling problem. It’s debt. Every founder I’ve talked to has a version of Tuesday, the blocked afternoon that didn’t survive contact with the week, the work that keeps not getting done. The details change. The structure is always the same.
The calendar wasn’t designed for your company. It was designed to schedule shared physical resources in an era when coordination required presence. The hourly grid made sense when getting twelve people in the same room was the only way to move something forward.
Paul Graham named the problem in 2009. The hourly calendar is a manager’s tool. It assumes time is fungible, that an hour is an hour regardless of what came before or after it. That assumption works for coordination. It destroys creation. A single meeting, he wrote, can blow a whole afternoon by breaking it into two pieces, each too small to do anything hard in. That essay is nearly two decades old. Nothing about the calendar has changed since.
The work has changed. The calendar hasn’t.
Walk through the recurring meetings on your calendar and ask what each one is actually solving.
The weekly status meeting exists because no one built a system that surfaces project state without being asked. That’s what the status reporter does. It pulls from the tools the team is already working in, formats it for whoever needs it, and delivers it on a schedule. Nobody has to ask. Nobody has to attend.
The approval meeting exists because authority is undocumented, so decisions route upward by default until they hit someone willing to say yes. That’s what the decision router handles. It picks up the request, attaches the context, and moves it to the right person with everything they need to act. No sync required.
The quick check-in exists because the async channel isn’t reliably moving context between people, so the gap gets patched with scheduled time. That’s the check-in replacement. The loop closes automatically. No calendar invite, no thirty-minute block, no recovery window on the other side.
The financial outlook meeting exists because the numbers aren’t visible unless someone pulls them together and presents them. So I built an agent that does the pulling, formats the summary, and delivers it when it’s needed.
Every recurring meeting is a maintenance contract on a broken system. These four agents are my attempt to cancel four of those contracts.
The cost of running a company on interrupt-driven coordination is real, and almost no one measures it.
Gloria Mark at UC Irvine found it takes roughly 23 minutes to fully recover focus after an interruption. Not 23 minutes to finish the meeting. 23 minutes after it ends before the interrupted work resumes at depth. A calendar with four meetings spread through the day doesn’t cost four hours. It costs four hours plus four recovery windows. For a team of ten, that math compounds fast.
And because the cost never shows up on a P&L, it never gets treated as a cost. It hides in slower cycle times, lower quality decisions, and the persistent feeling that the work isn’t moving as fast as it should. Nobody looks at a week of meetings and calculates the recovery tax. They just wonder why output is falling despite everyone being busy.
That’s what I was doing every Tuesday. Not measuring it. Just absorbing it.
Building the four agents took a few hours. Claude Cowork connected to the tools we already use — Slack, calendar, project tracking, financials. The agents aren’t sophisticated. They’re doing simple things: pulling data that already exists, formatting it, routing it to the right place at the right time. The meetings were doing that work manually. Now the agents do it.
What I don’t know yet is whether it actually gives the time back. Whether the meetings stay gone or just get replaced by new ones. Whether the information lands the way it needs to or generates a different kind of follow-up. I’ll run it for a few weeks and report back.
But here’s what I already know. The meetings I cut weren’t valuable. They were necessary. There’s a difference. Valuable is something you’d protect. Necessary is something you do because the alternative doesn’t exist yet. The agents are the alternative.
If the alternative works, the meetings don’t come back.
I’m still in meetings. Some of them are genuinely irreplaceable. The conversations where something needs to be felt, not just communicated. The decisions where alignment can only happen in real time. Those exist. They’re maybe 20 percent of what most calendars contain.
The other 80 percent is sync debt. Coordination problems that were easier to schedule than to solve.
The question isn’t how do I have fewer meetings. It’s: what is this meeting compensating for? And then: can a system do that instead?
For four of mine, the answer was yes. Build took a few hours. If it works, I get every Tuesday back. Permanently.
That’s the trade I’m trying to make. I’ll let you know how it goes.
Chris Grimes is the founder of FundMore, an AI-native loan origination platform. FundMore builds agentic mortgage and lending infrastructure for institutional clients across Canada and the US.