How to Win a Competitive Deal When You Are Not the Market Leader

When you are not the market leader, competing head-to-head on the same criteria as the incumbent is a losing strategy. They have the brand recognition, the installed base, the analyst ranking, and the reference customers. If the prospect evaluates you on the same terms they use to evaluate the leader, the leader wins almost every time.

The only way to win competitive deals consistently is to change the terms of the evaluation. Not dishonestly. Not by obscuring your weaknesses. By shifting the criteria to the dimensions where your product and your motion are genuinely stronger, and by surfacing the questions that reveal gaps the incumbent would rather the prospect not ask.

This is the 5-move competitive deal playbook. It works for challenger SaaS companies competing against category leaders, legacy vendors, or entrenched point solutions. Each move is distinct. Together, they shift the deal from "who is the safer choice" to "who is actually the right fit."

Move 1: How do you reframe evaluation criteria in a competitive deal?

Every competitive evaluation has a default set of criteria. Usually, those criteria were either inherited from a previous evaluation, set by the incumbent during an early discovery call, or pulled from an analyst framework the buying team found online. In most cases, those criteria favor the market leader. Your first job is to add the criteria that reveal where you win.

Reframing evaluation criteria is not about arguing against the prospect's existing criteria. It is about expanding the list.

The mechanism:

During discovery, listen carefully to the business problem behind the evaluation. Not the features they are asking about. The underlying business outcome they are trying to achieve. Then introduce evaluation criteria tied to that outcome that the current criteria do not cover.

For example: if the prospect has a feature comparison matrix that covers integrations, reporting, and user management, those are table-stakes criteria that probably favor a more mature product. But if their underlying problem is slow time-to-value from onboarding, you can introduce a new criterion: average time from contract signature to first productive workflow. That is a criterion you can win on. It is also a criterion that reveals a gap the incumbent may not want measured.

The introduction should feel natural, not strategic: "One thing we see a lot in companies at your stage is that time-to-value becomes a bigger constraint than feature depth. Have you thought about including implementation timeline as an evaluation criterion? We see significant variance between vendors on that dimension."

What makes this work:

The prospect accepts the new criterion because it is genuinely relevant to their problem. You are not inventing a category advantage. You are surfacing a dimension where your product performs better and where their problem is real. The best reframes are ones where the prospect thinks: "We should have been measuring this all along."

For more on how to build competitive positioning that creates these advantages, see competitive positioning for SaaS companies.

Move 2: How do you plant landmine questions in a competitive evaluation?

A landmine question is a question you suggest the prospect ask your competitor. If asked, it will either reveal a gap in the competitor's product, expose a weak point in their implementation or support model, or create doubt about a capability they are claiming.

The goal is not to be adversarial. The goal is to help the prospect ask better questions so they can make a better decision. When the questions you suggest consistently produce uncomfortable answers from the competition, you win deals. More importantly, you win deals with customers who are choosing you for the right reasons.

How to plant effectively:

Do it during discovery or during the evaluation setup, before the prospect has finalized their evaluation script. The framing is always customer-first: "When you talk to [competitor], it is worth asking them about X, because that is an area where we see a lot of variance between vendors and it can have a meaningful impact on outcomes."

The most effective landmine questions target three categories:

Total cost of ownership. The headline price is rarely the real number. Ask about implementation fees, professional services requirements, the internal engineering time required for the integration, and the ongoing admin overhead. Market leaders often have lower sticker prices that come with significant hidden costs in services and customization.

Recent customer experience. Ask for references who went live in the last 12 months, not just long-tenured customers. Ask what the onboarding experience looked like, not whether they like the product. A competitor's best references are from customers they signed and onboarded 3 years ago when they had a smaller install base and more hands-on implementation support. Recent references tell a different story.

Roadmap accountability. Ask them to point to specific capabilities on their current roadmap that were promised more than 18 months ago and have not yet shipped. Every mature SaaS vendor has some of these. This question does not always land, but when it does, it creates real doubt about whether the roadmap items the prospect is banking on will actually materialize.

What to avoid:

Do not plant questions you cannot answer yourself. If you suggest the prospect ask about implementation timeline and your own implementation timeline is embarrassing, you have created a problem, not an advantage. Only plant questions on dimensions where your answer is clearly better.

Move 3: How do you control the reference check narrative in a competitive deal?

Reference checks are where deals flip. You do everything right in the evaluation, you run the demo perfectly, you price competitively, and then the reference check happens and something the prospect hears changes the deal dynamics. Usually it is not that the reference said something terrible. It is that the prospect asked an open-ended question, got a nuanced answer, and filled in the gaps with their own doubt.

You cannot control what your customers say. But you can influence the narrative going in.

Curate references with specificity:

Do not give the prospect a list of five customers and let them pick. Match the reference to the prospect's specific situation. Company size, industry, use case, even buying process similarity. Then brief the reference before the call: here is who they are, here is what they care about, here is the specific outcome you want to make sure gets covered.

The briefing is not coaching the reference to lie. It is making sure the most relevant parts of their story get surfaced. A reference who had a similar problem and solved it with your product will naturally tell a compelling story when they feel the parallel. Help them see the parallel before the call starts.

Set the reference context for the prospect:

Before you hand over the reference, set context: "I am connecting you with [customer name]. They were in a very similar position to where you are: they had [situation], they evaluated [alternatives], and they chose us because of [specific reason]. One thing they found surprising after go-live was [positive outcome]. I think their experience on [specific area the prospect cares about] will be directly relevant to your evaluation."

This does two things. It primes the prospect to listen for specific things. And it tells the reference customer what the prospect is going to be listening for, so they lead with the most relevant parts of their story.

Handle the competitive reference proactively:

If you know the incumbent is using a specific customer as a reference and that customer is well-known in your category, address it before it comes up: "You may hear from [company] during their reference process. Their use case is [X]. Yours is [Y]. Worth keeping that distinction in mind when you assess how transferable their experience is." You are not attacking the competitor's reference. You are giving the prospect a lens for interpreting it.

Move 4: How do you sequence a demo to highlight gaps in the incumbent?

Most demos are product tours. Here is feature A, here is feature B, here is our dashboard. That format might work when you have no competition. In a competitive evaluation, it is a missed opportunity.

A competitive demo is sequenced to solve problems in the order that reveals where the competitor falls short.

Build the demo sequence backward from competitor gaps:

Start by mapping the specific areas where the incumbent is weakest: whether that is implementation complexity, reporting flexibility, workflow customization, or the administrative burden of configuration. Then sequence your demo to lead with those areas, framed as solutions to the prospect's stated problems.

You are not saying: "Our competitor cannot do this." You are saying: "The thing you mentioned about [pain point] is something we see a lot. Here is exactly how we solve it." The implicit contrast is created by the framing, not by a competitive smackdown.

Use their language:

During discovery, the prospect told you what they care about. Use their exact language in the demo. When a prospect hears their words come back to them in a product walkthrough, it signals: this vendor was actually listening. It also anchors the demo to the specific outcomes they care about rather than the generic capabilities you are proud of.

Show the things that are hard to show:

In competitive deals, speed matters. If your product configures faster, show it in real time. Do not tell them it takes less time. Configure it live, time it, and contrast it with the quoted implementation timeline from the competitor's proposal. If your reporting is more flexible, build a report live during the demo. If your workflow automation requires no code, automate something live that would require a developer with the competitor.

The demo has to make the prospect feel the difference, not just understand it intellectually. The gap that lives in a slide deck does not close deals. The gap that a prospect experiences live does.

Create a moment of contrast:

Build one moment into the demo where you explicitly surface a use case the competitor handles poorly. Not a gotcha. A genuine use case that you know is part of their workflow. Walk through it in your product. Then say: "Some of the companies we talk to who came from [competitor] tell us this specific workflow used to take them [X time] or required [Y level of manual effort]. Here is what it looks like in our product." Let the contrast speak without editorializing.

For a deeper framework on building competitive differentiation into your messaging, see how to build competitive battlecards that actually get used.

Move 5: How do you handle the "we already have a solution" objection?

This objection comes in two flavors, and they require different responses.

Flavor 1: "We have already evaluated the market and selected a vendor."

This means the deal is either dead or you are in a second-place evaluation to pressure the incumbent on price. Find out which one it is before you invest more time. Ask directly: "Is this evaluation still open to a different outcome, or are you using it to benchmark the current vendor's pricing?" If it is a pricing exercise, you can decide whether to participate. If the evaluation is genuinely open, proceed with the full playbook.

Flavor 2: "We already have a solution that does most of this."

This is the more common version and the one where most sales reps lose by arguing on the wrong terrain. The default response is to list features the current solution does not have. The prospect hears: "You will have to replace something that is working and take on switching costs." That is not a compelling argument.

The better response reframes the cost of status quo:

"What are the outcomes you are not getting from the current solution?" Not "what features are you missing." The outcome framing forces the prospect to articulate the business cost of staying put, rather than evaluating whether your features are better than the incumbent's features. If they cannot name outcomes they are missing, the deal is probably not real. If they can, you have the conversation you need to have.

The three-part status quo challenge:

Part 1: Get them to quantify the gap. "How much time is your team spending on [manual process] that the current solution does not handle well?" Real numbers make switching costs feel smaller relative to the problem.

Part 2: Project the gap forward. "If you are 18 months from now and this is still the same, where does that leave you on [business outcome]?" This shifts the framing from current switching cost to future business risk of not switching.

Part 3: Name the switching cost directly before they raise it. "I know switching anything mid-stream is a real cost. Let me show you what that typically looks like for a company of your size and why most of our customers tell us the transition was faster and cheaper than they expected." If you surface the objection yourself, you control the framing. If you wait for them to raise it, you are always on defense.

For a detailed breakdown of how to position against a competitor from a challenger position, see startup vs. competitor positioning: how to play offense without looking desperate.

What information do you need before entering a competitive deal?

Walking into a competitive deal without intelligence is walking in with one arm tied behind your back. Before the first call, you need to know:

What the competitor is selling in this deal. Not just their product in general. The specific package, the pricing tier, the services they are wrapping around it. If you can get the proposal they submitted, even better. Prospects will sometimes share this if the relationship is right and if they trust that you will use it to sharpen your own proposal rather than to attack the competitor.

Why the prospect is evaluating at all. The trigger event matters. If they are re-evaluating because of a failed implementation, the competitor's reliability is already in question. If they are evaluating because a competitor salesperson got into the account, you are in a defensive position. If they are evaluating because of a business change (new exec, new use case, new scale), you have a genuine opportunity to win on fit.

Who is in the buying committee and what each person cares about. The economic buyer, the technical evaluator, and the end-user champion often have different criteria. The economic buyer cares about total cost and risk. The technical evaluator cares about implementation complexity and integration depth. The end-user champion cares about whether it actually makes their work easier. You need a message for each of them, and you need to know which criteria will drive the final decision.

The incumbent's weakest customer segments. Every market leader has segments where they overperform and segments where they underperform. If you can identify which segment the prospect falls into and map that to the incumbent's track record, you have a factual basis for competitive contrast that is harder to dismiss than a feature comparison.

How do you handle price pressure when competing against an established vendor?

The market leader will often reprice aggressively when they know you are in the deal. There are three ways to handle it.

Reframe value before the price conversation happens. If you have done the outcome-framing work throughout the evaluation, the prospect is thinking in terms of business outcomes, not features per dollar. When the competitor drops their price, the prospect's question becomes: "Is the outcome difference worth the price difference?" rather than "Are they asking me to pay more for the same thing?" You want the first question.

Make total cost explicit. If the competitor's headline price is lower but their total cost of ownership is higher, build a TCO comparison that shows the real numbers: implementation fees, professional services, integration costs, internal IT time, training, and ongoing admin. A $20K lower sticker price can evaporate quickly against a $40K implementation engagement and a 90-day longer go-live timeline.

Resist discounting to close. If you discount to win the deal, you have set the pricing expectation for renewal and expansion. You will fight that battle forever. Hold your price if you can. If you need to move on price, attach the discount to something that has a real cost for you: an accelerated close date, a reference commitment, a case study agreement. That makes the discount a trade, not a concession.

What does a competitive win look like vs. a competitive loss?

Understanding the pattern behind your wins and losses is the only way to systematically improve your competitive win rate. Most sales teams track win/loss at a high level and stop there. The data that actually matters is deeper.

In your wins, look for:

The evaluation criteria that were in place when you closed. Were you able to add criteria that favored your product? Which landmine questions the prospect asked the competitor and what answers they got. Who the champion was and what their internal framing was for why you won. The stage at which the deal started to shift in your direction.

In your losses, look for:

Whether the prospect evaluated on your terms or the incumbent's terms. Whether the decision was driven by risk aversion rather than outcome fit. Whether there was a reference or a relationship advantage on the competitor's side that was not about product at all. Whether you were in the deal late and the competitor had already set the evaluation criteria.

The pattern across multiple wins tells you what your competitive playbook is actually doing. The pattern across multiple losses tells you what the next version of the playbook needs to fix.

Build a win/loss analysis cadence: interview one lost prospect per month with a genuinely open question, not a survey. The real reasons deals are lost are almost never captured in a CRM dropdown. They require a conversation where the prospect trusts you enough to be honest.