Command an army of agents.
Talk to one agent, the VP. It files the tickets and puts an agent team on every one, and they work in parallel.
How one brief becomes an army.
You align with the VP on what you want.
- The VPTurns what you ask for into tickets.
- SentriesSpot recurring work and suggest tickets.
- The routerPuts the right agent team on each ticket.
- Agent teamsAI roles that do the work, alone or in sequence.
- Your peopleMake the calls that need judgment.
Set up a department.
A department is your AI team for one part of the company, like Marketing. You choose its roles, each with its own job, skills and model, and group them into agent teams. Marketing's tickets are worked by Marketing's roles, following its steps and gates.
A big ticket gets a team of roles.
The roles pass the work along. On the announcement, a Planner outlines from the research, a Writer drafts, and a Reviewer checks every claim before the work comes back to you. In the app, a team like this is a pod.
How one person steers it all.
Steer by intent.
Brief the VP, or set up sentries: scheduled checks that spot recurring work and propose or launch new tickets for agent teams to work on.
Monitor by exception.
The teams work while you're away. Home brings each person the calls that are theirs, with the research behind them, so you review the work, not the chats.