How to Choose a Salesforce Consulting Partner: 12 Questions to Ask
Twelve questions that separate a good Salesforce consultant from a risky one — on discovery, who does the work, data, testing, handover and cost.
Choosing a Salesforce consultant is hard to get right from proposals alone. Every proposal promises discovery, best practices and on-time delivery. The differences show up in the answers to specific questions.
These are the questions we'd ask if we were on your side of the table — including a few that are uncomfortable for consultants, us included.
Questions about how they'll understand your business
1. "What happens before you configure anything?"
Look for a discovery phase that maps how work actually moves today — the process, the exceptions, the handoffs — before talking about objects and fields. A team that jumps to a demo in the first meeting is selling configuration, not solutions.
2. "What would you recommend not building?"
Good consultants push back. Ask for an example of when they talked a client out of a feature, a custom build or an add-on product. If the answer is "never," expect scope to grow.
3. "How will you handle our existing org?"
For an existing org, ask how they'll find out what's already there: automation, integrations, permissions and technical debt. An assessment before changes is a good sign. Building new features on top of an org nobody has reviewed is how technical debt compounds.
Questions about who does the work
4. "Who exactly will work on our project?"
Ask for names and roles — architect, admin, developer, project lead — and whether you can speak with them before signing. The people in the sales meeting aren't always the people doing the work.
5. "What experience does that team have with projects like ours?"
Ask for examples similar to your size, industry and Salesforce products. A partner whose experience is all large enterprise may over-engineer a 30-user rollout; one with only small projects may struggle with complex integrations.
6. "What certifications and partner status do you hold — and do they matter for this project?"
Certifications show baseline knowledge; ask which ones the assigned team holds and how they apply to your scope. Partner tier reflects a firm's overall volume with Salesforce — useful context, but not a substitute for relevant experience on your kind of work.
Questions about delivery
7. "How will you handle data migration?"
Ask about mapping, cleansing, deduplication, load order and how many test loads they'll run. Data migration is one of the most common reasons go-lives slip. Our data migration checklist shows what a good plan covers.
8. "How do you test, and who signs off?"
Look for user acceptance testing with your real scenarios and representative data — not just "it works in the sandbox." Ask who writes the test cases and what happens when something fails.
9. "How do you deploy changes?"
Ask how changes move from sandbox to production, and how they're tracked. Even small teams should have a repeatable release process and a way to roll back.
10. "What will we own at the end?"
You should receive documentation of the data model, automation and integrations, plus admin training. Ask to see an example. If only the consultant understands the org, you've bought a dependency.
Questions about cost and scope
11. "How do you price, and what's not included?"
Fixed price, time and materials, or phased — each can work. What matters is clarity on what's included: data migration, integrations, training, post-launch support and licenses (which are billed by Salesforce, separately from consulting fees).
12. "What happens after go-live?"
Ask about hypercare (the first weeks after launch), ongoing support options and response times. Salesforce changes three times a year; your org will need care too.
Red flags
- A fixed price before anyone has understood your process.
- No questions about your existing data until late in the project.
- Every problem solved with another add-on product or custom code.
- Vague answers about who will do the work.
- No plan for documentation or handover.
A simple scorecard
| Area | Weight | What good looks like |
|---|---|---|
| Discovery & process understanding | High | Maps how work moves before configuring |
| Relevant experience | High | Comparable projects; named team |
| Data & testing approach | High | Clear migration and UAT plan |
| Handover & documentation | Medium | You own and understand the org afterwards |
| Pricing clarity | Medium | Inclusions and exclusions explicit |
| Support after launch | Medium | Defined hypercare and support options |
Talk to us
CRM360 is an independent consulting company. We're happy to answer every question on this list — specifically, for your project. Request a consultation and tell us what you're trying to improve, or read how our Salesforce consulting methodology works.