River
Y CombinatorBacked by Y Combinator

Sales & PartnershipsFree

Competitive Trap Questions for Sales Calls

Every question traces to something the competitor published, with a date on it. Anything your own product answers no better is cut before the call.

Start here

The genre has a shape and the shape is the problem. A competitive brief arrives as a two-column battlecard: their weakness on the left, your talking point on the right, sourced to a sales engineer who heard it on a call in March. Reps love it right up to the moment a buyer says that is not what their documentation says. It turns out the documentation changed. The rest of the meeting goes on recovering credibility that was never worth the point being made.

Three tests fix it and the first one is the one nobody applies. Draft every question from something the competitor published themselves, then ask it of your own product. Twelve of thirty-four candidates die immediately, because the honest answer is that we are no better. That test has a systematic version: extract the recurring complaint themes from their public reviews and from yours, and the seventeen that appear in both are category problems rather than competitor problems.

Six more go for resting on a review rather than a document, three for a source page carrying no date, and thirteen survive the funnel. Eight of those the buyer can settle by opening a file, which means you never have to be believed in the room. Built for the rep walking into a bake-off. The battlecard itself belongs to product marketing, the room you are walking into is the stakeholder map, and the tool index has the rest.

The regulator is on the side of naming them, under one condition

There is an official position on this and it is more permissive than most sellers assume. The Federal Trade Commission holds that comparative advertising, when truthful and nondeceptive, is a source of important information to consumers and assists them in making rational purchase decisions. It encourages naming the competitor outright rather than gesturing at an unnamed market leader. It goes further and says it will scrutinise industry codes that restrain the practice. The condition doing all the work in that sentence is truthful.

Reviews are the shakier half of the evidence and the rules now say why. It is an unfair or deceptive act for a business to write, create or sell a consumer review that materially misrepresents that the reviewer exists or used the product. The existence of a rule against something is a decent indication of how much of it there is. So a review corpus is useful for finding which complaints recur across hundreds of accounts, and useless as the sole support for a specific factual claim about one competitor.

That split is why the brief treats the two bodies of evidence completely differently. Reviews generate the intersection, which is a statistical read used to disqualify questions rather than to make any claim about anybody. Claims come only from the competitor's own published artifacts, each carrying the date it went up, because that is the one category of evidence the competitor cannot dispute in the room without also disputing themselves.

How it works

  1. Name the competitor

    Who you are against, what stage the evaluation is at, and what they have already said.

  2. Be blunt about yourself

    Your real weaknesses, since this is what stops a question coming straight back at you.

  3. River reads both records

    Their published material and both review corpora, then runs the symmetry, source and date tests.

  4. Take the brief in

    Thirteen questions with their sources, plus the answers to what they will say about you.

What you get

  • Every question traced to a document the competitor published, with the date on it
  • The symmetry test applied first, cutting anything your own product answers no better
  • Recurring complaint themes from both review corpora, with the shared ones ruled out
  • Questions split by whether the buyer can settle them alone or must ask the vendor
  • A staleness flag on any source old enough that they may have quietly fixed it
  • Their likely attacks on you, each with the response and the record behind it

Common questions

Is a trap question not just a dirty trick?

The dirty version is the one that rests on a rumour and hopes nobody checks. Every question here has an honest answer sitting in a document the competitor wrote, which is why eight of the thirteen can be settled by the buyer without you in the room. If the answer turns out to be fine, you have lost nothing and learned something true.

Why cut twelve questions before anyone hears them?

Because a question your own product also fails is a question you have handed to the other side. It comes back within a minute, it comes back sharper, and the buyer now has a reason to discount everything else you raised. Twelve of thirty-four is a normal proportion, not a sign of a weak product.

We do not have enough reviews for the intersection.

Then it runs on whatever exists and says how thin it is. Support tickets work, so do lost-deal reasons and the objections your own team logs. The point of the intersection is to catch complaints that belong to the category rather than to one vendor, and any two comparable corpora will surface the obvious ones.

What counts as a source with a date?

A page with a last-updated stamp, a release note, a versioned document, a report with an observation period, a dated changelog entry. What does not count is an undated marketing page, because the sentence you are relying on may have arrived last week or three years ago, and you cannot tell which while standing in the room.

Their documentation changed the day before our call.

Which is exactly what the staleness flag is for. Anything past six months gets re-read before the meeting, and in the worked example one source is 402 days old and would have produced a question about behaviour they quietly fixed. Re-checking eight pages takes a few minutes and it is the highest-return preparation in the whole brief.

How is this different from a battlecard?

A battlecard is a standing document about a competitor, maintained by product marketing, and that is the battlecard generator. This is one brief for one meeting against one competitor at one moment, where the freshness of each source and the symmetry against your own gaps both matter and neither is stable enough to keep on a card.

Does it help with the demo itself?

Indirectly. What you show is set by what the buyer raised, which is the demo script, and it does not change because a competitor is in the deal. The brief changes how you close, since the questions you leave behind get asked of the other vendor after you have gone.

Competitive Trap Questions for Sales Calls

Fill in the form and your workspace opens with the work already underway.