Ad Ops: The Team That Absorbed The Volume
Every conversation about cheaper creative production skips the same step. The work still has to be named, checked, sized, trafficked, scheduled and reconciled, and ad ops is where all of that lands.
When a campaign went from twelve deliverables to two hundred, nobody added six people to that team. The volume simply arrived.
What Ad Ops Actually Absorbs
Naming conventions, which sound trivial until a hundred files with similar names are live in four markets. Specification checks against each platform's requirements. Trafficking and tagging. And the reconciliation at the end of the month, where the number of things that ran has to match the number of things that were booked.
Each of those scales linearly with deliverables. None of them got cheaper when generation did.
Why This Is A Quality Problem, Not Just A Workload One
Because the errors this team catches are the ones the audience would have seen. A wrong offer, a mismatched language, an old price, a creative that ran a week past its legal window.
Under volume pressure, checking becomes sampling, and sampling means the error rate is no longer zero by design. That is a decision most agencies have made without discussing it.
The savings appear in the production line. The cost appears in a team nobody mentions in the credentials deck.
What To Do Before It Breaks
Automate the checks rather than the making, which is the inversion most agencies have not tried. Naming, specification validation and version reconciliation are rule-based problems and are a far better use of these tools than another set of variants.
And put an ops person in the room when a campaign's deliverable count is being agreed, because that is the meeting where the workload is created and it is currently held without them.
Related: what happens to retainers when output is unpredictable.
More in The AI Shift.