Executive meeting prep: a brief for every meeting on tomorrow's calendar

Each evening an agent walks through the executive's calendar for the next day and prepares a brief per meeting: who is attending and their role, the last few interactions, commitments still open on either side, relevant documents, and the decision or outcome the meeting needs. The executive walks in prepared without asking anyone to assemble it.

01the problem and who owns it

Executives move between eight or ten meetings a day, internal and external, and arrive at many of them reconstructing context in the first five minutes. Commitments made in the last meeting with the same person get forgotten, which costs credibility that is hard to earn back.

The executive assistant owns the calendar and does what prep time allows, but assembling history across email, CRM, documents, and prior notes for every meeting is more than one person can sustain alongside scheduling and travel.

02what the AI does, step by step

1. Read tomorrow's calendarThe agent lists the next day's meetings with attendees, agenda text, and attached documents, skipping blocks the executive marks as personal or private.
2. Identify the peopleInternal attendees are matched to the org chart and their role. External attendees are matched to CRM contacts and accounts, with a short public profile summary where none exists.
3. Gather recent historyFrom permitted sources, it pulls the last few meetings with the same people, recent email threads, open CRM opportunities or support issues, and notes from earlier conversations.
4. Find open commitmentsIt extracts promises made on either side, such as "send the proposal" or "intro to our CFO", and checks whether they appear to have been completed.
5. State the purposeUsing the agenda and history, the brief names the likely objective and the decision or output needed. If the meeting has no clear purpose, the brief says so, which is useful in itself.
6. Deliver in one placeAll briefs for the day arrive together in the morning email or a pinned document, ordered by meeting time, each short enough to read in a minute.

03systems it connects to

• Calendar and email. Google Workspace or Microsoft 365, through scoped API access.
• CRM. Salesforce or HubSpot for external relationships, deals, and account history.
• Notes and documents. Meeting note tools, Google Drive or SharePoint, Notion or Confluence.
• HR system. The HRIS org chart for internal roles and reporting lines, without access to compensation or performance records.

04human checkpoints

• Source permissions. The executive and assistant decide which mailboxes, folders, and systems the agent can read, and exclude legal, HR, and board folders by default.
• Assistant review early on. For the first weeks, the assistant reviews briefs before the executive sees them and notes errors.
• Commitment follow-through. Open commitments the brief surfaces go to the assistant to schedule or delegate, rather than being actioned automatically.

05what to measure

• Brief accuracy. Errors flagged by the executive or assistant per week.
• Commitments closed on time. Open items surfaced by briefs and closed before the next meeting with the same person.
• Assistant prep hours. Time the assistant spends on meeting prep, before and after.
• Usage. Whether the executive actually opens the briefs, which is the honest test of value.

06risks and guardrails

• Over-broad mailbox access. An executive's email contains HR matters, legal advice, and deal information. Use read-only, scoped access, exclude sensitive labels and folders, and log every access.
• Privilege and confidentiality. Sending privileged legal communications to a third-party model can create risk. Keep counsel threads out of scope and confirm the model provider's data terms with your legal team.
• Wrong person matched. Two contacts with the same name can merge histories. Show the match basis in the brief and flag low-confidence matches.

07build vs buy

Calendar assistants and the AI features in Microsoft 365 and Google Workspace can summarize meetings and emails, and for an individual executive they may be enough.

A custom agent is worth building when the useful context lives in your CRM, support system, and internal documents together, when commitment tracking matters, or when you need tight control over exactly which sources are read.

08related playbooks

Browse every executive and leadership playbook or the full library.