CEO front door over a worker hierarchy

The idea

The operator talks to one CEO worker; department heads and workers sit below it, and each level's budget and tool limits bind its whole subtree.

The problem
Many separate agents need one point of contact and consistent limits.
Why it matters
One conversation reaches the whole team, and a manager's cap applies to everyone under it.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • AI employees with names and roles

    Each AI worker is a named employee with a role, persona, model, memory and tools, hired into the organization.

  • Delegation down the chain with fan-out

    A manager splits work into parts, creates every child in one transaction with dependencies, and waits once for all of them.

  • Authority ladder: the owner is the last resort

    A question goes to the asker's manager worker, then the CEO, which decides from the org profile and record; a person gets it only for an owner reason, and their answer becomes a precedent.

  • Campaigns over a goal

    A campaign is a root item and all work under it, with limits, one-click hold and resume, one instruction sent to all open work, and a report of runs, pull requests, cost and follow-ups.

  • Approvals on web, WhatsApp, Slack and Teams

    A governed action waits for an approval that eligible people decide on the web, WhatsApp buttons or Slack/Teams direct messages; the requester never decides, and owned resources are approved by their owner.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.