Claude operator maps 6‑agent org

On May 21, the X account Claude Operator posted an “org chart for a 6-agent operating company” and described a setup with “No humans below the operator.” The post listed six roles — Outreach, Research, Content, Sales ops, Asset and Reporting — and linked to a public system page with job descriptions for each function. The outline framed AI agents not as a single assistant, but as a small operating layer divided by task. The post drew attention because one of the six roles was Sales ops, with work that included pipeline triage and reporting. ### What exactly did Claude Operator publish? Claude Operator’s post described a six-agent structure in which a single human operator sits above a set of specialized agents. The six named functions were Outreach for drafting messages, Research for gathering intelligence, Content for newsletters and threads, Sales ops for pipeline and triage work, Asset for pages and PDFs, and Reporting for daily and weekly updates. The X post linked readers to a system page on Claude Operator’s site, where the roles were presented as distinct job tracks rather than one general-purpose bot. The short descriptions emphasized repeatable work: drafting, organizing, packaging and summarizing. ### Why did the Sales ops role stand out? The Sales ops role stood out because it put back-office revenue work inside the same agent map as content and outreach. In the post, Sales ops was described around pipeline handling and triage, alongside Reporting’s daily and weekly summaries. (claudeoperator.co) That places CRM-adjacent work in the same automation stack as prospecting and publishing. Pipeline triage is a specific term in revenue operations. (claudeoperator.co) It usually refers to sorting active deals, flagging stale records, identifying missing next steps and preparing review material for managers or founders. Claude Operator’s description suggested that kind of repetitive maintenance work is one of the first candidates for agent-based automation. ### What does this say about how agent teams are being organized? The six-role map showed an emerging pattern in agent design: split the work by operating function, then assign each function a narrow brief. (claudeoperator.co) Rather than asking one model to do everything, the system separates intelligence gathering, outbound drafting, publishing, sales administration, asset creation and reporting into different lanes. That structure also reduces the amount of context any one agent has to hold at once. (claudeoperator.co) A research agent can focus on inputs, a content agent on packaging, and a reporting agent on cadence and summaries. The Sales ops agent, in that setup, becomes a workflow manager for pipeline hygiene rather than a closer. ### What has to be true for this to work inside a real sales team? CRM data has to be structured well enough for an agent to act on it. (claudeoperator.co) A sales-operations agent can only triage a pipeline if fields such as stage, owner, next step, close date and activity history are consistently populated. Without that structure, the agent can still draft updates, but it cannot reliably sort risk or identify what is missing. That inference is based on the kinds of tasks Claude Operator assigned to Sales ops and Reporting. The same applies to reporting. Daily or weekly summaries depend on a system that can pull comparable records from one period to the next. If the underlying data model is inconsistent, the output becomes a polished narrative rather than an operational report. That is an inference from the workflow described on the system page. ### Where does the project go from here? The next reference point is Claude Operator’s own system page, which the May 21 post identified as the place for the “full JD per agent.” That page is where readers can track whether the six-role map expands, changes responsibilities or adds tooling details for Sales ops, Asset or Reporting. (claudeoperator.co)