How to Choose a Salesforce Consultant (and the Questions to Ask First)
What to look for in a Salesforce consultant, the questions to ask before you hire, and the red flags that predict a rough project.
Choose a Salesforce consultant who has worked in an org like yours, who will do the work themselves rather than hand it to someone you haven't met, and who asks about your process before talking about features. Check verified reviews on the Salesforce AppExchange, ask how they would phase the project, and ask what they would leave out. The right consultant makes your org simpler to run, not just bigger.
Start with what you actually need
"Salesforce consultant" covers very different jobs. Be clear about which one you are hiring for, because the best fit changes with it.
- A new implementation. You are moving off spreadsheets or another CRM and need Salesforce designed around how you sell or serve.
- Fixing an inherited org. Someone built it years ago, nobody documented it, and every change breaks something else.
- A specific project. A new department, an integration, a migration or an automation rebuild.
- Ongoing help. You need changes and support every month, but not a full-time hire.
If it's ongoing help you're after, you may want a managed Salesforce admin rather than a project consultant.
What to look for
- Experience with orgs like yours. Similar size, similar cloud, similar level of mess. Ask for examples, not a client logo list.
- The person who scopes it does the work. In many firms a senior person sells the project and a junior team builds it. Ask who will be in your org every day.
- Process first, features second. A good consultant asks how a deal or a case moves through your team before suggesting anything.
- Clear phases. Look for a plan that delivers something useful early, rather than one big launch months out.
- Documentation and handoff. You should be able to run what they build after they leave.
- Certifications and verified reviews. Certifications show knowledge. Reviews on the Salesforce AppExchange are tied to real projects and are harder to fake.
Questions to ask before you hire
- Who will do the work day to day, and can I meet them?
- What would you build first, and what would you leave out?
- Tell me about an org like ours you worked in. What went wrong, and what did you do?
- How do you handle a change request in the middle of the project?
- What will we have when you leave: documentation, training, admin access?
- How do you test before something goes live?
- Can I talk to two clients with projects like ours?
Red flags
- A proposal that lists features before anyone has asked how your team works
- No one can tell you who will actually build it
- Everything goes live at once at the end
- Heavy custom code for problems that standard features or a Flow could solve
- No plan for documentation or handing the org back to you
- Vague answers about past projects, or no references you can call
Freelancer, agency or something in between
| Independent consultant | Salesforce partner agency | |
|---|---|---|
| Who does the work | The person you hired | A delivery team, often different from the sales team |
| Best for | Focused projects, inherited orgs, ongoing help | Large programs needing several specialists at once |
| Speed to start | Usually fast | Depends on staffing |
| Range of skills | One senior generalist, with specialists brought in when needed | Broad bench in one firm |
| Main risk | Capacity if the scope grows a lot | Hand-offs between sellers, consultants and developers |
Neither is better in general. The question is whether the shape of the team matches the shape of your project.
How I work
I've led revenue and operations teams, and now I design and build the Salesforce orgs those teams use. I hold 13 active Salesforce certifications and have 25+ Salesforce-verified projects reviewed on the AppExchange. The person who scopes your project is the one who builds it. You can see how I approach Salesforce implementation and optimization, or get help while you hire an admin.
FAQ
What does a Salesforce consultant do?
A Salesforce consultant works out how Salesforce should support your sales, service or program process, then designs and usually builds it: objects, fields, automation, permissions, reports and integrations. A good one also tells you what not to build.
Is a Salesforce consultant the same as a Salesforce admin?
No. An admin keeps an existing org running day to day: users, small changes, reports and data. A consultant designs bigger changes and new implementations. Many smaller teams need someone who can do both. Salesforce admin vs consultant vs developer covers the difference in more depth.
Should I hire a freelance Salesforce consultant or a Salesforce partner agency?
A freelancer suits focused work where you want one senior person who scopes and builds. An agency suits large programs that need several specialists at once. The bigger risk is a mismatch between who sells the work and who does it. Freelance consultant or agency walks through when each wins.
What certifications should a Salesforce consultant have?
Look for the Salesforce Administrator certification at minimum, plus the consultant certification for the cloud you use, such as Sales Cloud or Service Cloud. Certifications show knowledge. Verified reviews on the Salesforce AppExchange show delivery.
How do I check a Salesforce consultant's work?
Ask for two references from similar projects and read their verified reviews on the Salesforce AppExchange. Ask them to walk you through a decision they talked a client out of, and why.
If you're comparing consultants now, tell me about your org and I'll tell you honestly whether I'm the right fit.
Is your CRM getting in the way?
Start with the free funnel check to see where deals stall. If you would rather talk it through, a 30-minute call is usually enough to tell whether I can help.

