Anthropic and Salesforce shipped Salesforce in Claude in beta on September 15. It is a plugin built with Salesforce: accounts, opportunities, and pipeline inside Claude, plus 37 skills aimed at account research, call prep, pipeline review, and CRM updates. Slack is bundled so deal-channel threads can be read and written. Claude proposes the change. The seller approves. Then Salesforce is the system of record. Admins connect the org once. Each seller signs in with their own Salesforce credentials and sees only what those credentials already allow. Team and Enterprise: Anthropic says it does not train on your data by default. GitLab, Siemens, and Legora are named deployers; Anthropic says 7,000 Salesforce sellers already use it. Alexa Vignone, Salesforce’s President and CRO, is quoted in the same post.
That is a sales product. A music company that runs the book in Salesforce will treat it as a rights-and-roster product whether they mean to or not.
What the agent can do to a music record
From the blog, the skills will, once approved:
- Push a close date, change a stage, add a follow-up task
- Add contacts found in Slack or email who are not yet in Salesforce
- Score a deal against “the team’s methodology,” fill qualification fields, add contact roles
- Turn a call transcript or notes into a follow-up email, a Slack summary, and opportunity updates (next steps, stage, close date)
- Build a pipeline dashboard and move dates/stages from that dashboard
- Draft a Friday forecast note for a manager
On a label, distributor, publisher, management, or live shop, those objects are not “ACME Corp / Q4 renewal.” They are an artist, a tour, a territory license, a sync, a distribution term, a festival offer. An auto-added “contact” can be a lawyer, a radio programmer, or a promoter who was only in a Slack thread. A stage change can move a hold to confirmed in the same system finance uses to issue a deposit invoice. A close-date push can desync routing, visas, and holds. That is the diligence, not the demo.
Who should touch it first
Do not start with A&R or business affairs. Start with the team whose Salesforce objects look like ordinary B2B: brand-partnership sales, sync pitching (if the opportunity is a licensee, not the composition), sponsorship, and live-event ticket or VIP packages sold like enterprise deals. Keep catalog, royalty, and split data out of the first permission set.
Admin sequence (from Anthropic’s setup guide)
- Confirm the org is on a paid Claude plan. Beta is not Free.
- Salesforce admin requests the plugin on AgentExchange (Sales Cloud in Claude beta access). Approval is Salesforce’s gate, not Anthropic’s.
- In Claude: Organization settings → Connectors → Salesforce (Beta). Paste the OAuth client ID and secret. Save.
- Assign the plugin to named groups only — not “all sellers.”
- Each user signs in with their own Salesforce account. First open runs a setup skill that fingerprints role and book of business.
- Confirm the Salesforce MCP marketplace connector if you want headless access without the full plugin.
- Surfaces at launch: chat and Claude Cowork (web and desktop). Assume mobile brief is read-only until you test writes.
Hardening before a single write hits production
- Clone a sandbox. Point the connector at sandbox first. If the OAuth app can see production, you do not have a pilot.
- Field-level security. Strip write on: royalty balances, recoupment, split percentages, ISRC/ISWC fields, option/hold flags, guaranteed vs. overage, visa/immigration notes, minor-artist flags, unpublished works, legal hold. Leave write on: next step, meeting date, stage (if you accept that risk), task.
- Validation rules. Block stage jumps that skip “legal review” or “hold confirmed.” Block close-date changes inside 14 days of an on-sale without a reason field.
- Contact-create lock. The skill that adds stakeholders from Slack/email is the quietest leak. Require a record type (“External – unvetted”) and a duplicate rule against artist, manager, and counsel.
- Transcript hygiene. Post-call updates from a Zoom/Gong dump will pull names of artists not yet announced, conflicted co-writers, and offer numbers. Treat the transcript as MNPI-adjacent. Do not let the Slack-summary skill post to a channel that includes contractors.
- Approval is not an audit log. Anthropic’s default is “ask before write.” Log who approved, which skill, which fields, before/after values — in Salesforce, not in Claude chat. If you cannot query that next quarter, do not enable writes.
- Group scope. Promoters, radio, and brand teams can have the plugin. Royalty ops, catalog admin, and outside counsel do not.
Pilot design that survives diligence
Two weeks. Five named sellers. Sandbox. One object family (e.g. Brand Partnership Opportunity only). Morning brief + call prep on. Post-call Salesforce write off until you have compared ten human notes to ten Claude drafts. Friday forecast draft on, send off. Measure: time to first useful brief, number of proposed field writes rejected, number of net-new contacts that were already in the org under another name.
If your Salesforce already mixes “Account = Artist” with “Account = Brand,” stop. Fix the data model before an agent learns the wrong noun.
What not to claim in a board or buyer narrative
This is not a music-rights system. It is not an A&R tool. It does not replace a royalty platform. Salesforce remaining system of record only helps if the record was clean. Anthropic’s “we don’t train on your data by default” on Team/Enterprise is a contract sentence — keep the DPA and the Salesforce Connected App scopes next to it. GitLab/Siemens/Legora quotes are software and legal-tech sellers. Do not analogize their “law firms we serve” line to a roster.
Do this week
- Inventory which music objects live in Salesforce vs. a royalty or tour system.
- Name the one team allowed in beta.
- File the AgentExchange request and stand up OAuth against sandbox.
- Write the field-lock list before anyone clicks Approve.