Salesforce Admin vs Consultant vs Developer: Which One Do You Need?

For most growing teams, the best answer is one person who can do all three: keep the org running like an admin, design changes like a consultant, and write or review code when clicks really can't do the job. That person should also have trusted specialists they can bring in for the rare work outside their lane. The three job titles still describe different kinds of work, but the lines between them are fading fast.

Here's what each role covers, why the old split makes less sense every year, and how to tell whether the person you're hiring can really cover all of it.

What each role covers

Admin work. Users, permissions, page layouts, fields, reports, dashboards, data loads, duplicate cleanup, and answering "why can't I see this?" It keeps the lights on and never really finishes.

Consulting work. Designing changes before anyone builds them: a new sales process, a pipeline restructure, an integration with your billing tool, a move to a new cloud. Good consulting asks why before how, then builds most of it with clicks, like Flow, record types, validation rules and reports.

Developer work. Code: Apex, Lightning Web Components, custom integrations through the API. It's needed when Flow and configuration genuinely can't meet the requirement. Salesforce's own guidance is to reach for Flow first and add code when you hit its limits.

Why splitting them up stops working

When these are three different people, every request becomes a handoff. The admin notices the problem, the consultant designs a fix, the developer builds it, and the admin inherits something they didn't design. Each handoff loses context and adds days.

It also leads to the wrong fix. A team with only an admin gets small patches when the design needs rethinking. A team with only a strategist gets recommendations nobody has time to build. A team with only a developer gets code for problems a Flow could have solved, and then pays to maintain that code for years.

Why one person can now do it all

The platform has changed. Each Salesforce release moves more work from code into configuration, so much of what once needed a developer is now point-and-click. AI tools now help a skilled consultant write, test and review code faster than before, and explain what older code in your org actually does. Reporting and automation tools that used to need a specialist are now part of everyday admin work.

The result is that one experienced person can cover the daily admin work, design the changes, and handle most of the technical build. They also know your org end to end, because they built most of it.

Where that person should bring in help

No one is an expert in everything, and a good generalist says so. The right setup is one owner backed by people they trust:

• A specialist developer for a large custom build, a complex integration with no connector, or heavy data processing.
• A product specialist for something like CPQ or a cloud they rarely work in.
• Extra hands when a deadline means more work has to happen in parallel.

You keep one point of contact who understands the whole org, and the specialists work inside a design that already makes sense.

How to tell if someone can really do it all

• Ask them to explain a recent request end to end: what the problem was, how they designed it, and what they built.
• Give them a problem and listen to their first answer. If it's code, ask what the click-based option would be. If they can't name one, keep looking.
• Ask what they won't do themselves, and who they call when that comes up. "Nothing" is the wrong answer.
• Ask how they document their work, so the next person, or the specialist they bring in, can pick it up.

How to tell if this is you

• Your team waits days for simple changes like a new field or a report.
• You've hired strategy and gotten slide decks, but the backlog hasn't moved.
• Someone has proposed custom code for something that sounds like a standard feature.
• No one can explain what the automations in your org actually do.
• Your Salesforce owner left and the job has quietly landed on a sales or ops lead.

FAQ

Do I need a Salesforce admin, a consultant or a developer?

For most growing teams, you need one person who can do all three, plus access to specialists for the rare big build. Hire separate roles only when the volume of work is large enough to keep each one busy.

Can one person be my Salesforce admin, consultant and developer?

Yes. The platform now handles much of what once needed code, and AI tools help experienced consultants with the technical work. One person who knows your whole org usually moves faster than three people handing work back and forth.

When do I actually need a dedicated Salesforce developer?

When the requirement is beyond configuration and Flow and too large for a generalist: a big custom application, an integration with no existing connector, or heavy data processing. Your generalist should be the one to recognize that and bring the developer in.

How is that kind of Salesforce help usually priced?

Most consultants work by the hour, on a retainer, or for a fixed project fee. A retainer reserves the same person's time each month, so they stay close to your org. After a short call I can scope your work and give you a real number.

If you want one person who can run, fix and build your Salesforce, and who will tell you honestly when you need someone else, I'm happy to look at your setup. Here's more on my Salesforce consulting work and covering admin while you hire, or let's talk. If you're weighing a freelancer against a firm for that role, I compare them in freelance Salesforce consultant vs agency.