The $1.5 billion Agentforce ARR figure and the Claudeforce launch landed the same morning. Read the ARR number against its new, wider definition. Read the product news as Claude on Salesforce's own surfaces, and Salesforce data reachable inside Claude.
Salesforce reported Q2 FY27 revenue of $11.3 billion, up 11% year over year, and said Agentforce annual recurring revenue exceeded $1.5 billion, up over 240% year over year (Salesforce, 2026). Marc Benioff called it one of the company's best quarters ever. The same day, Salesforce and Anthropic announced Claudeforce. Claude is now the default model for Slackbot and Agentforce Coworker, a reasoning model for the Atlas Reasoning Engine, and the engine behind Salesforce in Claude, a plugin with 37 prebuilt sales skills.
Revenue cleared the most commonly cited Wall Street estimates by a thin margin. GAAP earnings per share of $4.29 include about $2.6 billion in gains tied to Salesforce's stake in Anthropic (CNBC, 2026). Treat the operating results and that investment gain as separate facts.
Claudeforce Launches With a 37-Skill Plugin
Claudeforce launches with Salesforce in Claude. The plugin carries 37 sales skills, including meeting prep, deal health review, and pipeline review. A seller can pull live revenue context and push an update back into Salesforce without opening the CRM, or customer relationship management platform. Salesforce says those actions still route through Salesforce so existing business rules apply.
Select pilot customers have access now. Open beta is set for September 2026. More skills are due later in the year. Pricing and packaging remain subject to change.
Claude also runs inside Salesforce's own products. It powers Agentforce Vibes and Agentforce Coworker by default, is available in Agent Builder, and serves as a reasoning model for Atlas. Through Amazon Bedrock, Claude is available inside the Salesforce Trust Boundary. Salesforce will put Claude Code and Claude Enterprise on its own developers' and knowledge workers' desks as preferred tools.
Dario Amodei's line described placement: Claude belongs in the systems where commercial work already happens.
Salesforce Changes What Sits Inside Agentforce ARR
Effective this quarter, Agentforce ARR includes Slackbot and Headless 360, alongside the company's other AI offerings (Salesforce, 2026). Combined Agentforce and Data 360 ARR reached nearly $3.9 billion, up over 210% year over year. The $1.2 billion Agentforce ARR figure Salesforce reported for Q1 FY27 used a narrower set of products.
Slackbot users grew over 150% quarter over quarter. Data 360 ingested 104 trillion records, up 355% year over year (Salesforce, 2026). Part of the 240% Agentforce ARR growth is the wider definition. Part is demand. Salesforce has not said how much is each.
Salesforce also has not separated new customer growth from expansion inside its existing base:
- Net New Annual Order Value, or NNAOV, growth was "the strongest it's been in four years," according to chief financial officer Robin Washington (Salesforce, 2026). That is a company-wide figure, not an Agentforce split.
- Bookings for Agentforce One Edition and Agentforce for Apps more than doubled quarter over quarter (Salesforce, 2026). Those product editions sit on existing Sales and Service contracts, which counts as expansion, not new logos.
- Salesforce has not disclosed a net-new Agentforce customer count, or what share of the $1.5 billion comes from new accounts versus upsell into accounts that already had Salesforce.
Salesforce Keeps the Rules Regardless of the Interface
Salesforce in Claude does not hand the system of record to Anthropic. It changes the screen. Permissions, business rules, and the audit trail still run through Salesforce, whether the seller opens Claude, Slack, or the CRM.
That is the same design behind Headless 360: own the data and the rules, even when the customer never opens a Salesforce screen. Claudeforce applies that design to a larger model partner.
Salesforce in Claude does not remove Salesforce from the workflow. The seller can work inside Claude. Permissions and the audit trail still run through Salesforce.
Can Customers Opt Out of Claude?
The Claudeforce announcement does not force Claude onto every surface. The details vary by product.
- Agentforce and Atlas. Customers still pick the org-level model in Setup. Salesforce's current Help documentation lists three options: Salesforce Default, a Salesforce-managed mix in which new Builder agents use GPT-4.1 and legacy agents use GPT-4o; AWS-Hosted, meaning Claude running on Amazon Bedrock inside the Trust Boundary; and Google Gemini. Admins can also override the model per agent or subagent. Custom actions that call a prompt template, Apex, or the Models API can use other Salesforce-managed models or a customer's own model, brought in under what Salesforce calls BYOLLM, or bring your own large language model.
- Salesforce in Claude, the 37-skill plugin. This one is optional. It runs on Claude's side of the relationship. A customer who does not connect it does not use it.
- Slackbot, Agentforce Coworker, and Headless 360. The Claudeforce release states that Claude is the default model on these surfaces. It does not state that customers cannot change it, and Salesforce has not published a per-product opt-out. Slack admins can already restrict or block Slackbot access at the workspace level. Whether the underlying model can be swapped after this announcement is not addressed in the release. Treat that as unresolved until Salesforce's documentation catches up.
- Claude Tag in Slack. A separate product. A workspace admin has to approve it before anyone can use it.
The practical split: a customer can keep Agentforce on GPT or Gemini and ignore the Claude plugin entirely. That same customer cannot assume Slackbot and Agentforce Coworker stay off Claude without an explicit admin setting, because Salesforce has not shown that toggle in this release.
What Happens Next
Salesforce holds Investor Day alongside Dreamforce on September 16, and the September open beta will start answering questions that matter to customers already on Salesforce or evaluating Claude:
Will Salesforce in Claude carry its own price, or does it ride on an existing Agentforce license?
Will regulated customers using the Trust Boundary be able to map where their data sits once Claude, Bedrock, and Salesforce touch the same workflow?
Will the 37 sales skills perform as expected once they roll out to sales teams beyond the pilot group?
