The Short Answer
Choosing a Salesforce implementation partner often falls into one of two dangerous traps: being impressed by a dazzling demo during a sales meeting, or simply comparing prices between seemingly similar proposals. Neither method truly assesses what determines success – does the vendor understand your business process, how do they handle exceptions, and what happens when something goes wrong in the third week of the project?
A mature selection process sequentially evaluates four key areas: defining your internal needs before approaching the market, identifying the right type of vendor for your scope and risk tolerance, assessing professional depth beyond a mere demo, and structuring an engagement model that fairly distributes risk. We've extensively covered how to compare bids and terms in Comparing Salesforce Proposals; here, the focus is on the preceding step – how to even arrive at a worthy list of candidates.
Step One: What You Actually Need Before Going to Market
The most common mistake is asking vendors "How much does it cost?" before defining what "it" even is. A company that starts a procurement process without a written scope receives proposals that are impossible to compare, as each vendor fills in the gaps with their own assumptions. Before the first meeting, have a brief document outlining: the business process requiring change, who the users are, current systems in place, and what success will look like in six months.
This scope inherently dictates the appropriate pricing model – a project with a clear scope is better suited for a fixed price, while an exploratory project fits a Time & Material approach. We've detailed this in Salesforce Project Pricing Models. Organizations that skip the definition phase almost always pay for it twice: once with an inflated quote covering uncertainty, and again with scope changes mid-project.
Vendor Types: Boutique, Global, and Freelance
The Israeli market for Salesforce services broadly divides into three categories, each suitable for a different risk profile.
Boutique firms typically comprise 5 to 30 employees, specialize in one or two areas (Sales, Service, Marketing Cloud), and provide direct access to a senior architect throughout the project. Their advantage is agility and competitive pricing; the drawback is limited capacity – a large project requiring five people simultaneously might get stuck in a queue.
Global integrators bring documented methodologies, rapid scaling capabilities for additional personnel, and experience from similar sectors worldwide. Their pricing is 30-60 percent higher than boutique firms, and often there's a project management layer separating the client from the actual execution team – which can slow communication during a crisis.
Freelancers offer the lowest hourly rates but expose you to single-person dependency. If the freelancer falls ill, travels abroad, or moves to another project, work grinds to a halt. Best suited for ongoing maintenance or small projects with a defined and contained scope.
Assessing Professional Depth Beyond a Demo
An impressive demo proves the vendor knows how to showcase Salesforce, not that they can solve your organization's specific problem. True in-depth assessment requires three layers: First, request that the actual project execution team (not just sales personnel) participate in the meeting and answer technical questions. Second, ask for a concrete example of a similar project in scope and industry, including real screenshots, not marketing slides. Third, observe how the vendor responds to a trick question – for instance, "What happens if, mid-project, we discover the source data is unreliable?" An experienced vendor will respond with an example, not a platitude.
The individual actually leading the architecture determines the quality of the solution far more than the logo on the invoice. It's crucial to ensure that the architect presented in the sales meeting is indeed the person who will be involved in the project, and not a "face" shown to clients who is then replaced by a more junior team after signing.
Checking Actual References
A good reference call goes beyond "Would you recommend them?" and delves into operational details. Three questions that yield real information: Was the project completed within the original budget and timeline, and if not, what was the deviation and its cause? What happened when a mistake or bug was found in production, and how long did it take to fix? And, is the team that executed the project still employed by the vendor today? High employee turnover at an implementation company indicates that the knowledge gained from previous projects is no longer available.
It's advisable to request at least two references: one from a successful project and one from a project that encountered difficulties. A vendor who refuses to provide a "problematic" reference or claims all their projects were flawlessly successful is likely hiding something.
Engagement Model: How to Share the Risk
The engagement model determines who bears the risk when reality deviates from the plan – which happens almost always.
| Model | When Suitable | Primary Risk |
|---|---|---|
| Open Time & Material | Immature scope, Discovery phase | Exceeding hours without a cap |
| T&M with Cap | Partial scope, first project with vendor | Requires ongoing monitoring against cap |
| Fixed Price | Well-defined and documented scope | Vendor might cut corners to maintain margin |
| Monthly Retainer | Ongoing maintenance and support | Actual work volume doesn't always match payment |
For a first project with a new vendor, a T&M with cap model is often the most balanced choice: it prevents budgetary surprises but doesn't incentivize the vendor to cut corners on testing. Consider moving to a fixed price only after the scope has been validated against real end-to-end scenarios, as described in Choosing a Salesforce Vendor.
Vendor Scoring Scorecard
A weighted scoring table transforms subjective comparison into a process that can be defended to management. Suggested weights for a typical project:
| Criterion | Weight | What to Actually Check |
|---|---|---|
| Experience Match to Industry & Process | 25% | Similar projects in scope and sector, not just a recognized logo |
| Depth of Proposed Team | 20% | Tenure and actual role of architect and developers |
| Quality of Proposal & Scope | 20% | Detailed WBS, assumptions, exclusions, and written acceptance deliverables |
| References & Employee Turnover | 15% | Direct conversations with past clients |
| Engagement Model & Contractual Fairness | 10% | Reasonable risk distribution, not just low price |
| Cultural Fit & Communication Availability | 10% | Response time, language, time zone, and update frequency |
Each vendor receives a score of 1-5 for each row, multiplied by the weight. The gap between the leading vendor and the second is as important as the score itself – a gap of less than 5 points usually warrants an additional clarification meeting before a final decision.
Red Flags to Identify Early
- A quote without detailed hours by topic, only a global "total"
- Promising a "complete Salesforce solution" for a need never deeply investigated
- Refusing to reveal who on the team will actually perform the work
- Pressure to sign quickly "because this price is only valid this week"
- No reference to a failed case or a project that had difficulties
- A contract that doesn't define what constitutes project "completion" and final acceptance
What to Ask to See in a Meeting: A Short Checklist
- ☐ Presence of the actual execution team, not just a salesperson
- ☐ Concrete example of a similar project with real screenshots
- ☐ Preliminary WBS detailing assumptions and written exclusions
- ☐ Name and contact information for at least two references
- ☐ Proposed engagement model with an explanation for its suitability to the scope
- ☐ Description of the process for handling scope changes and post-launch bugs
Example Organizational Scenario
A medium-sized financial services company evaluated three proposals for Salesforce Sales Cloud: a local boutique, a global integrator, and a highly recommended freelancer. Management initially leaned towards the freelancer due to a 40 percent lower price, until a reference call revealed that his previous project was halted for three weeks when he fell ill. The organization ultimately chose the boutique, after the scorecard showed a 12-point advantage in the "team depth" and "low employee turnover" categories.
The project indeed encountered a mid-course requirement change – a new need for integration with an internal billing system not mentioned in the proposal phase. Thanks to the T&M with cap model, the change was handled as a pre-agreed addition rather than a renegotiation of the entire contract. Organizations deliberating between similar vendors and seeking additional question frameworks can utilize Questions Before Choosing a Salesforce Integrator.
How to Measure if the Choice Was Correct
| Metric | What to Check | When to Check |
|---|---|---|
| Adherence to Timeline | Deviation in days between plan and actual execution | At each milestone |
| Team Stability | Did the same people accompany the project to completion? | At the end of each phase |
| Handling Exceptions | Response time for a bug or requirement change | Throughout the project |
| Documentation Quality | Can maintenance be handed over to another team without single-person dependency? | Upon delivery |
A metric that cannot be practically checked is not a metric. If the contract doesn't include a clear definition of what constitutes project "completion," it's almost impossible to know if the choice was correct until it's too late to fix. An organization seeking external guidance in building its selection process can start with Consulting & Discovery Services, which helps define scope and build a tailored scorecard even before going to market.
Professional Resources
- HPI Pro – Consulting & Discovery — https://hpi.pro/consulting-discovery
- Salesforce Well-Architected — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
- HPI Pro – Salesforce Services — https://hpi.pro/services