Claudeforce Is New. Running Salesforce Through Claude Is Not.
Cirrius has been building the Claude-to-Salesforce integration for the past 12 months, long before the Salesforce plugin existed. We sit on both sides of this partnership: Salesforce implementations since 2009, and a Claude Partner Network member that runs its own operations on Claude agents connected to its own Salesforce org.
- Claude wired to Salesforce through MCP servers in our own production org
- 2027 Salesforce Partner of the Year, Customer Value, Consulting Partner
- Claude Partner Network member and OpenAI Services Partner
- A permission model built for agents, before the open beta opens
What 12 months of running Salesforce through Claude taught us.
These are lessons from our own production org, where we wired Claude to Salesforce through MCP servers and lived with the results daily: pipeline reviews, account research, meeting prep, opportunity updates. Claudeforce itself is still in beta, so nobody has field experience with the plugin yet. This is the architecture underneath it.
The value shows up faster than you expect
The first week feels like a parlor trick. By the third week nobody on the team wants to go back. Asking which open opportunities have gone quiet, and drafting the re-engagement note, beats seven clicks and a report filter every time.
Your permission model is about to be stress tested
When a person uses Salesforce through screens, over-provisioned profiles are sloppy but mostly harmless. Nobody clicks through 400 objects. An agent working headlessly can touch everything that user can touch, at machine speed. Per-user OAuth means every call executes with that person’s actual permissions.
AI writes are still writes
Every record an agent creates or updates fires your validation rules, your Flows, and your Apex triggers, exactly as if a human typed it. Your business logic still protects you. A poorly scoped agent can also trip automation you forgot existed. Start read-only, watch what the agent actually does, then open write access one skill at a time.
A trust layer enforces the permissions you have, not the permissions you should have.
The Claudeforce Readiness Assessment. Complimentary.
A structured review of whether your org is ready for agents to act inside it. Four workstreams, scoped to one pilot cohort, delivered as a written findings document you own. No cost and no obligation.
Permission audit on your pilot cohort
We pull the profiles and permission sets for a scoped group of sellers and answer one question: would you be comfortable with an agent exercising every one of these grants at machine speed? This is the single highest-leverage hour in the engagement.
Automation surface inventory
An inventory of the Flows, validation rules, and Apex triggers on the objects your pilot will touch, with the write paths flagged. Agents exercise routes that humans rarely do, and that is where the surprises live.
Connector governance path
A sanctioned route for connecting Claude to Salesforce, with the approval and logging decisions made in advance. Once the open beta opens, teams will connect these systems with or without you. A governed path beats shadow integrations.
Token measurement plan
How to capture real consumption over a four-week pilot before you project org-wide cost. Consumption is usage-based, needs its own Anthropic relationship, and sales workloads burn far less than coding agents. Measured, not guessed.
Where the assessment leads.
When you decide to go further, this is the arc. Each step ends with something your team owns and can operate without us.
Set the strategy
Decide which revenue workflows agents should own and which stay human. Scope discipline beats enthusiasm, and this is where it gets set.
AI readiness assessment
The permission, automation, and data review run against the full org rather than a single pilot cohort, with remediation sequenced by risk.
Brain development
The context layer. The account, product, and process knowledge an agent needs before it can reason usefully over your pipeline instead of summarizing it.
Governance and observability
Logging, approval paths, and write-scope controls, so you can answer what an agent did, why it did it, and what fired downstream.
Agent build and rollout
Read-only first, then write access one skill at a time. Pipeline updates lead, because the blast radius is small and the value is obvious.
Training and change management
The adoption work. Week three is when a team stops going back to tabs, and that only happens if people were taught what to ask.
Claudeforce questions we are hearing this week.
What is Claudeforce?
Claudeforce is the expanded partnership between Salesforce and Anthropic announced on August 26, 2026. It makes Claude the default reasoning model inside Agentforce and Slack, and it puts Salesforce inside Claude through a plugin with 37 prebuilt sales skills for meeting prep, deal health, and pipeline management.
When can my team use Salesforce in Claude?
Select pilot customers have access now. Salesforce expects open beta in September 2026, with skills beyond sales arriving in late 2026. If you want to be ready on day one, the permission and governance work should start now.
Is Claudeforce secure enough for enterprise data?
The architecture is sound: Claude inference for Agentforce runs through Amazon Bedrock inside Salesforce’s trust boundary, and the Salesforce in Claude plugin executes with each user’s own permissions. The honest answer is that Claudeforce is exactly as secure as your permission model. That is why the audit comes first.
Claudeforce-ready in weeks, not quarters.
Every Salesforce customer will hear about Claudeforce at Dreamforce. The teams that prepare now will spend it evaluating results instead of watching demos. Talk to us before the open beta opens. Most engagements reach a Production Readiness checkpoint at Day 30 and a live agent your team owns by Day 90.