The Shift
Agentforce 360 — previously available only to Salesforce customers directly — is now embeddable by ISV partners. Partners can build and commercially distribute AI agents and applications using core Agentforce capabilities. The change closes a gap ISVs have complained about since the 2024 launch: customers had to license Agentforce separately, then license the ISV agent on top, which doubled procurement and broke the per-call cost model. Under the new program, the ISV’s listing is a unified SKU that includes Agentforce platform consumption, billed through Salesforce.
What’s Embeddable
The full agentic stack: the Atlas Reasoning Engine, the Action framework (Apex, Flow, Prompt-Template, MCP, External Service), the Einstein Trust Layer, Data 360 grounding (vector and structured retrieval), and Command Center observability. ISVs get a platform-grade foundation without rebuilding. The boundary: ISVs cannot fork the Atlas planner or substitute their own router for the Trust Layer — those remain Salesforce-managed services. Everything above (Topics, Instructions, custom Actions, conversational UX) is the ISV’s to own.
ISV-owned Salesforce-managed
--------- ------------------
Topics Atlas reasoning
Actions (custom) Trust Layer
System prompts Data 360 retrieval substrate
Eval sets Command Center collector
Conversational UX Audit + compliance plumbing
Pricing + billing Model contracts (BAA, DPA)Distribution
Distributed through AgentExchange. Partners set pricing, manage billing, handle customer relationships. Salesforce provides the platform; the ISV provides the domain specialization and go-to-market. Three pricing models are supported out of the box: per-resolution (best for support), per-seat (best for productivity copilots), and per-transaction (best for finance and ops). Salesforce takes a platform fee on top, transparent in the ISV’s billing console.
Fit
Industry-specific agents (healthcare coding, legal research, financial compliance), workflow-specific agents (procurement, recruiting, CS, AR collections), geography-specific agents (regional payments, multi-jurisdiction compliance). The long tail of verticalized agents ISVs now serve directly without forcing the customer to assemble parts. ISVs that already hold AppExchange relationships get a 60-day head start to migrate, with white-glove onboarding from the Forward Deployed Engineering Partner Network.
Migration Path for ISVs
If you already operate an agent on a third-party stack (LangGraph, CrewAI, custom), the migration is non-trivial but well-documented. The recommended pattern: keep your domain logic in Apex Invocable Methods, port your prompt templates into Prompt Builder, register your tools as Agentforce Actions, and let Atlas handle planning. Eval sets carry over with minor reformatting into the Agentforce Testing Center schema.
What to Watch
Lock-in. Embedding Agentforce 360 ties your agent’s economics to Salesforce model contracts and Data Cloud consumption. Negotiate floor and ceiling pricing in your partner agreement before scale, and keep your domain logic portable enough to redeploy if terms change.
What to Do This Week
If you build agents and sell into Salesforce customers, request Agentforce 360 partner access through the Salesforce Partner Community and scope a 90-day migration plan for your top SKU.
