Inbox zero for CEOs: triage and draft replies in the terminal

An AI pass over your inbox that sorts the last day's mail into what needs you, what's just FYI, and what's noise, then drafts replies in your voice as Gmail drafts you review and send.

What you'll have when you're done

A morning ritual where, instead of re-reading 200 emails to figure out which 12 matter, you run one command and get a clean triage: the handful that need a real reply (with a draft already written in your voice), the ones to skim, and the noise. You read, tweak the drafts, hit send. The hour you used to lose to inbox archaeology becomes 15 focused minutes. The AI drafts; you always send.

The inbox tax is re-reading, not replying

The thing that actually eats your morning is not writing replies. It is the re-reading: scanning the same threads over and over to decide what deserves your attention, losing the important one under the newsletters, re-deciding things you already half-decided. That triage load is invisible and it is enormous, and it is exactly the kind of sorting an AI does instantly. I used to open my inbox six times before lunch and "process" it each time without actually doing anything, just re-reading the same forty threads and re-feeling the same low dread. The work was never the replies. It was the cost of holding an unsorted pile in my head all morning, paid over and over.

Connect a model to your inbox and it reads everything once, buckets it by what needs you, and drafts the replies that are mostly mechanical anyway. One genuinely reassuring design detail: the major AI email integrations let the model draft but not send on your behalf, so there is no risk of an AI firing off an email you never saw. You stay the sender. It just removes the sorting and the blank-draft friction.

What you need first

• Your email connected to AI: the Claude Google Workspace connector for Gmail, or a Gmail MCP server in Claude Code. Outlook works via the Microsoft 365 connector.
• A business/enterprise plan if your inbox carries sensitive threads (legal, M&A, personnel), so those are not used for training.
• A Claude Project holding a short "how I write" doc and a few reply templates.
• A few minutes to define your buckets (Needs-me / FYI / Newsletter is a fine start).

Step-by-step

Step 1Connect the inbox, read-only first

Set up the Gmail connector or MCP. Start with read and draft access only. You want to be confident in the triage before you grant anything more, and since the integration cannot send anyway, draft-access is the natural ceiling. Note that one connector typically binds to one Gmail account at a time, so decide whether you are pointing it at work or personal.

A few setup specifics save a frustrating first run. The native Claude Google Workspace connector is the simplest path: you authorize it once in settings and it covers Gmail and Calendar together, which you want anyway for the calendar workflow. If you live in Claude Code, a Gmail MCP server gives you more control but more setup. Either way, during the OAuth consent screen, grant read and compose scopes and decline send, if the option exists; the goal is a hard technical ceiling, not just a polite instruction. And point it at the account whose volume actually hurts, which for most CEOs is the work inbox, not personal.

Step 2Define the triage in a saved prompt

Write the instruction once:

Triage my last 24 hours of email. Bucket each into:
- Needs me: requires my decision or reply. For each, one-line summary plus a draft
  reply in my voice (see my writing doc), saved as a Gmail draft.
- FYI: I should know, no action. One-line summary only.
- Newsletter/noise: list senders, no summary.
Flag anything time-sensitive at the top.

Step 3Run it and read the triage

Run the prompt each morning. You get the three buckets and, for the Needs-me items, drafts already sitting in Gmail. Your job shrinks to: read the summaries, open the drafts that matter, adjust, send. The mechanical replies ("thanks, works for me," "looping in Sarah") are basically done.

Here is the shape of a morning's triage, illustrative:

⏰ Time-sensitive

• Board member Dana needs the updated cap table before her 2pm. Draft ready.

Needs me (4)

• Dana (board): wants the updated cap table before 2pm. Draft: "Hi Dana, attached, flag me if the new option pool looks off." [draft saved]
• Acme (key customer): raising a renewal concern. Draft acknowledges and proposes a Thursday call. [draft saved]
• Recruiter: candidate wants an answer by Friday. Draft asks for one more reference first. [draft saved]
• Co-founder: needs your call on the pricing change. No draft, this is a real decision, flagged for you.

FYI (6): two vendor invoices (forwarded to finance), a product update, three intro replies. No action.

Newsletter/noise (22): Stratechery, The Information, 20 others.

Notice the line that matters most: the co-founder's pricing question gets no draft. The triage correctly refused to put words in your mouth on a genuine decision, and instead surfaced it for you. That restraint is what separates a useful triage from one that lulls you into rubber-stamping things you should actually think about.

Step 4Edit the drafts, then send

Read every draft before sending, this is both quality control and the safety boundary. The drafts get the tone roughly right because the model has your writing doc; you make them exactly right. For anything sensitive or high-stakes, write it yourself; the workflow is for the volume, not the delicate one-percent. The time math is the point: the dozen routine replies that used to cost you a minute each of writing now cost a few seconds each of reading-and-sending, and the two emails that genuinely need your full attention now get it, because they are not buried under the twelve that did not.

Step 5Save it as a one-command routine

Once the triage prompt is dialed in, save it as a slash command or a scheduled routine so "triage my inbox" is one action, not a re-typed prompt. This is the step that turns a neat trick into a daily habit.

How you'll know it's working

Your time-in-inbox drops and your important emails stop slipping. The tell is qualitative too: you stop feeling the low-grade dread of an unprocessed inbox, because you know the triage already surfaced anything urgent. If a 60-minute slog became a 15-minute review, it is working.

When it breaks

• It mis-buckets things. Your bucket definitions are fuzzy. Tighten them with examples ("anything from the board is Needs-me").
• Draft replies sound off. The writing doc is thin. Add more real examples of how you actually reply.
• It surfaces too much as Needs-me. Tell it to be stricter, "only true decisions or replies, default to FYI when unsure."
• You worry it might send something. It cannot; the integration drafts only. But never wire up a separate auto-send tool for this; the human send is the whole safety model.
• Sensitive threads are flowing through a consumer plan. Move to a business tier before pointing AI at an inbox that holds legal or personnel mail.
• It drafts replies to threads you'd never answer yourself. It is being too eager. Tell it to draft only where a reply is clearly expected of you specifically, and to leave threads where you are cc'd or where someone else owns the response as FYI.
• The drafts are too long. The model writes more than you would. Add a length rule ("most replies are 1-3 sentences; match the brevity of my examples"), because a CEO's real replies are usually shorter than an AI's instinct.

Make it yours. The buckets should match how you actually sort. A founder who triages by relationship might want "Investors / Customers / Team / External" instead of the generic three. Someone drowning in a specific channel (recruiting, support escalations) can add a dedicated bucket for it with its own draft style. And if you have an EA or chief of staff, the highest-leverage version routes certain buckets to them: the AI triages, your EA works the "schedule this" and "send the standard reply" piles, and only the true Needs-me reaches you.

Where this fits in your harness

Inbox triage is the first of the daily-operations workflows. It pairs directly with an AI chief of staff for your calendar, inbox and calendar are the two systems that run your day, and feeds your daily executive brief, which can include the morning's triage. Together they are the core of the five workflows every CEO should install first.