Every team that adopts agents seriously hits the same second-order question about a quarter in: the missions work, the deliverables are real - so who does what now? The org chart was designed around the old cost structure, where research took analysts, production took specialists, and coordination took managers. When missions absorb the research and production layers, the structure that remains is answering a question nobody is asking anymore. This article maps the four topologies that actually emerge, and the accountability pattern that makes any of them work.
The org question nobody planned for
Adoption sequences are personal before they are organizational: one operator starts running missions, output jumps, others copy, and six weeks later the team is organized around an invisible new capability with job descriptions describing the old one. Left unmanaged, this produces the familiar pathologies - shadow processes, unclear ownership when a mission misfires, and the quiet anxiety of specialists whose specialty just became a tool call. Managed deliberately, it becomes a redesign with more leverage than any hiring plan of the past decade.
What actually changes in the work
The stable pattern across teams: work splits into three altitudes. Directing - choosing objectives, defining the ICP, setting the quarter's bets - stays fully human and becomes a larger share of everyone's week. Reviewing - the approval queues, the evidence sampling from the KPI system, the taste calls - becomes the new middle of the job. Producing - the research, assembly, drafting and formatting that consumed most hours - becomes mission work. Job satisfaction, counterintuitively, usually rises: the layer that left was the layer people complained about in exit interviews.
The four topologies
| Topology | Shape | Fits |
|---|---|---|
| Augmented team | Existing roles keep lanes; each runs missions inside their lane | Mid-size teams with strong specialists and low appetite for reorg |
| Operator pod | A small pod runs the mission portfolio for the whole function | Teams ready to centralize; the pod becomes the leverage point |
| Solo multiplier | One marketer + the full agent roster covers the entire function | Startups and founder-led motions - the shape in the solo-marketer use case |
| Agency rebuild | Per-client workspaces; humans own strategy and the client room | Agencies converting delivery cost into margin and capacity |
The augmented team is the lowest-friction start and the most common: the SEO lead runs audit and content missions, the demand lead runs the AI advertising loop, ownership maps cleanly onto existing lanes. The operator pod appears when someone notices the missions themselves are a craft - portfolio tuning, prompt libraries, promotion decisions - and concentrates it. The solo multiplier is documented in its own use case; the agency rebuild in the agencies solution. Most orgs migrate between topologies as maturity grows - augmented first, pod later is the classic path.
The RACI pattern: one per workflow
The classic mistake is writing a RACI for "the AI program" as a whole. Useless: a bid-adjustment mission and a lifecycle-email mission carry completely different risk and need different accountable owners. Write one per workflow, and the same pattern holds everywhere: the agent is Responsible (it does the work), exactly one named human role is Accountable (they own the approval queue for that workflow and answer for outcomes), functions with veto interest are Consulted (legal on claims, finance on spend limits), and downstream consumers are Informed (the channel the diff posts to). The accountability is exercised in a concrete place - the queue - which is what makes it real rather than ceremonial.
The roles that emerge
Two roles recur under different titles. The missions operator owns the portfolio: which playbooks run on which schedules, how prompts evolve, when a mission type is ready for promotion, what the four numbers say this month. It is a genuinely new craft - part RevOps, part editor, part SRE - and the person who grows into it becomes disproportionately valuable. The evidence editor owns quality: citation sampling, brand taste on creative output, the QA gate from content operations. Neither role requires a new hire at the start; both require a name, because unowned quality and unowned portfolios degrade identically - quietly.
Managing the transition honestly
The transitions that go well share three properties. They move people up the stack explicitly - the analyst becomes the operator, the specialist becomes the reviewer of their former craft - with the retraining framed as promotion, because it is one. They start with augmentation and let the topology emerge from observed load rather than imposing a reorg on day one. And they never frame the program as headcount arithmetic: teams that lead with "efficiency" get quiet sabotage and shadow processes; teams that lead with "we stop doing the layer everyone hated" get adoption. The honest version is also the true one - the constraint on every topology above is review capacity and direction quality, which are human properties, and the orgs that win are the ones whose humans moved up fastest.
Frequently asked questions
How do marketing teams reorganize around AI agents?
Four shapes recur: the augmented team (existing lanes, missions inside each), the operator pod (a small team runs the portfolio for everyone), the solo multiplier (one marketer plus the roster), and the agency rebuild (per-client workspaces, humans on strategy).
Who is accountable when an agent does the work?
One named human role per workflow, exercised through that workflow’s approval queue. The agent is Responsible; accountability never transfers to software. Write the RACI per workflow, never for the program as a whole.
What new roles does agentic marketing create?
The missions operator - owner of the playbook portfolio, schedules, prompt evolution and promotion decisions - and the evidence editor, owner of citation sampling and taste. Both start as hats before they become hires.
Does adopting agents mean reducing the team?
The teams that win move people up the stack - from producing work to directing and reviewing it - and their constraint becomes review capacity and direction quality. Framing the program as headcount arithmetic reliably produces resistance and worse outcomes.
Which topology should we start with?
Augmented team, almost always: lowest friction, ownership maps onto existing lanes, and the observed load tells you whether a pod should form. Solo multiplier is the startup default; the agency rebuild has its own economics.
Sources
- Team Topologies - the vocabulary this article borrows for org shapes
- Anthropic - Building effective agents
Every playbook on this blog ships as a runnable mission.
Open a workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, on your plan's monthly credits.