What happens when you hand a six-figure Salesforce project to a firm that looked brilliant in the pitch meeting but quietly assigns the actual work to a junior consultant who has never configured a single approval process? That gap between the sales room and the delivery room is where most CRM disappointments begin. The questions below are built to close that gap before money changes hands.
Quick Answer: What questions should I ask a Salesforce consulting company before hiring?
Ask which partner tier the firm holds, which named consultants will do the work, and whether those individuals’ certifications can be verified through Salesforce’s public credential check. Then push into delivery mechanics: how they separate declarative configuration from custom code, how they handle the three Salesforce releases each year, and how they define and measure success.
Firms vary enormously in shape. Some are large systems integrators with deep bench strength and slow processes; others are boutique shops with senior-only teams but limited capacity. The right fit depends on your project’s complexity, not on the size of the logo on the proposal.
Before signing, compare partner tier and assessment date, named delivery team, verified certifications, data processing agreement and hosting location, accessibility testing method, contract type and change-request process, IP ownership, post-go-live warranty, and exit or handover terms.
Why These Questions Separate Good Firms From Expensive Ones

Salesforce consulting is an unusual purchase. You are buying expertise you cannot easily evaluate, on a timeline that stretches for months, from people whose actual work you will only see after the invoice arrives. That information imbalance is why procurement discipline matters more here than in almost any other software-adjacent purchase.
The stakes are concrete. Salesforce ships three major releases a year, and each one can break custom code and integrations that were never regression-tested. A firm that treats go-live as the finish line rather than the starting line will leave you absorbing that breakage yourself. The same logic applies to data protection: under the EU GDPR, which has applied since 25 May 2018, a consultancy processing personal data on your behalf is typically a processor, and Article 28 requires a written data processing agreement. If you operate in the UK, GDPR-derived law remains in force through the Data Protection Act 2018, so UK-specific handling needs its own conversation.
None of this is exotic. It is simply the difference between asking about it before the contract and discovering it afterward. Buyers who research carefully in adjacent categories already know the pattern; the same instinct that drives someone to read a managed detection response checklist of 12 questions to ask before buying security services applies directly here. Ask early, ask specifically, and ask the people who will actually do the work.
Partner Tier and Certification Questions
Which partner tier do you hold, and when were you last assessed?
Salesforce runs a partner program with tiered designations, historically including consulting partner levels and later Navigator status. Tier names and criteria have changed several times over the years, so the specific label matters less than the discipline behind the question. Ask which tier the firm holds, when it was last assessed, and what changed since the previous assessment.
A firm that answers fluently and volunteers the assessment date is signalling that it tracks its own standing. A firm that gets vague is telling you something too.
Can you name the consultants, and can I verify their certifications?
Certification counts are a weak proxy for quality on their own. A firm can stack dozens of badges and still staff your project with someone who earned them last month and has never run a discovery workshop. The stronger question is narrower: who, by name, will do this work, and can those individuals’ credentials be checked?
Salesforce maintains a public credential verification tool through Trailhead, so you can confirm claimed certifications rather than taking a slide deck’s word for it. Ask for names in the proposal, not after the contract.
Who attended the pitch, and who will actually deliver?
This is the single most common source of post-signature disappointment in IT services. The people who impressed you in the sales cycle are often not the people who show up on Monday morning. Ask directly: what percentage of the delivery team was in the room during the pitch, and will the named leads stay on the account for the full engagement?
Get the answer in writing, including what happens if a named consultant leaves mid-project.
Delivery and Technical Questions
How do you decide between declarative configuration and custom code?
Salesforce’s own guidance favours declarative configuration (the “clicks not code” approach) wherever it can meet the requirement, reserving Apex and custom development for genuine gaps. That principle is easy to state and harder to follow, because custom builds are often more billable than configuration.
Ask the firm to walk through a recent example where they chose configuration over custom code, and one where they concluded custom development was unavoidable. Then ask them to justify it. A consultancy that can explain the trade-off in plain language, without hiding behind jargon, is usually the one you want.
How do you handle the three releases a year?
Salesforce ships Spring, Summer, and Winter releases, and the cadence has held at three per year for many years. Each release can affect custom code, integrations, and third-party packages. Ask how the firm manages release readiness: what sandbox strategy they use, whether regression testing is included in the support agreement or billed separately, and who monitors release notes on your behalf.
Watch for the answer “we handle it.” Push for specifics: which sandboxes, which test coverage, which named person owns the check.
What is your sandbox and deployment strategy?
A full sandbox, a partial sandbox, and a developer sandbox serve different purposes, and a firm that deploys straight to production is a firm to avoid. Ask how many sandboxes they will provision, who pays for them, and how deployment is executed. This is also a good moment to ask about DevOps tooling and version control, because a consultancy without a deployment discipline will eventually overwrite something you care about.
How will you define and measure success?
Salesforce’s own implementation guidance recommends a phased approach with clear business objectives and success metrics agreed before build begins. Turn that into a question: what does success look like at 30, 60, and 90 days after go-live, and who signs off on each milestone?
If the answer is a list of features delivered rather than outcomes achieved, you are buying activity rather than results. Buyers who think carefully about specifications in other technical purchases will recognise the pattern; the discipline of reading a Rillabox review before ordering rests on the same principle of matching claims to measurable outcomes.
Data, Security, and Accessibility Questions
Will you sign a data processing agreement, and where will data be hosted?
Under GDPR Article 28, a processor relationship requires a written contract governing the processing. Ask whether the firm will sign a data processing agreement as standard, where data will be hosted, whether any sub-processors are involved, and how they handle deletion at the end of the engagement. If you operate in the UK, ask separately about UK GDPR handling.
The same instinct applies to any AI features layered onto your CRM. Buyers evaluating AI chatbot security with 9 questions to ask before buying will find the questions familiar: data residency, sub-processors, retention, and who can access what.
How do you test accessibility?
Accessibility is a legal requirement in many jurisdictions. WCAG 2.2 became a W3C Recommendation on 5 October 2023 and is the common benchmark. The EU Web Accessibility Directive (Directive (EU) 2016/2102) and the European Accessibility Act (Directive (EU) 2019/882), with member-state application from 28 June 2025, create obligations for many organisations.
Ask how the firm tests: automated scans alone, or manual testing with assistive technology? Automated tools catch a fraction of real barriers. A firm that only runs a scanner is not testing accessibility; it is generating a report.
Contract and Commercial Questions
Fixed price or time and materials, and how do change requests work?
Both models are legitimate; the danger is an unclear one. Ask which model applies, what is explicitly in scope, and what the change-request process looks like when scope shifts. Get the hourly rates for change requests in the contract, not in a later email.
A useful comparison of what to pin down:
| Question | Weak answer | Strong answer |
|---|---|---|
| Pricing model | “It depends” | Named model with rates for changes |
| Scope | Feature list only | Outcomes plus exclusions |
| Change requests | Handled case by case | Written process with rates |
| Post-go-live support | Not discussed | Warranty period plus support terms |
| Exit and handover | Not mentioned | Documented transition plan |
Who owns the custom code, and what happens after go-live?
Ask about IP ownership of anything built specifically for you, the warranty period after go-live, and what support costs once the warranty ends. Then ask the question many buyers forget: what does exit look like? A firm that can describe a clean handover, including documentation and knowledge transfer, is usually confident in its own work.
Can I speak to references on comparable projects?
Ask for references at similar scope and organisation size, and ask those references what went wrong as well as what went right. Every project has friction; a firm whose references admit to friction and describe how it was resolved is more credible than one whose references are uniformly glowing.
Conclusion
Hiring a Salesforce consulting company is a test of whether you can see past the pitch. The firms worth your money will answer these questions directly, name their people, verify their credentials, and put uncomfortable details like change-request rates and exit terms in writing. The ones that deflect are telling you exactly how the project will feel six months from now.
Ask about tier, names, certifications, configuration philosophy, release readiness, data processing, accessibility testing, contract structure, IP, and exit. Then compare the answers side by side rather than in sequence, because the contrast between firms is where the real information lives. Whether you are weighing a major CRM engagement or something smaller, the habit of asking before signing is the same one that makes a Fidelity money market funds review worth reading before committing savings: verify the terms, understand the trade-offs, and never let a good presentation substitute for a good contract.
FAQ
How many Salesforce certifications should a consulting firm have?
There is no reliable benchmark, and certification counts are a weak proxy for quality. A firm with fifty badges and a junior delivery team is worse than a firm with twelve badges held by the exact people doing your work. Ask for named consultants and verify those individuals through Salesforce’s public credential check instead of counting logos.
Is a larger consulting partner always the safer choice?
No. Large systems integrators bring bench strength and process maturity but often assign senior people to sales and junior people to delivery. Boutique firms frequently offer senior-only teams but limited capacity and thinner coverage during holidays. Match the firm’s shape to your project’s complexity rather than to its headcount.
What should a data processing agreement cover?
At minimum: the subject matter and duration of processing, the nature and purpose, the categories of personal data, the obligations of both parties, and the sub-processors involved. Under GDPR Article 28 the agreement must be in writing. Ask where data is hosted and how deletion works at the end of the engagement.
How do I check whether a consultant’s certification is real?
Salesforce maintains a public credential verification tool through Trailhead. Ask the firm for the full names of the consultants assigned to your project, then verify each claimed certification yourself. It takes minutes and eliminates an entire category of misrepresentation.
Should I insist on fixed-price contracts?
Not necessarily. Fixed price suits well-defined scope; time and materials suits exploratory work where requirements will evolve. The real safeguard is a written change-request process with named rates, agreed before work begins, so that scope shifts are priced transparently rather than negotiated under pressure.
What happens to my Salesforce customisations when a new release ships?
Salesforce ships three releases a year, and each can affect custom code, integrations, and third-party packages. Ask your consultancy how they monitor release notes, which sandboxes they use for regression testing, and whether that testing is included in support or billed separately. Get the answer in the contract.


