Dreamforce is built for enterprises, and most of what gets announced there will not apply to you for two years, if ever.
That is not a reason to ignore it. Salesforce tells you what the platform is going to become at this event, and the parts of that which reach an organization without a dedicated platform team tend to arrive quietly, eighteen months later, in a release note nobody reads. Knowing what is coming is how you avoid buying something in March that ships free in October.
By platform team we mean the thing enterprises have and most organizations do not: people whose entire job is the system. If your Salesforce is run by two admins alongside their other work, or by an operations lead who also owns reporting and vendor management, or by one person who also runs the database, the announcements land on you very differently than they land on the company with a dedicated bench.
Dreamforce 2026 runs September 15 through 17 in San Francisco. We are on the ground September 14 through 18. Here is what we are tracking on behalf of the organizations we work with, and how to find us if you are going.
What We’re Watching
Salesforce has already told its partners what this year is about, which makes the guessing easier than usual. Four things we are chasing, and the question we are bringing to each.
Claude, running inside Salesforce. Salesforce and Anthropic have built Claudeforce: Claude working directly inside Salesforce workflows, reaching Data 360, Tableau and Slack through a new layer called Headless 360. The first piece is a seller plugin with 37 built-in skills, in pilot now with an open beta announced for this month. We run our own operation on Claude every day, so this is the one we are least willing to take on faith. Our question is narrow: what does it cost per seat once the beta ends, and does it hold up for an organization with one admin and no data engineer?
The one most likely to be oversold: agents that execute. The framing this year is a “System of Agency,” and the promise is that agents no longer just assist, they execute inside governed business constraints. That is a genuinely hard problem, and the demos will make it look solved. What a demo skips is the part you own. The business rules an agent inherits have to already exist, be written down, and be correct. If your approval chain lives in someone’s head, there is nothing for an agent to inherit. That is the question we are putting to every booth.
What it costs, which is what actually decides whether it reaches you. Announcements travel; pricing decides. Agent and data platform capabilities have been drifting toward consumption billing, where the bill scales with usage instead of seats, and that is a very different budgeting exercise for an organization with nobody on staff to model it. We are going to ask, repeatedly and at the specific scale our clients actually run at, what the entry price is and what the floor looks like after the introductory pricing ends.
What is quietly being wound down. Nobody announces a deprecation from the keynote stage. It surfaces in a release note months later, and it is usually the thing that breaks a small team’s carefully built workaround. Salesforce has organized this year’s story around five named systems, and consolidating products into a single architecture is exactly where things get retired. We will be asking what happens to the tools that do not fit the new shape, because that answer decides whether your next eighteen months contain a migration you never planned.
How We’re Covering It
We are publishing twice a day from the floor, Monday September 14 through Friday September 18, in two parallel tracks.
From the Architect’s Chair is written by Dave, and takes the buyer and architecture view: what an announcement changes about the advice we would give a client, and what is genuinely new versus repackaged.
From the Keyboard is written by Adam Cooper, joining us as a guest contributor for the week, and takes the developer view: what it would actually take to build, where the demo skipped a step, and what breaks first at scale.
Two people at the same conference, writing separately, every day. The disagreements between the two tracks are usually the most useful part, and we are not going to smooth them out.
We are also publishing a recap on September 22 that pulls the whole week into one piece of firm guidance for organizations that were not there.
Come Find Us
If you are going, we would like twenty minutes with you.
Not a pitch. The most valuable conversations we have at these events are with the people who actually own the system where they work, comparing notes on what worked and what quietly did not. If you are wrestling with something specific, bring it. We have been doing this long enough to have an opinion, and we will tell you when we do not.
You can see what is open and request a time here. If nothing on the page works, leave a comment on this post, use the consultation form, or reach out on LinkedIn, and we will sort something out.
If You’re Not Going
Send us your questions instead. We asked for these last week and they are still open, and the ones we have received are already shaping what we plan to chase.
The good ones are specific: what does this cost at our size, what did the rollout actually take, what is being quietly retired. We will chase them during the week and answer them in the daily notes or the recap. Where we cannot get a straight answer, we will say so, which happens more often than the agenda suggests.
The fastest way to get the answers as they land is the Iron Insights newsletter, where the daily notes get summarized.
Whatever gets announced, the thing that determines whether it helps you is unglamorous and unchanged: whether your team agrees on how the work is supposed to run before you automate it. That is true of every feature on the keynote stage, and it is why most Salesforce problems turn out to be process problems.
Ready to work out which of this year’s announcements actually apply to the way your organization runs? Let’s talk about your roadmap before the vendor conversation starts. Schedule a consultation today!
Responses