Pick the wrong Salesforce consulting partner and you’ll spend the next year unwinding what they built instead of growing on top of it. Salesforce says consulting partners lead roughly 70% of customer implementations, which makes this one of the highest-stakes vendor calls most revenue teams make. A good partner shortens your timeline and gets your team actually using the system. A bad one leaves you with unused fields and a renewal you regret.
Run your shortlist through these 9 checks before you sign anything. Want a fuller picture of what a complete engagement looks like first? Salesforce consulting services page is worth a look.
Most teams start this search after something already hurt: a rollout that stalled or a CRM nobody trusts. If you’re already mid-project with a partner, start with our Salesforce partner transition checklist. Then score each partner against these checks side by side, and drop anyone who can’t answer 3 or more.
1. Start With Your Business Goals, Not the Platform
Before you talk to a single Salesforce consulting partner, write down what’s actually broken. Reps avoiding the CRM, reports that don’t match reality, a renewal process that lives in someone’s inbox: name it specifically.
Partners who ask good questions about your goals before pitching a solution are worth a second meeting. Partners who jump straight to a demo usually haven’t done that homework themselves, and the gap shows up later in the build.
Put a number on each problem. If reps spend 6 hours a week updating records by hand, write that down. If forecast calls run off a spreadsheet because nobody trusts the pipeline report, write that down too. A partner can only scope work against a target you can measure.
Then rank the list. Most teams have 15 complaints and budget for 5 fixes. Pick the 3 changes that would move revenue or retention first.
Ask each partner to repeat your goals back in their own words. The ones who get it right listened. The ones who turn your goals into a feature list were waiting for their turn to talk.
2. Confirm Their Current Partner Tier and Certifications
Salesforce overhauled its partner program in March 2026. The old 4-tier system, Base, Ridge, Crest, and Summit, is gone, replaced by 2 tiers: Select and Summit. Summit sits at the top and requires verified Agentforce delivery experience plus documented customer outcomes.
Don’t take a partner’s word for their tier. Check it yourself on Salesforce’s own partner finder. Then ask who on the team actually holds the certifications, not just the company. A tier badge spread across 8 certified consultants means something different than the same badge resting on a single person’s shoulders.
Tier tells you what Salesforce has verified about a partner’s delivery record. Use it to filter out weak options, then compare the rest on experience and team.
Ask for the certification list by name and date. Salesforce certifications need regular maintenance to stay active, so a credential from 4 years ago with no updates tells you little about current releases.
Then match the certifications to your scope. A Sales Cloud project needs Sales Cloud and Administrator credentials on the team. A Service Cloud or Experience Cloud build needs its own. Ask for the credentials that match what you’re buying.
3. Check for Real Experience in Your Industry
A partner who’s built 50 Sales Cloud orgs for SaaS companies isn’t automatically ready for a healthcare rollout with HIPAA constraints, or a manufacturing org tied to an ERP. Ask for 2 or 3 examples of work in your specific industry. “We’ve worked with companies like yours” is not an answer.
If they can’t name a client, a challenge, and what they actually built, that’s your answer.
Industry experience shows up in small details. A partner who’s worked in healthcare already asks where patient data lives and who can see it. A partner who’s worked in manufacturing asks about quote-to-order and where the ERP sits.
Ask each finalist to describe 1 problem specific to your industry and how they’d handle it. You’ll hear the difference in 5 minutes.
Check how recent the examples are. Agentforce and Data 360 have changed what a build includes over the last 2 years, so work from 2019 tells you less than work from 2025.
4. Look at Who Is Actually on Your Project Team
Sales calls are usually run by your most polished consultant, and they’re rarely the person who’ll be in your org building flows and approval processes at 2pm on a Tuesday. Ask who gets assigned to the real work, how long they’ve been doing Salesforce development, and whether they’ll still be on your account in month 4.
Team composition matters more than headcount. 10 certifications spread across 8 people is a different offer than the same 10 certifications sitting with a single person who’s about to get pulled onto someone else’s fire.
Ask for names, roles, and years of Salesforce experience for everyone assigned to your project. Put those names in the statement of work, and ask for the right to approve any replacement.
Find out who writes the code. Many partners use subcontractors for part of the build. That can work well, but you should know who those people are and how the partner reviews their work.
Ask how many projects each consultant runs at once. A lead split across 4 clients probably won’t give yours the attention the pitch promised.
5. Pay Attention to How They Run Discovery
You learn more about a Salesforce consulting partner during discovery than during the pitch. Watch how they run it. Do they ask about your data model, your approval processes, your integrations, or do they skip straight to a timeline and a price?
A rushed discovery call is a preview of a rushed build.
A good discovery produces something you can hold. Expect a written summary of your current process, a data model sketch, a list of integrations, and a list of open questions. If you leave 3 calls with nothing in writing, the partner is keeping it all in their head.
Ask who joins the calls. If it’s only sales, the people building the work haven’t heard your requirements firsthand. Ask for the architect or lead consultant in the room.
Listen for questions about your users. Who logs in every day? Who logs in twice a month? The answers shape page layouts, permissions, and training. Partners who skip this tend to deliver a technically correct system that reps ignore.
6. Ask How They Manage Delivery and Scope Changes
Every Salesforce project hits a point where the scope wants to grow. What happens next separates good partners from expensive ones. Ask how they handle a mid-project request: is there a change-order process, or does it get absorbed and billed later with no warning?
Ask about their delivery method while you’re at it. Sprints, user acceptance testing, staged releases: a partner who can walk you through their process in plain language has done this enough times to have one.
Ask to see a sample project plan and a change order, with client names removed. A partner who has both ready runs every project the same way.
Find out how often you’ll see working software. Every 2 weeks is common for sprint-based work. If the first demo lands in month 3, problems have had 12 weeks to pile up.
Agree on who signs off. Name one person on your side who approves changes, and ask the partner to name theirs. Decisions made by committee are how scope grows.
7. Get References You Can Actually Call
Testimonials on a partner’s website are curated. A reference call is not. Ask for 2 clients in a similar industry and company size, then call them. Ask what broke, what surprised them, and whether they’d hire the same partner again.
Push every partner on your shortlist for specific numbers tied to a specific fix.
Prepare 5 questions before each call. Did they hit the timeline? How did the final budget compare with the starting one? How did the team handle a bad week? Who from the partner do you still talk to? What would you change about how you worked together?
Ask for 1 reference from a project that went sideways. Every implementation hits a rough patch, and how the partner behaved during it tells you more than a smooth launch does.
Check public signals too. Partner listings on Salesforce AppExchange carry customer reviews. Read the 3-star ones first, since they usually explain what the partner does well and where it struggles.
8. Compare Pricing Models, Not Just the Bottom Line
The cheapest proposal is rarely the cheapest project. A partner who can’t show real experience, a working methodology, or willing references is the expensive option, whatever their day rate says.
Ask whether they work fixed-bid or time and materials, and get clear on what’s included in each. A partner who walks you through the tradeoffs honestly, instead of pushing their preferred model by default, has done this enough times to trust the process. They’re managing your expectations, not managing around them.
Build a simple comparison sheet before the proposals arrive. Put scope, assumptions, team, hours by role, timeline, and exclusions in rows, and each partner in a column. Gaps show up fast.
Watch the exclusions. Data migration, integrations, training, and user acceptance testing get left out of low bids often, and each one comes back later as a change order.
Fixed-bid works when scope is tight and requirements are settled. Time and materials fits projects where you’ll learn as you go. Many partners offer a hybrid: a fixed fee for discovery and design, then time and materials for the build. Ask which fits your project and why.
Count your own hours too. Your team will spend real time in workshops, testing, and training, and that time costs money. Ask for a year 1 total that includes licenses, partner fees, and internal effort.
9. Find Out What Support Looks Like After Go-Live
Adoption problems tend to surface in week 2, after go-live, when a workflow breaks or someone can’t find a field they need. Ask what the plan is for that moment. Is there a support arrangement, or does the relationship end at handoff?
A Salesforce implementation partner worth keeping brings up training, documentation, and a path to ongoing support before you have to ask. If they only mention it when pushed, budget for a second vendor later.
Ask what the first 90 days look like. Many partners run a hypercare window right after launch, where they fix issues fast while your team gets comfortable. Ask how long it lasts and what it costs.
Get the documentation in writing: process maps, field definitions, and an admin guide. If your admin leaves next year, a new one should be able to pick up the org without calling the partner.
Ask about release management. Salesforce ships 3 major releases a year, and each one can touch your customizations. A partner with a managed services plan tests changes before they reach your users.
Training deserves its own line in the statement of work. Budget for sessions by role, recorded walkthroughs, and a way to ask questions after launch.
Red Flags That Should End the Conversation
Any one of these should slow you down. Two should end the call.
- A fixed price and timeline offered before any discovery.
- References that are years old, or none at all.
- Roles on the proposal with no names attached.
- Custom code recommended for things Salesforce handles with clicks.
- A yes to every request on the sales call.
- Silence when you ask about support after go-live.
How to Score Your Shortlist
After the calls, put every partner through the same scorecard. Rate each of the 9 checks from 1 to 5, and write one line of evidence next to each score. A score with no evidence is a feeling.
Weight the checks that match your risk. A regulated industry should weight industry experience and references higher. A team with a messy legacy org should weight discovery and delivery process higher.
Compare totals, then read the gaps. A partner who scores 5 on pricing and 1 on team is selling you a number. Use references as the tie-breaker: call the last 2 clients on each finalist’s list before you decide.
Also Read-How to Choose a Salesforce Consulting Partner: 9-Point Checklist
