Claude Code for a chief of staff

Your job is making sure someone else always arrives prepared. That means you are the one doing the filing, the following up and the synthesis, usually across more threads than any one person should be tracking from memory.

A chief of staff sits in an unusual spot: you are a delegation role for the executive you support, and a filing-and-follow-up role for yourself. Everything that lands on your desk, a half-finished initiative, a promise made in a meeting you sat in on, a question three people are waiting on, has to be tracked, chased and synthesized before it ever becomes the clean brief your executive sees.

The volume is the actual difficulty. It is not any single thread that is hard to hold. It is that you are holding all of them, across every function the executive touches, while also being expected to notice the one thing that is quietly falling behind before anyone else does.

What makes the role harder than it looks from the outside is that you are often the only person who sees the whole picture. Each function lead sees their own slice clearly and nobody else's. The executive sees a summary, usually yours. You are the one place where the full set of threads actually converges, which means any gap in your own memory becomes a gap in the organization's memory, with no one else positioned to catch it before it turns into a missed commitment or a repeated question.

What changes with a system that files as you go

Status is the first place this pays off. Instead of chasing five function leads for an update before you can brief your executive, a status record that updates itself as work actually moves is the mechanic behind AI project status tracking that updates itself, and it turns "let me go find out" into "here is where it stands."

The brief itself is the second place. The overnight synthesis that becomes your executive's morning read, described on the AI daily brief, assembled overnight page, is exactly the kind of work a chief of staff does by hand today: pulling together what changed, what needs a decision, what can wait. Having the first draft assembled before you touch it does not remove your judgment from the process, it removes the hour of raw assembly that used to come before your judgment could even start.

Coordinating across functions that do not talk to each other

Much of the job is translation between groups that each hold half the picture: finance knows the budget reality, the function leads know what is actually happening on the ground, and the executive needs both reconciled into one honest view. When each of those inputs has to be manually chased and stitched together, the chief of staff becomes a bottleneck by definition, no matter how fast they work. When the raw material files itself as those groups do their normal work, the coordination job shrinks to what it should be: judgment about what matters, not data entry disguised as strategy.

Where this sits between two other roles

On one side is the executive you support, whose own relationship to this kind of system is covered on the executives page, worth reading so you understand what "already prepared" should look like from their seat, not just yours. On the other side, much of the actual filing-and-tracking work you do daily resembles what a founder does for themselves before they can afford to hire a chief of staff at all, covered on the founders page.

Judgment is the part that does not automate

None of this replaces the actual skill of the role, which is knowing what to escalate, what to handle yourself, and what to quietly let drop because it does not actually matter. What it changes is the amount of raw assembly you have to do before you can apply that judgment. A chief of staff who spends less time reconstructing what happened this week has more time for the part of the job that was always the hard part: deciding what the executive actually needs to know, and what can wait.

Setting it up

This runs on plain files and an assistant with permission to read the mail, meetings and threads that already cross your desk. If you would rather see it running for a real organization, or want help setting it up rather than building it yourself, that is a separate conversation, below.