Will AI replace Salesforce admins?

There’s been a lot said about this topic over the last two years, and the short answer is “no”. The caveat is that the admin role has already shifted in response to AI, and it’s going to shift further.

The good news is that the parts of the job AI is taking over were never the most valuable parts. In this post, we’ll look at the fundamental areas of the admin role that AI can’t replace, why they’re so valuable, and how to adapt to the AI era as an admin.

AI is taking tasks, not your identity

It’s easy to conflate “changing” with “replacing”, especially in Salesforce careers. So much of our collective identity is tied to being the person who knows where to go in Setup, how to construct a Flow or Apex class, or how to run a SOQL query. That’s why watching an LLM or AI agent spin those up in seconds can trigger a fear response: those tasks have become part of our role identity.

But tying role scope and identity to clicking buttons on a screen or code appearing in a file does a massive disservice to the essence of what we do. Salesforce Ben’s 2026 admin survey found that 44% of respondents use AI daily or regularly, compared to less than 25% the year prior. So, we’re clearly okay with using these tools to help us, and I think it’s important to ask ourselves why.

My view is that we’re comfortable because we know the value we bring. Clicking the buttons is part of it, sure. But building used to be expensive, and now it’s close to free. I’d guess that those 44% of respondents know this. They have an implicit confidence in their identity as the owner of outcomes, and in their ability to do the genuinely hard part of being a Salesforce admin.

The “hard” bit of being a Salesforce admin

You hear “code is cheap” a lot these days, and it’s true. Building something is cheap: with a couple of prompts, you can have output in your hands in minutes. But knowing what to build, and what will actually add value, isn’t easy — and it certainly isn’t cheap if you get it wrong.

This isn’t a new idea. People like Ian Gotts have long championed the importance of building the right thing, and pointed out how often Salesforce orgs are bloated with redundant, unused configuration.

Teams driving themselves up the wall refactoring or removing tech debt, or getting blocked on new features by existing dependencies that add no value, is a tale as old as time. In fact, a lot of the time the cheapest change is the one you don’t make. What’s needed is a mindset shift: treating all code and configuration as a liability rather than an asset.

The three necessities of building the right thing

Building the right thing sounds easy enough. It isn’t. You need three things to get it right, and it’s rare that a Salesforce team has them all.

Strong relationships

You need relationships with users, power users, and (probably most importantly) detractors. Power users will help you drive adoption and be willing to test and try anything you build, but detractors will tell you straight up if something’s not right. They’ll be stubborn and skeptical, and if you’re able to build a relationship with them, you’ll get the full picture of how Salesforce is used (or not!) and adopted across your company.

Great communication

Building relationships relies on great communication. It’s also the cornerstone of understanding what a business needs. This includes questioning and selling. Questioning helps you understand the direction you need to go in. Selling helps you generate the buy-in and commitment from users that drives adoption.

Trust

You need to earn trust with your users. Do what you say you’re going to do. If the answer to a request is “no”, explain why. And act in the best interest of your users. If you follow through, have hard conversations when needed, and act with integrity, users will open up more. Building the right thing then becomes a breeze.

One thing is inescapable. Regardless of all the attention AI is getting, at the end of the day it really is all about the humans. The time you spend investing in people is time well spent in my book — and the more of it, the better.

Judgment and context are your friends

When you get relationships, communication and trust right, you’ll have a whole ton of context about the people you work with. You’ll deeply understand what purpose Salesforce serves within your company and what gets in the way of users being successful, and you’ll be able to figure out a path to success for everyone who touches the platform.

Context is critical. When you have it, you can exercise judgment and make the best decisions, like spotting when Jira tickets ask for the wrong thing, or understanding that two sales teams in the same company work in completely different ways. Effectively navigating ambiguity is the real currency going forward, and the mark of a Salesforce admin worth their salt.

First steps to becoming an owner of outcomes

Succeeding in the future doesn’t depend on getting a new certification or signing up to bootcamps. Curiosity and commitment are what count. Here’s how to start.

Audit your org

For AI tools to really free up your time to focus on bigger, better outcomes, you need to make sure the things your users use and need most are in the best possible shape. Check for redundant fields on objects, janky layouts, and business logic that’s not quite right. You can use AI to help speed up this process, but keep in mind that it’s your knowledge of the org that should guide the final call on whether something is redundant or not.

Doing this work upfront means the work you hand to AI in the future is going into a prepared org, which stops it getting stuck at testing or creating org spaghetti.

Shadow multiple users

This is the best way to see how work is actually done in Salesforce teams. Before you start, tell users not to change a thing about what they’re doing. If you don’t, they’ll do things the “right” way just because you’re watching.

You want to see where processes get skipped, the shortcuts users take, and the small things that frustrate them. Then, go fix them! Context is everything, and you’ll build trust fast with users who feel seen and heard.

Talk in outcomes

It’s easy to talk about the flow you built, or the permissions you fixed (or that AI fixed based on what you saw). So what?

Start talking about the impact of your work instead. “I cut triage time by 50%” or “I reduced the risk of accidental overwrites by 95%” shows tangible business impact, and that’s what keeps the business coming back to you.

The job was always human

The best Salesforce admins have always been the ones who understood the people behind the requests, not the fastest navigators of Salesforce Setup.

It’s easy to overlook, but AI is still approached with skepticism. When things don’t work as they should, trust in agents is nigh on impossible to rebuild. Trust in humans — and in humans working together, aided by AI — is a recipe for success.

So, no. AI isn’t coming for your job, but it is refocusing it on the things that truly matter. And that’s a good thing.