Your AI team
One Chief of Staff, a CEO that plans, five chiefs that do the work.
Every workspace gets an organisation, not a chatbot. You talk to one agent; it runs the rest.
Chief of Staff ← the only agent you talk to by default
└── CEO ← breaks objectives into tasks, never executes them
├── Growth Chief marketing, sales, acquisition
├── Operations Chief finance, HR, internal process
├── Product Chief product, design, research
├── Engineering Chief software, IT, infrastructure
└── Risk & Legal Chief compliance, legal, security
Why the shape matters
The Chief of Staff is an interface, not a worker. It gathers what it needs, routes work, and comes back to you. It does not do the work itself, which is why it can stay responsive while a lot is running.
The CEO plans and never executes. It decomposes an objective into two to seven tasks and delegates each. Separating planning from doing is what stops a single agent grinding on a task it should have handed off.
Chiefs own functions. Work goes to the chief whose function it belongs to, and they hire specialists beneath them when a task needs one.
Steps
- Open Team to see the org chart.
- Open a chief to read its instructions — this is what it has been told it is for.
- Adjust instructions where your business differs from the default assumption.
You're done when the org chart reflects how your business actually divides work.
Gotchas
- Specialists appear as needed. You do not staff the org up front.
- Editing a chief's instructions changes its judgement, not just its wording. Be specific about what you want done differently.