Where agentic systems actually help in a media operation
Not the strategy, and not the creative judgement. The parts of the week that a competent analyst resents doing.
iStudios, Applied AI practice
Eighty eight per cent of organisations report using AI regularly in at least one function, and thirty nine per cent can point to a measurable effect on the bottom line. Somewhere in that gap sits the difference between deploying a capability and changing a workflow.
In a media operation, the useful applications are unglamorous and specific.
Worth automating
- Anomaly detection across accounts. Something moved more than it should have; a system that notices at nine in the morning beats an analyst who notices on Thursday.
- First-pass reconciliation between platform numbers and the warehouse, which is pure tedium and entirely rule-governed.
- Drafting the weekly narrative from the data, for a human to correct. Getting from a blank page to a wrong first draft is most of the effort.
- Creative versioning and trafficking, where the rules are explicit and the volume is the whole problem.
- Monitoring pacing and flagging where a budget will land, rather than reporting where it landed.
Not worth automating
- Deciding what to test next. This depends on commercial context a system does not have.
- Interpreting a result that contradicts expectation, which is exactly when judgement is needed.
- Anything where being confidently wrong is expensive and the error is hard to spot.
- Client communication, for reasons that should not need explaining.
Automate the step where the answer is checkable. Keep the human where the answer is arguable.
The governance nobody sets up first
An agentic system acting on live accounts needs a spend ceiling, an audit log, a rollback path and a named human owner. Those four things are boring, they slow the pilot down, and every organisation that skipped them has a story about the week they wished they had not.
The organisations getting value here are not the ones with the best models. They are the ones that redesigned a process around a capable system and then measured whether it worked.