Full narration of the briefing. Click a section heading to jump the player to that moment.
Salesforce announced Headless 360 at TDX in April. It is the largest platform change Salesforce has made in over a decade, and commercially it is the least defined. Every capability in Data 360, Customer 360, Agentforce and Slack is now exposed as an API, an MCP tool or a CLI command for agents. There is no standalone price, and there will not be one.
The cost flows through meters that already exist, and two of those meters have no price yet. I am Claire, Tom is with me, and this briefing is what bills today, why January 2027 matters, and what a renewal signed before then must say.
Here is the rate card as it stands. Ordinary record operations through MCP consume your org's daily API allocation. Anything that touches a metered service draws Flex Credits: an Agentforce action is twenty credits, about ten cents, a Voice action thirty, at roughly five hundred dollars per one hundred thousand credits. Data 360 queries run on tiered credits that reset monthly.
Employee agent access is a per user add on at about one hundred twenty five dollars a month. And two usage types, record operations and process invocations, sit on the card with no multiplier at all. Those two are most of what a headless estate generates.
Salesforce has priced by the human in front of a screen for twenty five years. Headless 360 removes the human and replaces the seat with a stream of actions, queries and invocations, and value moves to the credit pool. That leaves three price lists on one product, per conversation, per action and per user, and headless traffic lands wherever the order form says. Credits carry no rollover and do not overage; when they run out, operations fail or throttle until you buy more.
In the headless estates we have modeled, account team burn forecasts ran forty to seventy percent below actual consumption.
Three calendars converge in the last week of January 2027. Salesforce's fiscal year closes on January thirty first, the quarter of most discretion and least patience. The missing multipliers: record operations and process invocations joined the rate card in 2026 without a price, and Salesforce prices a new construct two or three quarters after announcing it. Sign a three year order form before that price exists and you have accepted it sight unseen.
And seat counts: renewals signed now are built for how people used Salesforce in 2025, while by 2028 agents will do a material share of that work. The seats stay on the invoice; the credits arrive on top.
Take a mid sized estate: twenty five hundred CRM users on Enterprise Edition, renewing for three years with Agentforce attached. Salesforce's opening structure: seats flat with a seven percent uplift, the per user add on on every seat, five million credits a year at list with no rollover, record operations silent, top ups at card rate. About thirty nine point five million dollars, plus the open lines. The buyer side structure: fifteen percent true down at anniversary, uplift capped at three, six hundred named agent users staged to twelve hundred, eight million credits on a Pre Commit thirty percent below list with rollover.
About twenty seven point seven million, every line capped.
The response is a sequence. Inventory what already runs headless: every integration, agent, MCP connection and coding assistant calling the org today, by usage type and volume. Most estates find traffic they did not know they had. Forecast in the meters, not in seats: convert the planned agent use cases into actions, record operations, process invocations and Data 360 queries per month for three years, using production ratios, and expect a large gap against the account team's number.
Define the add on population as the people who invoke agents in their work, not every CRM seat, and get that definition into the order form. Then pin every rate that exists, with the rate card version attached and later card changes excluded.
The move from this briefing: write a treatment for the rates that do not exist. Record operations and process invocations are either included within the API allocation for the term, or priced at a stated multiplier no higher than a standard action. Silence is acceptance. Buy credits on your forecast on a Pre Commit, with rollover, top ups at the committed rate, and the conversion ratio fixed at signature.
Secure true down of ten to fifteen percent at each anniversary, the clause Salesforce resists most. And keep the architecture out of the deadline. The full research note is free to download under this video, at redresscompliance dot com slash newsletter slash september.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Salesforce negotiator