Ask a sales team why they lose to a particular competitor and you will get a list: price, features, timing, relationships. All plausible, none actionable, and mostly wrong — because they are reconstructed after the fact by people with an interest in the reconstruction.

What is actually useful is narrower: the small number of conditions that, when present at the start of a deal, predict the outcome. Those are win/loss triggers, and most companies have four or five.

Triggers are conditions, not reasons

The distinction matters.

A reason is a post-hoc explanation: “we lost on price.” It is unfalsifiable, arrives too late to use, and is the most socially convenient answer available to everyone involved.

A trigger is an observable condition present early: “when the evaluation is run by procurement rather than the end user, we lose to them roughly four times in five.” That is checkable, it is knowable in week one, and it tells a rep what to do.

The whole exercise is converting reasons into triggers.

Finding them

You need outcome data with enough context to spot patterns. Practically:

Step 1: Assemble the deals. Every deal in the last twelve months where this competitor was present, won and lost. Twenty is enough to see patterns; fewer and you will find noise.

Step 2: Record conditions, not narratives. For each deal capture observable facts known at the start: who initiated, who ran the evaluation, company size, existing stack, whether a deadline existed, whether an incumbent was being replaced, which department held the budget.

Resist recording “why we lost.” That is what you are trying to derive, and writing it down first contaminates the exercise.

Step 3: Sort by outcome and look for the split. Lay the conditions against outcomes and look for a condition where the win rate diverges sharply. You are looking for something like “when X is true we win 70%, when X is false we win 20%.”

Step 4: Sanity-check with reps. Show them the pattern. Either they recognise it immediately, or they explain a confound you missed. Both outcomes are useful.

Triggers that recur across categories

Yours will be specific, but these shapes appear often enough to check for:

  • Who initiated. Deals started by an end user with a specific problem behave differently from deals started by a procurement cycle.
  • Incumbent status. Replacing an incumbent is a different deal from a first purchase, with different objections and different odds.
  • Deadline presence. A real external deadline compresses evaluation and favours whoever can demonstrate value fastest.
  • Technical evaluator involvement. Whether a hands-on evaluation happens at all often predicts more than its outcome.
  • Budget holder. Which department pays determines which benefits count.
  • Existing stack adjacency. Whether the buyer already uses something from the competitor's ecosystem.

What to do with them

Triggers earn their keep in three places.

Qualification. The most valuable and least popular use. If a trigger predicts an 80% loss rate, the correct action is usually to spend less on those deals, not more. Sales teams resist this, because a disqualified deal feels like a lost one. It is not — it is time returned to deals you can win.

Early intervention. Some triggers can be changed. If losing when procurement runs the evaluation is a trigger, the play is getting an end-user champion engaged before procurement takes over. That is a specific, coachable action.

Battlecard content. Triggers tell a rep which deals need which arguments. They belong on the card alongside discovery questions that surface whether a trigger is present — see the anatomy of a battlecard.

The bias to correct for

Loss reasons collected from reps are systematically distorted, and predictably so: “price” is over-reported because it is the explanation that reflects least on the rep and least on the product.

The correction is talking to buyers, not sellers. A short conversation with a lost prospect — genuinely asking, not re-pitching — usually produces a different answer from the CRM field. Buyers are often willing, because nobody asks them.

Where direct conversation is not possible, public sources partly substitute. What people say in community threads and reviews about why they chose one vendor over another is win/loss data written by the buyer.

Re-derive them periodically

Triggers are not permanent. They shift when a competitor changes pricing, when you ship something, or when the market's default assumptions move.

Re-run the analysis every two quarters. It is a day of work and it prevents a sales team from optimising against conditions that stopped applying — the same decay that makes battlecards go stale.

Our Sales Battlecard report includes win/loss triggers derived from public evidence about where a competitor is strong and weak, framed as conditions a rep can check early rather than reasons to write down afterwards.