Salesforce splits Claudeforce billing across two vendor contracts

Salesforce splits Claudeforce billing across two separate vendor contracts. Patrick Stokes, Salesforce's president of applications, laid out the mechanics in VentureBeat's interview. Customers pay Salesforce for CRM access through headless consumption pricing, metered on API calls against their user license edition. They then sign a separate contract with Anthropic to cover inference. Stokes put it plainly: "you can't buy this on one piece of paper at the moment."

That's real friction for procurement teams used to one vendor per deal. Two contracts means two invoices, two sets of terms, and two companies to call when something breaks. To employees, it's just a chat window inside their CRM.

The integration traces back to Headless 360, a set of APIs, MCP servers, and CLI tools Salesforce introduced at TDX in March. It exposes Salesforce data, workflows, and governance controls with no user interface attached. An agent acting on CRM records needs that kind of access, not a screen to click through.

Internal adoption already looks past the pilot stage. Salesforce says 83% of its own employees use a Claude-powered Slackbot, and estimates it saves 3.8 million hours a year.

A two-contract deal like this signals how early the integration still is. Vendors often ship the technical piece before they work out commercial packaging, and the gap between those two timelines is where enterprise deals stall. Whoever closes that gap first, with a bundled contract or a revenue-share deal, sets the template other CRM-and-agent partnerships copy.