How to choose a Salesforce consulting partner
Choose the partner that has delivered the clouds you are buying for companies like yours, names the people who will do the work, and scopes your project in writing before quoting a price. Score every finalist on the same criteria, weighted toward what makes your project hard, so the decision rests on evidence rather than on the best presentation.
What good looks like
5: Has delivered Salesforce for companies like yours and can walk through the processes, data and regulations specific to your industry.
1: Generic experience; cannot describe how companies in your industry sell, serve or report.
What good looks like
5: Recent projects on the exact clouds and add-ons you are buying, with examples of what they built.
1: Strong in one cloud, learning the others on your project.
What good looks like
5: Names the consultants who will be on your project, their roles, certifications and location, and keeps them through go-live.
1: A senior team sells the deal; the delivery team is unnamed or changes after signature.
What good looks like
5: Asks detailed questions about your processes, users and data before quoting, and puts the scope in writing.
1: Offers a price after one call, with a scope that could apply to any company.
What good looks like
5: Explains how data will be cleaned, mapped, loaded and reconciled, and how each integration will be designed and tested.
1: Treats migration as a one-line item and integrations as "we will connect it."
What good looks like
5: Plans role-based training and says how adoption will be measured after launch.
1: One all-hands demo at the end of the project.
What good looks like
5: Clear hypercare period and a defined option for ongoing support or managed services.
1: Support after launch is undefined or billed ad hoc with no response expectations.
What good looks like
5: Pricing model, assumptions and change-order process are written down and easy to understand.
1: Vague assumptions that are likely to turn into change orders.
What good looks like
5: Case studies and references you can actually talk to, in situations similar to yours.
1: Logos and claims without detail, or no references available.
Runs in your browser. Nothing you enter is sent anywhere.
How to use the scorecard
- Set weights before the first meeting. Decide what matters most while no partner has impressed you yet. Keep the total at 100.
- Ask every partner the same questions. Use the "what good looks like" notes to plan them, and ask each partner to answer in writing where you can.
- Score separately, then compare. Have two or three people score on their own, then discuss the criteria where your scores differ most.
- Check the proof. Speak to references and read case studies before final scores. A 5 on proof means you verified it.
Scorecard questions
How should we weight the criteria?
Start with the defaults, then move weight toward what makes your project hard. If you are migrating years of data from several systems, raise data migration. If your industry is regulated or unusual, raise industry experience. Keep the total at 100 so scores stay comparable.
Who should score the partners?
Two or three people who sat in every partner meeting: usually the project owner, someone from the team that will use Salesforce most, and someone from IT or operations. Score separately first, then compare and discuss the biggest differences.
Is the highest score always the right choice?
Not always. Use the scorecard to make trade-offs visible. A partner that scores slightly lower overall but much higher on the criterion that matters most to your project can be the better choice.
Is my scoring saved or sent anywhere?
No. The scorecard runs entirely in your browser. Nothing you enter is sent to us or stored on our servers. Use the print button to keep a copy.
Salesforce partner vs. freelancer → Salesforce implementation guide → Our implementation approach →