Salesforce built Agentforce to be the reason you never leave the CRM. Claude takes a different approach: it works across whatever tools your business actually runs on, not just inside one vendor's data model. For Australian businesses weighing up AI agents this year, the real question isn't which platform is smarter. It's which one fits how your team actually works, and what each choice costs once you look past the demo.
What Agentforce Actually Does
Agentforce lives inside Salesforce. It reads and writes against your existing CRM objects: leads, opportunities, cases, and the point of that connection is real. If your entire operation already runs on Salesforce, Agentforce is a fast way to get an agent in front of customers, because the templates for support, SDR and service agents are built for you to configure rather than build from scratch. The trade-off shows up the moment a workflow needs to touch something outside the CRM. A finance system, a shared drive, a scheduling tool, or internal documentation that never made it into Salesforce all need a separate integration, and Agentforce pricing scales per conversation on top of your existing Salesforce licence.
Where Claude Fits Differently
Claude isn't tied to a single system of record. Built with Claude Agent Skills and Model Context Protocol connectors, a Claude-based agent can work across Xero, Gmail, a shared drive, internal documentation and a Salesforce instance at the same time, reasoning across all of them in a single workflow instead of staying fenced inside CRM objects. For a Sydney professional services firm, that could mean one agent that checks an invoice in Xero, reads the client's last three emails for context, and drafts a follow-up, all in a single pass. The trade-off runs the other way from Agentforce: a custom Claude agent takes more setup than a pre-built template, because you're defining the workflow instead of configuring one someone else designed.
Data scope: Agentforce reasons over Salesforce objects only. A Claude-based agent reasons across whatever tools you connect through MCP.
Setup time: Agentforce templates can go live in one to two weeks. A custom Claude agent typically takes three to six weeks, depending on how many systems it needs to touch.
Cost model: Agentforce charges per conversation on top of Salesforce licensing. Claude is priced on usage, which tends to undercut per-seat CRM add-on pricing once volume grows.
Lock-in: Agentforce's agent logic lives inside Salesforce. A Claude agent's workflow definitions are portable if you ever change CRM.
Governance: Agentforce inherits Salesforce's existing permission model. A Claude agent needs its access defined per connected tool, which takes more upfront design but gives finer control over what it can read and write.
The Real Cost, in Australian Dollars
Cost is usually where this decision gets made in practice. A mid-sized Sydney business running Agentforce across a 15-seat sales team can expect to add roughly $45,000 a year in conversation-based fees on top of existing Salesforce licensing, before counting the integration work needed to reach anything outside the CRM. A Claude-based agent covering the same ground, CRM interactions plus email, finance and internal documentation, typically lands lower on a per-outcome basis once it's built, because pricing tracks usage rather than per-seat conversation counts. The build cost is higher upfront. The running cost is usually lower once the agent is doing real work across more than one system, not just the CRM.
There's a compliance angle too, particularly for firms handling client financial data under the Privacy Act. Agentforce's data handling sits inside Salesforce's existing compliance posture, which is a known quantity if you're already a Salesforce customer. A Claude-based agent built with MCP connectors needs its access boundaries defined explicitly per tool. That's more work at setup, but it gives a business clearer visibility into exactly what the agent can read and write, tool by tool, rather than inheriting a single vendor's permission model wholesale.
When to Choose Which
Choose Agentforce if your entire workflow already lives in Salesforce, you want a templated agent live inside a month, and the agent doesn't need to touch systems outside the CRM.
Choose a Claude-based agent if your workflow spans more than one system (CRM plus finance plus email plus internal documentation), you want the agent's logic to survive a future CRM change, or per-seat conversation pricing doesn't scale well against your headcount.
Consider running both if you want Agentforce handling pure CRM tasks such as lead scoring or case triage, while a Claude-based agent handles the cross-system work Agentforce can't reach.
Neither platform is the wrong choice on its own. Agentforce suits a business that lives entirely inside Salesforce and wants a fast templated rollout. Claude tends to fit better once the workflow crosses more than one system, which describes most Australian businesses within a year or two of adopting any AI agent at all. If you're weighing this up for your own team, we run a free session mapping out exactly what an agent would need to touch across your stack and what it would cost to build it properly. Book a session and we'll walk through it against your specific tools.
