What does a marketing team look like in 2028?
The short answer
By 2028, marketing teams likely split into two groups on the same org chart: people who hold judgment, taste, and accountability, and systems that draft and monitor under them. Microsoft's WorkLab has reported AI-native agencies running teams of two to three people across roughly ten clients each, and the most detailed public account of an account-manager role rebuilt as a system found it covered about a third of the job in its first 50 days. Headcount is decoupling from workload faster than judgment is transferring to software.
Smaller at the top, and busier underneath with systems instead of people. Microsoft’s WorkLab has reported AI-native ad agencies running teams of two to three people across roughly ten clients each, a ratio that would have needed a staff several times that size under a traditional account-management model. That ratio is already showing up in 2026, rather than sitting years out as a projection. What it points to is a specific shape for 2028: judgment stays human and gets scarcer per client, while the volume work moves to systems that draft and monitor under it.
The ratio that’s already visible
Microsoft’s WorkLab profiled AI-native agencies reportedly operating with two to three person teams handling around ten clients each. That’s an account-to-headcount ratio that strains under a conventional staffing model, where each account typically carries a dedicated strategist, media buyer, and account manager. The reported ratio doesn’t mean the work shrank. It means most of the work moved off a full-time headcount and onto a system that runs daily.
The boundary we’ve actually tested
The clearest test case for what does and doesn’t transfer to a system comes from an account manager role rebuilt as software after a real hire left, not from a survey. In its first 50 days, the system covered about a third of the account-manager role: daily health checks, pacing monitoring, first-draft reporting. Taste, narrative, and final say on the account stayed with a person. That boundary held up under an actual client relationship, not just a claim in a pitch deck.
What bifurcates: judgment versus system-tending
| Role type | What sits here | What decouples it from headcount |
|---|---|---|
| Judgment | Strategy and positioning, creative taste, final sign-off on spend, the client relationship, accountability for a bad month | Nothing yet; still one person per unit of judgment needed |
| System-tending | Daily account health checks, first-draft reporting, anomaly flagging, campaign build and QA, data pipeline monitoring | A system runs it continuously, so volume grows without adding headcount |
Headcount decouples from workload before judgment does
By 2028, the lever on capacity looks less like hiring and more like the systems sitting underneath a fixed set of judgment-holders. The same senior person can hold the account relationship and final call across more clients, because the system-tending work under them runs continuously and scales without adding a person to run it. Headcount stops being the measure of how much a team can carry.
What the 2028 org chart adds
A team built this way ends up listing systems next to people, each with a named owner. An account health monitor, a reporting draft generator, an anomaly flagging layer, sitting on the chart under the judgment-holder accountable for what it produces, the same way a junior analyst sits under a director today. The systems don’t get a seat at the table, but they get a line on the org chart and a named owner who answers for what they produce.
What we don’t know yet
This read holds only as long as taste and narrative keep resisting automation the way they have so far. The clearest signal that would prove it wrong: a system-tending layer generating creative concepts, positioning, or client narrative that a client accepts without a judgment-holder editing it or standing behind it first, at real scale rather than as a novelty demo. We haven’t seen that yet in the accounts and systems we’ve built or watched. If it starts showing up, the 2028 org chart looks less like judgment plus systems and more like software with a thin human layer on top, and this read was wrong.
Where we land
We already run Rise this way: a small senior team, plus systems that monitor and draft, deciding little on their own. Our services start from that split, judgment priced and staffed as people, the repeatable work built once as a system, because that’s the boundary we’ve tested on our own accounts, not one we’re hoping turns out to be true.