Salesforce Ben

Every time the Salesforce release notes are published, I jump straight to the Salesforce Flow section – there’s always so much great content there that will make the lives of Salesforce Admins a lot easier.

As far as Salesforce releases go, the winter release is always one to watch. As the ecosystem gears up for Dreamforce, the Winter ‘27 Release offers an early glimpse into the announcements to come. Many of the updates introduced now lay the groundwork for the more transformational changes that will take center stage in San Francisco. From a marketer’s perspective, several themes stand out in the Winter ‘27 Release. One is undoubtedly the deeper entrenchment of Agentforce within the marketing domain.

Marc Benioff has suggested that Salesforce rebrand to ‘SalesforceSlack’ to “capture its AI-era power”. The Salesforce CEO put out a poll on X, asking people to vote on whether they thought the move was a good idea. 68.3% said no, 23.3% said yes, and 8.4% said ‘maybe so’. It isn’t the first time a name change has been suggested for Salesforce. Late last year, a company employee told Business Insider that the company could change its official name to match its flagship AI product, Agentforce.

There is no shortage of opinions about where Salesforce development is heading. AI, certifications, DevOps, technical debt, changing career paths – everyone has a view. Rather than guessing, we want to hear directly from the people doing the work. If you are a Salesforce Developer, we would love you to take part in our 2026 survey and help us create a report that reflects the experiences of the community itself.

This quarter has seen a few jarring headlines for the Salesforce ecosystem. Layoffs, restructuring, customers vibe-coding their own CRMs, and the dreaded ‘SaaSpocalypse’ have all appeared in headlines since the CRM company posted its Q1 ‘27 results. But it’s far from an entirely negative forecast for Salesforce, whose Q2 results are set to be released on August 26, after the close of the market. Let’s take a look at what to look out for.

A few years ago, we wrote about predictions related to the future of data collection in Salesforce. Revisiting those predictions three years later: Did AI really reshape CRM workflows? Did data privacy really become a competitive differentiator? And did better data collection tools become the foundation on which everything else would be built? For the most part, yes.

“Can you just add one field?” are six words that strike fear into the heart of every Salesforce Admin, because everyone who works with Salesforce knows that “just” is one of the most dangerous words in the English language. Just add a field. Just update a picklist. Just change a validation rule. Just import these records. Just turn on this new feature. How hard could it be? Usually, the answer is: harder than expected. Not because Salesforce Admins are making things complicated. Quite the opposite.

Salesforce’s flagship conference, Dreamforce, returns this year from September 15-17 and promises another few days of big product announcements, AI advancements, and connection opportunities. Although there’s around a month until the event kicks off, Salesforce has begun teasing some of the updates attendees and Trailblazers can look forward to, which is exactly what we’ll cover in this article. Let’s dive in.

The golden rule in Big Tech – much like politics or some aspects of the wellness industry – is to take everything the big dogs at the top say with a grain of salt. Salesforce CEO Marc Benioff is no exception. Earlier this month, Benioff financially backed artificial intelligence startup June, which helps businesses deploy AI agents across their existing software systems, effectively automating tasks.

Validation rules are one of the most well-known and commonly reached-for tools in an admin’s toolkit (and for good reason!). They catch bad data before a record ever hits save, without needing to code even a single line of Apex. But knowing how to write a validation rule is only half the story; knowing which rules are actually worth building is what separates a clean org from a cluttered one.