How to Choose the Right Salesforce Consultant (And the Questions to Ask Before You Hire)

Hiring a Salesforce consultant is one of the most consequential technology decisions an organization can make. A good consultant accelerates your team, cleans up years of technical debt, and builds systems that actually get used. A bad one leaves you with a more complicated org, a lighter budget, and a staff that trusts the platform even less than before.

After more than a decade in this industry — first as an in-house Salesforce admin, then as a consultant — I have seen both outcomes. Here is what separates the consultants worth hiring from the ones you should walk away from.

1. Certifications Matter — But They Are Not the Whole Story

Salesforce certifications are a meaningful signal. They demonstrate that a consultant has invested in understanding the platform at a technical level and has passed a rigorous exam to prove it. A consultant with no certifications is a red flag. But certifications alone are not sufficient.

What you want is certifications paired with real implementation experience. Ask how many orgs they have worked in. Ask what the most complex problem they have solved looked like. Ask what went wrong on a project and how they handled it. The answers to those questions tell you far more than a badge count.

2. Beware the Consultant Who Agrees With Everything

One of the clearest warning signs in a discovery call is a consultant who validates every idea you have without pushback. If you describe a complex automation you want to build and they say "absolutely, we can do that" without asking clarifying questions or raising potential complications, they are either not listening or not experienced enough to know what they do not know.

A good consultant will ask hard questions. They will tell you when a simpler approach would serve you better. They will flag risks before you commit to a direction. That kind of honest friction in the early stages is a sign of someone who is thinking about your outcome, not just your approval.

3. Ask About Their Discovery Process

Before any good consultant writes a line of configuration, they should spend meaningful time understanding your business. Ask them to walk you through how they start a new engagement. What do they need to know before they can scope the work? How do they document requirements? How do they handle scope changes?

A consultant who jumps straight to solutions without a structured discovery process is a risk. The most expensive Salesforce mistakes I have seen were caused by consultants who built what they were told to build rather than what the organization actually needed.

4. Understand Who Will Actually Do the Work

This is especially important when evaluating larger consulting firms. The senior consultant you meet in the sales process is often not the person who will be in your org every day. Ask directly: who will be assigned to this project? What is their experience level? Will you have access to them, or will you be routed through a project manager?

With an independent consultant or a small firm, you typically know exactly who you are getting. That transparency is one of the reasons many organizations — especially nonprofits and mid-market companies — prefer working with boutique consultants over large implementation partners.

5. Look for Industry-Specific Experience

Salesforce is a platform, but every industry uses it differently. A nonprofit managing donor relationships and grant cycles has fundamentally different needs than a sales team running a CPQ process or a healthcare organization tracking patient referrals. A consultant who has worked extensively in your sector will move faster, ask better questions, and avoid the mistakes that come from learning your industry on your dime.

Ask for examples of similar organizations they have worked with. Ask what the most common mistakes they see in your sector are. If they cannot answer those questions with specificity, they may not have the depth you need.

6. Pricing Structure Tells You Something

How a consultant prices their work reveals how they think about risk and accountability. Hourly billing puts all the risk on you — if the project takes longer than expected, you pay more. Fixed-price project scoping puts the risk on the consultant to estimate accurately and deliver within scope.

Neither model is inherently better, but you should understand which one you are agreeing to and what the change-order process looks like. A consultant who cannot clearly explain how they handle scope changes before the project starts is one who will create friction when they inevitably arise.

7. Documentation and Knowledge Transfer Are Non-Negotiable

The engagement ends. The consultant moves on. What happens to your org?

Ask every consultant you evaluate what documentation they deliver at the end of a project. Ask how they transfer knowledge to your internal team. If the answer is vague — "we document as we go" or "we can provide training if needed" — push for specifics. You should receive clear technical documentation of everything that was built, why decisions were made, and how to maintain it going forward.

An org you cannot maintain without the consultant who built it is not an asset. It is a dependency.

The Right Questions to Ask Before You Hire

• What certifications do you hold, and how long have you been working in Salesforce?
• Can you walk me through a recent project similar to ours — what the challenge was and what you delivered?
• What does your discovery process look like before you start configuring anything?
• Who specifically will be doing the work on our project?
• How do you handle scope changes mid-project?
• What documentation do you deliver at the end of an engagement?
• What is something you would push back on if we asked for it?

The answers to these questions will tell you more than any proposal document. A consultant who answers them clearly, honestly, and without hesitation is one worth taking seriously.