Level Up

Agent Org Chart Builder HalperBot

In the Prompt Lab you wrote your CLAUDE.md. In Agent Teams you designed your first agent. Now zoom out: design your whole AI agent team on one screen — a named head agent per department, 5–7 sub-agents underneath each, and a Chief Agent that fans work out and merges the answers back.

Name your agents like people. “Ask Nolan to draft the script” beats “open the content tool” — naming is what makes an agent team stick inside a real company.

Design Your Team

Fill in your departments below — the chart redraws live. When it looks like your business, download it as a standalone page or copy the build prompt and hand it to Claude.

Not sure where to start? Load a starter team and make it yours:
Executives

Your team build prompt

Fill in your departments above to generate the build prompt...
Each head agent needs a spec of its own — write one in the Agent Builder, and give the whole project a brain with a CLAUDE.md.
Every department head also needs a dashboard to run — browse 44 examples in the Dashboard Marketplace and pick one per department.

Why This Shape Works

01
One Head Agent Per Department

Employees don't need to learn ten tools — they need one name. Sales asks Ruby, content asks Nolan. The head agent takes the task, picks the right sub-agent underneath it, and hands back the result. You prompt the manager, not the whole team.

02
A Chief Agent for Executives

Executives ask questions that cross departments — “how did the launch go?” touches sales, support, and content at once. The Chief Agent fans that question out to every department head, then merges the answers into one brief. That's the top tier of the chart.

03
Access Tiers Keep It Sane

Executives talk to the Chief. Employees talk to their own department head. Heads talk to their sub-agents and tools. Nobody gets lost, and nobody touches a system they shouldn't — the org chart is the permission model.

04
5–7 Example Use Cases Per Agent

Adoption dies when people don't know what to ask. Every head agent should open its chat with 5–7 example tasks (“draft a script about…”, “summarize this meeting…”) so a brand-new employee is productive in an afternoon — not after a training course.