Choose Salesforce when its existing workflows and managed governance justify the platform commitment. Consider self-hosted EspoCRM when you want more control over AI integrations and have someone accountable for operating them. For a small professional-services firm, our recommendation is to test one useful CRM handoff before considering migration. Salesforce's announced agent-access pricing deserves attention, but its unpublished rate isn't a reason to replace a working system.
The job is getting useful work out of your CRM
An operations manager wants a usable follow-up draft, with the right account context, ready for review. The choice of CRM should make that job easier without creating an operating burden the practice can't support.
Salesforce's planned agent-access meter adds another consideration: what happens to the cost of that workflow as an agent makes more calls?
We prefer an operating model where we can connect AI tools to business records through an ordinary API and take responsibility for those connections. That preference comes with maintenance work. It also means accepting an interface we find less polished.
For us, that's a worthwhile trade. Your firm may reasonably decide otherwise.
What Salesforce has announced
The primary sources were checked on October 28, 2026. Salesforce's September 17 policy describes a new billing model alongside agent registration and security controls, targeting a November release. November isn't a confirmed first-billing date.
Under the announced model, every successful call a registered agent makes through MCP or direct API is counted as a Headless Platform Interaction, or HPI. Switching from MCP to a direct API doesn't, by itself, put registered-agent traffic outside that model.
The price is still unresolved. On October 28, Salesforce's policy said agentic usage wasn't being metered, the HPI credit multiplier remained TBA, and Salesforce would provide 30 days' notice when a numerical multiplier is added and metering begins. The linked rate card also listed HPI as TBA.
That leaves a genuine budgeting question. It doesn't establish a current surcharge on every API call. Salesforce explicitly says traditional integration pricing and security options remain unchanged.
Applicability matters too. Purchasers on or after September 17 must register API-using agents within three months of notice that Agentic Identity is available. Existing API-agent customers register and migrate their connections at renewal. Use of any Salesforce MCP server requires registration within three months' notice for all customers. HPI consumption is production-only; the exemption for sandboxes, scratch orgs and Developer Edition concerns HPI, not every possible AI charge.
Salesforce's identity model has a useful purpose: an agent gets a distinct identity rather than operating as the person it assists. Scoped permissions and visibility into agent activity are benefits worth considering alongside the eventual bill.
What we use instead
At Chrysis Networks, we use EspoCRM with separately integrated AI tools for research and record maintenance, plus an external n8n/Microsoft Graph bridge that creates unsent Outlook drafts for human review and sending.
The verified CRM connection uses EspoCRM's ordinary REST API and an instance-generated OpenAPI description. OpenAPI describes how software can interact with the CRM. It isn't an AI model, and it doesn't make the business autonomous.
Our AI tools use a separate API identity with role-defined access. The email bridge is our integration, not a claim that EspoCRM core includes native Outlook draft transport. A person reviews and sends the message.
This gives us a concrete way to put AI to work around business records without treating the CRM's interface as the only place work can happen. For a practice considering the same approach, the useful starting point is one handoff, such as preparing a follow-up for review. Define the records it needs and what a person must approve before building it.
The tradeoff we'd rather make explicit
We find our EspoCRM interface less polished than Salesforce's. That's our preference, not a usability benchmark. A screen your staff dislikes can become a daily cost, so have the people doing the work try the proposed workflow.
EspoCRM's self-hosted open-source core has no per-user software fee. Hosting and model use still cost money. Someone also has to maintain the integrations and keep the system running; connected services may carry their own licensing costs.
We haven't audited a like-for-like total-cost comparison, so we won't promise this route is cheaper. Self-hosting the CRM also doesn't mean external AI processing stays on that server or that the setup is more secure.
Choose by fit, not by reaction
- Salesforce fits when established workflows and managed governance are worth the ongoing platform commitment. Avoid assuming either an HPI price or that your current contract covers every proposed agent workload.
- Self-hosted EspoCRM with a separate AI integration fits when operational control matters and an accountable operator can maintain it. Avoid this route when you expect maintenance-free operation or identical Salesforce functionality.
- Keeping your current CRM and improving one existing process fits when the handoff can be fixed without migration. Avoid postponing a demonstrated recurring problem merely because a full platform decision feels too large.
Our recommendation is to test the handoff first. Record today's handling time, then assess the proposed workflow's review effort and running costs. Include migration and maintenance in any replacement decision. A published HPI rate could change the calculation; so could discovering that Salesforce already handles the job well, or that nobody can own a self-hosted system.
Describe the CRM handoff you'd like to stop doing by hand, including how often it happens and who approves the result.
Frequently asked
Is Salesforce charging for every AI API call now?
No. The October 28 policy check found agentic usage wasn't yet metered and the HPI multiplier was TBA. The announced model covers successful registered-agent calls through MCP and direct API; traditional integrations retain their existing pricing and security options.
Can we calculate an HPI price from Flex Credits pricing?
Not yet. The price per credit doesn't establish the number of credits per HPI. The HPI multiplier and your contract are needed.
Does EspoCRM run these AI workflows by itself?
Our demonstrated setup uses separately integrated AI tools through REST, plus an external bridge for unsent Outlook drafts. People review and send.
Should we migrate before November?
We wouldn't recommend migration solely because of an unpublished rate. November is a release target; evaluate your actual workflow and contract before committing.