Everyone’s asking if AI replaces the Salesforce admin. Wrong question.

I don’t think the Salesforce admin is going away. I think the job is asking something different of the people in it, and the smart teams are restructuring around that on purpose.

The old admin job was configuration, user management, standard automation. AI is absorbing a lot of that now. But the role isn’t shrinking, it’s shifting toward something closer to orchestration: understanding how Agentforce is actually working inside the platform, knowing when it should own a process versus when it needs a human in the loop, catching when the data underneath an agent’s decision doesn’t hold up.

That’s real, valuable work, and a good admin can grow into it. But orchestration isn’t the same skill set as architecture, or Data Cloud modeling, or Revenue Cloud design. Those are specialist problems, and trying to stretch a generalist admin to cover them is how you end up with the kind of org debt that’s expensive to unwind later.

The teams getting this right aren’t choosing between admin and specialist. They’re being deliberate about the mix. Develop the admin into an orchestrator who owns the day to day relationship between the business and the AI. Bring in the specialist for the architecture and the deep platform work the orchestrator shouldn’t be guessing at. That’s not a compromise, it’s a more accurate map of where the value actually sits now.

Most job descriptions still assume one role covers all of it. That’s the gap worth closing, not by replacing your admin, but by getting clear on what they should own versus what needs a specialist next to them.

If you’re looking at your team structure, I’m happy to have that conversation with you.