How consistent are competitor claims across a sales team's battlecards?

A claim-level audit that measures agreement, conflict, and unsupported statements across a set of seller-facing battlecards.

How consistent are competitor claims across a sales team's battlecards?

Question and scope

This protocol measures whether the same competitor claim appears consistently across a sales team's battlecards. The scope is written claims about a named competitor's product, packaging, packaging, or positioning. It excludes opinions about how to sell against the competitor, because those are judgment rather than fact. The question matters because two approved cards can give two different answers to a buyer in the same week.

The unit is a claim, not a document. A single battlecard may contain twenty claims, and only some of them overlap with another card. Measuring by document hides the conflicts inside the set. Measuring by claim shows exactly where the team agrees, where it diverges, and where no source exists.

Define the claim inventory

Extract each factual claim into a short normalized statement. A claim such as the competitor charges per seat belongs in the inventory with its source and the card where it appears. Normalize wording so that two sentences with the same meaning map to one claim. Keep the original wording beside the normalized version for verification.

Exclude claims that cannot be checked, such as the competitor is losing momentum. Those may be useful in a narrative but they are not part of a consistency audit. If the team wants to track them, use a separate category with a clear label. Mixing verifiable and unverifiable claims makes the audit impossible to interpret.

Assign each claim a stable identifier so the same claim can be tracked across audits. The identifier should not depend on the card or the page number, because those change. Use a short code based on the claim topic and a sequence number. A stable identifier turns a one-time audit into a trend.

Build a claim ladder

Group related claims into a ladder from broad to specific. A broad claim might be that the competitor targets enterprise buyers, while a specific claim might be that their entry tier caps named users. The ladder shows which claims depend on others. If the broad claim changes, the specific claims that rest on it need review.

Use the ladder to find gaps as well as conflicts. A card may make a broad positioning claim without any supporting detail, while another card has the detail but no source. The ladder makes both problems visible in one view. It also helps the reviewer avoid treating two claims as contradictory when they describe different tiers or segments.

Mark claims that are time-sensitive, such as a fee or a packaging limit. Those claims need a shorter review interval than a broad positioning statement. The ladder should show the review interval beside each rung. A time-sensitive claim without a date is a conflict waiting to happen.

Sample the battlecards

Include every card that sellers can reach, not only the newest set. Old cards often survive in saved folders and presentation decks. Record the card name, the owner, the last review date, and where it is stored. If the library has many cards, sample by competitor and by audience so the audit covers the combinations sellers actually use.

Note whether the card is current, archived, or unowned. An archived card with a conflicting claim is less urgent than an unowned card in the active library. The location and status of each card belong in the sample record. A conflict found only in an archive is a cleanup task, while a conflict in an active card is a live risk.

Record how sellers find the cards, not only where the cards are stored. A card that requires three clicks and a password is less likely to be used than one pinned in the sales tool. Access friction can explain why an old card survives. The audit should note the path a seller actually takes.

Code agreement and conflict

For each claim with more than one appearance, code the relationship as agree, conflict, or unclear. Agree means the claims are compatible after normalization. Conflict means they cannot both be true at the same time. Unclear means the wording is too vague to judge without more context. Record the evidence and the card locations for every conflict.

Have a second reviewer code a sample independently and compare the results. Most disagreements come from claims that describe different tiers or dates. Refine the normalization rule until the two coders can reproduce each other's decisions. The agreement level should be reported with the audit so the reader knows how much of the conflict count is solid.

Keep a short note for each claim that describes the tier and the observation date. A packaging claim for an entry tier may be accurate while a claim about the enterprise tier is not. The note prevents a later reviewer from forcing the two into a single statement. It also shows when a conflict is really a scope difference.

Test with sellers

Ask two or three sellers which claims they would use in a live objection. Their answers show which conflicts actually reach buyers and which ones sit in unused sections. A conflict in the positioning summary matters more than a conflict in an appendix nobody opens. Record the seller's choice and the reason they gave.

Do not ask sellers to resolve the factual conflict themselves. Their role is to report what they use and what buyers challenge. The fix belongs to the card owner and the source owner. This separation keeps the audit from turning into a debate about sales style rather than evidence.

Record the buyer's exact objection when a seller describes a conflict in use. The objection shows which part of the claim matters and how the competitor's change reached the deal. A conflict that never appears in an objection may be lower priority than the audit ranking suggests. The seller's report is evidence about use, not proof about the competitor.

Report the pattern

Report the number of claims reviewed, the number with multiple appearances, and the share that conflict. Break the result down by competitor and by claim type. A high conflict rate in packaging claims points to a different fix than a high rate in product capability claims. The breakdown should lead to a specific review task.

Include the unsupported claims that had no source at all. Those are not conflicts, but they are a related risk because a seller cannot verify them. List the top conflicts with the two card locations and the source that should settle each one. A report that only gives a percentage without the locations cannot be acted on.

Rank the conflicts by the size of the buyer decision they could affect. A conflict about a security certification is more serious than a conflict about a minor feature name. The ranking helps the owner fix the highest-risk claim first. Include the source that should settle each conflict, or state that no source exists.

Limits and sources of error

The inventory depends on what the reviewer can see, and some cards may be missing from the shared library. Claims in private decks or saved emails are outside the sample unless sellers share them. Record how the card list was assembled and what was excluded. The conflict rate is a lower bound if the sample missed active material.

The cited public sources describe market research and competitive analysis practice, business survey methods, and information protection. They do not provide an expected conflict rate for this team. Treat the audit as a local baseline and repeat it after the cards are corrected. Keep the claim definitions stable so the next audit measures the same thing.

Turn the audit into a review queue

Create a review queue with one item per conflict and one owner per item. Group items that share a source so one check can settle several claims. Set a due date based on the risk ranking rather than the order the conflicts were found. A queue makes the audit operational instead of leaving it as a report.

Close each item by updating the card and recording the source. If the source cannot be found, mark the claim as unverified and remove it from seller-facing material until it is confirmed. Re-run the audit after the queue is cleared and compare the conflict count. The reduction is the evidence that the review did something.

Related GTM research