After this lesson you will be able to
- Qualify the competition: who is in the deal, why, and who brought them in
- Shape decision criteria early around the customer's processes and outcomes
- Position Salesforce honestly, including where another platform may fit better
- Decide with evidence when to keep fighting and when to walk away
Find out who you are really competing with, and why they are there
Customers often say they are looking at a few options. That tells you nothing. You need to know which vendors, how far along each one is, and who inside the customer brought each one in. A competitor sponsored by the CFO because it is bundled with the finance system is a different problem from one a sales manager used at a previous job.
Remember that the most common competitor is not another vendor. It is doing nothing, extending spreadsheets, or asking IT to build something. Treat the status quo as a named competitor with its own strengths: it is cheap, familiar and requires no change.
Ask directly and early. Most buyers will tell you if you ask in a neutral way and explain why it helps them. Write the answers into your opportunity record so the next person on the deal does not have to ask again.
- Which other options are you considering, including keeping things as they are?
- Who on your team suggested each option, and what did they like about it?
- How far along are you with each one: early conversations, demos, pricing, references?
- What would have to be true for you to choose the option you are not leaning toward?
Set the decision criteria before anyone builds a comparison grid
Whoever helps the customer write the criteria has a large say in the outcome. If you arrive after a feature checklist is written, you will spend the deal defending yourself line by line. If you arrive early, you can help the customer describe what they need in terms of processes and results, which is where a good fit shows.
Do this by asking about the business first. What has to work on day one? Which processes cross departments? What will the system need to connect to in two years? Who will maintain it after go-live? Then summarize their answers back as criteria and ask them to correct you. Criteria the customer wrote with you are criteria they will defend in the room.
Be fair. Criteria that are slanted toward your product will be spotted by an experienced evaluator and will cost you trust. Criteria that honestly reflect the customer's needs give you a fair contest, and that is usually what you want if the fit is real.
Position honestly: strengths, trade-offs and fit
Technical evaluators and procurement teams compare notes. If you overclaim, they find out, and every other thing you said becomes suspect. Honest positioning means saying clearly where Salesforce is strong for this customer, where the other option has a real advantage, and why the trade-off favors you for their situation.
Talk about the customer's processes, not about the competitor's flaws. Instead of saying another platform is weak at something, show how Salesforce would handle the customer's specific scenario and invite them to ask the other vendor to show the same scenario. That moves the evaluation to what matters and keeps you from sounding defensive.
Our battlecards at /salesforce-account-executives/battlecards/ cover common situations against HubSpot, Microsoft Dynamics 365, Oracle, SAP, ServiceNow and Zoho. Use them to prepare questions and to anticipate the objections you will hear. Check any product claim against current documentation before you repeat it, because every vendor ships changes several times a year.
Run the evaluation on scenarios, not features
Feature demos favor whoever has the longest list. Scenario demos favor whoever fits. Offer the customer a scripted evaluation: three to five real scenarios from their business, run by every vendor, with the same data and the same audience. For example, a 150-person insurance agency might pick quoting a renewal, routing a claim inquiry, and showing a producer's book of business on a phone.
Ask the customer to include total cost of ownership in the evaluation, not just license price. That means implementation effort, integration work, admin time and the cost of the change for users. The resources at /resources/how-long-does-salesforce-implementation-take/ and /resources/salesforce-consulting-pricing-guide/ help a buyer think through those costs without relying on your numbers alone.
Offer references that match the customer's size and industry, and let them speak to the hard parts too. A reference who says the first months were difficult and explains how they fixed it is more convincing than one who says everything was perfect.
Know when to walk away
Some deals are not worth winning and some cannot be won. Walking away early frees time for deals where you fit, and it often earns respect that pays off later. Make the call with evidence, and discuss it with your manager before you act.
Consider stepping back when the customer will not let you meet the people who decide, when the criteria were written around another product and the customer will not revisit them, when the requirements fit a different kind of system better, or when price is the only criterion and your number cannot move enough. If you step back, say so plainly, leave the door open, and offer something useful such as a scenario they should test with whoever they pick.
- No access to the economic buyer after two clear requests
- Criteria locked around another product, with no willingness to revisit
- Requirements that are mostly a better fit for another category of system
- Price as the sole criterion with a gap you cannot close
- A request to bid only to make up the numbers for a three-quote rule
Bring delivery credibility into the contest
In close competitive deals, the question is often not which platform is better but which project is less likely to go wrong. Customers worry about timeline, cost overruns and adoption. A credible implementation plan, written by people who will do the work, can decide the deal.
Bring a delivery partner into discovery when implementation risk is part of the evaluation. A partner can review the scenarios, write a scoped estimate and talk through the risks with the customer's technical team. The deal desk at /salesforce-account-executives/deal-desk/ is one way to get that input. The lesson on implementation risk in this academy covers what to do before signature in more detail.
Talk tracks
The customer says they are looking at a few options
“That makes sense for a decision this size. Would you share who else is in the running and who on your side suggested each one? It helps me focus on what matters to you instead of guessing.”
A neutral reason to ask usually gets an honest answer.
Before any evaluation grid is built
“Before we compare products, can we agree on what has to work on day one and what will matter in two years? I'll write it up, and you can correct it and share it with every vendor.”
It helps the customer set criteria based on their needs and positions you as fair.
The customer repeats a competitor's claim about Salesforce
“I'd rather show you than argue. Which of your scenarios does that concern affect? Let's run it with your data, and I'd suggest asking them to run the same one.”
It moves the debate to evidence and keeps you from sounding defensive.
The other platform is genuinely stronger in one area
“You're right that they do that well. The question is how much it matters against everything else on your list. Here is how we would handle that need, and here is where I think we fit you better.”
Admitting a real strength makes the rest of your positioning believable.
The deal comes down to license price
“I understand price matters. Can we compare the full cost over three years, including implementation, integration and admin time? If we are still not the right answer after that, I'll tell you.”
It widens the comparison to total cost without dismissing the concern.
You have decided to step back from the deal
“Based on what you've told me, I don't think we're the best fit for this project, and I'd rather say that now than waste your time. If your needs change, I'd like to hear from you. Meanwhile, make sure whoever you pick runs your renewal scenario end to end.”
A clean, helpful exit protects your reputation and leaves the door open.
A technical evaluator is skeptical
“What would you need to see to be confident this works in your environment? I'd rather bring the right person for a working session than run another demo.”
Technical buyers respond to depth and access, not polish.
Competitive deal review
Use it on a live deal. Tick items off as you go; nothing you tick leaves this page.
Common mistakes
Attacking the competitor
It makes you sound worried and invites the customer to defend the other vendor. Talk about their scenarios instead.
Arriving after the criteria are written
You end up defending line items you did not choose. Ask to help define criteria in the first or second meeting.
Repeating battlecard claims without checking them
Vendors change fast. One outdated claim caught by an evaluator can undo weeks of trust.
Ignoring the status quo as a competitor
Many deals are lost to no decision. Build the cost of staying put into the business case.
Staying in deals you cannot win
Time spent on a column-filler quote is time taken from deals where you fit. Use the walk-away test.
How you will know it is working
- Customers ask you to help write the evaluation criteria or scenarios
- You can name every competitor and its sponsor in your active deals
- Technical evaluators ask for working sessions instead of more demos
- You walk away from some deals early and your forecast gets more accurate
Questions
Should I ever mention a competitor by name?
Yes, when the customer brings them up and you can speak accurately. Keep it about fit and scenarios, never about flaws you cannot show. If you are unsure of a current fact about another product, say so and suggest the customer ask that vendor directly.
What if the customer will not tell me who else is in the deal?
Respect it, but note it as a risk. Ask what they liked in the other options instead, which often tells you who they are. If secrecy continues alongside limited access to decision makers, apply the walk-away test.
How do I handle a request for a feature-by-feature spreadsheet?
Fill it in honestly and completely. Then offer to add a short section on the three to five scenarios that matter most, and ask whether every vendor can demonstrate them. That keeps you responsive while moving the evaluation toward fit.
When should I bring a partner into a competitive deal?
Bring one in when implementation timeline, cost or risk is part of the evaluation, or when the customer's technical team needs depth you cannot provide. Earlier is better, because a scoped plan is more credible than a promise made in the final week.