Dreamforce 2026 Recap: What AIforce, Claudeforce and Koa Mean If You Already Pay for Salesforce

AIforce is Salesforce saying the interface is optional

Benioff opened with the interface changes we've all lived through: DOS to Windows, desktop to web, web to mobile. AIforce is his name for the next one. The idea is that your team can work with Salesforce from Claude, from Slack, or through an agent, without going through the Lightning screens they were trained on. Under the AIforce umbrella Salesforce grouped Claudeforce (the Anthropic partnership), Slackforce (Salesforce data inside Slack), Agentforce Coworker (an AI teammate inside Lightning) and a headless toolkit of APIs, MCP servers and plugins for developers.

The line I'd want every executive to hear came right after that. Benioff said other software companies think their product is the interface, and Salesforce doesn't. Its product is the trust customers place in it to hold their data, their workflows, their business processes, their permissions and their security rules.

That sounds like a keynote line, but it's a practical way to think about your own licence. If your sales team can get an answer from Claude instead of a dashboard, the dashboards you paid to build were never the asset. The records, the process rules and the permissions underneath them are, and Dreamforce 2026 was Salesforce saying exactly that.

Claudeforce is the part you can try this quarter

The Salesforce plugin for Claude is in open beta on the AppExchange now. Patrick Stokes demonstrated it on stage: a view of global pipeline and open service cases built inside Claude by asking for it, plus 37 prebuilt sales skills at launch, with meeting prep and pipeline reviews among them. Amodei described a colleague on Anthropic's go-to-market team who still uses Salesforce every day, but now uses it through Claude, asking which ten deals are most likely to be lost this week and what those deals have in common.

Two things to know before your administrator connects it.

• Claude works through each person's own Salesforce access, so it can see whatever that person can already see. In an instance that's a few years old, that's usually more than anyone expects. I wrote about the permissions review to run first in an earlier post.
• The pricing works differently from seat licences. Usage is what you pay for, so the budget conversation belongs before the pilot, not after the first invoice.

Koa is a CRM model trained without your data

Koa is Salesforce's first CRM reasoning model, built with NVIDIA on Nemotron 3 Super and trained on a synthetic dataset modelled on nearly 27 years of CRM deployments. Salesforce says no customer data was used, and Benioff repeated the zero data retention promise from the stage: your data is your data, and it doesn't go into the models.

What Koa does for you is make Agentforce agents better at multistep CRM work, such as updating opportunities, routing cases and scheduling follow-ups, with three times fewer errors on Salesforce's own CRM benchmark. Pilot access is open now and general availability is expected in winter 2026 in US regions, which is worth checking on if your data has to stay in Canada.

"Hallucination does not really work on the shop floor."

That was Siemens, describing why they can run a family of Agentforce agents across their business. Their Salesforce instance is already the single source of truth for their products, parts and service instructions. Koa improves the model side of that equation. The data side is still yours.

What I'd do in the next 90 days

Amodei said something near the end of the keynote that I think is the honest summary of Dreamforce 2026: the number of people who've seen what this can do is still small compared to the number who could use it. He put the value being captured today at five or ten percent of what's possible. The gap between those two numbers is mostly cleanup, and here's the order I'd do it in.

• Watch the Claudeforce demo with your sales leader and write down the first three questions they'd ask. Those questions tell you which records need to be right first.
• Run the permissions review before anything gets connected. Who can see everything, what the sharing defaults are on accounts and opportunities, and which active users shouldn't be.
• Pick one team, one region, and turn the plugin on read-only. Claude drafts, a person saves.
• Decide who owns the usage bill and what the number is before the pilot starts.

That is the work my team at Apexify Consulting does for corporate Salesforce customers across Alberta and the rest of Canada: getting the data, the permissions and the process rules ready so that what you saw at Dreamforce 2026 works on your instance the way it worked on stage. If you'd like a second set of eyes on where yours stands, you can reach us at apexifyconsulting.com.