There are two ways to raise a competitor's weakness. You can state it, or you can ask a question that leads the buyer to find it.

The second is dramatically more effective, for a reason that has nothing to do with cleverness: a buyer discounts what a vendor tells them about a rival, and does not discount what they concluded themselves.

What a good discovery question does

It has four properties.

It never names the competitor. The moment you name them, the question becomes an attack and gets read as one.

It is a genuine question. If you would not ask it of a buyer with no competitor in the deal, it is a rhetorical device wearing a question mark, and experienced buyers hear the difference.

It surfaces a requirement, not a feature. You are helping the buyer articulate something they need, which happens to be somewhere the competitor is weak.

It is answerable. A question the buyer cannot answer produces awkwardness, not insight.

How to build them

Work backwards from a real weakness, in three steps.

Step 1: Name the weakness precisely. Not “their reporting is weak” but “their exports are manual and cannot be scheduled, so recurring reporting is a repeated task.” Vague weaknesses generate vague questions.

Step 2: Identify who feels it, and when. The manual export problem is invisible to an evaluator and painful to whoever produces the monthly board pack. It appears in month two, not during the trial. That timing is the leverage.

Step 3: Write the question the person who feels it would recognise. “Who ends up assembling the monthly numbers, and roughly how long does that take them today?”

Nobody has been attacked. The buyer has been asked about their own process. If the answer is “two days a month,” a requirement has just been created that the competitor cannot meet — and the buyer created it.

Where the weaknesses come from

The questions are only as good as the underlying research. Sources, in rough order of yield:

  • Public reviews and community threads, where customers describe friction in their own words. See listening where you don't own the channel.
  • The competitor's own documentation, which describes limits honestly because it is written for people who already bought.
  • Their pricing page, where tier boundaries reveal what costs extra and therefore where the surprise bills come from.
  • Your own win/loss records, particularly deals won late after a competitor was already ahead.

Question shapes that travel well

Four patterns that adapt across categories:

  • The recurring-cost question. “How often does that need to happen, and who does it?” Surfaces manual work that a trial period hides.
  • The scale question. “What does this look like at three times your current volume?” Surfaces ceilings, which are invisible at evaluation size.
  • The failure question. “What happens when this goes wrong at 2am?” Surfaces support and reliability differences that nobody checks up front.
  • The second-user question. “Who else will need to get into this, and what will they need from it?” Surfaces permissions, collaboration and onboarding gaps.

Each works because it moves the conversation from the evaluation to the eighteen months after it, which is where most competitive differences actually live.

The line not to cross

These questions carry a real risk of becoming manipulative, and buyers who detect it react badly and permanently.

The distinction is whether the requirement is real. Asking about monthly reporting because the buyer genuinely does monthly reporting is discovery. Asking to manufacture a concern about something that does not affect them is a trick, and the buyer will work it out — often after signing, which is worse.

A test that holds up: would you still want the buyer to have this information if they were going to choose the competitor anyway? If yes, the question is legitimate.

Where they belong

On the battlecard, next to the weakness they are built from, so a rep can see the connection. Three or four per competitor is the right number — more than that and none get used. See the anatomy of a battlecard.

They also need to be dated, because they depend on the competitor not having fixed the weakness. A discovery question aimed at a gap that was closed last quarter makes a rep look uninformed at exactly the wrong moment — see why battlecards go stale.

Our Sales Battlecard report derives discovery questions from documented weaknesses, with each one traceable to the evidence it came from rather than invented to fill a section.