Salesforce and Anthropic announced Claudeforce on 27 August: Claude’s reasoning wired into Salesforce data, workflows, business rules, and permissions. The first product is Salesforce in Claude, a plugin with 37 prebuilt sales skills. Sellers can prep a meeting, review deal health, or run a pipeline check against live CRM context without exporting a spreadsheet first. Actions still route through Salesforce, so existing approval rules apply. A single admin connection is meant to cover the team instead of a per-user maze.
The other direction matters if you already run Agentforce. Claude becomes a reasoning model for the Atlas engine, and it powers Agentforce Vibes and Agentforce Coworker by default. It is also available in Agent Builder. For regulated setups, Claude can sit inside the Salesforce trust boundary via Amazon Bedrock. Extra skills start landing through Q3. Salesforce in Claude is in a limited pilot now, with open beta expected in September 2026.
This is not a new chatbot bolted onto a sidebar. The pitch is that models do not run a company on their own, and rigid CRM workflows do not reason. Claudeforce tries to join those two. Marc Benioff called it the “#1 AI” meeting the “#1 CRM.” Dario Amodei framed it as pointing Claude at the customer record companies have spent years building, then letting it act inside that record rather than summarise it in another tab.
If Salesforce already holds your pipeline, this is a September test. If it does not, skip it.If two people still copy next steps from call notes into Opportunity fields, a pilot is worth it.
Meeting prep from live accounts, a deal-health pass before a forecast call, and a governed pipeline update from chat are the jobs that eat mornings on a small sales team. You do not need 37 skills. You need two that touch real records and a human check on anything that changes stage or discount.
If your CRM is HubSpot, Pipedrive, or a Sheet, ignore the launch until a connector exists for your tool. Paying for Salesforce only to unlock Claude inside it is the wrong sequence. Watch the beta, not the keynote. Start the plugin as read-plus-draft. Keep stage changes and quotes on a confirm step. Test one skill on one pipeline for two weeks and measure hours saved against bad updates. That is the only score that matters.