Claude Code for Virtual Assistants: Do More per Client

Claude Code for virtual assistants is the biggest change to VA work I have seen. I have hired and managed virtual assistant teams for years, including a team of ten in the Philippines, and the best VAs now pair their judgment with an AI that drafts, researches and documents for every client.

Claude Code for virtual assistants means keeping each client in a folder an AI agent reads before every task: their preferences, tone, contacts and recurring jobs. It drafts emails and replies, researches, writes SOPs and weekly reports. The VA reviews, sends and owns the relationship.

Here is the setup, the daily work it helps with, and the rules that keep clients' trust.

Why a folder per client changes VA work

The hard part of VA work is context switching: five clients, five tones, five sets of preferences. In a chat window you re-explain each client every time. In Claude Code, each client has a folder with a short brief, so every draft starts from that client's world.

• client.md: what they do, how they like to be written to, who matters, what never to do.
• recurring.md: the weekly jobs and how each is done.
• contacts.md: key people and how the client knows them.
• notes/: a running log of decisions and requests.

New to Claude Code? My Claude Code for business owners guide covers the setup without any coding. Supporting one executive rather than several clients? See Claude for executive assistants.

The daily work it takes on

Inbox and replies

Paste an email thread and ask for a reply in the client's voice, using their preferences from client.md. You check it and send it. For anything sensitive (money, legal, personal), draft and flag it for the client instead of sending.

Scheduling

Give it the request and the client's availability rules ("no calls before 10, keep Fridays clear") and ask for three time options and the confirmation message. If the client uses connected calendars, Claude can read them through connectors; start read-only.

For recurring meetings, ask for a short scheduling rules file per client: preferred days, buffer time between calls, which people always get priority and which meetings can be moved. Once those rules are written down, every scheduling draft follows them, and you stop double-checking the same preferences every week.

Research

Booking travel, finding a venue, comparing software, building a prospect list: ask for options with sources and the trade-offs in a short table. You verify the top choices before presenting them.

Ask for the research in a format the client can decide from in one minute: a short table with three options, the price, the main trade-off and your recommendation in one line. Clients hire assistants to make decisions easier, and a clear comparison does that better than a long list of links.

Documents

Meeting agendas, call summaries with action items, a quick slide deck, a cleaned spreadsheet. Claude can create real Word, Excel and PowerPoint files, so the output is ready to share.

Meeting notes are a quick win. Paste a transcript or your rough notes and ask for a summary with decisions, action items with owners and dates, and open questions. Send it to attendees within the hour and clients will notice the difference immediately.

SOPs: the habit that makes you indispensable

Every recurring task should have a written SOP. Record yourself doing it while you talk it through, paste the transcript, and ask for numbered steps with checks and "what can go wrong". When you go on leave or add a second VA, the client's work does not stop. I go deeper on documenting work in Claude Code for consultants.

Keep the SOPs in the client's folder, so they are the first thing a new team member or a backup VA reads.

The weekly report clients love

End each week with a one-page report per client, same shape every time:

A clear weekly report is the easiest way to show your value and justify a rate increase.

A worked example: one client's Monday

Here is a Monday for a made-up client, a busy agency founder.

client.md (fictional): Priya, agency founder. Short emails, no
exclamation marks. No calls before 10am. Fridays clear. Partners and
existing clients come first.

This morning: 14 new emails, two meeting requests, a request to book
flights for a conference next month.

Read client.md and contacts.md. Sort today's emails into reply now,
reply this week, Priya must decide and archive. Draft replies for the
first group in her voice. Offer three meeting times for each request
that respect her rules. Find three flight options for the conference
with price, times and baggage, in a table.

The sort puts the two partner emails at the top and flags a pricing question as "Priya must decide" rather than drafting a commitment for her. The meeting options avoid mornings and Fridays automatically. The flight table compares three options with a one-line recommendation. You review the drafts, send the routine replies, and give Priya a short list of the four things that need her, all before lunch.

Mistakes to avoid

• Sending on the client's behalf without a clear rule. Agree in writing which kinds of email you can send and which need approval.
• One folder for everyone. Client preferences and confidential details must never mix.
• Skipping the SOPs. Without written processes, every holiday or sick day becomes a crisis.
• Hiding that you use AI. Be open about your tools; clients care about results and confidentiality.
• Letting quality drift as you add clients. Use the weekly report to check that every client is still getting your best work.

Rules that keep client trust

• Confidentiality first. Keep each client's folder separate, check your contract before using AI on their material, and turn off model training in your Claude settings.
• Never paste passwords. Use a password manager share or delegated access, never credentials in a chat or file.
• Drafts, not sends, for anything that matters. Money, legal, HR and personal messages get the client's approval.
• Be open about tools. Tell clients you use AI to draft and research, and that you review everything.

Claude Code for virtual assistants: FAQ

How do I use Claude to work as a virtual assistant?

Create a folder per client with their preferences and recurring jobs, open it in Claude Code, and ask for one task at a time: a reply draft, three meeting times, a research table, an SOP or the weekly report. You review and send everything.

Will AI replace virtual assistants?

AI replaces the slowest parts of VA work, the drafting, formatting and searching, not the VA. Clients still need someone who knows their preferences, makes judgment calls and owns the result. VAs who use AI well can serve more clients at a higher standard.

Can I use Claude Code remotely?

You can use Claude Code from any computer with the Claude desktop app, and Anthropic also offers cloud sessions. Keep client files where your contracts allow, ideally on a work machine you control.

How much should a VA charge when using AI?

Price on the value and the outcomes you deliver, not the hours a task used to take. Many VAs move to monthly packages with a clear scope once AI makes them faster.

What tasks can a virtual assistant automate with Claude?

A virtual assistant can hand Claude the drafting and sorting work: email replies, meeting options, research tables, meeting notes, documents and weekly reports. Decisions, sensitive messages and client relationships stay with the assistant. If you support one executive rather than several clients, Claude skills for executive assistants has the inbox, brief and meeting prep skills to set up first.

Get the operator workspace

The AI Operator Kit gives you a ready workspace with commands for daily planning, outreach, client onboarding, SOPs from recordings and one-page client reports, plus 107 prompts sorted by job.