Your AI Chief of Staff — Set Up an AI Assistant That Actually Runs Your Week
Most founders use AI like a vending machine: fresh chat, generic answer, forget everything. The upgrade is a persistent assistant with context — your business model, clients, priorities and voice — that briefs you weekly, drafts in your style, and carries tasks across sessions.
The setup is a weekend of writing context files plus rituals that keep them current. After that, every AI interaction starts from "already knows your business" instead of "please explain your business again".
The short answer
- Context files cut per-task prompt time dramatically and improve output quality — the assistant stops guessing your business each session.
- A weekly briefing ritual converts AI from a Q&A tool into an operating cadence.
- Delegation quality lives in the brief: role, context, constraints, format. Assistants fail on vague requests exactly like people do.
Who this playbook is for
Built for solo founders who use AI ad-hoc and want a persistent assistant that knows their business.
Step 1: Write the three core context files
Business.md: what you sell, to whom, prices, current priorities. Clients.md: active clients, statuses, sensitivities. Voice.md: three writing samples, phrases you use, ones you ban. One page each, in a project folder your AI tool reads (Claude Projects, custom GPT, or files you paste). This is the entire foundation — quality here determines everything downstream.
Step 2: Set the weekly briefing ritual
Monday, 15 minutes: paste the week’s calendar, pipeline state and top three priorities; ask for a briefing — conflicts, prep needed, realistic capacity warnings, suggested order. The ritual turns AI from reactive to proactive, and the briefing quality improves every week the context files stay current.
Step 3: Build delegation prompts for your five repeat jobs
Saved prompts with structure: role ("you are my ops manager"), context (auto: the files), task, constraints, output format. Typical five: email drafting, client update writing, research briefs, meeting prep, decision framing (options with tradeoffs). Named and saved, so delegation is one paste, not an essay.
Step 4: Run a weekly context update
Friday, 10 minutes: update Clients.md statuses, Business.md priorities, and anything new in Voice.md. Stale context is the failure mode — an assistant briefed on last quarter’s priorities actively misleads. The update ritual is small; skipping it quietly breaks everything.
Step 5: Draw the assistant’s boundaries
It drafts, summarizes, researches, frames decisions; it never sends, never touches credentials, never makes commitments, and its numbers get verified before use. Write the boundaries in the project instructions themselves so every session inherits them. Trust compounds when the failure modes are designed out.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Setup weekend | Write and test the three context files | half day |
| Monday | Weekly briefing ritual | 15 min |
| Daily | Delegate through saved prompts | as needed |
| Friday | Context update ritual | 10 min |
| Monthly | Prune prompts that stopped earning their place | 20 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Context files freshness | Updated weekly | The leading indicator of everything else |
| Repeat-context prompting | Near zero | You should never re-explain your business |
| Delegation save rate | Drafts kept 70%+ | Below that, prompts need structure not effort |
| Friday ritual adherence | Weekly | The keystone habit of the whole setup |
Common mistakes to avoid
- Writing context files once and never updating. A stale chief of staff is worse than none — it confidently briefs you on a business that no longer exists.
- Delegating fuzzy tasks. "Help with marketing" produces mush; "draft 3 subject lines for the pricing email, under 40 chars, no exclamation marks" produces value. Structure is the skill.
- Letting the assistant make commitments. Calendar says yes, invoice says maybe, client reads a promise — commitments flow only through you, permanently.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Claude Projects / custom GPTs | Persistent context without re-pasting |
| Notion / Obsidian | Where the context files live and version |
| Your calendar + pipeline export | The Monday briefing inputs |
| A prompts library doc | The named delegation prompts |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- The Automated Content Calendar
- The AI Proofreading Workflow
- AI Data Enrichment for Lead Lists
FAQ
Q: Which AI tool should be the chief of staff?
Whichever you will actually use daily — switching costs are low because your context files are portable. Prioritize: project-based context (so files persist), long context windows, and your familiarity with its editing style. The files matter more than the brand.
Q: How much detail should context files have?
One page each, dense. Specific enough that a new employee could act: real prices, real client states, real banned phrases. If a file exceeds two pages, split it — assistants retrieve focused context better than sprawling context.
Q: Can the assistant replace my task manager?
No — it drafts and advises; the task system remains the source of truth for commitments. The briefing reads from your systems. AI as chief of staff means it works the systems you own, not that it becomes a system you cannot audit.
Q: What’s the first real payoff to expect?
Week one: drafting speed and zero re-explaining. Week three: the Monday briefing catching real conflicts and prep gaps. Month two: the compounding — every artifact it drafts lands closer to final because the context keeps maturing.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.