Admins / Artificial Intelligence

Should You Be Vibe Coding as a Salesforce Admin in 2027?

Tim Combridge

By Tim Combridge

Add SF Ben as a preferred source

Highlights

  • According to SF Ben’s first-party survey, almost three-quarters of Salesforce Admins (71.4%) have never tried using a vibe coding tool. 
  • Vibe coding is the next step in the clicks-not-code journey. Flow Builder was a prebuilt builder that allowed Salesforce Admins to build automation without writing code directly. So, too, does vibe coding.
  • AI is an accelerant, not a replacement for someone who knows Salesforce well. Anything that an AI vibe coding tool builds should be properly reviewed and validated by a Salesforce professional before going into production. Notably, AI does not own the deployment – this remains the responsibility of the human.
  • Salesforce Admins have years of governance and security best practices that they’ve mastered. This puts them in a prime position to take advantage of AI vibe coding tools in a responsible way. 

If you’ve read any of my content since the Salesforce Ben Admin Survey 2026 Results dropped, you’d know that I’m flabbergasted that three in four Salesforce Admins have never touched a vibe coding tool. That’s not saying they don’t do it frequently, but have never even tried it. 

Well, I’m here to share a strong conviction that I have: I believe that any Salesforce Admin who doesn’t learn how to vibe code is missing out and will be left behind. Whether you agree or disagree with me may change as you read this article. Join me as I unpack this and explain why you must learn how to vibe code in the Salesforce ecosystem.

What Vibe Coding Actually Is

In case you haven’t heard the term “vibe coding” before, it’s a relatively new term coined by Andrej Karpathy, co-founder of OpenAI and former AI director of Tesla. In the now-infamous post on X, he calls it a “new kind of coding… where you fully give into the vibes, embrace the potential, and forget the code even exists.” 

Essentially, it’s where you instruct an AI developer to write code for you and click “‘Accept All’ always”, allowing the tool to not only write the code, but also make some of the design decisions for you.

Now, as Salesforce Admins, you won’t often think of code as something that you build as part of your role. Coding, programming, and software development are usually seen as the domain of Salesforce Developers. The reason why this is a relevant topic for Salesforce Admins comes down to one part of Karpathy’s post: “Forget the code even exists.”

This sounds a bit more like something a Salesforce Admin would be interested in! Think of what Flow Builder has ultimately done for Salesforce Admins and other declarative builders: we can build complex automations using clicks, not code. 

With this in mind, and taking a bit of a different approach to Karpathy’s original definition (as in, don’t just click ‘Accept All’ all the time), I would argue that vibe coding will soon become the next big step in the evolution of no-code building both in and out of Salesforce. 

This is why it’s something that I believe Salesforce Admins should be aware of and learn how to do sensibly.

READ MORE: Salesforce Flow Demonstrates Why Vibe Coding Isn’t Enough

Putting the “Vibe” in Vibe Coding

If you’re anything like me, you built your Salesforce career on the back of the clicks-not-code mantra. Flow Builder (or, Cloud Flow Designer in its earlier days) was the tipping point for me as a young, wide-eyed technology professional.

I was astounded by how much power I had without having to write a single line of code. I could make a very real impact on the business that I worked for, and I could see how mastering this tool would let me bring value to many, many more businesses in the future. 

Although I did eventually learn how to write a bit of code in my Salesforce career, I am still extremely bullish on the idea of vibe coding as a tool for non-coders. Where Process Builder began to add new dimensions to Salesforce declarative automation, Flow Builder took it to the next level.

Now, with the advent of agentic AI development tools that create output files that Salesforce Developers can read and write to directly, we’re standardizing the language that we all build on.

READ MORE: Vibe Coding for Salesforce Admins: Top Use Cases and Pitfalls

The new skill is learning to ask a machine for what you need done, and to do it clearly. You need to learn how to master the art of giving the right context, managing the size of that context to ensure you’re not overloading the agent, and ensuring that you’re clear about the outcomes you want to achieve.

AI Is an Accelerant

Rather than needing to navigate across multiple different screens and menus in a tool like Flow Builder, Salesforce Admins can use a tool like Agentforce Vibes or Claude Code to write the code that they need. That code can then be deployed into a scratch org or sandbox to test thoroughly. Then, it can be deployed into production – although this typically should only be done once it’s been stress-tested by a Salesforce Developer. 

While it empowers you to make a lot more impact in terms of code in your Salesforce org, I need to stress this: AI coding tools are not a replacement for a Salesforce Developer. Having a coding tool ready to build and create according to your demands is one thing, but it is not a scapegoat for ownership of the outcome. 

READ MORE: AI Was Supposed to Create New Salesforce Jobs – So Where Are They?

Anything that is produced using an AI coding tool needs to be owned by a human. That means that any time it needs to be updated, maintained, or fixed, that responsibility falls on a human. An AI coding tool can help, but it’s not a replacement for a human. It is an accelerant rather than a replacement. 

Salesforce First-Party Tooling and Beyond

With the warnings out of the way, it’s important to understand what tooling is available to Salesforce Admins who wish to get their hands dirty in the world of vibe coding. This list is not exhaustive, and it’s not even exhaustive in terms of the first-party Salesforce offerings. There are so many options to choose from, so I’ve narrowed it down to some of the ones I’ve been suggesting to those who ask me directly. 

First and foremost, there’s Agentforce Vibes – Salesforce’s own first-party vibe coding tool. It’s a vibe coding tool specifically designed for use in Salesforce orgs, having been trained on Salesforce data. It includes an autonomous AI coding agent called Vibe Codey that you can collaborate with to build metadata in your org. 

READ MORE: Why Salesforce Is Betting on “Enterprise Vibe Coding” With Agentforce Vibes

This tool is the go-to agentic AI coding tool for building apps, agents, and metadata on the Salesforce platform. You can access it either through the web interface or as a plugin for VS Code.

This is where my vibe coding journey in Salesforce started, but not where it ended. Today, now that I’m more comfortable with agentic coding, I prefer to use Claude Code connected to the Salesforce DX MCP. This empowers me to use the Claude AI coding agent that I’m familiar with and use beyond my Salesforce work. I ground it in my org data and use the Salesforce DX MCP to ensure it’s got the tools it needs to do its job properly.

The Price of Inaction

I want to bring your attention back to the statistic behind this article: Almost three-quarters (71.3% to be exact) of Salesforce Admins have never touched a vibe coding tool of any kind. This is according to the responses in our SF Ben Admin Survey 2026. I’ve raised this statistic so many times since the report was released, and I’m convinced we’ll see that number significantly drop in the 2027 report.

What this means is that those who continue to ignore the power of vibe coding tools will fall behind even further. The Salesforce Admin role is evolving rapidly, and it’s becoming more and more important that admins can work with AI tooling. The expectation isn’t that you become a master of reading and writing Apex, but that you’re able to start working with tools that can accelerate your work. 

Vibe coding tools like Agentforce Vibes or Claude Code aren’t just great for writing code, but also for writing metadata. One of my favourite examples is using it to build Permission Sets and Permission Set Groups on your behalf. Doing this manually through the Setup UI is a nightmare, and extremely sluggish in comparison to vibe coding. 

READ MORE: 10 Claude Use Cases for Salesforce Admins

There’s no denying the changing expectations that are being placed on Salesforce Admins. Learning how to properly use vibe coding tools is a great step in the right direction. The blatant truth is that if you don’t make an effort to at least learn about these new tools and how to use them, you’ll be left behind compared to others in your role.

Think Different

It doesn’t take a lot to learn how to vibe code as a Salesforce Admin. The biggest thing is a mindset shift. Where Salesforce Developers are known to write code by hand, and Salesforce Admins typically build using clicks instead of code, vibe coding as a Salesforce Admin is slightly different. Instead of using a prebuilt builder like Flow Builder or even the Setup UI, you’re communicating directly with your Salesforce org, so to speak. 

Your goal is less actually building the thing, but learning how to communicate exactly what you need built effectively. The AI tool then does the build, and you can validate that it’s done so according to what you were expecting. 

As a seasoned Salesforce Admin, your governance insights are a massive strength in this process. You know how to keep Salesforce secure and are well-versed when it comes to best practices. This will come in handy when it comes to instructing the vibe coding tool on what to build and how to build it. 

So, believe it or not, you’re extremely well-placed as a Salesforce Admin to get started with vibe coding. You don’t need to go deep into Apex or LWC development, but you should definitely learn how to use it to build things that you would normally build through a Salesforce UI. 

Summary

This year, three-quarters of Salesforce Admins have not touched a vibe coding tool. Next year, I’d expect to see that number almost flip entirely. My money is on at least 70% of Salesforce Admins having used a vibe coding tool at least once in the next year. AI isn’t going anywhere, and this is a low-hanging fruit that you could be missing out on in your role.

If you’ve not vibe coded before, are you going to start having a play with something like Agentforce Vibes after reading this? Why, or why not? If you have used one before, what’s some advice you’d offer to someone who is starting out? 

The Author

Tim Combridge

Tim Combridge

Tim is a Technical Content Writer at Salesforce Ben.

Leave a Reply

Comments:

    Kayla
    November 02, 2026 6:57 pm
    As an admin, I've been doing this for about a year now. I don't have Claude Force, but I have Claude.ai, and it works great.
    Shawn
    November 03, 2026 8:23 pm
    This stance isn't really considering that most admins do not know how to code themselves, and therefore cannot properly audit the code for security, efficiency, dependability, or scalability. It will also quickly lead to no one at the org understanding how or why things are happening. Before AI it was already a common observation that admins frequently made very inefficient automation because they didn't understand how things worked under the hood, and didn't know coding best practices. Vibe coding adds another layer to that issue, since you no longer retain the readability of a Flow for non devs. And even if Admins are just asking AI to build them a Flow, I've already seen countless times where Claude has created new Flows with zero entry criteria, or even removed entry criteria from existing Flows. Admins should be able to audit and notice those kinds of mistakes, but as people lean harder and harder into AI, those skills fade (and we're already seeing that) and these design mistakes will make their way into production even more frequently than they did before. This will result in even more messy orgs with mountains of unintelligible tech debt. In my opinion, anyone with a basic understanding of the Salesforce backend can give AI some Salesforce skills and run with it. So I really don't understand the argument that using AI is going to set you apart from the crowd. Without AI, you might get things done a little slower, but you'll also be doing higher quality work that can actually be a true innovation, instead of the same homogenized output that every single company will be getting from AI. You'll have a deeper understanding of the inner workings of your org and the business itself. You'll actually be learning and growing instead of seeing your skill regress. Personally, I get way more fulfilment from building something, and learning a lot on the way, than I do from pulling the lever on the AI slot machine until it gives me something functional. Ps: why is saving my name and email required to post a comment? Stop that.
    Charlie Lang
    November 07, 2026 11:52 pm
    I would also recommend using playwright as part of the workflow so Claude can test its own work and create documentation and training videos as it will find its own faults and fix them