Structuring a multi-Bot team
Twelve Bots is easy to create and hard to run. The structure that works: one chief of staff, one Bot per theme, delegation flowing one way, shared knowledge files.
Short answerOne chief-of-staff Bot you talk to. Specialists, one per theme (not per task). Delegation flows down from the chief of staff; reports flow up. No specialist delegates to another. Shared knowledge files hold who you are and where things live.
Why themes
A reviewer who built twelve Bots in eight hours landed on the rule that stops you creating useless roles: a Bot owns a theme, not a task. "Sales ops" is a theme; "send Tuesday's follow-ups" is a task that belongs to it. Task-Bots multiply, overlap, and start delegating to each other.
The shape
You
└── Chief of Staff (single point of contact; batches approvals; delegates)
├── Sales Ops
├── Finance Ops
├── Inbox
├── Research
└── Ops (spend watcher, heartbeat, cleanup, pages us)
Rules
- Descriptions don't overlap. If two Bots could both own a request, rewrite until one can.
- Specialists report to the chief of staff or you. They don't ask each other.
- Every skill ends with "if you can't complete this, report to a human; don't re-delegate."
- Shared knowledge files: who the company is, where files live, what Composio is for, house style. Every Bot reads them.
- Group chats have a human in them and a message cap.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.