A Kennett Revenue Architecture practiceStart a conversation

— Field Notes No. 13

The Organization Has to Change

AI does not just make the old revenue organization faster. Once software can carry the repeatable work, the organization itself has to be redesigned.

August 10, 2026·10 min read

A few things happened almost on top of each other.

Google's Ads Advisor and Analytics Advisor now let users ask natural-language questions, surface tailored recommendations and analyze data without leaving the advertising workflow. In Google Ad Manager, a separate beta called Ask Ad Manager can generate reports, tables and comparative benchmarks from a prompt instead of requiring someone to stitch the pieces together manually. (Google Ads & Commerce, March 25, 2026; Google Ad Manager, June 18, 2026)

OpenAI is no longer just an AI company that might someday have an advertising business. It is gradually rolling out a beta self-serve Ads Manager through which advertisers can buy and manage ChatGPT campaigns. It has also launched pixel-based measurement and a Conversions API. (OpenAI, May 5, 2026)

Then came one of the stranger stories of the summer. According to Digiday, TIME is piloting ads intended for AI agents with Mobian: sponsored, FAQ-form brand information placed on markdown versions of TIME pages so machines can read it directly. That is commercial information designed for a machine audience, not simply for the person looking at a webpage. (Digiday, July 30, 2026)

And in local media, Scripps is working through a much harder version of the same conversation. The company has publicly tied its transformation plan to AI, automation and other technology, while reorganizing local and national television leadership to pursue growth and efficiency. (Scripps Q1 results, May 7, 2026; Scripps organizational realignment, July 22, 2026)

Those sound like four different stories.

I don't think they are.

I think we are starting to see the revenue organization itself change.

We keep aiming AI at the old organization

I wrote recently that the work was never the value.

Most companies are still using AI to make existing tasks a little faster. Write the email faster. Build the report faster. Summarize the meeting faster. Make the proposal faster.

That is useful.

It also leaves the basic operating model untouched.

The seller still researches the account. The seller still prepares for discovery. After the sale, a strategist or account manager may become the client's primary point of contact. Someone still builds the proposal. Someone enters the order. Someone asks for the creative. Someone traffics it. Someone checks the campaign. Someone assembles the report. Someone remembers that the client is due for renewal.

We have automated pieces of the work while preserving an organization built around people carrying the work.

That is the part I think changes next.

A comparison of today's manual revenue workflow with an AI-native model. In the future model, agents carry repeatable work, systems provide governance and measure outcomes, and people focus on relationships, judgment, exceptions and creativity.
Figure 1. The operating-model shift from people carrying the workflow to agents performing repeatable work inside governed systems that measure outcomes. Built Revenue analysis.

For decades, revenue organizations were designed around an obvious constraint: if work needed to happen, a person had to do it.

So we organized people around the tasks.

Research. Sales. Proposals. Ad operations. Creative. Campaign management. Reporting. Account management.

And then we built software to help all of those people do their individual jobs.

CRM records the seller's activity.

The proposal platform helps build the deck.

The project-management system tells operations what is due.

The ad platform lets a campaign manager optimize.

The reporting platform helps somebody assemble the results.

It is an enormous stack of software built mostly to help humans carry work from one human to the next.

AI changes the underlying assumption.

If software can now research the account, prepare the seller, capture the discovery, assemble the recommendation, draft the proposal, create the order, request the assets, monitor fulfillment, identify a pacing problem, build the report and flag the renewal opportunity, then the question is no longer:

How do we help our people do all of this faster?

The better question is:

Why are our people doing all of it in the first place?

The people doing the relationship work should stop being the workflow

Look at a good local-media seller.

The scarce thing is not her ability to enter an order.

It is not her ability to hunt through five websites before a meeting, resize a logo for a proposal, chase an advertiser for creative or remember to check a dashboard on Thursday morning.

The scarce thing is that the business owner answers when she calls.

She knows the market. She knows which new restaurant is opening before the sign goes up. She knows why the dealership stopped advertising last year. She understands whether the owner sitting across the table actually has a marketing problem or a cash-flow problem.

That relationship took years to build.

And the seller is not always the person doing that work.

At the Star Tribune, many of our long-term digital agency relationships were not led by sellers after the sale. Strategists and account managers became the client's primary point of contact.

The title is not the point. What an organization calls these people will vary. The work is the point: holding the context, earning the trust, advising the client and owning the consequence.

Yet we routinely surround the people doing that work with administrative work and call the resulting number "capacity."

Then we add headcount when the client-facing team runs out of hours.

AI creates the opportunity to change the math.

Not by removing the people doing the relationship work.

By removing the machinery they have been carrying around.

If ten people doing the relationship work could spend materially more of their time talking to prospects, advising clients, finding opportunities and keeping business — rather than moving information between systems — the economic impact is much larger than "we saved everyone four hours."

That is why I think capacity is a better AI metric than productivity.

Productivity asks how quickly someone completed the same work.

Capacity asks how much more valuable work the organization can now absorb.

Those are not the same thing.

The agent is not the system

There is another mistake waiting for us.

We can move directly from an organization where humans do everything to one where we imagine an AI agent doing everything.

That is not the operating model I want either.

An agent might research the advertiser.

It should not decide whether it is allowed to expose confidential client data.

An agent might recommend a media plan.

It should not invent the company's margin floor.

An agent might assemble an order.

It should not decide that a missing political disclosure probably does not matter.

An agent might detect that a campaign is underperforming and recommend a change.

It should not necessarily get an unlimited budget and permission to make it.

This is the layer that I think gets missed in a lot of the agent conversation.

There still has to be a system.

Permissions.

Workflow state.

Approvals.

Budgets.

Evidence.

Compliance.

Client data.

Audit trails.

The more work agents can perform, the more important this layer becomes.

That leads me to a model I keep coming back to:

Agents do the work. Systems govern the work. Humans make the consequential calls.

The exact line will move over time.

Agents will get better.

Some approvals that need a person today will become safe enough to automate tomorrow.

But the distinction matters.

Autonomy without governance is not an operating model. It is a demo.

What is left for the humans is the good part

This is also why I am uncomfortable when this conversation starts and ends with headcount.

Yes, jobs will change.

Some will disappear. It would be dishonest to pretend otherwise. Scripps itself has described a transformation that uses AI, automation and other technology to fundamentally change how the company operates. (Scripps, May 7, 2026)

But "how many people can we eliminate?" is still the smallest version of the question.

For many local media companies, the constraint is not that they have too many talented people.

It is that talented people spend too much time doing work that does not require their talent.

Take away the machinery and what is left?

Relationships.

Judgment.

Strategy.

The weird exception that does not fit the rules.

The advertiser who needs to hear that the campaign they are asking for is the wrong one.

The idea nobody asked the software to generate.

The story.

The negotiation.

The decision where somebody actually has to own the consequence.

Those are not the scraps left over after automation.

They are the valuable part.

The economics are different from the org chart

This is the piece I think media operators should be working through now.

Not a list of AI tools.

Not an AI committee.

Not another round of licenses so everyone can write faster.

Take one revenue process from beginning to end.

Research to renewal.

Put every piece of work on the table.

Then ask three questions:

  1. Who should actually do this?

  2. What part could an agent carry?

  3. What must the operating system govern?

You may discover that the boxes on the org chart describe tasks that no longer need to be jobs.

You may also discover the opposite: there are valuable things you have never been able to afford to do because every new service required another person.

That is where this becomes especially interesting for local media.

A publisher that could never afford deep pre-call intelligence for every advertiser may now be able to provide it.

A small agency that could not assign an analyst to every account may effectively have one.

A newsroom that could never support a salesperson with bespoke research, category intelligence and proposal strategy may no longer have to choose.

Products that did not work economically when every step required labor may suddenly work.

That is not simply cost reduction.

It is a different production function.

The valuable layer sits above the platforms

There is another implication here.

As advertising platforms automate more of the campaign work, knowing which buttons to push becomes less valuable.

The platforms are already moving in that direction. Google is automating more targeting, creative, bidding, budgeting and pacing through AI Max and related campaign tools. Snap has announced an MCP server that opens its advertising platform to third-party AI agents for planning, creation, optimization and scaling. (Google Ads & Commerce, April 15, 2026; Google Ads & Commerce, May 7, 2026; Snapchat for Business, June 18, 2026)

That does not eliminate the need for an operating system.

It makes the operating system more important.

The valuable layer sits above the platforms.

It knows the advertiser's actual business objective.

It carries the publisher's first-party data and the history of the client relationship.

It decides which agent can use which information, which actions require approval and where the budget limits are.

It records what happened, why it happened and what evidence supported the decision.

And it measures whether all of that activity produced an economic result.

That last part matters.

An organization should be able to see the cost of a workflow, the human time it released, the work the agents completed and the revenue or margin that followed. Otherwise we are still measuring AI by activity instead of value.

For publishers and agencies, this is the strategic opportunity: not rebuilding Google, Meta or every other platform, and not simply reselling access to an AI tool.

Build the governed layer that coordinates the platforms around the client's business, the publisher's data and a measurable outcome.

That is a much more defensible place to operate than between the user and the next button.

Don't automate the org chart

The easiest way to implement AI is to drop it into the organization we already have.

Give every department a tool.

Automate a task here.

Add a copilot there.

Declare success because everyone saved a little time.

The harder move is to ask whether we would design the organization this way at all if we were starting today.

Would the people doing the relationship work still touch ten systems?

Would a person still manually move an approved proposal into an order?

Would campaign performance wait until the monthly report to get interpreted?

Would someone still need to remember a renewal date?

Would five different employees touch the same client information simply because five different software systems require them to?

Probably not.

So I would not start with the question I hear most often:

Where should we use AI?

Start with this one:

If we were building this revenue organization today, knowing what software can now do, what work would we still choose to give to people?

That answer is the organization you should be building toward.

AI does not replace the team.

But it should absolutely change the work we ask the team to do.


Sources

— Get the next note

The full essay, by email, when it publishes. No filler, unsubscribe anytime.