Salesforce Admins Podcast podcast

How Builder Central Is Changing the Way Admins Build

0:00
39:27
Rewind 15 seconds
Fast Forward 15 seconds

Today on the Salesforce Admins Podcast, we talk to Tiaan Kruger, Senior Director of AI Product Management, and Daivat Dholakia, Product Manager for Builder Central at Salesforce.

Join us as we chat about how admins can use Builder Central to create better solutions, faster, for their organizations.

You should subscribe for the full episode, but here are a few takeaways from our conversation with Tiaan Kruger and Daivat Dholakia.

What is Builder Central?

Every admin has a backlog of ideas that are good but never quite urgent enough to build. Builder Central, now in beta, is here to help you take those ideas into production. This week, I sit down with Salesforce product managers Tiaan Kruger and Daivat Dholakia to find out what it's all about.

With Builder Central, you can go from describing an idea to a working solution on the platform without using code. You can use the agent-powered tools that you love while keeping your data on the platform you trust, grounded in the context of your business and configuration.

Most importantly, it's delightful to use. "I have not had this much fun building on the platform in probably 16 years," Tiaan says. With Builder Central, you can build things in hours that used to take days or even weeks.

See what you're building before publishing to a sandbox

Obviously, we want to test things out in a sandbox before pushing them to production, but that can mean making changes to your metadata as you're building. It's cumbersome, time-consuming, and sometimes dangerous.

That's why Builder Central lets you work things up in a virtual environment before pushing them to your sandbox. You can explore an idea and hash things out without having to roll back metadata. Similarly, visualizers let you see how a flow you're building looks in your org before it ever gets there. 

By the time something hits the sandbox, it's already working the way you want it to, and you can focus on the finishing touches to push your solutions to production.

How Builder Central helps you with tech debt

With 10 years under his belt as an admin and developer, Tiaan understands that a big part of the job is fixing, maintaining, and improving existing infrastructure. So how does Builder Central help with that?

Because it has access to all of your metadata, you can refactor or test existing flows. If you have tech debt in your org (and who doesn't?), you can probably get an agent to help you with that. You can refresh existing apps with a modern UI and your brand's colors, then make modifications to your heart's content.

Finally, everything you create in Builder Central follows your security settings and naming conventions, so your solutions are secure and easy to maintain.

Make sure to listen to the full episode for more from Tiaan and Daivat about Builder Central, and check out the video to see the demo. And remember to subscribe to the Salesforce Admins Podcast to catch us every Thursday.

Podcast swag

Learn more

Admin Trailblazers Group

Social

Full show transcript

Mike:
This week on the Salesforce Admins Podcast, we're talking Builder Central, and I'm going to admit upfront, I'm its biggest fan. I'm joined by Tiaan Kruger and Daivat Dholakia from the platform product team, who spent the last couple of years really figuring out how to bring AI to low-code builders without putting your sandbox at risk. Now, we're going to get into why you build in a virtual environment and how you can scrap everything if it goes sideways, and really how it helps with that 90% of your job, which is just fixing and maintaining what already exists. Not to mention what's coming in terms of governance and policies. Now, if you're in and you enjoy the show, make sure you follow and subscribe wherever you're watching, wherever you're listening. So with that, let's get Tiaan and Daivat on the podcast. So Tiaan, Daivat, welcome to the podcast.

Daivat Dholakia:
Thank you.

Tian Kruger:
Thank you, Mike.

Mike:
Good to see you. Long time since we've talked, I think it was what, Dreamforce just a few months ago, which in Salesforce terms is like 14 years, because months are years at the rapid pace that things are innovating. For those people that haven't met you at Dreamforce or one of our events, Tiaan, let's start with you. What do you do at Salesforce?

Tian Kruger:
Thank you, Mike. So I am in the product group in platform, been here about seven years, I have built a bunch of different things, but I've really spent the last couple of years focusing on how we bring AI to our low-code audience. It's a very big challenge, it's something we want to do really well. And before that, I was actually a developer and an admin. So I actually worked in the industry for 10 years. So before I came to Salesforce, actually did the job that I'm trying to make easier for people.

Mike:
Which is awesome. Diva, I had the pleasure of meeting you this Dreamforce. You thankfully were on our Salesforce Plus feed, as I can't put Tiaan everywhere because he's also in the keynote.

Daivat Dholakia:
Yes, thank you, Mike. Yeah, it was an amazing experience being on Salesforce Plus. Just to give a brief background about myself, I've been with Salesforce almost five years at this point, I've done a couple of different things, including working on identity and also working on the Salesforce authenticator app that we still have around and it's still being used by a lot of people. And I also worked on mobile before I started working with Tiaan on Builder Central and helping out our admin persona to reduce the amount of time it takes them to get to build, and then soon we'll have a lot of additional things as well that we'll probably talk about in here as well. But super excited to be talking with you on this podcast.

Mike:
Yeah. So the cool thing about this, is you have the number one fan of Builder Central hosting this podcast with you. I saw it a little bit before Dreamforce, but I got my hands on it after Dreamforce. And let me tell you, I am the happiest, one of the happiest admins on earth. I can't wait until this gets unleashed for people to try. But let's talk about that because this is the most fun podcast I'm going to record all year because we're going to talk about Builder Central, and I can't build enough things with Builder Central. If you follow me on LinkedIn, you know that I've already built an app and I'm a kid of the '80s, so I built a Knight Rider dashboard, and then I built a car dashboard. I do have plans for a Goliath dashboard, so I'll sneak peek that just because I like building dashboards. But let's talk about quite possibly in my opinion, the coolest thing Salesforce has ever released, which is Builder Central. Tiaan, tell me what Builder Central is.

Tian Kruger:
Absolutely. So by the way, I loved your enthusiasm. It's hard to get somebody who works on the platform all day long, to be this excited about something. So I'm enjoying your enthusiasm so much.

Mike:
Good.

Tian Kruger:
But Builder Central is the end result of about two and a half years of work internally to figure out how we build on the platform with AI in a constructive way. How do we go from idea, describing it, to a working solution on the platform? And not just using any process, but making it no-code, low-code friendly, taking an admin and giving them the same tools that developers have been enjoying for the last two years, and creating things on the platform. It's built on top of all of the hard work the team has put in in their headless story, trying to figure out how do we make it easier for you to build with agents on the platform, do everything from MCPs, do it using skills, all of this stuff that we've been doing for vibes and we've been doing for frontier models. How do we take advantage of all of that, but then bring it in a package and an easy to use kind of experience that makes it delightful to use. And I think we actually managed to achieve it. The experience of-

Mike:
Oh, you did, in my opinion.

Tian Kruger:
The experiences, I've been on the platform for 17 years, I have not had this much fun building on the platform in probably, I don't know, 16 years, because it just takes so much of the pain out and that's really the goal. The goal is just to be delightful, to be fun, to be visual, take the schlep work out of it and just make it fun to create on the platform again and just unleash it for your business.

Mike:
Yeah. I will say it's never not been fun to build on the platform. I think it's rewarding and I think that's why people come in, because I can tell you exactly how I felt the first time I created Dependent Picklist. And Dependent Picklist sounds like the easiest thing in the world to make, until you get in the Wayback Machine and you go back to 2007 and CRM and everything was hard and Salesforce Dependent, this, this, next save. Oh, oh, oh, it's there. And I remember showing it to people because the first Picklist had three ideas and then it depended on the answer, and everybody in the office was like, "Wow, Mike, you did really good." I was like, "Yeah."
Builder Central is the next evolution of that. The last time I was this excited was when we introduced branding and themes, because I was really big into the show Top Gear, and I created an entire org to track cars and episodes and lap times and podcasts. And I was like, "This is amazing. This is the best thing I've ever built in Salesforce." And then Builder Central came along and it's scratched an itch I didn't know I had.

Tian Kruger:
I think it's time for a reprise of that app, don't you think?

Mike:
Oh, you have no idea. I have so many plans to build things. Daivat, tell me a little bit about you were at Dreamforce and got some customers sharing their experiences and talking about stuff that they were building. What was some of the stuff that you heard and have heard while it's still in beta?

Daivat Dholakia:
Yeah. The feedback from the customers that have tried it has been phenomenal. It's very similar to what you have also been sharing, which is it's opened up new possibilities that they did not even think were even in their realm of what they could do within Builder Central. For example, we have had a couple of different customers that have said that, "Hey, what used to take us about seven days, 10 days worth of time for multiple people to do, now a single person can do it in like two to three hours at most." The way they are thinking about solving problems is changing now because they were previously dependent on, "Hey, do we need to have the right prioritization for this?" This goes into this bucket list of, "Yeah, it would be great to have this, but we don't have the bandwidth and it's not high enough in our priority list." Versus now they're like, "Yeah, let me just go ask this and get this done in Builder Central and show what is possible."
And when everyone's aligned, they're like, "Yeah, this is great. Just let's push it out into production and get it to work." So it's changing how they're working as well. We have one customer that has been very, very engaged in the product and for them, their primary use case is how do they go about building an entire service portal, for example, for internal as well as external? And that is also, they're trying to do a POC on that to show that, hey, today in the traditional world, it takes about six to eight weeks for that to get done, versus now they were able to actually build something within a couple of hours as a prototype, and now they're iterating on it to be able to see how far they can push just by having a natural conversation without them having to know every nitty gritty detail of how that is getting done under the covers.

Mike:
Yeah. No, I agree. Tiaan, I don't know if you baked this in, it's got a little bit of attitude. I love how it sometimes comes back. When I was building the Knight Rider dashboard, it was like, "Ooh, I like this idea." And I was like, "Well, hello, how are you?" And it's not a lot, but it's a little bit of something that was just enough to be like, "I'm with you on this. I'm not just a robot doing what you tell me to do." And it kind of felt like it was on the path. So I had to tell you about that because I thought it was pretty cool.

Tian Kruger:
There's a little SaaS in it.

Daivat Dholakia:
Yes.

Mike:
Oh, yeah.

Tian Kruger:
And it's not a lot, but it just reminds you that SaaSy is still alive somewhere out there. And it cracks me up because it does feel a little bit like a coworker at times in a positive way. It sometimes challenges you sometimes. My favorite moment was I was asking to build an agent for me and it said, "Can I build an employee agent?" And I said, "No, no, I want you to build a customer service agent." And it's like, "But that's a lot more metadata." And I said, "Yes, it is." And it said, "Okay, if you really want me to build it, that's the right thing to do, I'll go do it." But it just cracked me up, because I was like, "Really? Does it really make a difference?"

Mike:
I know.

Tian Kruger:
Just a little personality, it makes it a little bit more fun, but it'll do what you want it to do ultimately for sure.

Mike:
Yeah. No, it did for me. When I went back into the dashboard and I said, "Hey, I need to add an exit button because I realized I don't know how to get out of the dashboard without just closing the tab and I think that's really bad," and it replied, it was like, "Yeah, we probably should have done that to begin with, shouldn't we?" And I was like, "Folks, thank you for baking that in." Talking about building something new though, I know you guys have a demo and we'll put the demo in here in a little bit, but before I get to the demo, I do want to talk about one thing that you both pointed out to me, which is when you tell Builder Central to do something, it doesn't actually build it in your org. Can you explain that?

Daivat Dholakia:
Yeah. So historically, what we have done is if you are trying to build something new, you go to your sandbox and you're making changes to the metadata as you are building. Now the problem with that is rolling back metadata is extremely hard and extremely dangerous. So in order to avoid that, what we did in Builder Central is build this whole concept around how you can build in sort of a virtual environment, so that you can keep vibing on it, you can keep exploring, you can keep trying out new things, but at any point you're like, "Yeah, this is not going in the direction I wanted or actually I do not want this to affect my sandbox," you don't have to worry about it because it did not change any of your sandbox metadata.
At any point you're like, "Yeah, this looks perfect to me now. I'm ready to push this into my sandbox," You hit a button and it publishes your project essentially the same as how you would in an Agentforce vibes project as a developer would do it. It pushes all of that into your sandbox and that's it. It gives you the peace of mind so you're not worried about like, "Oh, I'm going to mess up my sandbox." And that means that you can work, you can vibe, you can play around with it, you can explore and push it hard as much as you can. And then when you're ready, it is available for you in a single button.

Tian Kruger:
And I want to point out there's a really key piece to this. One of the number one questions we get, is "I already have Claude Code. Why do I need this?".

Mike:
Good question.

Tian Kruger:
Like, "What does it really give me?" I had two customers, we did a big workshop that started with that question. And after two hours of using it, they both said, "This is revolutionary. This is amazing." And I said, "Why? I love it. Yes, I agree. But why? Why do you say that?" And they all were in agreement that the fact that we give you visualizers and previews, so this means concretely, and you'll see it in the demo, concretely, when you generate a flow, even though it's just local, it's your project, you can actually see it. We actually load up a visualizer, you can see the flow just as if it's in your org. So that gives you the ability to visually see the way that you're used to seeing a flow, it looks just like a flow than it does in the org. You can see what you're building before it's ever in your org.
This is a superpower, because it allows you to, as Daivat just said, vibe and revibe and tweak things and whatever, ever before it ends up in your org. In fact, one of our early renditions of the product about a year and a half ago, I actually found out that there's a custom object limit in the org in about two hours. I managed to fill up an entire org with custom objects in about two hours. So that's when we realized, we're like, "Metadata can be created, like it's no longer a difficult thing to produce." Producing the right metadata is important and producing it as efficiently and with as little impact as possible in your org is actually really important to help that flow feel more magical.
And so yeah, it was really interesting to me to watch both of these customers go, "Oh, this is different. This is a different experience." And I was like, "Yeah, those visualizers." And we're adding more, by the way. We're adding more visualizers constantly to help you. So if people have strong opinions about which visualizers they'll use, tag me or Daivat on LinkedIn and say, "Hey, they help me visualize X, Y, and Z." We're looking for that input.

Mike:
Cool. Well, we've teased out the demo enough. So do you want to introduce the demo? And then for everybody listening on audio podcasts on iTunes, there'll be a video version of this over on YouTube, two versions actually. One will just be a replay of the audio and the other is actually the video one that you'll get to see the demo in. So I'll let you guys introduce the demo.

Daivat Dholakia:
Awesome. So the demo that we're going to have is about a branded customer that wants to create a site for support so that the users in the field that are customers, end users essentially, are able to go to this portal, able to ask questions about whatever problems they have, and at the same time, interact with an agent. The other piece that you will also see is a way where when you are trying to work on building out the agent, all you need to do is do inline editing. And this is one of the critical pieces, because what Claude cannot give you is a way to say, "Hey, I want to change this one very particular thing in this agent or in this flow or in the UI." Every time you are asking to make a change in Claude, for example, you have to put the entirety of the text saying, "Hey, on this particular page, on this particular agent, I want this exact change." And that means you're having to type out a lot of text to try and tell Claude that this is the exact change you want to do.
Versus in Builder Central, because we have visualizations, because we have a way to edit in line, all you do is say, "Hit edit at the top," and then you will select a specific component you want to change and just say, what do you want to change over there. And the change can be as simple as, "Hey, I want to change colors of this particular component, or I want to change the text of this particular component." Or it can be, "Hey, I want to add this particular piece in this flow." Or it can be, "I want to change this particular agent to do an additional action." All of that becomes possible because of this editing piece that is extremely pinpointed, which no one else offers you today. And this saves you so much more time, because you're not having to type out everything and you're not going back and forth with the Claude agent or Codex or any other tool to say, "I actually want to make this change, but I need to tell you all of my details around it." It simplifies the whole process.
And as we add more visualizations, we will have more ways for you to do pinpointed changes, and that's a massive differentiator.

Mike:
Yeah. Cool. Well, let's go to the demo. Okay. So we spent the beginning part of this podcast talking about building stuff, because it's called Builder Central. But I think it's important, it doesn't just build scratch new. So Tiaan, we're not going to immediately sit down and within a few hours fill our orgs with custom objects. Oh, man. But you can also go back to other projects and improve things. And I realized this immediately after I built my Knight Rider dashboard of like, "Oh, I need an exit button and then while I'm here, maybe I should be able to click through and improve on things." So tell me how that works in Builder Central. Tiaan, I'll start with you.

Tian Kruger:
Sounds good. So first of all, interesting nugget, Builder Central, the builder in Builder Central actually refers to the people who build.

Mike:
Oh.

Tian Kruger:
Anybody who builds on the platform. Not the central builder that is a single builder who rule them all. All right. So when we talked, we talked about over 50 customers, and the one thing that came from every single customer is, "I wish I built new stuff every day. It'd be really, really nice. But you know what? 90% of my job is actually fixing, tweaking, maintaining, improving, refactoring existing stuff." So we fully understand that that is a very important part of the story. We are actually going to make what I'm about to describe even stronger as we get closer to TDX. So expect the story to get better, but we fully understand that builders don't just get to build new stuff. I mean, as much as we all would like to build Knight Rider dashboards every day, most of the time we're adding a button to our opportunity page to help you add products in a different way or giving you recommended products.
And how does Builder Central help with that? Well, there's a couple different ways. Builder Central has access to all the metadata in your org, so you can actually start by asking the agent to help you do something like refactor or test existing flows. And I actually have a demo we could potentially consider showing, that actually shows you how you can just be talking to the agent in the Builder Central today, pull flows from your org and then test them, get flow tests created for it, you can be cool too, you can have flow tests without having to build them. Even the flow test PM looked at the flow tests that were built and said, "Ah, these are actually really good." He was very surprised by the way. I was slightly offended. But no, it was great, it was absolutely fantastic because FlowTest is a brand new capability and Builder Central did a great job building those.
So when you have that tech debt, you have that difficult thing in your org that you want to fix, simply start by asking the agent to help you with that. Now, we're going to put some enhancements in place by TDX that's going to help you actually go grab metadata from your org and say, "Hey, grab this app, this old app that I have, bring it in. It's ugly. I want to make it pretty. I want to make it be more user-centric. I want to bring our brand colors and we'll let you quickly pull that into the project and then go to town." And I'll tell you what, you have not seen beautiful lightning apps like what Builder Central can create. I have seen some of the most extraordinary, beautiful lightning apps in the last two months that I've seen probably in all my career here at Salesforce.
It's absolutely extraordinary what it can create. So we fully understand that most of people's jobs are modifying what's there. And so we're going to make that journey better and better. Right now it's Builder Central, it's built first, but we're bringing so many more capabilities to help you bring the stuff that you already have, into the latest technology, refactoring, reformatting, beautifying. Come on, your users deserve a beautiful app. You can do it now with just describing it and giving it a brand kit and saying, "Hey, follow this design and make our app look amazing."

Mike:
And sometimes even a screenshot. So my question on the edit part, and maybe Daivat, this is you, you talked about it doesn't really do anything in your production environment. And I think we've talked a lot about building. The one thing I haven't said is I love how before it does anything, it's like, "Do you approve this? Is this okay?" I want to make sure that we're not saying all you do is give it two sentences and then off it goes and magically you come back from lunch and it's done all this without your approval. It keeps you in the loop the entire time. But you mentioned when we're building something new, it's building it in a virtual environment. So when we're editing something, does it edit in that virtual environment or how does that work?

Daivat Dholakia:
Yeah. So the same concept applies when you're trying to edit as well, right? And the human in the loop piece is very critical over here, right? What you're trying to say over here is, again, when you're trying to make a change to an existing stuff, you still want to make sure that you're not making changes, because again, you're working with an agent over here to be able to make these changes, and the agent may do something that you did not intend it to do. So to make sure that you're not going down the path of then having to roll back a flow change that got deployed, for example, you always want to make sure that you're working in a virtual environment before the changes get pushed out. And again, the agent will never, never automatically push the change without asking for your approval. So there are two ways that you can push this.
One is you can ask the agent to do it, or the second is there is a button in the UI that you can use to be able to push the change to the org as well. But in both of these scenarios, the user is explicitly saying they want this change to go out into the org.

Mike:
Cool. That's super helpful to know because I didn't understand. I'm fine building stuff in a sandbox, but then as I was listening to you, I was like, "Oh yeah, I could completely mess up a sandbox pretty fast if that's all it's doing in there." And I do love the idea of scrapping something. I think the aha moment came for me was when I gave it something, it built it in like 12 minutes. And I thought in the span of a workday, it was pretty common for me to have a 9:00 AM meeting where people were like, "Show me Salesforce." That's literally what it was. And I could just sit there and gather requirements. Over lunch, I could have Builder Central build stuff, because I'll be honest, I didn't know there was a visualizer because I was so caught up in watching the chat work through what it was doing, that to me was the interesting part.
And I was like, "What's this? Oh my God, there's a whole thing over here." It was too much. But you could do that over lunch and you could literally contact that stakeholder and say, "Hey, I got a prototype I want you to just click through." And they could click in the visualizer, done. Within a day, you could sit down and comfortably have something, a V1 to deploy to somebody. I was blown away.

Daivat Dholakia:
I do want to add one more thing that is actually rolling out this week, which is previously what used to happen is when you gave in the prompt initially, it would go and ask you a couple of follow-up questions. The agent would ask you a couple of follow-up questions and then it would start building. What we are changing now is when you given that initial prompt, agent will still get that clarification, but it'll build a project plan for you to then review and approve before it starts building.

Mike:
Oh, that's huge.

Daivat Dholakia:
And this actually is a very important change, because what happens now is you are in control of what exactly the agent builds before it starts building rather than after.

Mike:
Right.

Daivat Dholakia:
So you have a chance to say exactly what you want the agent to build. If you want to say that, hey, there's a particular object you want to use, there's a particular flow you want to use, you have a way to specify all of that and make sure that that's part of the project plan, and then the agent will use that as part of the building process.

Mike:
Yeah. And sarcastically, we're all really good at building project plans.

Tian Kruger:
You know, Mike, I want to throw a challenge at you.

Mike:
Yes, please.

Tian Kruger:
When you have that 9:00 AM meeting, take your transcript from the meeting, shove it into the build agent and tell it as an attachment and tell it to help you figure out what you need to build out of it.

Mike:
Yeah, that'll be the next thing I should try. So one more topic to cover, but I know you have a demo that I want to put in for this podcast on showing Builder Central edit something. Do you want to set that up now?

Tian Kruger:
Yeah. I think that the best example, it's not the most beautiful example, but it's a very practical example, is I'll walk you through in this demo, a flow improvement scenario that I had, where I had a bunch of existing flows, I wanted them to get hardened, I wanted to get flow tests created. And so I'll take you through that project and show you how I used the agent to actually improve my project. It actually found a bunch of bugs in the flow. So it's more of a walkthrough of what I had done as opposed to an interactive walkthrough, but I think it'll inspire you and making you think what tactic in your org can you actually go do this with?

Mike:
Like it. Well, let me put that demo in here. All right, so we covered a lot, we covered building, we covered editing, but I think Tiaan, you said it best. We'd all love to live in a world where we built Knight Rider dashboards. I would. But the reality is, in a lot of big organizations and small, there's governance, there's procedures, there's policies. I think my job gets to be a little bit of the fun creator in that I'm trying to show people different possibilities, but also I know there are people out there that have watched my video and been like, "Cool. In order for me to build a dashboard, it has to do X, Y, and Z, and then A, B, and C have to approve it." So I'd love to talk about what for Builder Central we have or we have coming in terms of governance and policies, and I'll kick off that topic here. So I don't know which one of you would like to tackle that.

Daivat Dholakia:
Yeah, I can take it. So we are today in beta, as we all know. And even in beta, we do have integration with Governance Org or DevOps Center, which is now rebranded to Lifecycle Center. And as part of that, what you can do is set up policies that flow down from that governance org down into every sandbox that you have. So as soon as you open up Builder Central, it'll say, "Hey, there is governance attached to this, governance org attached to this, so you need to log in first so that you can connect those two." And as soon as you do that, all of the policies immediately apply to whatever the agent is building within Builder Central. Now this is very important because you have probably a group of admins that are saying, "Hey, here is how we want the org data model to behave, the naming of it or for the flows." And then you have a bunch of architects that also are putting in their policies to make sure that how should new stuff get built in the org before they get deployed, right?
And then you have a whole bunch of testing policies and a whole bunch of different policies that you can have today out of the box. And then Lifecycle Center is also planning to add custom policies, which means that now you can decide what is the specific policy you want to use that gets applied across your entire ecosystem of orgs, regardless of whether it's your production org, your sandboxes, your partial copy, full copy, UAT environments, all of them apply the same policies. So as soon as Builder Central starts building something, it uses the policies out of the box without you having to do anything additional.
And as soon as you then publish, all of these are Already built with those policies in mind, so there is no refactoring work that needs to be done. You don't have to change any object data names or any flow names. Everything works as what you would have wanted it out of the box. And at the same time, the admins that actually set up these policies don't have to worry about what happens in those environments. They can set it up once and then it gets applied automatically.

Mike:
Yeah, that's super important. I know having watched presentations that Jennifer Lee gives, she always gives a best practice on how she names her flows. And I think it's one thing, I've had orgs where I've had everything beautifully named, and then I could come in and Builder Central's like, "Cool, I just threw all this pasta at the wall." But you got your app and you're like, "Oh, I got to rename things."

Daivat Dholakia:
Yes.

Mike:
And I like that you can actually give it some kind of guardrails to follow.

Tian Kruger:
And that's actually a fairly fundamental thing that we are trying to build into the product, which is kind of lead you into the bit of success. We're trying to help implement best practices everywhere we can. This means we are going to be natively integrated with Lifecycle Center, so that if you just follow what the agent's telling you to do, we're going to make sure that you set up pipelines and drive your change management process the way it is if you don't have it set up. We're going to streamline it for you, help you get to that kind of best practices. And that's very much tied to the, let us help you get some of the pain out of the way so that you can just focus on the creative aspect, the understanding the business aspect, the focus on the fun part of getting that dashboard perfect for your customer, and not have to worry about as much of the foundational plumbing.
The more we can set up for you, so it's kind of a little bit of a picture into where we're going with the product. And there's also something that's fundamentally different when you use something like Claude Code directly. Policies are implemented automatically, you don't have to do anything. Any kind of skills that's coming from your org is automatically included in Builder Central, you don't have to do anything. We have our best practices built in automatically, we're going to be doing code scanning for you to make sure that any code that's produced is secure as best as we can. So you are building with all the power of something like Claude Code, but you're building with it, trying to do its best to set you up for success every step of the way. And by the way, you may wake up tomorrow morning and it's a little better without you having done anything.
And it's kind of magical. We've all used phones that update overnight and you wake up the next morning and you're like, I got this brand new feature that I didn't have yesterday. Imagine that for building on Salesforce. That's what you're going to have, and that's what you have already today. I mean, Daivat literally just called out when people wake up this morning, this week and they open up within this week or two, they open up Builder Central and they start building, they're going to actually start with a spec, with a one pager where they can understand what's going to be built. That's a change from yesterday.

Mike:
Wow.

Tian Kruger:
It's better and it's going to help you get to that better success. So it's very fundamental to understand that's the magic that this thing brings. We are constantly making it better so that you have to do less to be successful.

Mike:
But I mean, that's also, I remember I used this analogy in another blog post, the way that Salesforce did releases, on-prem IT releases, those guys, hey, we're here for the weekend, camping out, we're ordering pizza, we've got sleeping beds and cots and stuff. And I remember leaving Friday and I told somebody, "Well, Salesforce has a release this weekend." "Oh, are you going to be up?" "No. I'll come back Monday and it's all there." And so all of that just feels natural in the Salesforce world.

Tian Kruger:
Yeah.

Mike:
Last question that I thought of, and I'm wondering we have the answer, because I think people are probably going to ask this after hearing this entire podcast. When I build something in Builder Central and then I love everything it did, I press deploy, it goes to production, what does it say, who built it?

Daivat Dholakia:
Yeah. So essentially it still uses the same user that actually is using Builder Central, because the deployment to the org and then into the production will come through that same chain. Right?

Mike:
Okay.

Daivat Dholakia:
Even though the agent is building it, that does not take away the testing and who owns it. Essentially the same user that built it in Builder Central and then pushes it in the org and then pushes it into the production org, is still owning and responsible for that particular project and everything in it.

Mike:
Okay, cool. So I get all the credit.

Tian Kruger:
You do. You do get all the credit. I do want to call out though that this will change as we move forward over the next couple of months. A very foundational thing that's changing in the platform is as agents become more and more autonomous, doing more work, we want to make sure that we understand when work was done as you, when work was done for you by an agent. Right?

Mike:
Right.

Tian Kruger:
So you still get the credit, but you get the credit for asking the agent to do the right thing sometimes, right?

Mike:
Right.

Tian Kruger:
And so there's a foundational shift that's happening in the platform with agent identity, where the platform at its most foundational layer understands that sometimes that change that was made was made for a person by an agent. So this is not imminent, it's not coming like tomorrow, but it is coming. And so if it's something in the back of people's minds where they're like, "I need to be able to understand from a traceability, from an auditability standpoint, what did I build, what did an agent build?" that is coming. That being said, something that we kind of glossed over, but it may not be completely obvious, I wanted to call it out right here at the end, is the metadata we produce is standard metadata.
There's nothing magical about it. Once the agents built it and deployed it's just traditional metadata. And this is really important. We're not inventing a new way to build a platform. Yes, we are too, but not for this one for Builder Central. We are just leaning into where the platform' already great. So if you're used to using pipelines, you're used to using DevOps Center, you're used to using one of our ISVs that actually help you do change management, all of that still works. Your developer can pull down that same source and work with it and help you figure out, make sure that this Apex is perfect. None of that is broken or changed with Builder Central. So you build with the latest and magical technology that AI is providing for you, but you can still use the metadata and all of the experience and the history that you have.

Mike:
Awesome. I love it. Thank you guys for coming on the podcast. I think I can't wait to see all the changes that come to Builder Central perfectly fine by me right now. I think it's a great V1. Every improvement is just going to be that much cooler. So you guys are rock stars in my opinion. Thanks for building this stuff and empowering people.

Tian Kruger:
Thank you for getting the word out there, Mike. We love being on your show.

Daivat Dholakia:
Yeah. Thank you, Mike.

Mike:
Big thanks to Tiaan and Daivat for coming on and for showing us what Builder Central can do, and really just making me super happy. The idea I keep coming back to is that Builder Central doesn't touch your sandbox until you tell it to. So you can explore things, you can scrap ideas, you can try again, all without worrying about how you have to do a rollback. Now Tiaan reminded us that most of our jobs are fixing and improving what's already there. And you know what? Builder Central does that really well too. And I think for the exit of this, I'm going to just try Tiaan's suggestion and feed Builder Central a transcript of this podcast and see what it builds. So if you follow me on LinkedIn, I'm going to post it there. And if you watch this on YouTube, I'm going to post it after the close of this video.
So let's see what Builder Central can do. But the cool thing is as Salesforce admins, we still get credit for all of that we've told Builder Central to do, which is really nice. And it looks like they're going to improve that to add for auditing and clarification purposes. So I love that. If you have opinions on what visualizers Builder Central should add next, be sure to tag Tiaan and Daivat on LinkedIn, because they said they're listening and I can affirm to that, because I gave them ideas after this podcast. So we'll see if those get worked in. Anyway, thanks for listening. Until next time, I'll see you in the cloud.

 

More episodes from "Salesforce Admins Podcast"