Roll Out Claudeforce in Three Steps, So Each Step Adds Only One New Kind of Risk

Claudeforce reaches your company in three ways: the Claude plugin, where individual people work with live Salesforce data inside Claude; Claude in Slack, where teams work together; and Agentforce agents, which change records and talk to customers on their own. All three are becoming available around the same time, and the obvious plan is to switch them on together and let each department pick what it wants.

I'd turn them on one at a time, in a particular order, and I'd want each one working before the next starts. This post explains why, and what the order looks like.

If everything goes live at once, you can't tell what caused a problem.

Say a customer account shows the wrong renewal date three weeks after launch. There are at least four ways that could have happened.

• The date might have been wrong before Claude was ever connected, and Claude repeated it.

• A sales rep might have accepted a draft from Claude without checking it.

• Someone might have had permission to edit an account that wasn't theirs.

• Or an agent might have read a customer email saying "we're looking at pushing the renewal to the third quarter" and taken it at face value, where a sales rep who knows the account would have heard a maybe.

Each of those has a different fix and a different owner. If the plugin, Slack and customer-facing agents all went live in the same quarter, your team spends the week working out which one it was, and while they do, the people using Claude start trusting it less. If only one of them is live, the list of possible causes is much shorter, and the answer is a lot easier to find.

Each step adds one new kind of risk,

Assist. Individual sales reps use the ready-made skills in the Claude plugin: meeting prep, pipeline reviews, call notes, account plans. It runs read-only, so Claude drafts and a person decides what gets saved. The new risk at this step is what people can see and whether the answers are right, which comes down to permissions and data quality. Nothing changes in Salesforce unless a person changes it.

Coordinate. Teams use Claude in Slack, for deal reviews and forecast preparation in the channels they already work in. The new risk is sharing. An answer one person was allowed to see can end up posted in a channel full of people who weren't, so this is the step where you find out whether your channel membership matches your Salesforce access. I'd treat that as the thing to watch here.

Act. Agents that change records and talk to customers, starting with routine service requests. The new risk is Claude doing something on its own, with no person between the decision and the customer. Before this step starts, the rules need to be written down: which records the agent may change, which requests it must hand to a person, and who reviews its changes for the first month.

Each step has an exit test, and one executive signs off before the next begins.

The order only helps if you hold to it. Each step needs a test it has to pass, agreed before it starts, and one named executive who signs off that it passed. That executive owns the program, with a revenue operations lead, a Salesforce architect and someone from information security working alongside them.

For assist, the test is that hours back per sales rep and cost per user have been measured, and there have been no cases of someone seeing data they shouldn't have. For coordinate, it's that the team is using Claude in its deal reviews and nothing restricted has turned up in a shared channel. For act, it's that the agent's changes have run for thirty days without having to be reversed, and the share of requests it closes on its own is holding up alongside your customer satisfaction scores.

If a step doesn't pass, it keeps running until it does. That's slower than turning everything on in one quarter, but it means every problem your team investigates has a short list of possible causes.

Sales goes first and service goes last, because service is where Claude starts acting autonomously.

This order also settles which department starts. Sales can begin read-only on skills that already exist, so it fits the assist step with almost no setup. Service is the first place Claude changes records and talks to customers, which puts it in the act step, after your team has watched how Claude behaves on your own data for a couple of months.

There's one team I'd give Claude to even before sales, because the sales and service rollouts both depend on work only they can do. That's your Salesforce team, and it's the next post.