Publisher Revenue Leaders Are Still Steering by the Rearview Mirror
Where traditional publisher revenue workflows can't meet the moment, and how agentic AI provides a better path to reliable revenue outlooks and modeling

It's Monday morning and the weekly revenue meeting is starting. Sales brings pipeline from the customer relationship management (CRM) system. Advertising operations (AdOps) brings delivery numbers from the ad server. Programmatic has its own report. Finance has bookings. The result is a meeting built from data delivered by four teams, resulting in four different versions of the quarter.
The first 30 minutes go to reconciling the numbers. The next 30 go to explaining a campaign that under-delivered two weeks ago and has now become a make-good. By the time anyone gets to what should happen next, the meeting is over.
Most publisher revenue leaders will recognize some version of this. The data exists. It just lives in too many places, it’s highly challenging to reconcile, and it shows up too late to change the outcome. There’s no single version of the truth that everyone is operating on.
Where the traditional revenue workflow falls short
The picture is fragmented. Pipeline sits in the CRM. Orders sit in the order management system (OMS). Delivery sits in the ad server, split across direct and programmatic. Avails, commitments, and pacing rarely live in the same view, so no one sees the whole business at once.
Reporting looks backward. Dashboards tell you what happened last week. That’s useful for a board deck, but it does very little for a campaign that is drifting off pace right now, or a deal that’s quietly stalling.
Forecasts run on confidence. Without a data-backed read on which deals are likely to close, pipeline reviews depend on how confident each seller sounds, or old fashioned qualification frameworks that are subject to seller interpretation. Revenue leaders end up applying their own haircut to every number.
Leakage gets discovered after it's gone. Under-delivery turns into make-goods and refunds, which come straight out of margin. Premium inventory that isn't optimized in real time gets sold for less than it's worth. Both problems are usually visible in the data days before anyone acts on them.
Renewals turn into negotiations. When you can't connect delivery to advertiser outcomes, every renewal starts with defending the budget instead of growing it. Advertisers who don't get clear, timely performance reporting start moving dollars to partners who seem more transparent.
What a better path to reliable revenue management could look like
The shift revenue leaders are after is simple to describe: see risks and opportunities while there’s still time to act on them. Getting there takes a few changes in how the work gets done. Here’s what we recommend to our publisher and media friends:
One shared context across the business. The foundation should be a single layer of context that connects the CRM, the OMS, and the ad server, so pipeline, inventory, and delivery can be read together. At TIME, Kana built this using Salesforce, the OMS, and the ad server across direct and programmatic. Once that exists, the Monday reconciliation exercise mostly goes away.
Signals that point forward. With connected data, AI agents can flag what is likely to happen next. Examples include which campaigns are forecast to miss their goals, which deals look like your historical wins or losses, which accounts are heading into renewal without a strong performance story, etc. As a result, revenue leaders get a short list of things to act on.
Scoring you can see into. Win likelihood should be scored against your own history, with the contributing factors shown. Because a black-box score with no context will be read as just another opinion, whereas a transparent one lets managers coach and lets revenue leaders forecast with fewer surprises.
Plain-language answers. Leaders should be able to ask a question like "which guaranteed campaigns are at risk this month and why?" and get a grounded answer with sources. When the data is missing, the system should say so instead of guessing.
Leaders set the guardrails. Agents work inside limits your team defines: budget ceilings, pricing guidance, and approval thresholds that decide when an agent acts on its own and when it escalates to a person. The judgment stays with the people accountable for the number.
How TIME is using agentic AI to drive revenue growth
TIME is treating agentic AI as core infrastructure for how it sells, delivers, and scales advertising. On the pre-sales side, sales uses an application to turn requests for proposal (RFPs) into inventory-aware proposals in minutes. On the post-sales side, Ad Ops uses Campaign Orchestrator to monitor delivery and pacing across every live campaign and catch under-delivery before it becomes a make-good.
The less obvious result has been for revenue planning. Mark Howard, Chief Operating Officer at TIME, told AdExchanger that TIME's revenue operations team is also using the tool, and that he has seen "a significant increase in what they're able to accomplish in any given day or week." It is helping with budget planning too, "and not just for how we're going to finish this year and how Q1 looks, but actual 2027 modeling. It's a whole new world when you can have these kinds of insights delivered to you."
A few questions to bring to your next revenue review:
- How long does it take your team to agree on a single number for the quarter?
- How many days pass, on average, between a campaign falling off pace and someone acting on it?
- What did make-goods and refunds cost you last year, and how many were visible in the data beforehand?
- When a renewal comes up, can your seller show the advertiser what their last campaign delivered against their goals?
- If you had a forward-looking view of pipeline, inventory, and delivery in one place, what decision would you make differently this week?
In all likelihood, just seeking out these answers will give you a strong sense for the best place to start.
If you’re looking for a partner to help build your AI growth engine? Get in touch.