Recommended
Builder Central lets admins build and edit in a virtual layer before touching the sandbox (opens in a new tab)
You will learn how Builder Central keeps proposed metadata changes out of your sandbox until you approve them, how it edits existing flows and apps, and what its new project-plan review step does.
Why read this
The piece is a podcast transcript, so the specifics are mostly the speakers' claims and a demo.
- Describe the idea in Builder Central
- Review the project plan before building
- Explore changes in the virtual environment
- Publish to the sandbox on your approval
Builder Central, now in beta, is a Salesforce tool that lets admins go from a description of an idea to a working solution on the platform without writing code. The podcast hosts describe it as the result of about two and a half years of internal work, built on the team’s headless and MCP efforts, and aimed at low-code builders. Early customers reported that tasks which took seven to ten days for several people now take one person two to three hours.
The central design point is that Builder Central works in a virtual environment rather than changing sandbox metadata while you build. Changes stay out of the org until you explicitly publish the project to the sandbox with a button or by asking the agent to do it. Visualizers show flows and other output as they would look in the org before anything is deployed, and the speakers say the team keeps adding them.
The tool also covers the maintenance work that makes up most of an admin’s job. Because it can read all the metadata in an org, it can refactor or test existing flows, and the hosts say it generated flow tests that a product manager judged to be good. A feature due around TDX will let users pull an existing app into a project and restyle it with a brand kit. A new step, rolling out that week, has the agent build a project plan for the user to review and approve before it starts building, and inline editing lets users select a single component to change.
The episode is promotional in tone and mostly anecdotal, so treat the productivity figures and comparisons with Claude Code as the speakers’ own account. The practical takeaway is the publish-on-approval workflow and the plan review step, which are the parts most relevant to governance and sandbox risk.
Read the original at Salesforce Admins Blog (opens in a new tab)