The original operating snapshot described three operators coordinating work across nineteen markets and twelve languages. Those are different denominators from brands, active ad accounts and delivered outputs; the headline's thirty-times comparison did not define a stable unit of work.
What the systems prepared was concrete: product-feed content, candidate headlines, pre-launch checks and repeatable reporting. What the people retained was equally concrete: strategy, product and claim review, client relationships, account changes and exception handling.
The useful connection is the shared context. Research informs copy. Product facts inform feeds and pages. Campaign observations inform the next brief. That can remove repeated handoffs without turning generated material into a finished result automatically.
An internal text-uniqueness score is a heuristic, not a Google quality measure. A rejection rate also needs its submission denominator, period and platform context; it is not evidence that an account will perform.
Inspect one output end to end: source inputs, prepared artifact, review, applied change and the later observation. Then inspect the queue of exceptions and the operator capacity left to resolve them.
The bottleneck can move when preparation becomes faster. The response is to keep human decisions and live responsibility visible, not to promise that every workload can be multiplied without limit.
Take the idea further
Read the operating-model account