What Just Changed
Starting November 2026, Salesforce will meter every successful external agent call into Salesforce — whether it arrives over MCP or API — as a Headless Platform Interaction (HPI). Each HPI draws from Flex Credits via the Digital Wallet. Thirty days' notice is promised before the switch flips.
The problem: multiplier rates are listed as TBA. That means any organization currently building or pricing out multi-agent Salesforce workflows cannot produce a defensible total cost of ownership number for Q4 or 2027 budget planning. You are committing engineering and implementation resources against a cost structure that Salesforce has not finished writing.
This is not a hypothetical risk. It is a live one.
Why This Hits Non-Tech Operators Harder
Enterprise software shops have licensing teams and architects who watch these threads. Most non-tech companies running Salesforce do not. They find out about pricing model changes when a renewal conversation surfaces them — or when a Flex Credit balance runs out mid-quarter.
The HPI model is structurally different from seat-based or usage-tiered pricing most operators are familiar with. It charges per successful call, which means volume scales with automation success. The better your agents perform, the faster you burn credits. That inversion of the usual cost curve is worth explaining to finance before they approve an Agentforce rollout budget built on assumptions that no longer apply.
A 13-year Salesforce architect went public arguing this move "locked away three years of progress" and that no other major vendor charges for MCP or agentic API usage. Salesforce reached out directly afterward — which suggests the policy is not fully settled, but also that it is not being walked back.
What to Do This Week
Three concrete moves before the November rollout:
Audit your current agent architecture. Map every external system calling into Salesforce via MCP or API. Each successful call becomes a billable HPI. Volume estimates are your cost floor — and the multiplier will land on top of that.
Put a placeholder in your Q4 and FY27 budgets. Finance needs to know there is an unknown variable. A range — even a wide one — is better than a number that assumes the old model still applies.
Get on the record with your Salesforce AE. Ask directly: what is the multiplier rate, and when will it be published? Document the conversation. If you are mid-contract, ask whether existing Agentforce commitments grandfather under the old terms.
The 30-day notice window Salesforce is promising is not enough runway to renegotiate contracts, reforecast, or redesign agent workflows. The time to pressure-test your architecture and your numbers is now, while the policy is still in motion.