Integration Services
Business Consulting & Advisory
AI Solutions
AppExchange Development
Tailored Salesforce Engineering
Managed Services
Implementation
Executive Summary
- The problem: search for a Salesforce implementation partner and every “how to choose” guide online is written by one, including this one. That structure predicts self-ranking advice, criteria that flatter the author, and tier recommendations that conveniently match whatever tier the author holds.
- Our answer: we publish the full evaluation scorecard and red-flag list first then score ourselves against it in public, including where the honest answer routes you to a competitor.
- What changed in March 2026: Salesforce cut its partner program from four tiers to two (Select, Summit) and its badge system from roughly 170 badges to 28 verified competencies. Summit now requires proven outcomes, not accumulated certifications. Firms still marketing “Gold” or “Platinum” haven’t updated their positioning in months.
- The buyer mistakes this guide prevents: treating tier as a single ranking instead of matching partner profile to project shape. A well-scoped single-cloud rollout often doesn’t need or benefit from a Summit partner at all.
- Your first move: take the seven-area scorecard in this guide into your RFP as the evaluation sheet, before you take a single sales call.
Try the search for yourself. Every guide on the page is written by a firm that implements Salesforce. That’s just how the category works.
But it has a predictable effect. Criteria lists flatter their authors. Tier advice tends to land, coincidentally, on whatever tier the author holds. And the buyer reading the guide has no way to tell where genuine advice ends, and quiet self-interest begins.
This guide is written by Achieva, a Salesforce implementation partner. We’re naming that upfront because it’s the only way the rest of this guide can be trusted.
Table of Content
- What Does a Salesforce Implementation Partner Do?
- What Changed in Salesforce’s 2026 Partner Program?
- Which Type of Salesforce Implementation Partner Fits Your Project?
- How Do You Score a Salesforce Implementation Partner?
- What Are the Red Flags and What Really Causes Implementations to Fail?
- How Do You Evaluate a Salesforce Integration Partner?
- What Does Cost, Engagement Model, and Good Process Look Like?
- How Does Achieva Score Against Its Own Rubric?
- Frequently Asked Questions
Here’s what we do differently, concretely:
- We publish the complete evaluation scorecard before we mention ourselves anywhere in the piece.
- We include the red flags that could disqualify us, not just ones that flatter us.
- We score Achieva against our own rubric in Section 9, weaknesses and routing elsewhere included.
- We tell you directly when a smaller, less expensive partner is the better fit for your project, even though that costs us the sale.
If you’re a RevOps leader, sales or service operations executive, CIO, or a procurement team evaluating Salesforce implementation partners for a new deployment or a stalled rescue, here’s what follows: the roles buyers confuse, the 2026 partner program decoded with verified currency, a routing table matched to your specific project, and a scorecard built to be copied straight into your RFP all before a single word of pitch.
What Does a Salesforce Implementation Partner Do?
A Salesforce implementation partner delivers the whole working system, including configuration, migration, integrations, training, and go-live. Consultants advise on strategy; developers build inside someone else’s plan; staff augmentation is a different purchase entirely. Most buyers need the first role.
The market blurs four distinct roles constantly, and that blur costs buyers money before a project even starts, usually by buying the wrong type of help for the actual problem.
| Role | What They Own | When You Buy It |
|---|---|---|
|
Implementation partner |
End-to-end delivery: configuration, data migration, integrations, training, go-live |
You’re deploying or replatforming and need one accountable team |
|
Salesforce implementation consultant |
Strategy, architecture, and roadmap often before or alongside delivery |
The architecture question is still open |
|
Developer |
Build capacity inside a plan someone else owns |
Scope and architecture are already decided; you need code written |
|
Freelancer / staff augmentation |
Individual capacity, no whole-system accountability |
You’re filling one skills gap inside your own existing team |
A few distinctions worth knowing before you shortlist anyone:
- Implementation is the classic systems-integrator role. It’s the work that turns a purchased license into a system your people actually use day to day, not just a configured instance.
- A salesforce implementation consultant is the right purchase earlier in the process, when the architecture question is still genuinely open. Once you know what you’re building, a consultant’s value drops relative to an implementer’s.
- Developers are the narrowest of the four purchases. Valuable, but only once someone else already owns the plan they’re building inside; hire a developer before that plan exists, and you’re paying for guesswork.
- If what you actually need is headcount rather than a delivered outcome, for instance, a contractor sitting inside your own team or reporting to your own project manager, that’s staff augmentation. It’s a different purchase with different economics; Achieva’s Salesforce developer hiring guide covers rates and staffing routes separately, since this guide doesn’t.
The common buyer mistake here isn’t picking the wrong firm but picking the right firm for the wrong role. A strong implementation partner brought in for what should have been a scoping engagement will often over-build; a developer brought in without an owned plan will often under-deliver, because nobody handed them one.
“Implementation teams build solutions. The FDEs make sure those solutions drive value.”
– Sarah Khalid, Forward Deployed Engineer & Director, Salesforce
Most readers of this guide need the first role, i.e., implementation, often followed later by managed services once the system is live. That’s Section 8.
What Changed in Salesforce’s 2026 Partner Program?
On March 2, 2026, Salesforce cut its four-tier program (Base, Ridge, Crest, Summit) down to two, that is Select and Summit, and replaced roughly 170 legacy badges with 28 competencies.1 Summit now requires verified outcomes and demonstrated Agentforce and Data Cloud delivery. Take a detailed look at this part.
The old system, which comprises four tiers, Base, Ridge, Crest, and Summit is retired now. Informally known as Registered, Silver, Gold, and Platinum, these tiers climbed mainly through a points system tied to certification counts and deal volume. A firm could reach the top tier by accumulating certified staff without ever proving delivery outcomes. It rewarded scale over results.
The new system, comprising of only two tiers, Select and Summit looks like:
- Select confirms foundational, demonstrated delivery capability; the entry and mid-level tier for salesforce implementation partners
- Summit is the higher bar: verified customer outcomes, satisfaction evidence, and demonstrated delivery competency in priority areas, specifically Agentforce and Data Cloud
- Badges collapsed from roughly 170 to 28 competencies, each rated Accredited or Expert
- Points-based scoring became outcome-based verification where individual Trailblazer scores and certifications now sit alongside firm-level competencies as supporting evidence, not a substitute for them
The rollout, for context: Salesforce phased this in rather than flipping a switch; partners were notified and given access to updated program documentation, then given a window to apply for their new tier, with early applicants getting preferential positioning. Partners who didn’t apply were placed by default. That’s part of why so much web content still describes the old four-tier structure: firms wrote their “how we compare” pages before their own placement was final.
What Does This Mean for a Buyer?
- The tier signal now carries more information than it used to. Summit is a claim about verified delivery, not accumulated credentials, a materially higher bar than the old top tier was.
- A useful diagnostic just appeared for free: any firm still leading with “Gold Partner,” “Platinum Partner,” or “Crest Partner” language hasn’t updated its marketing since early 2026. That’s not automatically disqualifying, plenty of good CRM implementation partners are simply slow to refresh a website, but it’s worth asking about directly.
Tier is a filter, not a verdict. The next section is about matching tier to your actual project, not assuming higher is always the right answer.
Which Type of Salesforce Implementation Partner Fits Your Project?
Fit depends on project shape, not a single ranking. A well-scoped single-cloud rollout is honestly served by a strong Select-tier firm. Multi-cloud programs need governance evidence; integration-heavy estates need the integration test.
- A well-scoped single-cloud rollout (Sales Cloud or Service Cloud, one defined team):
Strong Select-tier firms among CRM implementation partners serve this well. The requirements are contained enough that Summit-level program governance mostly goes unused.
You may not need a Summit partner for this, paying Summit rates here is often paying for capability the project won’t use.
That’s an inconvenient sentence for us to print, since we’re Summit partners. It’s still true.
- A multi-cloud program
Needs program governance, architecture ownership across clouds, and demonstrated change-management history, not just per-cloud competence.
- An industry-specialized build
Wants domain scars over platform badges. A partner who can whiteboard your industry’s workflows unprompted has usually earned that the hard way.
- An integration-heavy estate
Should be evaluated on the integration test above everything else on the scorecard.
- A rescue engagement
Needs a partner who leads with diagnosis, not a proposal, with references from other rescues specifically.
- An AI-era program
Should weigh the new competencies with real skepticism; verified delivery over demo-stage fluency.
The partner-selection criteria are also changing as AI moves from experimentation into implementation. Salesforce’s 2026 CIO research2 reports that AI implementation surged 282% globally in 2025, increasing the importance of evaluating partners on production experience rather than demo-stage AI fluency.
How Do You Score a Salesforce Implementation Partner?
Seven weighted areas, each with an evidence standard and one revealing question. This is our practical answer to how to choose a Salesforce implementation partner: copy this into your RFP.
| Area | Evidence Standard | Ask This |
|---|---|---|
|
Delivery evidence |
Named outcomes, references in your project shape |
“Show us a go-live like ours, and the team that ran it.” |
|
Team seniority |
Named roles in the SOW, not the sales team; individual Trailblazer scores as one data point |
“Who staffs this project, versus who sold it?” |
|
Industry fit |
Domain workflows they can whiteboard unprompted |
“Walk me through how you’d handle [your specific process].” |
|
Data & migration depth |
Documented method: audit, mapping, test runs, validation, rollback |
“What’s the rollback plan if a migration test fails?” |
|
Integration capability |
Section 7’s test, summarized |
“Which of our exact systems have you connected before?” |
|
Adoption & governance |
Training plans, admin enablement, post-go-live ownership |
“Who owns this on day 91, and what does that cost?” |
|
AI-era readiness |
Competency-verified (Section 3), weighed against actual need |
“Show a live deployment with a measured outcome.” |
Weight these by shape, not equally:
- Single-cloud rollout → weight team seniority and adoption heavily; AI-readiness lightly
- Integration-heavy estate → weight the integration row above every other criterion
- Multi-cloud or rescue → weight delivery evidence and team seniority heavily
Take this this table is your RFP’s scoring sheet. A scorecard only means something if the publisher is willing to be scored on it too, and we built this one expecting to be scored.
In fact, Salesforce’s own partner-selection guidance recommends weighting evaluation criteria according to the project’s size, complexity, risk and available internal expertise, not applying identical criteria to every implementation.3
What Are the Red Flags and What Really Causes Implementations to Fail?
Six patterns predict specific failures, and the real causes of failure are almost always people and data, not the platform.
- Vague scope + “we’ll figure out the data plan later” → predicts a change-order engine that grows monthly
- Unclear staffing → the bait-and-switch: a senior architect sells, a junior bench delivers
- Retired-tier marketing → the currency diagnostic from Section 3
- Logo lists instead of outcome evidence → the outcome evidence probably wouldn’t hold up if pressed
- Lowest-bid pricing → a junior-heavy team priced to win often reworks its way to double the original quote
- No defined post-go-live plan → the partner’s incentives end the day you go live
On failure statistics: guides in this category often cite a precise CRM or Salesforce implementation failure rate, somewhere between 50% and 90% depending on the source. We looked for a first-hand, dated, primary source behind those numbers and couldn’t find one meeting a credible bar. What’s consistent across the available research:
- Implementation failure is common enough to plan around
- It’s rarely the platform’s fault
- Failures trace overwhelmingly to people, process, and data; adoption, unclear ownership, skipped data discipline
Treat any guide citing a precise, uncited failure percentage as a red flag in its own right.
Validate Your Scope, Architecture, Migration Requirements, Integrations, & Delivery Model Before You Commit to a Partner
How Do You Evaluate a Salesforce Integration Partner?
For integration-heavy estates, the integration test outranks everything else on the scorecard: hands-on history with your exact systems, tool fluency with reasons, and how the partner handles failure.
Salesforce integration partners is really a request for evidence in three parts:
- Hands-on history with your exact systems, asked by name: not “we’ve done integrations,” but “we’ve connected this ERP to this CRM before”
- Tool fluency with reasons: native APIs, MuleSoft, or third-party middleware, and why that tool fits your case specifically
- Failure discipline: every integration breaks eventually. How a partner answers on monitoring, retry logic, and reconciliation reveals more than any feature list
Ask about failure handling before feature handling. If HubSpot sits anywhere in your stack, Achieva’s HubSpot-Salesforce integration guide goes deeper on execution than this section does.
Data-migration depth follows the same standard i.e., audit, mapping, test runs, validation, rollback.
What Does Cost, Engagement Model, and Good Process Look Like?
Cost varies by scope, cloud count, data complexity, integration count, team seniority, and geography; no single number is honest without knowing your project.
What drives cost:
- Scope and cloud count
- Data complexity
- Integration count
- Team seniority (senior-heavy teams often cost less overall)
- Geography
Engagement models:
- Fixed-scope — well-defined rollouts, stable requirements
- Time-and-materials — evolving programs
- Dedicated pods — long, multi-phase roadmaps
What good process looks like and what to demand in writing:
- Discovery that produces a written, signed scope
- Build in sprints with a real demo cadence
- UAT against actual business scenarios, not a feature checklist
- A rehearsed, dated cutover
- Hypercare with defined exit criteria into support
A buyer who demands signed-scope discovery and a rehearsed cutover in the contract has already filtered most of the field.
A strong implementation process should make ownership and milestones visible from discovery through post-go-live support. The journey typically follows this sequence:
These milestones should translate into contractual expectations, from signed-scope discovery and sprint-based delivery to UAT, cutover rehearsal, hypercare, and defined post-go-live ownership.
Start Your Salesforce Implementation with the Right Delivery Model
How Does Achieva Score Against Its Own Rubric?
Scored against the seven areas above: Achieva is a re-verified Salesforce Summit Partner (March 2026 program) with 28+ years of delivery and listed AppExchange products as checkable evidence.
- Delivery evidence: Summit Partner status, re-verified against the March 2026 program restructure
- Team seniority: More than two decades of experience of Salesforce delivery, named team models per engagement
- Industry fit: domain depth applied per engagement, not claimed generically
- Data, migration, and process: run to Section 8’s standard; signed scope, sprint cadence, rehearsed cutover, defined hypercare exit
- Checkable proof: Achieva’s own listed AppExchange products
- AI-era readiness: Agentforce and Data Cloud capability bounded to what’s currently published and verifiable
External Links:
- [1]: Salesforce
- [2]: Salesforce
- [3]: Salesforce
