Battlecard
A battlecard is a sales reference document that compares a vendor’s product against named competitors, giving reps talking points, objection handling, and feature comparisons to use during a competitive deal. It is a CI team’s primary output, and its usefulness depends entirely on the accuracy of the intelligence feeding it.
Most battlecards are built from rep-sourced input: debrief calls, CRM competitive tagging, and whatever objections reps report hearing during a sales cycle. That input reflects what a rep heard, filtered through a relationship the buyer was managing at the time. A buyer who softened their real objection, or never raised it at all because it felt too personal to say to the person they were declining, leaves nothing for the battlecard to capture.
The limitation shows up most clearly in how battlecards get refreshed. A card gets updated after a string of losses, using the same rep-sourced input that produced the original card. If the underlying competitive loss attribution was already off, the refreshed card inherits and often compounds the error, because each update cycle adds another layer of inference on top of the last without ever checking the inference against what buyers actually experienced.
A battlecard built around a full platform comparison illustrates this well. Every capability gets mapped feature-by-feature against a competitor’s, while the buyer who actually chose that competitor may have wanted only one specific capability rather than the whole platform. That objection never surfaces in a call a rep was on, so it never shapes the card. The next rep who runs into the same competitor walks in prepared for the wrong fight.
Independent win/loss interviews strengthen a battlecard by supplying the half of the comparison rep debriefs structurally cannot reach: what a buyer actually believed about the competition, confirmed directly rather than inferred from what they were willing to say to a vendor’s sales team. A buyer who describes exactly what a competitor’s team did differently, in a conversation with no relationship left to manage, gives a CI team something no rep debrief can replicate.
The cost of skipping this step accumulates quietly. A card built entirely on rep-sourced input gets refreshed on the same cadence, using the same limited source, and each refresh reinforces whatever assumptions were already baked into the previous version. The card always looks current. Whether it’s current with what buyers actually experienced is a separate question, and one most CI teams never think to ask until a pattern of losses forces the issue.