How to Evaluate a Salesforce System Integrator: The Checklist That Actually Works

The process most companies use to select a Salesforce SI is broken. They shortlist three firms from a Google search, sit through polished presentations, pick the one that gave them the best vibe, and then wonder six months later why the project is over budget and under-delivered.

A better process is available. It takes a little more time upfront and saves a significant amount of pain downstream. This is the checklist — not a list of interview questions, but a structured evaluation methodology for reading what partners actually are, not what they claim to be.

Step One: Read the AppExchange Listing Like an Auditor, Not a Buyer

Every Salesforce consulting partner has an AppExchange profile. Most buyers skim it for the star rating and move on. Here’s how to extract the signal from it.

Certifications: Depth Over Breadth

The certification count on an AppExchange listing is a vanity metric. A firm with 300 total Salesforce certifications sounds impressive until you learn that 240 of them are Salesforce Administrator or Platform App Builder — entry-level credentials that any practitioner has. What matters is the depth of advanced certifications in the clouds and use cases relevant to your project.

If you’re implementing CPQ, look for Salesforce Certified CPQ Specialists. If you’re implementing Service Cloud with Field Service, look for Field Service Consultants. If you’re in financial services, look for the Financial Services Cloud accreditation. Count those specific credentials, then ask how many of those certified people will actually be staffed on your project. “We have 12 CPQ Specialists” means very little if 11 of them are on other accounts.

The certifications that indicate real program leadership capability: Salesforce Certified Technical Architect (CTA) and Application Architect. There are roughly 6,000 CTAs globally out of hundreds of thousands of certified professionals. A firm with one or more CTAs on staff has people who have passed one of the hardest certification programs in enterprise software.

Reviews: Volume, Recency, and the Middle Range

A 4.9/5.0 with 8 reviews is statistically meaningless. AppExchange reviews are submitted by customers the SI self-selects to invite. The sample is biased toward satisfied clients and recent happy engagements.

Look for: firms with 30+ reviews, a consistent pattern over the last 24 months (not all clustered in one quarter), and the text of 3- and 4-star reviews. Four-star reviews from happy clients often reveal the real friction — “great technical work but project management was disorganized” or “the implementation was solid but they underestimated the data migration.” That texture tells you more than any five-star testimonial.

Also note: if a firm has 100 reviews from two years ago and a handful in the last 12 months, they may be in decline. Delivery quality and staffing are correlated over time; review volume reflects delivery volume.

Specializations: The Signal That’s Hard to Fake

Salesforce awards product and industry Consulting Specializations to partners who demonstrate: a minimum number of completed projects, a minimum number of certified headcount in that area, and customer CSAT evidence from those projects. Specializations in Manufacturing, Financial Services, Health and Life Sciences, or specific product areas (Revenue Cloud, Marketing Cloud) are meaningful because they require documented proof, not self-assertion.

A partner claiming deep Revenue Cloud expertise without a Revenue Cloud Specialization should be asked to explain why. The most common reason is that they don’t have enough completed Revenue Cloud projects to qualify — which is exactly what you need to know if Revenue Cloud is your priority.

Step Two: Interpret Partner Tiers Correctly

Salesforce’s partner tiers (Registered, Silver, Gold, Platinum, Global Strategic) are based primarily on three factors: the number of certified employees, the amount of Salesforce ARR sold through the partner channel, and customer success metrics. They are not a quality ranking.

A Platinum partner is a large firm that moves a lot of Salesforce licenses and employs many certified people. That says nothing about whether their mid-market implementation team is any good, whether the senior consultant you meet will be on your account, or whether their delivery methodology is sound.

Use partner tier as a rough proxy for firm size and the range of engagements they can handle, not as a quality indicator. A Gold partner with 45 consultants and deep Revenue Cloud experience will almost always deliver a better Revenue Cloud implementation than a Platinum partner who treats it as one of 30 clouds their practice covers.

The minimum useful signal from tier: don’t work with a Registered partner for a complex implementation. Registered status requires very little from a firm — it’s essentially just having a Salesforce business relationship. Silver and above indicates at least some threshold of certified headcount and customer success history.

Step Three: Distinguish True SIs from Staff Augmentation Firms

This distinction is underappreciated and critically important. Many companies that list themselves as Salesforce consulting partners are functionally staff augmentation firms — they provide individual certified contractors who embed in your team and work under your direction. They are not System Integrators in the traditional sense.

A true SI takes end-to-end delivery responsibility. They scope the work, design the solution, manage the project, deliver the build, and stand behind the outcome. When something goes wrong, they fix it. Their revenue model is based on delivering complete implementations, not filling hourly contractor seats.

A staff augmentation firm provides bodies. If your Salesforce architect leaves mid-project, they provide another architect. They don’t own the outcome; they own the resource supply.

Neither model is wrong, but they address very different needs. If you have strong internal project management and a Salesforce team that can provide direction, staff aug may be efficient. If you need someone to own delivery from discovery through go-live, you need an SI, not a staffing firm.

The test: ask the firm to describe their delivery methodology. A true SI can articulate a repeatable approach — discovery, design, build, test, deploy, hypercare — with defined roles, standard artifacts, and a project management structure they own. A staff aug firm will describe their resource quality and how fast they can place people. Both are valid answers; they’re just different businesses.

Step Four: Red Flags in Proposals

The Suspiciously Fast Fixed-Price Bid

A fixed-price proposal that arrives within 72 hours of your RFP almost certainly contains a contingency buffer of 30–40% to protect the SI against scope they didn’t have time to assess. A thorough scope assessment takes 2–4 weeks for a mid-market implementation — it involves reviewing your existing systems, your data model, your integration landscape, your internal readiness, and your business processes. Firms that skip this step aren’t more efficient; they’re just guessing, and they’re protecting themselves from their own guess.

A proposal built on insufficient discovery will either blow scope or be packed with change order triggers. Ask any fixed-price bidder: “What assumptions are embedded in this price, and what triggers a change order?” If the answer is long, that’s your actual contract risk.

Vague Staffing Commitments

Any proposal that lists roles without naming specific individuals or without committing to a minimum experience level for each role is a staffing risk. “Senior Consultant” can mean five years of Salesforce experience or 18 months. “Offshore resources” can mean highly competent practitioners or can mean junior staff billing at premium rates.

Request a staffing plan that includes: named individuals for project manager, lead architect, and lead developer; years of Salesforce experience for each named person; their current availability and what they’d be rolling off of to start your project; and a policy for what happens if a named person leaves the firm or rolls to another account mid-engagement.

Pricing That Doesn’t Reflect Your Risk Profile

Implementation proposals are priced based on the SI’s risk tolerance as much as the actual scope. A proposal with no contingency line item is either very confident in the scope or is planning to recover margin through change orders. A proposal with a 25% contingency line is honest about scope uncertainty. Neither is inherently wrong — but they reflect different things, and you should understand which you’re looking at.

No Discovery Phase Proposed

Any legitimate SI implementation for a mid-market company should begin with a paid discovery or design phase (typically 4–8 weeks, $15K–$50K) before committing to a full implementation scope and price. Firms that skip this and jump straight to an end-to-end implementation proposal are either pattern-matching from similar projects (which may or may not apply to your situation) or are avoiding the cost of discovery by baking those assumptions into their risk margin.

Step Five: Structure a Paid Discovery to De-Risk the Selection

Even after a thorough evaluation, the best way to de-risk an SI selection is to begin the relationship with a bounded, paid discovery engagement before committing to a full implementation. Here’s why it works.

A paid discovery (sometimes called a design sprint, discovery workshop, or requirements phase) is typically 4–6 weeks and costs $15K–$60K depending on firm size and scope complexity. It produces: a current-state assessment of your systems and processes, a documented future-state design with Salesforce configuration recommendations, a data migration assessment, an integration architecture, a project plan with timeline and resource requirements, and a refined implementation quote based on actual scope rather than assumptions.

At the end of discovery, you’ve accomplished three things: you have a real scope document, not assumptions; you’ve seen how the firm thinks and communicates; and you’ve worked with the actual people who will deliver the implementation, not just the sales team. If you don’t like what you see during discovery, you’ve spent $30K to avoid a $300K mistake.

Some firms resist paid discovery because they prefer the simpler sell of going straight to an implementation contract. That resistance is a mild red flag — an SI confident in their discovery process should be comfortable standing behind it for a modest fee.

Step Six: The Reference Call Script

Reference checks are almost always perfunctory. The candidate gives you a list of three happy clients, you call them, they say positive things, you feel validated. Here are three questions that cut through that pattern:

“Describe a moment in the project when something went wrong. How did the SI handle it?” Every real implementation has problems. A reference that can’t describe any problems either had a very small implementation or isn’t being candid. The answer to this question tells you more about the SI’s integrity and escalation behavior than any positive reference.

“Was your project delivered on time and on budget? If not, how did the SI communicate the variance, and how was it resolved?” You want the actual numbers, not “generally on track.” Projects that ran 20% over budget with clear communication and mutual accountability are acceptable. Projects that ran 20% over budget because the SI kept the client in the dark until month 8 are not.

“Would you hire this SI again for a different Salesforce project, and if yes, is there anything you’d do differently in the engagement structure?” The second part of that question is the important one. References who say “yes, absolutely, no changes” are either very satisfied or being polite. References who say “yes, but I’d push for more documentation” or “yes, but I’d demand a weekly executive check-in” are giving you actionable information about how to structure your own engagement.

Putting It Together

A thorough SI evaluation takes 3–4 weeks, not 3–4 days. The difference in outcome — the quality of implementation you get, the accuracy of your budget, the likelihood of a successful go-live — justifies the time.

The shortcut most buyers take is optimizing for the sales experience. The firms that are best at selling aren’t always the firms that are best at delivering. Build your evaluation process around delivery evidence — certifications in the right areas, reviews with honest texture, named staff with verifiable experience, a discovery process you can assess before committing — and you’ll make a better selection.

---

Estarei is a boutique Salesforce consulting firm built by ex-Salesforce employees. Every engagement starts with a structured discovery that produces a real scope before we commit to a price. If you’re evaluating implementation partners, book a free consultation and we’ll tell you exactly what you should be asking everyone on your shortlist.