Claudeforce Puts 37 Sales Skills in Claude—but Access Starts as a Pilot

On August 27, Salesforce published details of Claudeforce, its expanded partnership with Anthropic, and Salesforce in Claude, the first product under it. The official launch release identifies a Claude plugin with 37 prebuilt sales skills, including meeting preparation, deal-health review and pipeline review, available initially to selected pilot customers.

This is not a general release. TechTarget’s August 27 coverage independently identifies the 37-skill plugin and its expected September open beta, while no general-availability date has been published.

The 37 skills cover planning, deal analysis and CRM actions

The initial package is built for sales work rather than every Salesforce function. The Salesforce in Claude product page groups the named examples around daily planning, deal strategy, account development, meeting workflows and governed CRM actions, although it does not provide all 37 names as one text catalog.

• Meeting preparation: call preparation and conversation summaries can combine the relevant account history, opportunity context and next steps before or after a customer interaction.
• Deal health: stakeholder mapping, close planning and objection handling are intended to assess an opportunity using calls, emails and recorded stage changes.
• Pipeline review: daily briefings, pipeline reviews and forecast narratives can surface movement, risk and work that requires attention.
• Account and prospect development: the named examples include account planning, lead triage and customer-health analysis.
• Supported actions: meeting scheduling, activity logging, win-loss review and Salesforce hygiene checks extend the plugin beyond retrieval and summarization.

The list establishes a range of packaged workflows, not unrestricted access to every Salesforce function. It also distinguishes a skill from a raw prompt: each skill supplies task-specific instructions and invokes the Salesforce capabilities available for that workflow.

What Claude can read and do—and where it must stop

Salesforce in Claude can work with authorized customer data, accounts, opportunities, pipeline context, workflows and business logic exposed by the connected Salesforce environment. Its onboarding process can also use Salesforce, Slack and other connectors available in Claude to assemble a seller-specific view of accounts and current business context.

For actions, the confirmed scope includes updating supported records, automating pipeline changes and running eligible workflows from Claude. A VentureBeat product briefing describes execution through Salesforce’s MCP server, which inherits the requesting user’s existing permissions and cannot read or write a record that the user is not permitted to access.

The resulting governance boundary can be summarized precisely:

• Readable data: only records and fields available to the authenticated Salesforce user.
• Permitted actions: only supported operations that the same user is authorized to perform.
• Business enforcement: actions are routed through Salesforce, so configured business rules remain in the execution path.
• Write autonomy: the organization controls when Claude must request confirmation before actions such as 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 already been tested by external customers. The pilot is therefore important for assessing how those boundaries behave across real enterprise configurations.

Pilot access requires central administration and existing permissions

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 does not make the product available to organizations outside the selected pilot.

A prospective pilot customer’s access checklist is currently limited to what the public materials establish:

• The organization must be selected for the pilot; no general self-service installation route has been published.
• 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 choose how much write autonomy to allow and which actions require human confirmation.

Important commercial and deployment details remain unresolved. The public launch materials do not specify pilot-selection criteria, pricing, regional availability, supported Salesforce editions or the required Claude subscription. They also do not establish whether every pilot organization will receive identical skills, limits or support terms.

The September beta is broader testing, not general availability

The September milestone remains prospective: the current plan is to begin an open beta in September 2026. “Open” indicates broader access than a hand-selected pilot, but “beta” still describes a pre-release stage in which eligibility, functionality, packaging and support conditions may change.

The rollout therefore has 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 present scope is also narrower than the broader Claudeforce roadmap. Salesforce in Claude starts with sales skills, while additional prebuilt capabilities for other business functions are planned for later in 2026. Service, marketing, commerce, revenue, field service and other areas displayed as forthcoming should not be counted as part of the current sales pilot.

As of August 28, the confirmed position is specific: Salesforce and Anthropic have packaged 37 sales skills for use inside Claude, selected customers can pilot them under existing Salesforce permissions and business rules, and September is the target for broader beta access. General availability, final pricing, deployment eligibility and evidence from external pilot use remain outstanding.

Also read:

• Claude Security Replaces Claude Code Security—but Its Hosted Beta Is Enterprise-Only
• Mobile Banking Puts Your Bank in Your Pocket—But Not Every App Is a Bank
• Yale Puts Expanded Aid Into Practice—but $200,000 Is Not a Free Ride