Competitive Landmines

Most competitive strategy focuses on what happens after a competitor is named: how to handle the objection, what to say about their weaknesses, how to reframe the comparison. That’s reactive. Landmines are proactive.

A landmine works by shaping the evaluation criteria before the prospect has finalized them. In early discovery, prospects rarely have a fully defined list of requirements. They know they have a problem. They’re starting to think about what a solution needs to do. That window is where landmines get planted.

A rep who asks “How important is it that guidance surfaces without a bot joining the call?” is not just asking a question. They’re introducing a criterion that, if the prospect agrees it matters, becomes part of how they evaluate every vendor including the ones they haven’t talked to yet.

The most effective landmines have three characteristics:

• They connect to something the prospect genuinely cares about, not just something the rep wants them to care about
• They reflect a real and defensible advantage your product has over a specific competitor
• They’re framed as the prospect’s requirement, not your differentiator

The mechanics are straightforward. During discovery, the rep asks a question that introduces a requirement framed as a natural extension of the pain the prospect has already described. The prospect either agrees the requirement matters or they don’t. If they agree, the landmine is set.

The framing matters. “Our product doesn’t require a bot on the call” is a pitch. “How would it affect your team if prospects could see a bot had joined?” is a question that lets the prospect reach the same conclusion themselves. One lands. The other sounds like a feature list.

Examples of landmine questions in practice:

• “How much of your reps’ time is spent searching for answers mid-call versus having them surface automatically?” (plants a push vs. pull criterion)
• “What happens when a rep gets coaching advice after the call is already over?” (plants a real-time vs. post-call criterion)
• “How important is it that the guidance your reps get is specific to your product and playbook, not generic best practices?” (plants a customized vs. generic content criterion)
• “If a vendor required a significant implementation timeline before your reps could use it in live calls, how would that affect your decision?” (plants a time-to-value criterion)

Each question is designed to get the prospect to articulate a requirement. Once they say it out loud, it’s theirs. It goes into how they evaluate the rest of the market.

Landmines only work before the prospect has set their evaluation criteria. If they’ve already run a demo with a competitor, already talked to procurement, or already put together an RFP, the criteria are largely fixed. Trying to introduce a new requirement at that stage feels like moving goalposts rather than helping them evaluate well.

The window is the first one or two calls, before the prospect has solidified their requirements. That’s when discovery questions double as landmine-setting. The rep is simultaneously uncovering pain and shaping the frame through which the prospect will evaluate every option.

This is also why qualification and competitive strategy can’t be treated as separate stages. By the time a rep knows which competitors are in the deal, the window to plant criteria is already closing. Competitive landmines need to be part of early discovery, not a reactive move made after a competitor appears.

Fear, uncertainty, and doubt (FUD) is the lazy version of competitive positioning. It works by making prospects afraid of the competitor rather than genuinely confident in you. It relies on exaggeration, selective framing, or occasionally false claims about what a competitor does or doesn’t do.

Landmines are different in two important ways.

First, they need to be true. A landmine only holds up if the requirement you planted actually reflects a real advantage. If the prospect tests it in a demo or asks the competitor directly, the answer needs to confirm the criterion, not undermine it. A landmine built on an overstated claim becomes a trust problem the moment the prospect discovers the exaggeration.

Second, they should serve the prospect’s actual interests. The best landmines are criteria that genuinely matter for the prospect’s use case. You’re not manipulating them into caring about something irrelevant. You’re ensuring they don’t overlook something that will affect whether the solution works. That’s a service, not a trick.

The line between FUD and a legitimate landmine is whether the criterion is real, whether your advantage on it is real, and whether it connects to something the prospect actually cares about.

Planting landmines your product doesn’t clearly win on

The most common error. A rep introduces a criterion in discovery, the prospect cares about it, and then in the technical evaluation it turns out the competitor also meets it. The landmine became a neutral criterion rather than a differentiator. Only plant requirements where your advantage is clear and defensible.

Being too obvious

A prospect who realizes a question was designed to frame out a competitor rather than understand their needs will trust the rep less. The framing has to be genuinely consultative. If it sounds like a talking point, it lands like one.

Planting too many at once

Introducing five criteria in a single discovery call makes none of them stick. One or two well-placed requirements that connect to real pain are more effective than a checklist of differentiators dressed up as questions.

Waiting until the competitor is already in the deal

At that point, introducing new criteria looks defensive. Landmines need to precede the competitive conversation, not respond to it. If the criteria aren’t set before the first competitor demo, the window has closed.

Competitive landmines require the rep to know, in the moment, which criteria to introduce for which competitor and how to frame them as natural discovery questions rather than positioning moves. That’s a lot to hold in working memory during a live call while simultaneously managing the conversation.

Commit surfaces competitive context in real-time based on what’s being said. When signals in the conversation suggest a specific competitor may be in the picture, the relevant landmine questions appear on screen before the rep has to recall them from a battlecard they reviewed two weeks ago. The criteria get introduced at the right moment, framed correctly, while the evaluation window is still open.

That’s real-time competitive enablement: not a better training program on competitive strategy, but a system that executes it in the live conversation before the opportunity to shape the evaluation closes.