Claude Project Executive Assistant
Turn meeting transcripts into a continuously updated action system
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 7
- Confidence
- 98%
Create a Claude Project whose singular role is to act as an executive assistant for one workstream. Persistent project instructions define how it summarizes meetings, extracts decisions, formats actions, prioritizes deadlines, and drafts communications. A structured reference file establishes fields such as owner, description, due date, and deliverable, while incoming meeting transcripts supply new context. Claude combines newly extracted commitments with the existing action list, flags urgent or overdue work, and produces daily or weekly views on request. Completed items are removed and newly assigned work is added, preserving a running operational picture across chats. For complex responsibilities, use a separate assistant for each major project so its context remains focused. Keep outbound messages and shared-document updates under human control until reliable write-back integrations are available.
Origin
Extracted from Marketing Against The Grain as Kieran demonstrated a Claude Projects workflow that he planned to deploy across three large HubSpot pods.
Core principles
- 01Give each assistant one clearly defined responsibility
- 02Preserve operating instructions across conversations
- 03Convert every meeting into structured decisions and actions
- 04Track owners and deadlines in a consistent format
- 05Keep human control over outbound communication
- 06Separate assistants by project when context becomes complex
How to run it
- 1
Create a focused project
Create a Claude Project and assign it one role, such as executive assistant for a specific workstream. Use separate projects when unrelated teams or initiatives would create excessive context.
Pro tip Start with one active project and duplicate the pattern after its instructions work reliably.
Watch out A single assistant spanning too many unrelated projects can produce noisy priorities and confused context.
- 2
Define persistent operating instructions
Specify how the assistant should analyze meetings, manage follow-ups, communicate, and format its outputs. State explicitly whether it may suggest or draft follow-up messages without being asked.
Pro tip Include distinct requirements for summaries, action lists, email drafts, and shorter Slack messages.
Watch out Ambiguous autonomy rules can cause the assistant to generate follow-ups before you want them.
- 3
Provide the action schema
Upload a template or reference document showing the exact structure of the running action list. Require consistent fields such as owner, description, due date, and expected deliverable.
Pro tip Use a table so omissions and inconsistencies are easy to spot.
Watch out Actions without owners or due dates cannot be prioritized reliably.
- 4
Feed in meeting transcripts
Add each meeting transcript to the project, either immediately after the meeting or as a batch at the end of the day. Ask Claude to summarize decisions and extract every follow-up action.
Pro tip Daily batching reduces interruptions while still keeping the system current.
Watch out Do not upload sensitive transcripts unless the account and organizational data policies permit it.
- 5
Merge and prioritize actions
Have Claude combine newly extracted actions with the existing tracked items. Request views for today's urgent work, this week's commitments, overdue items, and relevant history or context.
Pro tip Begin each morning by asking for the most urgent tasks and the context behind them.
Watch out Verify extracted owners and deadlines against the transcript before treating them as authoritative.
- 6
Draft targeted communications
Request a specific communication only when needed, identifying whether it is a status check, task assignment, email, or Slack message. Include the owner, deadline, and desired confirmation behavior.
Pro tip Ask Slack drafts to be materially shorter than email drafts.
Watch out Review every draft before sending because the demonstrated workflow does not independently validate recipients or commitments.
- 7
Maintain the running record
Tell the assistant when actions are completed, reassigned, or given new deadlines so it can refresh the list. Copy the latest table back into a shared document when teammates need access.
Pro tip Run a brief end-of-day reconciliation to catch changes made outside Claude.
Watch out Claude could read connected documents in the demonstrated setup but could not write updates back to them automatically.
In the wild
A manager creates one Claude executive assistant for each of three large organizational pods. After meetings, each project receives its own transcripts and maintains a focused list of decisions, owners, deadlines, and follow-ups. Every morning, the manager asks each assistant for urgent work and supporting context rather than manually rereading notes from all three pods.
→ The manager receives project-specific daily priorities without blending unrelated teams or commitments.
After identifying an unassigned action, the manager asks Claude to draft a message that clearly names the owner, states the deadline, and requests confirmation. Once the assignment is made, the manager supplies the task and due date so Claude can add it to the running action list.
→ The responsibility becomes explicit in both the communication and the tracking system.
Common mistakes
Omitting due dates
A loosely structured action list prevents Claude from accurately identifying what is due today or this week. Require every tracked item to include an owner and deadline.
Allowing unsolicited follow-ups
If the instructions broadly request suggested messages, Claude may generate communications before they are needed. Constrain drafting to explicit user requests.
Assuming connected documents are updated
Reading a Google document does not mean Claude has written its revised table back to that document. Manually synchronize shared records until write-back is supported.
Is it for you?
Best for
It is best for managers coordinating several projects, meetings, and responsible owners at once.
Not ideal for
It is not ideal when actions must automatically update shared systems without manual review or copy-and-paste.
From the transcript
“think of projects as an AI assistant tasked with a singular thing, in this case, to be my executive assistant.”
“Then we're just adding all of our meeting transcripts.”
“And then we provided guidelines on what we want those follow up actions to, like, what format to keep those follow up actions in, and…”
From the episode
How To Use Claude As Your Executive Assistant (10-min to setup)