An AI chief-of-staff for your calendar

An AI that reviews your week the way a great chief of staff would: flagging conflicts and back-to-backs, defending your deep-work time, and briefing you on every meeting before it starts.

What you'll have when you're done

A weekly and daily calendar review you did not have to do yourself. The AI looks at the week ahead, flags the problems (double-bookings, five meetings with no gap, calls with no agenda), proposes focus blocks, and for each external meeting tells you who you are talking to and why, pulled from your recent email with them. You walk into every meeting prepared and into every week with your priorities actually protected on the calendar.

You are doing a chief of staff's job in the cracks of your day

Most CEOs without a chief of staff manage their own calendar reactively: accept the invite, notice the conflict too late, realize at 1:59 that you have no idea what the 2:00 is about. The calendar runs you instead of the other way around. I have walked into a meeting, sat down, and quietly searched my own email under the table to remember who the person was and what we last said, while they assumed I had prepared. It is a small, specific embarrassment, and it happened often enough that I stopped pretending it was a discipline problem. The information existed; I just had no system that put it in front of me at the right moment. A great chief of staff fixes this by looking ahead, protecting your time, and prepping you, and that role is largely pattern-reading over your calendar and inbox, which AI does well.

Connected to your calendar and email, a model can review the week, surface the problems while you can still fix them, and brief you per meeting. The important discipline: give it read access first and let it propose, not act. You want it flagging "these two overlap, want me to suggest a fix?" before you ever let it touch the calendar directly.

What you need first

• Your calendar connected: the Claude Workspace connector or a Google Calendar MCP server. Outlook via Microsoft 365.
• Granola or your notes tool so it can pull context on who you are meeting.
• A business plan if your calendar reveals sensitive deals or people.
• A decision to start read-only. Write access (moving/accepting meetings) comes later, if ever.

Step-by-step

Step 1Connect calendar and inbox, read-only

Set up the calendar connector with read access. Resist granting write access on day one. A model that can read your week and propose fixes is almost all of the value with none of the "it moved a meeting I needed" risk. You can always grant more once you trust it.

Step 2Run the weekly review

Each Sunday or Monday, ask it to review the week ahead:

Review my calendar for next week. Flag: double-bookings, stretches of 3+ meetings
with no buffer, and any meeting with no agenda or unclear purpose. Propose two
2-hour focus blocks in the open gaps. For each external meeting, tell me who the
person is and our recent context, pulled from my email with them. Propose only;
do not change anything.

What comes back is a chief-of-staff's Monday memo: here are the problems, here is your protected time, here is who you are seeing and why. Illustrative:

Conflicts and crunches

• ⚠️ Tue 2:00: investor call and product review are double-booked. One has to move.
• Wed is six meetings back-to-back, 9am to 3pm, no lunch, no buffer. Suggest shortening or dropping the 11:00 sync (recurring, usually light).
• Fri 4:00 "quick chat" has no agenda. Suggest asking for one or declining.

Proposed focus blocks

• Tue 9:00-11:00 (before the day fills) for board-deck work.
• Thu 2:00-4:00 (the only open 2-hour gap) for the hiring-plan review.

External meetings

• Wed 10:00, Sarah Chen (Acme), your renewal call. Last email: she asked about the API roadmap and cares about uptime.
• Thu 11:00, intro from [investor]: a founder raising a seed. No prior context; here is their site.

Read that and your week is already half-managed before it starts. The double-booking you would have hit at 1:59 on Tuesday is a Monday-morning fix instead of a Tuesday-afternoon scramble.

Step 3Defend the focus blocks

The proposed focus blocks are the highest-value output, because protecting deep-work time is the thing CEOs always intend and never do. Put them on the calendar as real holds. The AI found the gaps; you make them sacred. The practical trick is to book them before the week fills, which is exactly what the Monday review is for: an open Tuesday morning is yours to claim on Monday and gone by Wednesday once meetings find it. Treat the block as a meeting with the most important person at the company, because in the sense that matters, it is.

Step 4Get the per-meeting brief

Pair this with a per-meeting brief that fires before each call (the same idea as a pre-meeting brief): who is in the room, what you last discussed, what they care about. Walking in cold to a meeting becomes a thing of the past, and you did zero prep. Illustrative, the brief for the Wednesday renewal call:

10:00 · Sarah Chen, VP Ops, Acme · Renewal call

• Relationship: customer 14 months, renews end of quarter. Healthy but not effusive.
• Last touch (your email, 9 days ago): she asked whether the API rate limits are changing. You said you'd confirm. You have not followed up, close that loop on the call.
• Open thread from your last QBR (Granola): she flagged that onboarding new analysts is still slow.
• Likely agenda: renewal terms; watch for the rate-limit and onboarding concerns as friction.

That brief took the AI seconds and would have taken you ten minutes of digging through email and notes, which is exactly why you never did it and walked in cold instead.

Step 5Decide carefully about write access

Only after the read-only version has earned your trust should you consider letting it accept or move meetings, and even then, scope it tightly (maybe it can propose-and-you-one-click-approve). Never let it auto-accept on your behalf; a wrongly-accepted meeting is exactly the kind of small disaster that erodes trust in the whole setup.

How you'll know it's working

You stop being surprised by your own calendar, no more "wait, these overlap" at the worst moment, and you stop walking into meetings unprepared. The deeper win: your focus blocks actually survive the week, because something is watching for the meeting that would have eaten them.

When it breaks

• It misreads recurring or all-day events, or botches a timezone. Common failure. Tell it your timezone explicitly and spot-check anything it flags around recurring events.
• The per-meeting context is thin. It needs more to read; connect Granola and ensure it can see the relevant email thread.
• It proposed a focus block on top of something. It is proposing, not acting; you catch it in review. That is the point of read-only.
• You are tempted to grant write access early. Wait. The read-only version is most of the value; write access is where the real risk lives.
• It proposes focus blocks you never actually defend. The tool found the time; you kept letting meetings land on it. The fix is behavioral, not technical: put the blocks on as real holds with a title that makes people hesitate ("Deep work, do not book"), and treat a request to move one the way you would a request to move an external meeting.
• The weekly memo flags everything as a problem. Your thresholds are too sensitive. Tell it what "normal" looks like for you ("3 back-to-backs is fine, flag 5+"; "standing 1:1s don't need agendas"), so it surfaces real issues instead of nagging.

Make it yours. The right cadence depends on how your week is shaped. A heavily externally-facing CEO (lots of sales, fundraising, partnerships) gets the most from the per-meeting briefs and should run them daily. A more internally-focused operator gets more from the focus-block defense and the conflict-flagging, and can run the full review just weekly. Tell the model which meetings actually need prep (external and first-time, usually) so it does not waste effort briefing you on your standing team sync.

Where this fits in your harness

Calendar is the second of the two systems that run your day, alongside the inbox. The per-meeting briefing connects to the broader Granola meeting pipeline, and the whole picture rolls up into your daily executive brief. These together form the backbone of the five workflows every CEO should install first.