Executive assistant EA Admin

Claude for Executive Assistants: Keep Executive Context Persistent

Executive assistants operate in a world of fine-grained, constantly-updating context: who the executive trusts, how they like their emails written, which board members to handle delicately, which vendors are on thin ice, what's landing on their desk next week.

Claude is genuinely useful for drafting, scheduling logic, research, and comms. The problem is it resets. Every session, you're re-explaining things that should just be known — who Sarah Chen is, why the Henderson account is sensitive right now, that the executive prefers bullet points over prose in briefing docs.

Stash gives Claude a persistent, searchable record store that you control. You brief it once. It remembers across every conversation.

What EAs store in Stash

What this looks like in practice

Draft a response to David Walsh at Pinnacle Capital asking for a breakfast meeting next month.

David Walsh — Pinnacle's MD, relationship is warm but he's been pushing for a larger commitment since Q1. The executive prefers to keep these meetings brief and breakfast is fine. Given the current fundraise timing, you may want to check whether this should go via the CFO first. Here's a draft that's friendly but non-committal on timing until you confirm...

That's Claude drawing on context it stored weeks ago — relationship notes, the fundraise situation, the executive's preference for routing investor conversations. No briefing paste.

Setting up in 30 seconds

Step 1 — Add the connector Claude Settings → Connectors → Add custom MCP server → paste https://app.stashlite.com/mcp → Save
Step 2 — Sign in with Google Claude will prompt you to authenticate. One click. Your private record store is provisioned automatically.
Step 3 — Start building your context library "Stash a record in 'exec-context' — key: communication_style, value: prefers 3-bullet briefings, never PDFs, always wants the ask in the first sentence."

Concrete use cases

1. The morning briefing

At the start of the day, ask Claude to pull together a briefing: what's on the calendar, any open threads from the day before, who's likely to call about what. Claude draws on your stored priorities and contact notes to make it relevant rather than generic.

2. Drafting sensitive correspondence

When a tricky email comes in — from a board member, a difficult client, someone the executive has history with — Claude can draft a response that reflects the relationship context you've stored. No explaining who they are or what the situation is.

3. Preparing the executive for meetings

"Brief me on the Henderson account before the 3pm call." Claude pulls the account notes, recent interactions, open issues, and the executive's last known position — in under a minute.

4. Tracking delegated actions

When the executive delegates something to a report, store it: "Stash in 'delegated' — to: James, task: follow up with the Barcelona venue by Friday, delegated: June 7." Check back in a week: "What's James supposed to have done by now?"

5. Standing instructions library

Build a searchable record of the executive's standing preferences: how to handle speaking invitations, which charity requests to pass on, which vendors they'll take calls from. Stop reinventing the wheel every time a similar request comes in.

Free tier and pricing

The free tier covers 2,500 records and 50 queries per month — enough for a comprehensive executive context library and daily use. Most EAs use Claude multiple times a day and move to Pro (£8/month) within the first few weeks. At that price, it's less than a daily coffee for a tool that saves an hour or more of re-briefing every week.

Add Stash to Claude — free, no credit card Paste this in Claude → Settings → Connectors → Add custom MCP server:

https://app.stashlite.com/mcp

Sign in with Google, done. Your executive context library starts with the next conversation.

A note on what to store

Stash is your working context layer — preferences, relationships, priorities, notes. Don't store sensitive personal information, credentials, or confidential documents. Keep it to the operational context that helps Claude be useful: how things work, who people are, what matters. The more accurately you capture that, the more useful Claude becomes across sessions.