Your Buyer's Agent Reads One File. Product Marketing Reports to the CPO Now.

On October 30, Bret Taylor and Clay Bavor posted Sierra's third quarter. More than $400M in ARR, more than $150M of it added in the quarter, and a pricing line I keep coming back to: customers "pay for outcomes, not tokens used." In the same post they say Sierra is building an open standard for personal agents, called Poppy, with more than 50 enterprises, Meta, Shopify, Stripe, and Walmart among them.

Open the Poppy draft and the first building block is discovery. A company publishes "one file at a standard address on their website" that tells a customer's personal agent how to work with it. What the agent can ask as a guest. How the customer signs in. What the agent is allowed to do, and what it isn't.

That file is positioning. It's also a product artifact, versioned and shipped like an API.

It won't be the only one. The buyer's first conversation about your product is already happening with a model, and the next one will be with an agent acting for them. Both read what product ships. Neither reads the launch deck.

This is part 1 of The Product Marketing Transition, a twice-weekly series on where product marketing goes when building is cheap. The argument for the whole series fits in one sentence. Product marketing reports to the CPO.

The short version

When a working prototype costs a day and the product changes weekly, shipping stops being the hard part, and the outcome is decided by whether buyers find, trust, buy, and adopt what shipped. More and more of that happens through machines. Sierra and more than 50 enterprises are drafting a standard where a buyer's agent reads one file on your site before any person talks to you. An AI tool is now the top answer to how Notion's users heard about it, at 25.4%. About half of ServiceNow's net new business comes from non-seat pricing, which turns the outcome definition into a product spec. The discovery file, the docs a model reads, the outcome definition, and the onboarding an agent runs are product surfaces, and they ship with the build or they're wrong. So positioning, agent-read messaging, pricing and packaging, and the adoption number move into the product org, under the CPO, who owns the whole outcome.

The first reader is a machine

Rich Holmes reported on Monday that Notion co-founder Akshay Kothari shared the answers to a simple survey question: how did you hear about Notion? The top answer was an AI tool. 25.4% of responses. Holmes adds that Granola's monthly activated users attributed to AI discovery are up 4,600% since January, and that Vercel's share of signups referred by ChatGPT grew 10x.

I wrote about the traffic side of this on Tuesday, in the referrer is the assistant. The org side is the bigger story.

Kyle Poyar's state of paid ads on Sunday has the other half. "AI Overviews are squeezing out inventory on Google," he writes, and Keith Putnam-Delaney, co-founder and CEO of Primer, told him "AI answers have eaten into the placement of unbranded search campaigns." The paid workaround isn't ready either. Only 3% of the respondents to his State of B2B GTM report use ChatGPT ads today, and 39% plan to try them in 2027.

So what does the assistant read when your buyer asks it who to shortlist? Your docs. Your changelog. Your pricing page, your help center, your integration listings, the comparison page somebody wrote two years ago. In most companies product or support owns nearly all of that. Product marketing owns the deck and the messaging house. The model reads the first list and never sees the second.

That's the gap. The story the market hears is assembled from product surfaces, and the team that owns the story doesn't own the surfaces.

The price is a spec now

Jason Lemkin reported on Saturday that about 50% of ServiceNow's net new business now comes from non-seat pricing. Sierra's examples of what customers pay for are "a loan refinanced, an insurance claim paid, a sale closed, a customer retained."

When you sell an outcome, the definition of the outcome does three jobs at once. It's the thing the product has to measure. It's the price. And it's the promise the buyer believes before signing. One sentence, three owners, if your org chart splits them. I've written about the mechanics in per-outcome pricing and what the margin does on the way in the trough and the month. The org point is simpler. A sentence that's product, price, and promise can't be negotiated across three reporting lines every time the product changes.

Pricing gets its own part later in the series. For now, notice who has to be in the room when that sentence gets written: the people who know what the product can measure, and the people who know what the buyer will pay for and believe. Today those are usually in different orgs.

The story has to ship in the same sprint

The Sierra post has one more number worth sitting with. A US retailer with more than $40B in revenue went from first meeting to a live agent in 27 days.

That's the speed the whole loop runs at now. Customer, spec, build, story, adoption. In part 1 of the FDE series I called the person who runs that loop end to end the Product Builder. Forward deployed engineers close the edge from customer to spec. Design owns the spec, as the Design Transition argues. Product marketing owns the edge from story to adoption.

And that edge breaks first when it sits in a different org. If the product changes weekly and the story lives three handoffs away, the story is always describing last month's product. The agent reading your discovery file won't wait for a launch tier. The assistant summarizing your docs won't wait for the messaging refresh. Whatever's live is what they say.

Why the CPO, and why now

SAP made the opposite bet. In July it moved its product marketing teams into its global marketing unit under the CMO, as Tarsilla Moura reported at ERP Today. That's a coherent choice when the story is a campaign. I think the next five years make it the harder org to run, because the story isn't a campaign anymore. It's the discovery file, the docs, the outcome definition, and the onboarding the agent runs.

This isn't a case against marketing. Brand, demand, events, and the creator programs Poyar has been writing about stay in marketing, and they matter more when AI makes generic outreach cheap. What moves is positioning, the messaging that agents and assistants read, pricing and packaging, and the adoption number. Those are the parts that change every time the product does.

Here's the through-line across all four series. The CPO Transition started from the claim that the CPO now owns the operating model. The FDE series put deployment in the product org. The Design Transition put the spec there. This series puts the story and the adoption number there. Product, design, product marketing, and forward deployed engineering under one leader, because the outcome is decided by a loop, and a loop split across four reporting lines can't close as fast as the product changes.

That makes the CPO the person who answers for whether what shipped got bought and used. It's a bigger job than it was, and I think it becomes one of the most influential seats in the company.

What I expect

These are my predictions, not facts, and I'll check them in later parts.

By the end of 2027, an agent-facing discovery file, Poppy or whatever standard wins, is as normal for enterprise software as a pricing page. The PMM who owns positioning owns what it says.

Within two years, an AI assistant is a top-three answer to "how did you hear about us" at most B2B software companies that ask. Notion's 25.4% is one company's survey. I expect it to be ordinary.

By 2028, most new heads of product marketing at AI-native software companies report to the CPO, not the CMO. SAP is the proof that it won't be universal, and that's fine. The companies that move first will ship their story at the speed of their product.

One thing to try this week

Ask ChatGPT, Claude, Gemini, and Perplexity the question your best buyer asks before building a shortlist. Write down what each one says you do, who you're for, and what you cost.

Put that next to your positioning doc. Every gap is a fix on a product surface: a docs page, a pricing line, a changelog entry, an integration listing. File each one as a ticket in the product backlog, not a marketing brief. Then watch who picks it up. That tells you where product marketing sits in your company today.

Sources: Bret Taylor and Clay Bavor, "Our customers' ambition is accelerating our growth," Sierra, October 30, 2026. Bret Taylor and Clay Bavor, "Poppy," the Personal Agent Protocol draft, Sierra, October 9, 2026. Rich Holmes, "Notion's #1 Discovery Channel is AI Tools," Department of Product, November 2, 2026, for Akshay Kothari's survey result and the Granola and Vercel figures as he reports them. Kyle Poyar, "Paid ads are back," Growth Unhinged, November 1, 2026, including Keith Putnam-Delaney's remarks and the State of B2B GTM survey figures. Jason Lemkin, "SaaS Isn't Dead. Old SaaS Is Dead," SaaStr, October 31, 2026, for ServiceNow's non-seat share as he reports it. Tarsilla Moura, "SAP Announced Product Leadership Reorganizations Around AI and the Autonomous Suite," ERP Today, July 1, 2026, context only.

Part of the running argument on Product Leadership: the product org chart was calibrated to a build cost that collapsed, and when anyone can ship, the story, the proof, and the adoption number become part of the product, so product marketing moves under the CPO who owns the outcome.

Related answer: Should product marketing report to the CPO?