A VA without Armbrain access spends their first month asking you the same questions your clients already answered. A VA with access is productive from day one. The difference is 20 minutes of setup.
Generate the VA Guide
For each client the VA will support, generate a tailored onboarding guide:
"Switch to Acme"
"Create an onboarding guide for my VA on this client"This produces a client-specific reference document with the VA's daily workflows, key stakeholders, active rocks, and current priorities. It's not a generic onboarding doc - it's built from what Armbrain actually knows about the client.
Do this for every client they'll touch. A VA supporting 5 clients gets 5 guides in 10 minutes.
Set Up Team Access
Add the VA as a team member with the right permissions:
"Add Jordan as a viewer for Acme"| Role | What They Can Do | When to Use |
|---|---|---|
| Viewer | Search memories, run meeting prep, view rocks and briefs | Default for new VAs |
| Editor | Everything a viewer can do + store memories, update rocks, add agenda items | After they've proven reliable |
| Owner | Full access including deletion and configuration | Only for senior team members |
Start with viewer access. Upgrade to editor after they've demonstrated they understand what belongs in Armbrain and what doesn't. A VA who stores noise is worse than one who stores nothing.
What to Delegate First
Don't hand them everything at once. Start with the tasks that have the highest leverage and lowest risk:
Week 1 - Read-only tasks:
- Run the morning briefing across all clients
- Prep meetings (review the brief, flag anything missing)
- Pull action item lists before your calls
- Search for answers when clients email status questions
Week 2 - Light capture:
- Ingest meeting transcripts after your calls
- Review extracted memories (promote/dismiss)
- Add quick notes for routine updates
Week 3 - Active management:
- Update rock status and sprint deliverables
- Add and manage agenda items
- Draft follow-up emails for your review
- Run weekly summaries
This progression lets you verify their judgment before giving them write access to your client knowledge base.
The VA Morning Routine
The morning routine is the VA's most valuable workflow. It takes 15 minutes and saves you an hour:
"What's happening across all my clients?"For each client with activity:
"Switch to [client]"
"What commitments are overdue?"
"Are there any meetings today that need prep?"The VA compiles a brief and sends it to you before your first call. You scan it in 2 minutes and know exactly where your day stands.
Point the VA to the Morning Routine guide for VAs for the detailed version.
How to Verify They're Using It
Trust but verify. Two ways to check:
Knowledge health check:
"How healthy is Acme's knowledge base?"If memories are growing, transcripts are being ingested, and action items are being updated - the VA is doing their job. If the knowledge base is stale, they're not.
Spot-check meeting preps:
Run a meeting prep yourself and compare it to what the VA sent you. If theirs is missing things, they're either not capturing enough or not reviewing extracted memories.
Common Mistakes to Watch For
| Problem | What You'll See | How to Fix |
|---|---|---|
| Storing noise | Memories like "discussed various marketing topics" | Show them what a good memory looks like - specific decisions, not summaries |
| Missing commitments | Action items from meetings aren't being captured | Review a transcript together, point out what they missed |
| Wrong client context | Memories stored to the wrong client mind | Emphasize always checking which client is active before storing |
| Over-classifying | Spending 5 minutes deciding if something is a "decision" or a "fact" | Tell them to use quick notes for speed, classify later |
| Not dismissing noise | Extracted memories accepted without review | Walk through one transcript's extractions together |
The most common failure mode is a VA who ingests transcripts but never reviews the extracted memories. The system extracts everything it thinks might be relevant - but 20-30% of extractions are noise or duplicates. If nobody dismisses the bad ones, the knowledge base gets polluted and meeting preps start including irrelevant context.
Scaling to Multiple VAs
If you have more than one VA or a small team:
- One VA per client cluster works better than one VA for everything. They build deeper context.
- Viewer access for all, editor access per assigned clients. A VA shouldn't edit clients they don't actively manage.
- Weekly sync on knowledge quality. Spend 5 minutes reviewing what was captured. It keeps standards high.
The team sharing model supports this naturally. Each VA sees only the clients they have access to, and Armbrain's client isolation ensures they can't accidentally leak data between clients.
The Day-One Checklist
| Step | Time | Command |
|---|---|---|
| Generate VA guide per client | 2 min each | create an onboarding guide for [VA] on [client] |
| Add VA as viewer | 1 min each | add [name] as a viewer for [client] |
| Share the VA guide series | 1 min | Link to the For VAs guides |
| Walk through one morning briefing together | 15 min | what's happening across all my clients? |
| Assign first task: tomorrow's meeting prep | 2 min | "Prep my meeting with [client] tomorrow" |
Total setup: 20-30 minutes. By tomorrow morning, you have a briefing waiting in your inbox that you didn't write.
Related Guides
- Your First Week with Armbrain - your own onboarding
- Handing Off a Client - the other end of the people spectrum
- Running Your Monday - the rhythm your VA supports
- Client Handoff - team access and sharing details