🧠 Build Your AI Chief of Staff Workflow

TL;DR — Too Long Didn’t Read

• The problem: Managers spend an estimated 28% of their workweek on email alone, and a significant chunk of the rest on meeting prep and admin work that AI can now handle.

• The solution: A small stack of AI tools — primarily Claude connected to your Google Workspace — that triages your inbox, preps your meetings, summarizes your docs, and organizes your day before you've had your first coffee.

• The core tools: Claude (with Google Workspace connectors), Reclaim.ai for calendar protection, and a meeting notetaker like Read.ai or Fireflies for post-meeting summaries.

• The workflow: Run a morning triage prompt. Check your meeting prep brief. Upload any docs that need reviewing. Let AI draft responses you approve. Protect your focus time.

• The honest caveat: AI handles the information load. The judgment, relationships, and decisions still sit with you.

1. What Is an AI Chief of Staff Workflow

An AI chief of staff workflow handles information processing tasks such as email triage, meeting preparation, document summarization, and daily planning before human decision-making.

Precisely this covers four key areas of work:

1. Email triage — scanning your inbox, categorizing by urgency, drafting responses, and surfacing only what actually needs your attention.

2. Meeting prep — pulling context from emails, documents, and past notes before a meeting so you walk in with the background you need.

3. Document summarization — compressing lengthy reports, proposals, and threads into the key points and actions, without you reading every word.

4. Day planning — translating your tasks, meetings, and priorities into a workable daily structure.

None of these require a dedicated AI assistant product. With Claude connected to your Google Workspace, most of this is available today through a standard subscription.

2. The AI Chief of Staff Tech Stack

Claude (with Google Workspace connectors)

Claude is the central tool in this stack. It connects directly to Gmail, Google Calendar, and Google Drive — meaning you can ask it to read your emails, check your calendar, and pull documents without leaving the conversation. This is what makes it function as a real chief of staff rather than just a writing assistant.

Claude's Google Workspace connectors are available on Claude.ai and Claude Desktop for all users. To connect them, go to your Claude settings, find the connectors section, and authenticate your Google account. Once connected, Claude can read emails, surface calendar events, and access files in Drive when you ask it to.

What Claude does well: Long-form summarization, drafting in your voice, pulling context across multiple documents or threads, and holding a lot of information in a single conversation.

Reclaim.ai

Reclaim connects to Google Calendar (or Outlook) and automatically blocks time for your priorities — deep work, habits, and tasks — working around your meetings. It defends those blocks when new meetings try to take over, and reschedules when your calendar shifts.

It's not an AI assistant in the conversational sense. It's more like a calendar optimizer that runs in the background. Think of it as protecting the time you free up by offloading email and prep to Claude.

Pricing: Free tier available. Pro starts at $8/user/month.

A Meeting Notetaker (Read.ai, Fireflies, or Fellow)

These tools join your Zoom, Google Meet, or Teams calls, transcribe the conversation, and generate summaries and action items afterward. They feed back into your chief of staff workflow — you can paste their summaries into Claude to draft follow-up emails or track open items.

Read.ai is particularly strong for managers because it tracks engagement patterns and surfaces insights across meetings over time.

Fireflies is solid for teams who want searchable transcripts and keyword tracking.

Fellow adds agenda collaboration and manager-specific features like one-on-one templates.

Optional: Superhuman (for email-heavy roles)

If email volume is your primary bottleneck, Superhuman is worth considering. It's an email client built for triage speed — keyboard shortcuts, split inbox, AI-drafted replies — and cuts the mechanical overhead of email processing. It doesn't replace Claude for analysis or summarization, but it makes the email interface itself faster.

Pricing: $30/month. Gmail and Outlook only.

3. How to Use AI for Email Triage

What to do

Connect Claude to Gmail using the Google Workspace connector. Then, instead of opening your inbox first thing in the morning and reading every subject line, start a conversation with Claude and run your triage prompt.

The triage prompt

This gives you a structured view of your inbox in under two minutes of reading, instead of thirty minutes of clicking.

What to do with the output

Review Claude's categorization. Correct anything it got wrong — over time, being specific in your prompt about what counts as noise vs. important trains you to give better instructions. Approve and send the drafted replies you're happy with. Add your edits to anything that needs a personal touch.

The key rule here: Claude drafts, you approve. Never set up any workflow where AI sends email on your behalf without your review. Beyond the obvious risk of errors, it removes the signal that a real person is behind the message.

Best practices

Be specific about what counts as urgent. Your triage prompt works better when you tell Claude who your most important contacts are, what projects are live right now, and what types of requests need same-day responses. You can paste this context at the start of a new conversation or save it in a Project in Claude.

Run triage twice a day, not continuously. Checking email constantly is the habit you're trying to break. A morning triage and an afternoon check is enough for most roles.

Use email aliases if your domain supports them. Routing newsletters to a separate alias ([email protected]) makes the triage dramatically more accurate because the noise is already separated before Claude sees it.

What this looks like in time

The goal is to get from 60+ minutes of scattered email checking to a 10-15 minute structured triage session. The actual reading and responding gets compressed. The decision-making — which emails get real attention — stays with you.

4. How AI Prepares You for Meetings

What to do

Before any significant meeting, run a prep prompt in Claude that pulls context from your email and calendar. The output is a two-minute brief you read before joining.

The prep prompt

If you have a document related to the meeting — an agenda, a proposal, a project brief — upload it to Claude alongside this prompt and ask it to incorporate the file into the brief.

For recurring meetings

One-on-ones and weekly team standups benefit from a slightly different prep approach. Keep a running document in Google Drive or Claude Projects with notes from previous sessions. Before each meeting, ask Claude to pull that document and summarize what was discussed last time, what was committed to, and what's been resolved vs. still open.

This means you walk into a one-on-one actually knowing what you said you'd follow up on two weeks ago, without having to dig through notes.

Best practices

Run prep 15 minutes before the meeting, not the night before. Context is most useful when it's fresh. A brief you read at 9:45am for a 10am meeting is more useful than one you forget you read the night before.

Don't skip the document upload step. Claude's meeting prep gets meaningfully better when it has the actual agenda or background document to work from, not just email history. If there's a proposal on the table, upload it.

After the meeting, use your notetaker's summary as input. Once Read.ai or Fireflies gives you the transcript summary, paste it into Claude and ask: "Based on this meeting summary, draft a follow-up email to the attendees with the decisions made and action items. Keep it under 150 words." This closes the loop without you writing the recap from scratch.

5. How to Use AI for Document Summarization

What to do

For any document you need to engage with — a report, a proposal, a lengthy email thread, a contract — upload it to Claude and ask for a targeted summary. The key is being specific about what you need out of it.

The summarization prompt (better than just asking Claude to "summarize")

This is meaningfully better than asking Claude to "summarize" because it tells Claude what dimensions matter to you. A summary of a financial report looks different from a summary of a vendor proposal, even if they're the same length.

For email threads

Long email chains are one of the most time-consuming things managers deal with. Claude handles these well. Paste the thread into a conversation (or let Claude pull it via Gmail if it's recent) and ask:

For documents in Google Drive

If the document lives in Drive, you can ask Claude directly: "Find the document called [Title] in my Google Drive and summarize it using the framework above." This works with the Google Workspace connector active.

Best practices

Be specific about your role in the document. If you're a reviewer vs. a decision-maker vs. just being kept in the loop, your summary needs will be different. Tell Claude upfront: "I'm being asked to approve this proposal — tell me what I need to know to decide."

For high-stakes documents, read the sections Claude flags. Claude's job is to reduce what you have to read, not eliminate reading entirely. If Claude says "section 4 contains a clause you should review personally," read section 4.

Build a document library in Projects. Claude Projects let you upload reference materials that persist across conversations. If you're regularly working with a particular vendor, client, or internal team, upload the key documents once and reference them in future conversations without re-uploading.

6. How AI Organizes Your Daily Schedule

What to do

Start each morning with a planning prompt that synthesizes your calendar, outstanding email actions, and any tasks you're tracking. The output is a prioritized agenda for the day.

The planning prompt

What Reclaim.ai adds to this

While Claude gives you the plan, Reclaim.ai enforces it on your calendar. It automatically blocks focus time around your meetings, reschedules those blocks when meetings shift, and surfaces time for recurring habits like weekly reviews or project check-ins.

The combination works like this: Claude tells you what your priorities are and how to structure the day. Reclaim makes sure your calendar actually reflects that structure instead of defaulting to back-to-back meetings.

Best practices

Set your weekly priorities on Monday, not daily. Run a slightly longer planning prompt at the start of the week that sets your top three priorities. Then your daily planning prompt can reference those priorities rather than starting from scratch each morning.

Protect at least one two-hour block for deep work. Reclaim can do this automatically. If your calendar doesn't have this built in, AI planning loses much of its value — you'll have clarity on priorities but no time to act on them.

Use the end-of-day check-in. A quick prompt at 4:30pm — "What didn't get done today that I said I would? What needs to move to tomorrow, and what can I drop?" — takes three minutes and keeps your task list from becoming a guilt ledger.

7. A Sample Daily Workflow

Here's what a realistic AI chief of staff routine looks like for a manager:

7:30am — Morning triage (10 minutes) Open Claude, run the email triage prompt. Review the output. Approve any drafted replies. Note the Action Required items.

8:00am — Day planning (5 minutes) Run the planning prompt with your calendar and action items from triage. Reclaim has already blocked your focus time. Claude gives you the order of priorities.

9:45am — Meeting prep (3 minutes per meeting) Before each significant meeting, run the prep prompt. Upload the agenda if there is one.

Throughout the day — Document summaries as needed Any document that lands in your inbox goes to Claude before you read it. You read Claude's summary first, then decide whether to go deeper.

Post-meeting — Follow-up drafts (5 minutes) Paste your notetaker's summary into Claude. Get a draft follow-up email. Edit and send.

4:30pm — End of day check-in (3 minutes) Quick prompt on what's open, what moves to tomorrow, what drops.

Total active AI time: roughly 30 minutes spread across the day, replacing what was previously 2-3 hours of scattered processing.

8. Next Steps: Going Beyond the Basics

Once the core workflow is running, there are a few directions worth exploring.

Save your prompts as reusable templates. Claude Projects let you store instructions and context that persist across sessions. Build a project for your chief of staff workflow, save your triage prompt, planning prompt, and prep prompt there, and reference them daily without retyping.

Build a personal knowledge base. Upload your key reference documents to a Claude Project — org charts, project briefs, client context, strategic plans — so Claude can pull from them in any conversation without you re-explaining the background.

Automate recurring summaries with scheduled tasks. Claude Desktop's scheduled tasks feature lets you set up a recurring prompt that runs automatically. For example: every Monday at 7am, run a weekly review prompt that surfaces your top three priorities and flags any unresolved items from last week.

Add a CRM connector. For roles where client relationships are central, tools like Alfred or Carly extend the chief of staff workflow into CRM data — surfacing contact history, deal status, and follow-up items alongside your calendar and email context.

Start delegating research. Once you're comfortable with the core triage and prep workflows, extend into having Claude do preliminary research before important decisions — competitive landscape summaries, background on a new vendor, synthesis of a topic you need to brief your team on. The same summarization skills apply; it just takes a different kind of prompt.

9. What AI Cannot Do (Yet)

This workflow is practical and available today, but it has real limits worth naming.

It cannot read political context. Claude can tell you what was said in a meeting. It cannot tell you what it meant, who's frustrated, or where the interpersonal tension is. That reading still requires you.

It cannot make judgment calls. AI can flag that an email is urgent. It cannot judge whether the person sending it is reliable, whether the request is reasonable, or how to navigate the relationship. That's yours.

It cannot build trust for you. A follow-up email drafted by AI and sent without thought lands differently than one that reflects genuine engagement. People notice. Use AI to draft, but make sure the final message sounds like you and reflects what you actually think.

Accuracy is not guaranteed. Claude can misread tone, miss context, or categorize something incorrectly. The review step in every workflow above isn't optional — it's the safeguard that keeps this system trustworthy.

10. FAQs

Is it safe to connect Claude to my Gmail and Calendar? Claude's Google Workspace connectors use OAuth, the same authentication standard that other Google-connected apps use. Claude does not store your emails — it reads them within the conversation to respond to your prompt. For sensitive organizational email, check your company's policy on third-party AI tool connections before setting this up.

Do I need a paid Claude subscription for this? The Google Workspace connectors are available to all Claude users, including the free tier. However, the free tier has message limits. For daily professional use, Claude Pro ($20/month) is practical — it gives you priority access and higher limits.

What if I use Outlook instead of Gmail? Claude's Google Workspace connectors work with Gmail and Google Calendar. If you're on Outlook and Microsoft 365, Microsoft Copilot is the equivalent tool — it's natively integrated into Outlook, Teams, and the rest of the Microsoft suite. The workflow principles in this guide apply, but the specific setup differs.

Will AI make mistakes in my emails? Yes, sometimes. Which is why the rule is always draft, never auto-send. Every email Claude drafts should be reviewed before it goes out. Over time, you'll develop a sense for where Claude's drafts need editing (usually: making the tone feel more like you, adjusting anything nuanced) and where they can go out with minimal changes.

How long does it take to set this up? The Claude connector setup takes about five minutes. Writing your first triage and planning prompts takes another 15-20 minutes — most of that is thinking through what you actually want in the output. The workflow becomes habitual within a week.

Can I use this with a team? Yes. The principles work at the individual level, but teams can share prompt templates, run collective meeting prep (each person runs the same prep prompt for a shared agenda), and use Fellow or Read.ai to create shared meeting notes that Claude can then pull from. Claude's Team plan adds admin controls and shared projects.