One thing, several names. In LeedAB, operator, agent, Artificial Being (AB), and your team all refer to the same idea: a specialist AI worker with a job. “Artificial Being” is the brand name for the concept; “operator” is what we call it day to day in these docs and in the console.
COO, SLS, CFN) so it reads cleanly across the console at a glance.
Built-in and custom
- Built-in operators ship with the templates and cover common back-office jobs. You can browse the full roster.
- Custom operators are tailored to your operation. The console treats built-in and custom operators the same way, so you work with your whole team through one interface.
How a team is assembled
During onboarding, LeedAB reads your role and your operation and hires a team to match. A template gives you a sensible starting set, and the team is tuned from there. A back-office team might include an operator that clears your inbox, one that reconciles invoices against your ERP, one that chases confirmations across your portals, and one that prepares your reporting.What an operator can do
- Read your live data and answer from it, citing the same numbers the rest of the workspace shows.
- Propose actions within its area, which you confirm before anything happens.
- Hand off to the COO or another operator when a job crosses into their authority.
Browse the operators
Every built-in operator, its code, and what it is authorised to do.
How the team is orchestrated
The COO ties your operators together and routes the work.