October 15, 2026
3 min read
I walked into my first Dreamforce with three goals: experience the event, meet people across the ecosystem, and learn what’s coming. I left with a new certification, a stack of conversations, an added thirty-three miles on my shoes, and one announcement I haven’t stopped thinking about.
For years, Salesforce development has happened in a silo. A developer works in their own environment, the admin waits, the business stakeholder sees the result at the end, and the feedback loops through tickets and screenshots.
Slack Code ends the handoff. Using Claude, a team can work on enhancements together, in the Slack channel where the conversation is already happening. The business user who knows the process, the admin who knows the org, and the developer who knows the code can be in the same thread, watching the change take shape.
I’ve used AI tools like Claude and ChatGPT almost daily for the past three years, and this one demo still showed me something new. I watched Claude Code build a Lightning Web Component inside Slack Code, then used the Preview button to see it right in Slack before deploying anything. That cuts out one of the most time-consuming loops in Lightning Web Components (LWC) work: deploy, open the page, see that it doesn’t look right, go back, rinse and repeat. A preview doesn’t replace sandbox testing with real data, but it catches the glaring problems before they cost a deployment cycle.
For a consulting firm, that matters. The slowest part of most enhancement work isn’t writing code. It’s confirming we understood the requirement. When those requesting the change can see a preview of the request in the same channel where they asked, a confirmation happens in minutes instead of days.
The slowest part of most enhancement work isn’t writing code. It’s confirming we understood the requirement.
While I was there, I earned my Salesforce Platform Administrator II certification, one of the perks of attending. Preparing for it reinforced something I’d tell any client excited about Slack Code: collaborative development still needs discipline. Code written in a channel still needs review, testing in a sandbox, and a controlled path to production. It also needs clear rules about who can request changes and who approves them.
The teams that get the most out of this will be the ones that put that governance in place first. Parts of this are still rolling out, so now is the time to plan, not rush.