Salesforce and Anthropic have packaged 37 prebuilt sales skills into Claude through a new product called Salesforce in Claude, but the first release is limited to selected pilot customers. The product, announced August 27 as the first offering under the expanded Claudeforce partnership, covers meeting preparation, deal-health review, and pipeline review for sales teams. TechTarget's coverage confirms the 37-skill plugin and points to an open beta expected in September, with no general availability date published.
The skills are built for sales workflows rather than every Salesforce function. Salesforce's product page groups them around daily planning, deal strategy, account development, meeting workflows, and governed CRM actions, though it doesn't publish all 37 names in a single catalog.
What the 37 skills cover
Meeting preparation gets the most direct treatment. Call preparation and conversation summaries pull relevant account history, opportunity context, and next steps before or after a customer interaction.
Deal health tools include stakeholder mapping, close planning, and objection handling, which assess an opportunity using calls, emails, and recorded stage changes. Pipeline review features deliver daily briefings, pipeline reviews, and forecast narratives that surface movement, risk, and work requiring attention.
Account and prospect development covers account planning, lead triage, and customer-health analysis. Supported actions extend beyond retrieval and summarization to meeting scheduling, activity logging, win-loss review, and Salesforce hygiene checks.
Each skill is a packaged workflow with task-specific instructions, not a raw prompt. That distinction matters for sales teams evaluating what the tool can actually do.
What Claude can read and do
Salesforce in Claude works with authorized customer data, accounts, opportunities, pipeline context, workflows, and business logic exposed by the connected Salesforce environment. Its onboarding process can use Salesforce, Slack, and other Claude connectors to assemble a seller-specific view of accounts and current business context.
Confirmed actions include updating supported records, automating pipeline changes, and running eligible workflows from Claude. Execution runs through Salesforce's MCP server, which inherits the requesting user's existing permissions. Claude cannot read or write a record the user isn't permitted to access.
The governance boundary breaks down cleanly:
- Readable data: only records and fields available to the authenticated Salesforce user
- Permitted actions: only supported operations that same user is authorized to perform
- Business enforcement: actions route through Salesforce, so configured business rules stay in the execution path
- Write autonomy: the organization controls when Claude must request confirmation before actions like external communication or record updates
These are architectural claims about inherited controls, not evidence that every custom object, validation rule, approval chain, or unusual permission combination has been tested by external customers. The pilot is where those boundaries get tested across real enterprise configurations.
Pilot access and the September beta
The connection model is administered centrally: an administrator connects Salesforce in Claude once, while authentication and permissions continue to be managed through the organization's Salesforce environment. Central setup reduces per-user integration work, but it doesn't make the product available outside the selected pilot group.
Public materials establish a limited access checklist. The organization must be selected for the pilot; no self-service installation route exists yet. An administrator must establish and manage the Salesforce connection. Each seller must already hold the record and action permissions required by the workflows they intend to use. Existing business rules, validation logic, and approval controls remain relevant to Claude-mediated actions. The organization must decide how much write autonomy to allow and which actions require human confirmation.
Commercial details remain unresolved. The launch materials don't specify pilot-selection criteria, pricing, regional availability, supported Salesforce editions, or the required Claude subscription. They also don't establish whether every pilot organization receives identical skills, limits, or support terms.
The September milestone is broader testing, not a finished release. "Open" indicates wider access than a hand-selected pilot, but "beta" still describes a pre-release stage where eligibility, functionality, packaging, and support conditions may change.
That leaves three distinct states: selected customers have pilot access now, a wider beta is planned for September, and a production release has no published date. Calling the September beta general availability would erase the difference between expanded testing and a finished commercial release.
The current scope is also narrower than the broader Claudeforce roadmap. Salesforce in Claude starts with sales skills, with additional prebuilt capabilities for service, marketing, commerce, revenue, and field service planned for later in 2026. Those forthcoming areas aren't part of the current sales pilot.
Sales teams interested in the underlying technology can track related training through AI for Sales resources or Claude courses to build familiarity with the platform before broader access arrives.
Why this matters for sales professionals
The pilot structure means most sales teams can't use this yet, but the 37-skill list signals where Salesforce and Anthropic believe AI assistance adds value in sales work: meeting prep, deal health, pipeline review, and CRM hygiene. Those are the workflows where sellers spend time on manual data gathering and record updates.
For sales leaders, the governance model is the detail worth watching. Claude inherits each user's existing Salesforce permissions, which means the tool's reach is bounded by what the organization already allows. The pilot will show whether that inheritance holds up across complex permission schemes, validation rules, and approval chains in real enterprise environments.
The open questions - pricing, eligibility, edition support, and general availability - will determine whether this becomes a standard sales tool or a niche offering. For now, the confirmed position is specific: 37 sales skills packaged for Claude, pilot access for selected customers under existing Salesforce permissions, and a September target for broader beta access.
Your membership also unlocks:
