Claude for Salesforce Teams
Give your team Claude that knows your Salesforce: set up safely, tuned to how you sell and serve, and used every week rather than once.
The fit.
- Cloud
- Sales Cloud today through Salesforce in Claude (beta). Other teams scoped case by case after the assessment.
- Who it’s for
- Sales, service and operations leaders, Salesforce admins and IT leads at organizations that run on Salesforce and have bought, or are about to buy, Claude for their team
- Typical go-live
- 2 to 4 weeks
- Runs as
- Claude, working in your Salesforce through your own users' access
Fixed price, USD
- Simple
- $4,500
- Standard
- $9,000
- Complex
- $13,500+
- Fixed quote after the Readiness Assessment.
What needs to change.
Someone signed for Claude seats. A few people use it well, most tried it twice, and nobody is sure what it can see in Salesforce or what it is allowed to change. The Salesforce plugin ships with sales skills, but those skills do not know your definitions of a healthy deal. Your teams need access rules, a write policy and training around their own work.
What it does.
- Sets up Salesforce in Claude for your organization: beta access, the Salesforce-side connection, the Claude-side connector and distribution to the groups in scope.
- Reviews what Claude will be able to see before anyone signs in. Claude acts as each user, so we check the permissions it will inherit and flag over-broad access first.
- Agrees a write policy: which fields and actions Claude may propose, which need approval and which are off the table. We test it before launch.
- Tunes the built-in sales skills to your process, then writes the skills specific to you: stage exit criteria, qualification methods, account briefs and renewal checklists.
- Extends Claude to teams beyond sales where a Salesforce connection makes sense, scoped case by case after the assessment.
- Sets up Claude Code for your Salesforce admins and developers, with read-only defaults for production.
- Writes your team's Claude usage guide: what to use it for, what data stays out and how to check its work.
- Trains each group with its own tasks, then measures weekly use for the first 60 days.
Price.
Prices in USD. Simple and Standard are fixed scope. Complex is scoped after the assessment.
| Tier | Your org looks like | Arkeforce price (USD) |
|---|---|---|
| Simple | One sales team, native plugin, clean permissions, up to 6 tuned skills | $4,500 |
| Standard | Sales plus one more team, access fixes needed, custom skills, Claude Code for admins, Slack | $9,000 |
| Complex | Several business units or regions, teams beyond sales scoped case by case, strict data rules, developer enablement | $13,500+Fixed quote after the Readiness Assessment. |
- What you pay Salesforce
- Sales Cloud Enterprise during the beta, billed by Salesforce
- What you pay anyone else
- Claude seats, billed by Anthropic.
- What you pay Arkeforce
- The tier price above, fixed before we start.
Outcomes we target.
| Outcome | How we measure it | Typical 90-day target, tracked with you |
|---|---|---|
| Claude used every week | Weekly active users divided by licensed seats | 60%+ of seats |
| Skills that match your process | Custom and tuned skills in regular use | 5+ skills each used weekly by their team |
| Salesforce updates approved and saved | Approved Claude-proposed updates saved to Salesforce | Tracked from week 2, reviewed monthly |
| Access reviewed before launch | Launch groups whose Salesforce access was reviewed before sign-in | 100% of launch groups |
Targets are targets, not measured results or guarantees. Adoption is tracked for 60 days. Post-launch support is included for 30 days; ongoing tuning and reviews use retainer hours.
Sample exchange.
Illustrative examples, not results from a client engagement.
You:Prep me for the Globex call at 2.
Claude:For example: Globex has a USD $180,000 renewal on March 31, in Negotiation. Your close plan is missing the legal review date your team requires before Commit. Last contact was 19 days ago with the CFO. Here is a brief and three suggested questions.
You:Move all my past-due close dates to the end of next month.
Claude:For example: that is 11 opportunities. Here is each one with its old and new date. Approve and I will update them, or pick the ones to change.
You:Email the Globex procurement contact our updated pricing.
Claude:Your team's policy says external pricing emails go through Deal Desk. Here is a draft for their review.
Built for your org.
- We tune skills to your stage names, required fields, methodology and vocabulary.
- We review the Salesforce access each launch group will inherit before connecting.
- Your written policy defines what Claude can draft, propose and change.
Set up in your Claude workspace and your Salesforce org. Nothing is installed as a package.
Uses your Claude seats. Salesforce entitlements and any connected-service usage are checked separately.
Compared with what’s already out there.
| Option | What it covers | When it may be enough |
|---|---|---|
| Native Agentforce | Agentforce Employee agents can access company knowledge and carry out actions inside Salesforce; supported actions and licences vary by agent type.Source · 2026-10-28 | The job needs to run on records inside Salesforce, with its own actions and permissions. |
| Salesforce in Claude | Salesforce’s plugin brings seller accounts, opportunities and pipeline into Claude, with 37 sales skills and approval per proposed change by default. Sellers can also set up scheduled briefs.Source · 2026-10-28 | Your sellers need the built-in skills and a capable admin can set up the plugin with tidy permissions. |
| Arkeforce | Give your team Claude that knows your Salesforce: set up safely, tuned to how you sell and serve, and used every week rather than once. | |
Verified on 2026-10-28. Availability and licensing can change; we confirm them for your org.
If you are on Sales Cloud Enterprise, only need sellers using the built-in skills, and your permissions are already tidy, a capable admin can set up the native plugin without us. We add the access review, the write policy, process-specific skills, teams beyond sales where they fit, and training. When a job must update every record on an event or a schedule, we assess an Agentforce agent for that work.
See the full comparison →What’s included.
- Discovery: who will use Claude, for what, and a written fit report
- Access review of every launch group's Salesforce permissions, with fixes listed for your admin
- Written Claude usage and write policy for your organization
- Plugin and connector set-up, group distribution and a test group first
- Up to 6 tuned or custom skills in the Simple tier, tested on your records
- Claude Code set-up for admins and developers in Standard and Complex
- Training per group on their own work
- 60 days of adoption tracking and 30 days of post-launch support
Prerequisites.
- A paid Claude plan for the users in scope. Salesforce in Claude is available in beta on all paid Claude plans. Seats are bought from Anthropic, not from us.
- For the native plugin: Salesforce's approval for the beta and the latest Sales Cloud Enterprise edition required by the beta documentation. We confirm your licences before connecting.
- A Salesforce admin who can configure the connection and required access.
- Your organization's AI and data-use terms reviewed before any connection. If a client contract restricts AI use on their data, we scope around it.
Retainer (optional, monthly).
Monthly adoption review, new skills as your process changes, and a re-check of access and write policy after each Salesforce or Claude release come out of your retainer hours.
- Essentials $1,000/mo with 3 hours
- Growth $3,000/mo with 10 hours
- Partner $5,500/mo with 20 hours plus one integration per quarter
Retainer prices in USD.
Trust and safety.
- Claude acts as each user and inherits their Salesforce access.
- Changes to records are proposed and approved per your written policy. Approval per change is the starting point.
- External emails and messages follow your sending policy, and drafts are the default.
- We review your AI and data-use terms, and your clients' where they apply, before anything connects.
- Unattended record processing is scoped as an Agentforce engagement with its own controls.
Start with the job.
Tell us what needs to happen and where it gets stuck. We’ll check the fit and agree the scope before anything is built.
Not sure yet? Explore the Readiness Assessment →