Most people install OpenClaw and get one agent doing one thing. That's fine for personal use. But what if you want an entire team? A COO, a social media manager, a video editor, a newsletter writer, an analytics scraper, an intelligence crawler, and a community manager. All running on one Mac Mini. All coordinated. All working while you sleep.
The 13-Agent Team: Every AI Agent and Its Role
Every agent has a single job. No overlap. No confusion.
| Agent | Role | What They Do |
|---|---|---|
| Marc | COO | Coordinates everything. Dispatches tasks. Makes decisions. Talks to me on Telegram. |
| Bob | Ops | Health checks every 2 hours. Monitors all crons. Fixes or escalates. |
| Dan | X Growth | Manages @profitfounder. 3 posts/day via Typefully API. |
| Jimmy | YouTube | Monitors for new episodes. Extracts clips. Maintains transcript archive. |
| Tyler | Newsletter | Writes drafts from transcripts. Pushes to Notion. Teasers only. |
| Claude | Copy Editor | Scans transcripts for clip moments. Writes posts. Quality scores 1-10. |
| Adrien | Video Editor | Whisper transcription, smart cuts, silence removal, subtitle burn-in. |
| Mona Lisa | Sponsorship | Researches targets. Personalized X DM outreach. Pipeline in Notion. |
| Loop | Analytics | Daily scrape of YT, X, IG, Skool, Beehiiv. Weekly correlation analysis. |
| Crawly | Intelligence | Daily web crawl: Reddit, HN, YouTube, X. READ ONLY. |
| Billy | Community | Scans Skool daily. Content gaps. Module drafts. Churn tracking. READ ONLY. |
| Ariane | Notion | Daily cleanup. Moves misplaced pages. Archives stale items. |
| Alfred | Personal | Real-life tasks. Contractors, errands, local services. |
How OpenClaw Multi-Agent Coordination Works
You don't run 13 separate OpenClaw instances. You run one gateway with one main agent. (Need to set up the hardware first? See our Mac Mini setup guide or VPS setup guide.) (Marc). Marc spawns sub-agents when work needs to happen.
Florian (human)
|
Marc (main agent, COO)
|
+-- Bob (dispatcher)
| +-- monitors all other agents
| +-- health checks every 2 hours
|
+-- Content Pipeline
| +-- Jimmy (YouTube / clips)
| +-- Claude (copy editor)
| +-- Adrien (video editing)
| +-- Dan (X posting)
| +-- Tyler (newsletter)
|
+-- Growth & Revenue
| +-- Mona Lisa (sponsorship)
| +-- Loop (analytics)
| +-- Billy (Skool community)
|
+-- Operations
+-- Crawly (intelligence)
+-- Ariane (Notion)
+-- Alfred (personal)The pattern: Marc never does the work himself. He delegates to the right agent, checks the output, and reports back to me. Bob watches everything and alerts Marc if something breaks.
How to Spawn OpenClaw Sub-Agents
When Marc needs Jimmy to check for new episodes, he spawns a sub-agent session:
sessions_spawn({
task: "Check YouTube for new podcast episodes...",
model: "anthropic/claude-opus-4-6",
runTimeoutSeconds: 600
})The sub-agent runs in isolation, does its job, and reports back. Marc gets the result and decides what to do next.
OpenClaw Agent SOPs: How to Write Standard Operating Procedures
Every agent has a file in sops/[agent-name].md. Without SOPs, agents drift, forget rules, and overlap with each other.
Every SOP contains:
- Role: One sentence. What this agent does.
- Responsibilities: Specific tasks. No ambiguity.
- Access/Logins: Exactly which tools and credentials this agent can use.
- Hard Rules: Things this agent must never do.
Example:
# SOP: Adrien - Video Editor Agent
## Role
Processes raw clips into polished, subtitled videos.
## Responsibilities
- Whisper transcription of raw clips
- Smart cuts (filler word removal)
- Silence removal
- Clean subtitle burn-in
- Compress for Telegram delivery
## Hard Rules
- Source clips MUST be h264
- Subtitles: 4-5 words per line max
- Never clip from the introOpenClaw Agent Permission System: Who Can Access What
| Agent | Can Write To | Cannot Touch |
|---|---|---|
| Dan | X, Typefully | Notion deletions, memory files |
| Jimmy | Transcripts folder | Any external platform |
| Crawly | Nothing (READ ONLY) | All platforms |
| Billy | Notion drafts only | Skool (never posts) |
| Tyler | Notion drafts only | Beehiiv send (I send) |
| Marc | Memory, coordination | Social media, email |
Why this matters: The first time an agent accidentally deleted something, I built the access matrix. You don't want your analytics agent posting to X or your newsletter agent wiping Notion pages.
The Full 24-Hour OpenClaw Cron Schedule
| Time | Agent | Task |
|---|---|---|
| 12:30 AM | Crawly | Intelligence crawl (Reddit, HN, YouTube, X) |
| 12:45 AM | Crawly | Team brief → Telegram |
| 1:00 AM | Jimmy | Night research + episode check |
| 2:00 AM | Claude | Scan transcripts for clips |
| 4:00 AM | Bob | Clip QA gate |
| 5:50 AM | Loop | Usage cost tracker |
| 6:00 AM | Ariane | Notion cleanup + War Room |
| 6:30 AM | Loop | Daily analytics scrape |
| 7:00 AM | Marc | Morning brief → Telegram |
| 8:00 AM | Billy | Skool community scan |
| 9:00 AM | Billy | Churn monitor |
| 1:00 PM | Jimmy | YouTube research |
| 7:00 PM | Bob | War Room |
| 7:30 PM | Marc | Evening brief |
| 11:00 PM | Ariane | Daily backup + Notion sync |
Plus recurring: Git auto-backup every 30 min. Billy member count every 4h. Bob health check every 6h.
OpenClaw Shared Memory Architecture for Multiple Agents
13 agents need to share context without stepping on each other.
| File | Purpose | Who Writes |
|---|---|---|
MEMORY.md | Long-term curated memory | Marc only |
memory/YYYY-MM-DD.md | Daily notes / raw logs | Marc, Bob |
memory/regressions.md | Failure guardrails | Any agent |
memory/friction-log.md | Instruction contradictions | Any agent |
memory/predictions.md | Decision calibration | Any agent |
memory/context-holds.md | Temporary priorities with expiry | Marc |
Key principle: Every session, every agent reads the relevant memory files. A fresh session can reconstruct the full context from files alone. Nothing lives only in memory.
Master Rules: The Constitution for All OpenClaw Agents
On top of individual SOPs, master-rules.md applies to ALL agents:
- Every deliverable goes to Notion. Non-negotiable.
- No fake data. No sample content. Make it real.
- Write it down immediately. Rules go to memory that same turn.
- 80/20 only. If it doesn't move the goals, skip it.
- Model strategy: Opus 4.6 everywhere. No exceptions.
- All outreach on X DMs only. No cold emails. No bulk.
What Running 13 AI Agents Actually Costs
| Item | Cost |
|---|---|
| Mac Mini M4 | $700 one-time |
| Claude Opus API | ~$100-150/month |
| Electricity | ~$3/month |
| Total monthly | Under $155/month |
Compare that to hiring even one freelancer.
Lessons After Running 13 OpenClaw Agents for 2 Months
- Start with one agent. Add slowly. I started with Marc, added Bob, then specialists as I understood the workflows.
- SOPs prevent chaos. Write the SOP before spawning the agent.
- Permissions matter. Build the access matrix before something gets accidentally deleted.
- The dispatcher pattern is key. Marc → Bob → everyone else. Without this layer, the main agent gets overwhelmed.
- Memory files are your continuity. If it's not written down, it doesn't exist.
- Crons are the real power. Having agents work on a schedule without you asking is transformative.
Get the Complete Multi-Agent Template Pack
Inside OpenClaw Lab, members get the complete template pack: every SOP, the access matrix, the cron schedule, the memory architecture, and the coordination playbook. Copy-paste it, swap in your business context, and you have a 13-agent team running in an afternoon.
New to OpenClaw? Start with installopenclawnow.com to get your first agent running.
I share the exact playbooks, skill files, and workflows behind this system inside OpenClaw Lab. Weekly lives and AMAs with experts.
Join OpenClaw Lab →