Salesforce Says the Screen Isn't the Product. That Puts Your Data on Stage.

If your team opens Salesforce only when someone makes them, Dreamforce '26 had news for you. Salesforce spent its main keynote on September 15 arguing that the screen your team avoids is becoming optional.

The announcement is called AIforce. Patrick Stokes, Salesforce's President of Applications and Marketing, put the idea plainly: "The value of Salesforce has never been in the UI. It's been in the platform that stores the way our customers encode their business."

That sentence deserves a second read, because it moves the risk in your org to a new place.

What was announced: 

AIforce is a layer that lets people and agents work with Salesforce data and workflows from wherever they already work.

The pieces: Claudeforce. Salesforce inside Anthropic's Claude, with 37 prebuilt sales skills. It's in open beta. Slackforce. Live Salesforce data and apps inside Slack conversations. Agentforce Coworker. An AI teammate inside Lightning that works within your existing permissions. It's generally available, and Salesforce says 100,000 users were activated within 35 days of launch. A headless toolkit. MCP servers, APIs, plugins and skills that expose the platform to agents without a screen in between.

In the keynote demo, Stokes built a custom Salesforce interface by describing what he wanted to Claude. Salesforce's pitch is that each person gets their own interface, composed on the spot, instead of the page layout everyone shares today.

No pricing was announced for AIforce, and Salesforce's own announcement says pricing and packaging are subject to change.

Why this matters more for a messy org than a clean one: 

Think about what a page layout does for you today. It hides things. The fields nobody fills in sit below the fold. The picklist values from an old reorg sit in a dropdown nobody opens. The duplicate account records sit in a list view nobody filters. A cluttered org survives partly because the screen lets people ignore the clutter.

An agent doesn't ignore anything. Ask Claude or Coworker for "every client we haven't spoken to this quarter" and it reads the activity history you have, not the one you meant to have. When it drafts a follow-up, it pulls from whatever is in the contact record, including the field someone repurposed three years ago.

So the question Dreamforce raised isn't whether your team will like the new interface. It's whether the data and logic underneath can survive being read by something that takes all of it literally.

Here's a quick test. Pick one ordinary question your team asks every week and answer it with a report today. If the report needs a footnote before anyone trusts it, an agent will give you the same answer with more confidence and no footnote.

What to do before you turn anything on: 

1. Find out what's in there. Count the fields on your main objects, and how many hold a value in more than a handful of records. Look at the automation list and ask who owns each flow. Plenty of orgs we open have a layer nobody can explain.

2. Fix the definitions before the data. If "active client" means three different things to three people, an agent will pick one. Write down what your team means by the ten or so terms it uses most, then make the org match.

3. Check permissions with agents in mind. Coworker works inside existing permissions. That's good design, and it also means an over-permissioned profile now has a very fast reader attached to it.

4. Start with one job, not one platform. Pick a task that eats hours every week: meeting prep, follow-up drafts, pipeline updates. Point the tool at that. Measure the time saved. Expand from there.

5. Treat beta as beta. Claudeforce is in open beta. That's a fine time to test with a small group. It's not the time to redesign how your whole team works.

The part nobody put on a slide:

Salesforce is right that the screen was never the valuable part. The valuable part is years of your business encoded in objects, fields, rules and history. AIforce makes that encoding more useful. It also makes every shortcut in it more visible.

Teams that kept their org simple are about to see a real return on that discipline. Teams that didn't are about to find out where the shortcuts are, one confident wrong answer at a time.

If you'd like a second set of eyes before you connect an agent to your org, our Salesforce Health Assessment looks at your data, automation and permissions and tells you what to fix first. It's free. Book My Free Audit.