How to Choose a Salesforce Implementation Partner: 15 Questions to Ask Before You Sign

Choosing the wrong Salesforce implementation partner is one of the most expensive mistakes a business can make. A failed implementation doesn’t just waste the consulting fees — it wastes the license costs, the internal team’s time, and the opportunity cost of months spent on a system that doesn’t work.

We’ve seen companies spend $200,000 on an implementation that had to be completely redone. We’ve also seen $30,000 implementations that transformed a business. The difference almost always comes down to the partner.

Here are the 15 questions that separate great partners from expensive disappointments.

Key Takeaways

Certifications alone don’t predict success — ask about methodology and references
The discovery phase is the most important part of any implementation. Skip it, and you’re gambling
Beware fixed-bid pricing without thorough scoping — it usually means corners will be cut
The best partners tell you what you don’t want to hear, not just what closes the deal
Always talk to references, and ask specifically about what went wrong

Questions About Experience and Fit

1. What percentage of your business is Salesforce?

This matters more than you’d think. A firm that does 20% Salesforce and 80% other platforms will have Salesforce as a side skill, not a core competency. Their best people are likely on their primary platform.

What you want to hear: 80–100% of revenue from Salesforce work. This means their entire team, hiring pipeline, and training investment is focused on the platform you’re buying.

Red flag: “We do Salesforce, SAP, Oracle, Dynamics, and HubSpot.” Jack of all trades, master of none.

2. Have you implemented Salesforce for companies in our industry?

Industry experience isn’t just a nice-to-have — it directly reduces risk, cost, and timeline. A partner who has done five healthcare implementations knows HIPAA requirements, common integration patterns with EHR systems, and the specific workflows that healthcare organizations need. They won’t need to learn on your dime.

What you want to hear: Specific examples with similar company size and industry, along with the challenges they encountered and how they solved them.

Red flag: “Every implementation is unique, so industry experience doesn’t really matter.” Translation: they don’t have it.

3. Who will actually be doing the work?

Many firms sell with senior consultants and deliver with junior ones. The person in the sales pitch should be the person (or at least the team lead) on your project.

What you want to hear: “Here’s the architect who will lead your project, and here are the consultants who will do the configuration. You can meet them before signing.”

Red flag: “We’ll assign the right team once the contract is signed.” You may never see the people from the pitch again.

4. What Salesforce certifications does your team hold?

Certifications aren’t everything, but they establish a baseline. For a standard implementation, your team should include at minimum a Salesforce Certified Administrator, a Platform App Builder, and ideally a Solution Architect for projects over $75,000.

What you want to hear: Specific certifications held by the people on your project, not the firm’s total certification count.

Red flag: Citing the company’s total certification count across all employees globally. Your project doesn’t benefit from certifications held by people in a different office working on different projects.

Questions About Process and Methodology

5. Walk me through your discovery phase. How long is it and what does it produce?

Discovery is where good implementations are won or lost. A proper discovery phase takes 2–6 weeks (depending on complexity) and produces a detailed solution design document, data model, integration architecture, and project plan.

What you want to hear: A structured process with defined outputs — not a vague “we’ll figure it out as we go.”

Red flag: “We can skip discovery to save you money and start building right away.” This is how $100,000 projects become $200,000 projects.

6. How do you handle scope changes?

Every implementation encounters scope changes. The question is whether the partner has a mature process for managing them — or whether every change becomes a budget battle.

What you want to hear: A change request process with clear documentation, impact assessment (timeline and cost), and client approval before work begins.

Red flag: “Our contracts are fixed-scope, fixed-price.” Sounds great until you realize that “fixed” means they’ll deliver exactly what was scoped — even when you discover mid-project that the scope was wrong.

7. What does your testing process look like?

Testing should not be a checkbox at the end. A serious partner tests throughout the build: unit testing during configuration, integration testing when connecting systems, user acceptance testing with your team, and regression testing before go-live.

What you want to hear: A multi-stage testing plan with your team involved at the UAT stage. Specific mention of test scripts, data validation, and go/no-go criteria.

Red flag: “We test everything before we hand it over.” If your team hasn’t tested it in a realistic environment before go-live, you will find problems in production.

Questions About Support and Accountability

8. What happens after go-live?

The first 2–4 weeks after launch are when most issues surface. A good partner provides a hypercare period — dedicated support with fast response times to fix issues, answer questions, and make adjustments.

What you want to hear: A defined hypercare period (2–4 weeks minimum) included in the project scope, with specific SLAs on response time.

Red flag: “Our contract ends at go-live. We can discuss a support agreement separately.” This means you’ll be on your own when things break.

9. Can I talk to three recent clients — including one where things didn’t go as planned?

Any firm can give you their happiest client. The revealing references are the ones where challenges occurred. How the partner handled adversity tells you everything about what it’s like to work with them.

What you want to hear: Willingness to connect you with references, including honest acknowledgment that not every project is perfect.

Red flag: Reluctance to provide references, or providing only a scripted list of hand-picked advocates.

10. What is your team’s average tenure, and what’s your turnover rate?

Staff turnover kills projects. If the architect who designed your solution leaves mid-implementation, you’ll lose weeks to knowledge transfer — and the replacement may make different design decisions.

What you want to hear: Low turnover, long average tenure, and a knowledge management process that ensures continuity even if someone leaves.

Red flag: “We have a large bench of consultants.” Large bench often means high turnover and heavy use of subcontractors.

Questions About Cost and Value

11. How do you structure pricing?

The three common models are time-and-materials (T&M), fixed-price, and hybrid. Each has tradeoffs:

T&M: You pay for actual hours worked. Most flexible but requires trust and active project management.
Fixed-price: Total cost is agreed upfront. Seems safe but often leads to cutting corners or aggressive change order billing.
Hybrid: Fixed-price for well-defined phases (discovery, data migration), T&M for less predictable work (custom development, integrations).

What you want to hear: A thoughtful explanation of why they recommend a particular pricing model for your project, with transparency about the tradeoffs.

Red flag: Fixed-price proposals delivered before a discovery phase. If they haven’t studied your requirements, they’re either padding the price or planning to cut scope.

12. What does a typical project of our size and complexity cost?

A good partner will give you a range based on experience — not dodge the question. If they’ve done similar projects, they know the ballpark.

What you want to hear: “Based on what you’ve described, similar projects have ranged from $X to $Y. A discovery phase will narrow that range significantly.”

Red flag: Refusal to provide any estimate, or a suspiciously low number designed to win the deal.

13. What’s not included in your proposal?

The items excluded from a proposal often matter as much as what’s included. Common exclusions that surprise clients: data migration, user training, post-launch support, third-party app configuration, and Salesforce license procurement.

What you want to hear: A clear list of exclusions with explanations of what those items would cost if you decide to include them.

Red flag: A vague proposal with no explicit exclusions list. If everything seems included at a low price, something is missing.

Questions About Long-Term Fit

14. How do you transfer knowledge to our internal team?

A great partner doesn’t create dependency — they build your team’s capability. By the end of the project, your admin should understand how the system was built, why design decisions were made, and how to make common changes.

What you want to hear: Documentation deliverables, admin training sessions, and recorded walkthroughs included in the project plan.

Red flag: “We’ll handle everything — you don’t need to worry about the technical details.” This creates vendor lock-in.

This is the most revealing question you can ask. A partner who tells you to scale back your initial scope, phase the project, or skip an expensive add-on that you don’t need yet is a partner who prioritizes your success over their revenue.

What you want to hear: Specific recommendations to simplify, phase, or defer features — with reasoning tied to your business goals and budget.

Red flag: Agreement with everything on your wish list and encouragement to do it all at once. The more complex the initial project, the higher the risk of failure — and the larger the consulting bill.

How Boutique Firms Compare to Big Consultancies

For mid-market companies (25–500 employees), boutique Salesforce firms often outperform large consultancies like Deloitte, Accenture, or Wipro. Here’s why:

Senior attention: At a boutique firm, your project gets senior architects. At a large firm, seniors sell the project and juniors deliver it.

Speed: Boutique firms have less overhead, fewer approval layers, and faster decision-making. A change that takes a week at a large firm takes a day at a boutique.

Cost: Large firms charge $250–$400/hour. Boutique firms typically charge $150–$250/hour — with more experienced people on the project.

Flexibility: Boutique firms adapt their methodology to your needs. Large firms apply their standardized methodology regardless of fit.

The exception: if you need 50+ consultants working simultaneously on a global rollout, you need a large firm’s scale. For everything else, a specialized boutique often delivers better results at lower cost.

The Bottom Line

The right Salesforce partner will feel like an extension of your team — transparent, responsive, and genuinely invested in your success. The wrong partner will feel like a vendor — defensive about scope, slow to communicate, and focused on billing.

Ask these 15 questions, talk to references, and trust your gut. The discovery phase should feel like a collaboration, not a sales pitch. If it doesn’t, keep looking.

Estarei is a boutique Salesforce consulting firm built by ex-Salesforce alumni. We welcome all 15 of these questions — and we’ll give you straight answers. Browse our case studies to see our work, then book a free consultation to see if we’re the right fit.