When to Add Agents

The instinct is to add agents when the team is busy. Resist that instinct. Adding an agent to a busy team without a clear gap analysis is how you get a 21-agent team that performs like a 15-agent team with 6 agents doing redundant work. Every new agent adds coordination overhead — more handoffs, more context passing, more potential failure points. The agent must generate enough value to exceed that overhead. If it does not, the team got larger but not better.

I use three criteria to justify a new agent. First: is there an unowned responsibility? If a task type keeps falling between existing agents and requires the coordinator to handle it manually, that is a gap. CLAUSE was deployed because legal review questions kept escalating to Greg instead of being handled by an agent. Second: is an existing agent doing two jobs? If HUNTER is both qualifying leads and writing outreach emails, that is scope overload. Split the responsibilities into two agents with clear boundaries. Third: has a new domain emerged? When Ryan Consulting started doing technical consulting, no existing agent covered solution architecture. ATLAS was deployed to fill the new domain, not to help an existing agent.