Claude for Sales is Anthropic’s setup for sales teams: a Sales plugin, Salesforce in Claude, and CRM connectors such as HubSpot, so reps get account briefs, call prep and follow-up drafts built from live CRM data. This explainer covers what the program includes, how the Salesforce and HubSpot connectors handle permissions and write approvals, what reps approve, and how to log CRM access through a gateway you host.
Anthropic publishes a Claude for sales page that names account research, meeting prep, proposals, forecasting and CRM updates as the work it hands off, and it lists the Team and Enterprise plans. The pieces below connect Claude to the CRM, call recorder and enrichment tools a team already pays for, and the setup choices decide what Claude can read, what it can change, and who signs off.
What Claude for Sales Includes
Three parts make up the program:
- The Sales plugin. Anthropic publishes it with commands for /call-summary, /forecast and /pipeline-review, and skills for account research, call prep, daily briefings, outreach drafts and competitive intelligence. It connects through the Model Context Protocol (MCP) to a CRM, call transcription, enrichment and chat tools, and it also works on pasted notes or an uploaded CSV.
- Salesforce in Claude. A plugin built with Salesforce, in beta since September 2026.
- Connectors. Anthropic’s sales page lists Salesforce, HubSpot, Gong, Fireflies, Clay, ZoomInfo, Apollo, Outreach and Docusign.
Claude for Microsoft 365 adds PowerPoint and Word for proposals and RFP responses. On Team and Enterprise, Anthropic does not train models on customer data by default, and Salesforce actions run under the seller’s existing Salesforce permissions, per the sales page.
Anthropic’s help center also has a Claude for sales guide built around Projects, which hold reference material that a team’s chats draw on. Project sharing is available on Team and Enterprise, so a sales team can keep one shared project with its positioning, product sheets and objection notes, and every rep’s account briefs and follow-ups start from the same approved material. When positioning changes, the sales lead updates that project once.
The Claude Sales Plugin and Its Skills
Anthropic’s Sales plugin is open source in its knowledge-work-plugins repository on GitHub. Its README says it is built for Claude Cowork and also works in Claude Code, and Claude’s plugin marketplace lists it as Anthropic verified, with the /call-summary, /forecast and /pipeline-review commands described above. The plugin page on claude.com may show an earlier version, and the repository, now at version 2.1.0, is the current source. Version 2.0 in the repository took the plugin from 9 to 36 skills, which run when a request matches or by name, such as /sales:call-summary. The repository groups them by the rep’s day, as checked on November 3, 2026:
- Your day: setup, daily-briefing, call-prep, call-summary, inbox-sweep, schedule-meeting, log-activity, end-of-day and weekly-wrap.
- Accounts and prospecting: account-research, account-context, stakeholder-map, draft-outreach, lead-triage, route-lead, account-tiering, account-plan and expansion-whitespace.
- Deals: deal-review, deal-advance-gap, deal-signals, deal-slip-scenario, close-plan, handle-objection, competitive-intelligence, create-an-asset and update-opportunity.
- Pipeline and forecast: pipeline-review, crm-hygiene-check, forecast, team-pipeline, rep-context and win-loss-review.
- Customers: customer-health, customer-voice and renewal-radar.
The 2.0 skills read the CRM’s own stages and fields and run the same on Gmail or Outlook, Slack or Teams. With nothing connected, a skill works from an uploaded pipeline export or transcript. When a rep asks, skills can update CRM records, draft or send email, post to chat and book meetings within each connector’s permissions. Changes a skill suggests on its own go to the rep first, with the evidence behind them. In version 2.0 the forecast skill writes a commit, best-case and pipeline narrative. The create-an-asset skill builds decks, one-pagers and leave-behinds from account data.
The plugin’s connector file lists Salesforce, HubSpot, Close, Gong, Fireflies, Clay, ZoomInfo, Apollo, Outreach, Slack and Microsoft 365 among others. Salesforce and Microsoft 365 come included, and the organization’s admin enables each of them in Claude before reps sign in. For scheduled runs such as a morning briefing, the README advises setting send, post and write tools to ask, so a person approves each change. To adapt these skills to your own stages, templates and approval rules, our Claude Cowork plugins and custom skills service builds and packages a company version of the plugin.
Connecting Salesforce: Salesforce in Claude and Hosted MCP
Anthropic’s September 2026 announcement describes Salesforce in Claude as “a plugin built with Salesforce that brings a seller’s accounts, opportunities, and pipeline into Claude”, with 37 skills for the daily work of account executives. Anthropic’s Salesforce in Claude help article says it is in beta on all paid plans for organizations Salesforce approves, and that it works in chat and Claude Cowork on web and desktop. Setup runs in three steps:
- An admin requests access through Salesforce AgentExchange.
- The admin connects Salesforce once for the organization and chooses which groups get the plugin.
- Each seller signs in with their own Salesforce account, and Claude sees only what that seller’s Salesforce permissions allow.
By default, Claude asks the seller to approve each proposed change before it writes to Salesforce, with the options allow once, always allow or deny. Keep the default for opportunity stage, amount and close date, and reserve “always allow” for routine entries such as logging a call. A Slack connector covers deal-channel summaries and account-team threads that the skills can read and write.
Building an AI agent for Salesforce
Teams building their own AI agent for Salesforce can use Salesforce Hosted MCP Servers. Salesforce says any compatible AI client, including Claude, ChatGPT, Cursor or a custom agent, can connect to them, with per-user OAuth 2.0 and PKCE. A custom agent suits work outside the plugin’s 37 skills, such as a renewal review that combines Salesforce opportunities with product usage data from your own warehouse, or a deal desk check that compares a proposed discount with your pricing rules.
Connecting HubSpot: User Permissions and Write Approvals
HubSpot builds the HubSpot connector for Claude, which appears in Claude’s directory as Anthropic-verified and added in November 2025, and it requires a paid Claude plan. HubSpot’s setup guide for the Claude connector describes the controls:
- Each user connects with their own HubSpot login, and the connector “automatically respects the user permissions defined in HubSpot”.
- Super Admins and users with App Marketplace Access can connect it directly, and everyone else needs a Super Admin to approve the connector first.
- It views, creates and updates records, and deletions stay in HubSpot itself.
- Custom Sensitive Data properties stay outside the connector’s reach.
- HubSpot recommends setting write tools to “Needs Approval”.
With write tools on “Needs Approval”, a rep sees each proposed contact or deal update before it lands, the same review pattern as the Salesforce plugin. That gives a Claude CRM setup one rule across both systems, where Claude proposes each change and the rep approves it.
Account Briefs, Call Prep and Follow-Ups: What Reps Get
Anthropic’s sales page centers on the work around each meeting. The table shows how that work splits between Claude and the rep.
| Task | Manual today | With Claude | What the rep approves |
|---|---|---|---|
| Account brief | Read CRM history, emails and news before a call | Pulls account history, open opportunities and recent activity into a one-page brief | The brief’s accuracy before sharing it |
| Call prep | Write an agenda and discovery questions | Drafts an agenda and questions from the brief | Which questions to ask |
| Call summary and follow-up | Write notes and an email after the call | /call-summary turns the transcript into action items and a draft follow-up email | The email before it sends |
| CRM update | Type notes, next steps and stage changes | Proposes field updates from the call | Each change, through the approval prompt |
| Pipeline review | Export a report and scan for stale deals | /pipeline-review flags stale deals and suggests a weekly action plan | Which deals to act on |
| Forecast | Build commit and best-case numbers in a spreadsheet and write the forecast notes | /forecast writes the commit, best-case and pipeline narrative from open opportunities or an uploaded pipeline export | The number submitted to the manager |
Anthropic’s sales page also shows a scheduled task that sends pre-meeting briefs to Slack, so a rep starts the day with a brief for each external meeting. Call transcripts come from Gong or Fireflies through their connectors, and enrichment from Clay, ZoomInfo or Apollo. Measure the output the way a sales manager reviews a rep’s prep, by sampling briefs and follow-up drafts and counting the facts the rep had to correct, such as a wrong contact, a stale opportunity amount or a missed next step.
Call recorders and enrichment tools
Anthropic’s sales page lists Gong and Fireflies for call transcripts, Clay, ZoomInfo and Apollo for enrichment, and Outreach for sequences. Each vendor sets its own connector rules, so check four things before a team connects one: what data the connector reads, which actions it can take, whether it inherits each user’s permissions in that tool, and who in the company approves it. A call recorder that inherits user permissions keeps a rep to their own calls, which matters when the transcripts include pricing or legal terms.
How a Claude for Sales Rollout Runs
A rollout follows the same pattern whatever the team size. A pilot group of reps and a sales manager start with the CRM connected read-only and the Sales plugin installed, producing account briefs and call prep. Once the briefs check out against the CRM, write tools come on with approval prompts for call logs, next steps and opportunity fields. The team agrees which documents reps may share with Claude, such as contracts or pricing sheets, and writes that into the AI use policy. Reps get short training on the approval prompt and on checking a brief before they share it. The manager reviews a sample of briefs, follow-ups and CRM changes, and the rollout widens to the next group when the correction count is low enough for the manager’s standard.
AI for Sales Beyond Claude: ChatGPT and Prospecting Agents
ChatGPT for sales draws on the same systems. HubSpot publishes a connector for ChatGPT that respects HubSpot user permissions and can create and update CRM records, including contacts and deals. Salesforce lists ChatGPT among the compatible clients for its Hosted MCP Servers. On OpenAI’s side, ChatGPT Business includes apps that connect to internal tools, and Enterprise adds a connector registry, per OpenAI’s pricing page. The permission and approval settings in this guide carry over to whichever assistant a team chooses.
Prospecting can also run through an agent. Our self-hosted AI SDR agent researches each new lead, drafts a first-touch email for a rep to approve, follows up and books meetings, all on your CRM data in your own cloud account or on your own servers.
Logging CRM Access Through a Self-Hosted MCP Gateway
Vendor connectors handle per-user sign-in and CRM permissions. Sales teams also want Claude to reach systems that have no official connector, such as a pricing database, a product usage warehouse or a quoting tool. Those connect through custom MCP servers, with a self-hosted MCP gateway in front of them. What runs where:
- Anthropic’s infrastructure: the Claude model, chat, Cowork and the plugins.
- HubSpot’s and Salesforce’s clouds: their official connectors, under each rep’s own login.
- Your servers or cloud account: the MCP gateway, the custom MCP servers behind it, and a log of every tool call with the user, the tool and the arguments.
On Team, only Owners and Primary Owners add custom connectors, each user then connects individually, and Owners can disable specific tool calls, per Anthropic’s help center. Point the custom connector at the gateway, start each new tool read-only, and add write tools one at a time with an approval step. Enterprise adds audit logs on the Claude side. Our self-hosted MCP gateway covers that build.
How NeuralChainAI Sets Up Claude for Sales Teams
NeuralChainAI connects, scopes and governs Claude for sales teams. The work covers:
- Rollout. Claude Team or Enterprise with SSO, roles, the Sales plugin, an AI use policy and rep training, through our Claude Team and Enterprise rollout service.
- Connectors. Salesforce and HubSpot with per-user sign-in and write approvals on, plus custom MCP servers for pricing, usage or quoting systems, through our AI integration services.
- Logging. Every tool call recorded through a self-hosted MCP gateway on your infrastructure.
To connect Claude to your CRM, call recorder and internal sales systems with per-user permissions and approval steps, see our AI integration services, or book an AI strategy session to plan which sales workflows Claude takes on.