Opinion · Operating model · Executive accountabilityThe org chart, after the agent
The org chart you end up with is the agent tech you bought.
The agent era is making this dependency visible.
The org chart you end up with is the agent tech you bought. The agent era is making this dependency visible for the first time. For decades, organisations bought platforms and built org charts in parallel: HR drew the boxes, IT bought the systems, and the relationship between the two was managed by hand. The agent era ends the parallel. The agent tech now decides which work gets done by which function, what work disappears, what new work appears. The redraw is already visible in the budget numbers: CIO investment growing two to three points faster than the rest of enterprise tech for three years, CMO budgets flat, CRO headcount in regulated firms up double-digits, contact-centre headcount shrinking as agents take the front line. Five functions, redrawn in five places at once. The redraw is downstream of an agent-tech decision most CEOs have not yet recognised they are making.
Why the agent tech determines the org chart
The dependency runs in one direction. The agent tech the CEO buys determines what the agent does, what it escalates, what gets logged, what gets audited, what gets priced and what the operator can change without the vendor's permission. Those properties in turn determine what each functional executive's organisation does, who is accountable for what, and how the org chart redraws.
Operator-controlled agent tech produces one org chart. Vendor-controlled agent tech produces another. The first produces a unified org chart across functions: the CRO, the CMO, the CFO, the CIO and the COO read the same audit trail, measure against the same outcome metric, share one accountability mechanism. The second produces five fragmented org charts, each wrapped around its own vendor platform, each with its own audit trail, each negotiating with the regulator separately.
The five functions, redrawn
The redraws are visible in every function. The CMO from campaigns to decisioning. The CFO from periodic reporting to decision-level audit. The CRO from validating models to validating the agent that runs them. The CIO from running the stack to governing the agent layer. The COO from managing operations to governing the operations agent. Five charts, same shape of shift. Whether the result is one coherent org chart or five fragmented ones depends on whether the agent tech under them is one or five.
The boxes have not moved. The work has.
Is the agent the COO?
The provocation is worth posing. The COO's historical purpose was to be the execution arm of the CEO. In the agent era, that arm is the agent. It runs customer service, claim adjudication, fraud holds, payment exceptions. It makes the micro-decisions that were once the COO's primary work. Is the agent the COO?
The answer depends on who controls the agent tech. If the vendor controls the agent tech, the vendor's agent is the COO; the human COO becomes a vendor-relationship manager. If the operator controls the agent tech, the human COO becomes the architect of the agent operations: the function that designs how the agent decides, what it escalates, where it stops, who owns the failure.
The agent tech decides who the COO is.
| Function | What gets amplified | What is new | What shrinks |
|---|---|---|---|
| CMO | Brand stewardship; strategic creative. | Decision architecture; agent procurement. | Campaign management; segment building. |
| CFO | Audit-tech; real-time financial decisioning. | Decision-level audit; model-risk-aligned finance. | Periodic reporting; manual reconciliation. |
| CRO | Architecture review; agent governance. | Agent sign-off; conduct risk for AI. | Traditional model validation. |
| CIO | Architecture leadership; integration; identity. | Agent-layer governance; edge deployment. | Stack operations; tooling vendor coordination. |
| COO | Exception design; service-agent governance. | Agent operations; agent SLA design. | Contact-centre headcount; manual exception queues. |
Agent tech is the org chart. Buy one, you bought the other.
What the CEO has to choose
The CEO has a choice. Coordinate the agent tech across functions, or let each function buy its own. The default is function-by-function. The result is five org charts redrawn in parallel around five different vendor stacks. The integration problem the enterprise has wrestled with at the technology level for a decade arrives at the org-chart level by year three. The transformation window has narrowed from five years to eighteen-to-twenty-four months in regulated firms; five redraws have to fit inside one window or not at all.
The coordinated path is harder, and the only one that does not multiply the problem. The CEO commissions one agent tech for the era and asks all five functions to deliver against the same properties. The org chart that results is one chart, not five. It is buying-committee discipline applied to the agent tech, with the org chart as the consequence.
The agent tech that produces the right org chart
The agent tech that produces one coherent org chart is unlike most current vendor tech. Decisioning and execution happen in the same layer, so the org chart does not fragment along the seam between systems that decide and systems that act. Reasoning is produced as a by-product of every decision, so the audit trail is part of the architectural choice, not a downstream export. The operator owns deployment, data and the decisioning logic, so the agent tech stays with the operator as functions migrate within the org chart. The pricing aligns to decisions made, not to seats licensed in each functional silo. And the tech was built for regulated enterprise from the start, so when the regulator extends agent oversight to a new function, the architecture is already there. The CEO who insists on this across all five functional charts ends up with one org chart and one agent tech. The CEO who buys the feature list inherits five org charts, five vendor stacks, and the old integration problem at the org-chart level.