How to build sales battlecards from traceable evidence
A battlecard is trustworthy when every line links to a claim with a source and a date, and when contested claims are phrased as questions to ask, not facts to state. Reps stop using cards that were wrong once, so the first mistake is expensive.
Start from approved insights
A card is an action, so it should come from an insight someone has reviewed. If the insight is still a draft, the card is a draft. Build cards from approved insights and put the insight's review date on the card.
A card structure that fits on one page
- Where they win, with the claim behind each point.
- Where we win, with the claim behind each point.
- Questions to ask the buyer, each tied to a contested or unverified claim.
- Landmines: things Meridian will say that are true.
- Last checked date and the name of the reviewer.
Rules for wording
- Supported claim: state it, and cite the source and date in the notes.
- Contested claim: turn it into a question. “How many client accounts will you need to import?”
- Unverified claim: leave it off the card, or put it in an internal-only note.
- Stale claim: re-check it before the card ships.
A worked example
| Card line | Claim status | Evidence |
|---|---|---|
| Meridian's Team plan is $59 per seat per month with a 10-seat minimum. | Supported | Pricing page, 2026-10-09 |
| Ask: “How many client accounts need migrating, and who does the import?” | Contested (onboarding speed) | Vendor page vs three-week review |
| Meridian removed its free plan. | Unverified | One forum post; not on the card |
| Meridian's reporting export is strong. | Supported | Docs page and two reviews. Landmine entry |
The unverified claim stays off the card until the pricing history or the changelog confirms it. A rep who says it on a call and is corrected by the buyer loses the room.
Keeping cards current
- Put the pricing page and changelog of each named competitor on a watchlist.
- When a change is detected, check which card lines depend on the changed claim.
- Update the card and its date, and tell the team what changed in one sentence.
What the rep should be able to do on a call
When a buyer challenges a line, the rep should be able to say where it comes from and when it was checked. If the card cannot support that, the line does not belong on it.
Who reviews a card before it ships
Ask one person who sells against the competitor and one who built the research to read the card. The first checks that the wording works in a real conversation. The second checks that each line still matches its claim. A card that passes both is ready.
Battlecards in Sigblaze
Sigblaze creates battlecard actions from approved insights and keeps the link to the claims and sources behind each line. Cards can be exported as Markdown or JSON. Automatic distribution to sales tools is not available.
Questions
Should a battlecard cite sources to the buyer?
Not on the card the buyer sees. Keep citations in the internal notes so the rep can answer a challenge, and share a source only when it is public.
This piece contains no external statistics. Fieldnote and Meridian are fictional companies, and the figures in the examples are synthetic.