The SMB Buyer’s Checklist for Hiring a Salesforce Partner

Section 1: Before you contact anyone

☐ Define what you actually need — before you hear a single pitch

The most common mistake SMB buyers make is starting the partner evaluation process before they’ve defined their own requirements. When you enter a conversation without clarity, you’ll be shaped by whatever the partner is best at selling — not necessarily what you need.

Answer these questions for yourself first:

• Are you implementing Salesforce for the first time, or optimizing/extending an existing org?
• Which Salesforce clouds are involved — Sales Cloud, Service Cloud, Marketing Cloud, something else?
• Do you need a one-time project or ongoing support after go-live?
• Are you looking to integrate Salesforce with other systems (ERP, billing, product database)?
• Is Agentforce or AI automation part of your near-term roadmap?
• What’s your internal Salesforce capability — do you have a dedicated admin, or is this entirely outsourced?

Your answers determine which type of partner you need. A boutique firm that excels at initial Sales Cloud implementations isn’t the right choice if what you need is ongoing managed services and an eventual Agentforce build. Know the difference before you start.

☐ Set a realistic budget range

Salesforce consulting for SMBs in the US typically runs:

• Small business implementation (single cloud, limited customization): $10,000–$30,000
• Mid-market implementation (multi-cloud or significant customization): $50,000–$150,000
• Ongoing managed services/staff augmentation: $5,000–$20,000 per month, depending on scope and hours

If a partner quotes significantly below these ranges, ask what’s out of scope. If they quote above without a clear explanation of the complexity driving it, ask them to break down the estimate. The number itself is less important than understanding what it covers.

☐ Identify 3–5 partners to evaluate in parallel

Don’t evaluate one partner at a time. Speak with at least three simultaneously — it gives you a baseline for what’s normal, makes it easier to spot outliers (in both directions), and prevents you from anchoring on the first proposal you receive. The AppExchange is the right starting point: filter by industry, cloud, and company size served, and read the verified reviews rather than the marketing copy.

Section 2: The first conversation — what to listen for

☐ Do they ask questions before they talk about themselves?

A partner worth working with will spend the first 20–30 minutes of an initial call asking about your business — your current Salesforce setup, your team structure, your specific goals, and your definition of success. They’re doing discovery because they know they can’t scope a project or make a recommendation without it.

A partner who leads with a capabilities deck, drops logo names, or moves quickly toward proposal mode is optimizing for their sales process, not your requirements. That’s how you end up with a scope that doesn’t fit.

☐ Do they push back on anything?

The best Salesforce partners will challenge assumptions, flag risks, and tell you when something you’ve asked for isn’t the right approach — even if that’s commercially uncomfortable. “You don’t need a custom Apex solution for that, a native Flow will do the same thing in a tenth of the time” is the kind of pushback you want. A partner who agrees with everything you say either doesn’t know better or is more focused on closing the deal than on delivering well.

☐ Do they speak specifically about SMBs — or are they clearly enterprise-oriented?

Enterprise and SMB implementations differ in almost every dimension: governance, timeline, change management, budget flexibility, and team capacity. An enterprise partner who takes your project as a favor or to fill capacity will apply enterprise frameworks that don’t fit your organization. Ask directly: what percentage of their clients are businesses of your size? What’s their smallest active engagement? How do they adapt their process for companies without a dedicated Salesforce admin?

☐ Can they tell you who will actually work on your project?

Tier and certification are firm-level signals. What delivers your project is the specific people assigned to it. Ask for the named team before you sign anything: who is the project lead, who are the developers, who is your day-to-day point of contact? Request their individual certifications and, where possible, a conversation with the person who will actually be running the project — not just the partner or account manager who sold it.

This matters especially at larger firms where senior consultants run sales and junior consultants do delivery. It’s common, and it’s one of the primary reasons SMB clients feel misled after signing.

Section 3: Evaluating credentials and track record

☐ Check their AppExchange profile — don’t just take their word for it

Every legitimate Salesforce partner has a verifiable AppExchange listing. On it, you can see their CSAT scores, completed project count, and verified client reviews — all maintained by Salesforce, not by the partner. A firm without an AppExchange listing, or one with fewer than 3–5 verified reviews, is a signal to slow down.

Look specifically for:

• Client reviews from companies similar in size and industry to yours
• Completed project counts in the clouds you need (Sales Cloud, Service Cloud, etc.)
• Any Agentforce-related reviews or competency designations, if AI is in your roadmap

☐ Ask about their 2026 program status specifically

As established above, the partner tier system changed in March 2026. Go beyond asking “what tier are you?” Ask:

• Which of the 28 competencies do you hold, and at what level — Accredited or Expert?
• Are you a Select or Summit partner?
• If you’re in transition, where are you in the Summit application process?

A firm that can answer these clearly and, ideally, point you to its AppExchange profile for verification understands its own standing in the ecosystem. A firm that pivots to Gold/Platinum language or gets vague is one to be cautious about.

☐ Ask for references — and actually call them

Any partner worth working with should be able to introduce you to 2–3 past clients in your industry or business size. Not just written testimonials — actual conversations. This is where you’ll learn what you can’t find on a website: how they handle project challenges, how they communicate when things go sideways, what post-go-live support actually looks like, and whether the people on the reference calls are genuinely happy or just politely positive.

Ask reference clients specifically:

• Did the project come in on scope and on budget?
• How did the partner handle problems when they arose?
• Who was actually doing the work on your project day-to-day?
• Would you hire them again for a different project?

Section 4: Evaluating the proposal

☐ Be suspicious of a fixed price quoted without proper discovery

A reliable partner knows that Salesforce projects require deep investigation before a scope can be defined. If a firm offers a fixed price during or immediately after your initial call, they either haven’t understood your requirements or they’re quoting a standard package they apply to everyone. Both are risks.

What good looks like: a partner who runs a paid or unpaid discovery workshop (2–5 days) to map your workflows, data structures, and integration requirements before scoping the project. The proposal that emerges from that discovery is more reliable because it’s based on what your project actually requires.

☐ Check for change order risk

A proposal that includes a narrow scope and a low headline price often masks significant change-order exposure — work that was always going to be required but wasn’t included because it would make the proposal less competitive. Ask specifically: what’s typically excluded from engagements like this? What are the most common sources of scope expansion you’ve seen in similar projects? A partner who gives you an honest answer to that question is thinking about your long-term experience, not just the contract signature.

☐ Does the proposal include post-go-live support?

Implementation is where the project ends. Adoption is where the value starts — and adoption doesn’t happen automatically. Ask what post-go-live support looks like: who is your point of contact after launch, what’s the SLA for critical issues, and is there a managed services or retainer option for ongoing support. A partner without a clear, staffed support model is leaving you to figure out the hard part alone.

☐ Is there a plan for user adoption?

The most technically perfect Salesforce implementation delivers zero value if your team doesn’t use it. Ask every partner you evaluate: how do you handle change management and user adoption? What training do you provide? How do you measure whether the implementation is actually being used 90 days after go-live?

The absence of a concrete answer to this question is one of the most reliable predictors of a project that works in demo and fails in production.

Section 5: Red flags — stop and reconsider if you see these

☐ They lead with Gold or Platinum credentials without mentioning the 2026 tier change

As covered above, these designations are obsolete. A partner presenting them as current credentials either doesn’t know or is hoping you don’t.

☐ They default to custom Apex code for everything

Over-engineering with custom Apex when native Salesforce functionality would do the same job is a common way to inflate billable hours. When a partner proposes custom code, ask: Is there a native Salesforce feature or Flow that would accomplish this? If the answer is yes, ask why custom code is the recommendation.

☐ They can’t name the people on your team

As noted above, tier is a firm-level signal; people deliver projects. If you can’t get a named team and their individual credentials before signing, you don’t know what you’re buying.

☐ They promise an unusually fast timeline

Rushed Salesforce projects consistently underperform. If a partner is quoting a timeline that seems optimistic relative to what others are saying, ask what’s being deprioritized to hit that date. More often than not, it’s the discovery work, the testing, or the user adoption support — the parts that determine whether the project is actually successful.

☐ There are no AppExchange reviews from companies like yours

If every review on their AppExchange profile is from enterprise companies and you’re a 50-person business, that’s not necessarily disqualifying — but it means you should ask pointed questions about how they adapt their approach for smaller clients. If they can’t give you a clear answer, the risk is that your project gets run with enterprise-level overhead, timelines, and complexity that don’t fit your organization.

☐ They agree with everything you say

You need a partner who challenges assumptions and suggests process improvements — not one who validates every idea to close the deal. The right partner will occasionally tell you that what you’re asking for isn’t the best approach. If a partner never pushes back on anything across multiple conversations, treat it as a warning sign.

Section 6: The questions to ask every partner — use these verbatim

Print these and bring them to every evaluation conversation:

1. What is your partner tier under Salesforce’s new 2026 program — Select or Summit — and which competencies do you hold at what level?
2. Walk me through a project you’ve delivered for a company similar in size and industry to ours. What went wrong, and how did you handle it?
3. Who specifically will be working on our project, and can I speak with them before we sign?
4. What’s included in your proposal, and what are the most common sources of scope expansion you’ve seen in similar projects?
5. What does post-go-live support look like? Who is our point of contact, and what’s the SLA for critical issues?
6. How do you handle user adoption and change management, and how do you measure whether the implementation is actually being used?
7. Can you show me your AppExchange profile and walk me through the verified reviews most relevant to our situation?
8. If Agentforce or AI automation becomes part of our roadmap in the next 12 months, what’s your capability there, and what would that engagement look like?