Salesforce Ended Installing CRM. Now It Wants to End Opening It.

Claudeforce Changes Where Your People Work. It Doesn't Change What's in Your Org.

Back in 2000, Salesforce staged a mock protest outside a Siebel user conference, complete with "No Software" signs. It was a stunt, and it worked. The pitch was simple enough. Stop installing CRM, stop maintaining servers, and run the whole thing in a browser. Over the next decade, that idea helped push CRM out of the server room for good.

Twenty-six years later, at Dreamforce '26, the pitch moved again. While there were no protest signs, Benioff told the crowd this isn't the end of software, only the end of software that makes people do all the work. Salesforce spent the week demonstrating that its data, workflows, and permissions can now reach wherever people work, including within Claude. Claudeforce, the main product of the Salesforce-Anthropic partnership, is in open beta and runs on the new AIforce layer.

What got far less attention was the caveat that nearly every session eventually got around to. All of this depends on a well-architected foundation.

The Mess Came With Us Last Time

Anyone who worked on the move from on-premises CRM to the cloud remembers what happened next. Companies moved their data, and their problems moved right along with it. Duplicate accounts, half-finished integrations, and permission models built for org charts that no longer existed all made the trip.

The same risk sits underneath every Claudeforce demo. For a regulated business running on years of mergers, acquisitions, and quick fixes, "well-architected foundation" lands differently. The person who built half the org left years ago, simple changes take weeks, and there are a few areas nobody wants to touch.

The obvious response is a foundation project. To put it bluntly, we think that's the wrong place to start, and yes, we're a Salesforce consultancy saying so. A six-month overhaul before any AI work is a hard sell to any board, and it isn't the only way in. Five questions will tell you what must be fixed now, what can wait, and whether the AI will pay for itself.

Start With the Number, Not the Platform

The first question is what number this is supposed to move, and it decides everything else. AI that doesn't move a number your leadership already tracks is an expensive experiment, however good the demo looked.

For most large enterprises, that number is revenue. How much of next year's goal could come from putting AI in front of sellers, and from making sure they use it well? The mechanics aren't glamorous. They come down to faster deal cycles, better information going into each deal, and teams that know what the other teams are doing.

That number picks the first use cases, the data that gets narrowed, and which pieces of old debt make the critical list. We call it trapped value, the insight already sitting in your data that nobody can easily get to. A report tells someone what happened yesterday. A focused AI layer can tell them what has been trending over the past six months and the three things worth doing tomorrow.

Find What Would Break It

The second question is what would stop it from working. Say the goal is Claudeforce in front of a pilot group within 60 days, which is long enough to see whether it works before real budget goes in. Somewhere in the org are the things that would stop that. Worse, they could let it go live and hand people the wrong answers.

Wrong answers are rarely surprising. Consider the duplicate accounts left over from an acquisition, ownership fields that haven’t been trusted since the last reorg, or field-level security that hasn't been reviewed in years.

Whatever is critical to this specific use case is planned into the launch, and whatever isn't can be improved over time. In regulated industries, anything touching sensitive data goes to the top of the list.

Skip this step, and you get an AI confidently reading from the third copy of the same account, in front of a customer.

Decide What It Gets to See

Third, what is the AI allowed to see? Point it at a huge, messy dataset, and it behaves a lot like your mom answering "what did you do today?" by text. You wanted a sentence and got fifteen paragraphs, including a very long story about the grocery store.

AI can't tell which part you care about, so it reads everything it can reach. More data in scope means more chances of being wrong and a bigger bill for every answer.

Salesforce in Claude works inside the permissions people already have, which is good news if those permissions are sound. If your sharing rules are a crime scene, the AI inherits it. For regulated businesses, this is where a helpful assistant turns into a compliance conversation.

Salesforce also made a point of zero data retention on stage. That commitment belongs in your contract, not just in a keynote.

The Bill Didn't Get Much Stage Time

The fourth question is cost, and it got the least airtime of the week, so let’s talk about it. AI is billed by usage, and measured in tokens, which is roughly the amount of text the model reads and writes. Salesforce hasn't published pricing for AIforce, so the safe assumption is that you'll pay for both the Salesforce and Anthropic sides.

For some use cases, the running costs will be higher than with a simple custom app, so some analysis is warranted. Better to find that out in planning than on the first invoice.

A tip as you’re considering costs: caching helps by allowing the system to reuse work it has already done when many people request the same data. Narrowing the data helps more. The model reads less on every request, which lowers both the bill and the error rate.

Build for the Next AI, Too

Finally, which AI are you building for? Most organizations we talk to already have Copilot, ChatGPT, Gemini, and Claude in use somewhere, sometimes all four. Claudeforce is one of several ways Salesforce plans to reach people through AIforce, alongside Slackforce and Agentforce Coworker.

This shows how the way systems connect is also changing. The older approach meant spelling out every connection, exactly what to fetch and how to return it. Newer headless setups let the model decide which connections it needs and put the answer together itself, a bit like an air traffic controller who knows every plane in the sky.

So, the choice of AI matters less than ensuring that governance, data scope, and permissions travel with the data. Whichever tool your teams adopt next year should follow the same rules.

Final Thoughts

In 2000, the promise was that nobody would have to install CRM again. In 2026, it's that nobody will have to open it. Both promises are real, and both leave one thing untouched. Whatever was in the org before is still in the org after.

Salesforce is betting that the interface can change completely as long as the underlying data, workflows, and permissions remain trusted. That's a reasonable bet for Salesforce. Whether it pays off for your company depends on what's sitting underneath yours.

Foundree42 is an independent Salesforce and AI advisory firm, and these five questions come up in every engagement. If you want a straight answer on what would break first in your org, tell us which number you want AI to move. Book a free intro call, and we'll take it from there.