What is a sales battlecard?
In our method, a sales battlecard is a one-page card a seller uses live on a call against one named competitor. It shows where they win, where you win, your honest weaknesses, three traps and the real objections. Each card serves one buyer seat, and every claim about the rival carries a source and a date.
Last updated by Omair Dawood.
What a battlecard contains
The method is our own: the battlecard skill behind our Battlecard tool. These are the parts of a card, in the order the method's output format sets them.
- A dated header. It gives the last-reviewed date and a review-by date 30 days out. It also names one buyer seat and the profile the card was built from.
- A one-line read. One sentence says who the rival is and when they show up in deals. If it takes two, the method sends you back to the profile.
- Where they win. Each line is something a buyer would really choose them for, with a public source and the date it was checked.
- Where you win. Your side meets the same standard, and each line maps to a claim already in your messaging.
- Your honest weaknesses. The card names at least one, in the same plain type as theirs. The method calls this the point of the card. The method's reason: a card that only flatters your side gets ignored the first time a buyer contradicts it.
- Three traps. These are the spots where a seller is about to get hit, each with what to do instead.
- The real objections. Each row holds the buyer's words, the honest answer, and when to walk. That is the point where the honest answer is "we are not the right fit".
- Discovery questions. Three to five questions surface the difference early, before the buyer frames the deal on the rival's terms.
- Claims cut for lack of proof. Any win you could not prove lands here, next to the evidence that would bring it back.
- Sources. Every claim about the rival has a source and a check date. A claim nobody can verify is marked UNVERIFIED or cut. Two sources that disagree go to a person, marked CONFLICT, ESCALATED with the date.
- A refresh log. Each review adds one line saying what changed.
All of it fits on one page. The method's reason: a two-page battlecard is a document nobody opens mid-call.
What it needs before it starts
The method will not write a card without three inputs. The first is a competitor profile no older than 30 days, with every claim sourced and dated. The second is your current messaging, or at least a positioning statement, so the card points at language you already use. The third is a set of real objections from calls that happened. If one is missing, the method names it, says who can supply it, and stops. A card is not a research pass, so our battlecard vs competitor profile guide treats the two as separate documents.
Worked sample: Linear's switch page, read as a card
In our view, real cards stay inside sales teams, so a public "switch to us" page is the closest public copy. Linear's switch page opens with:
"Switch to Linear"
"Linear is shaping how product teams build with AI."
"Here is the case for why now is the time to move."
Read on . Source: Linear switch page
The page shows the H1 in capitals; the HTML text reads as quoted. Further down, a stat block reads:
"3.3x"
"Faster issue resolution"
"Average increased based on data from companies with 50+ employees migrating from Jira, Asana, and GitHub Issues."
Read on . Source: Linear switch page
What the copy does well. The H1 says what the page is for in three words. The stat shows its base: who was measured and which tools they left. That base lets a seller say where the number came from, so it can start a "Where you win" line. The page names its rivals outright, and three of the four migration stories near the end name Jira. Its FAQ takes on a question about being under contract with a current tool.
What is missing, against the definition. The stat line covers three rivals at once, and a card serves one. Nothing on the page says where Jira wins, and nothing names a weakness on Linear's side. In our view, a buyer page needs neither, and a seller's card needs both. The page does not say the contract question came from a call. The method takes objections only from calls that happened, so it is a lead to check with sales. The page also speaks to several roles, where a card picks one seat.
The fix, as card parts. Here is what a card against Jira could take from this page. Each open slot stays a question, because the public page cannot answer it.
| Card part | From the page | Still open |
|---|---|---|
| Header | Competitor: Jira. Last reviewed 2026-10-14, review by 2026-11-13 | [one buyer seat: needs a choice] |
| Where you win | "3.3x" "Faster issue resolution", checked 2026-10-14. The page's base covers Jira, Asana and GitHub Issues together | [a Jira-only figure, and the messaging claim it maps to] |
| Where they win | nothing | [what buyers choose Jira for: needs a dated public source] |
| Honest weaknesses | nothing | [needs field signal from won and lost deals] |
| Real objections | the contract question, as a lead only | [the buyer's words: needs real calls], plus when to walk |
| Traps and discovery questions | nothing | [needs call evidence] |
Common mistakes
- One card for every buyer. Our tool's reason for one seat per card: a practitioner and an executive fear different things. Write the card for one seat, and if one picks and the other signs, say which one it serves.
- One card for three rivals. The method builds one competitor per card.
- Serving a stale card quietly. The method sweeps every live card each month. A card past its review-by date, or whose rival has launched or changed pricing, gets flagged as stale.
- Writing a new pitch on the card. Counter-language comes from your existing messaging. The method invents no new positioning claims on a card.
- Running down what the buyer owns. The method never discredits a product the buyer already has.
Questions people ask
What should I know before making my first battlecards?
Start with the rival that shows up in your real deals. The method's test is that the card would be opened rather than filed. Gather the three inputs first: a dated profile, your messaging and real objections. Then give it the parts above, and never skip two of them: your honest weaknesses and the when-to-walk line on every objection.
What is a sales battlecard used for?
In our method, a card is for a live call against one named rival. The method builds or refreshes one in four cases. A named competitor appears in a real deal, or sales asks how to sell against a rival. A live card passes 30 days, or its rival has launched or changed pricing. Win-loss findings contradict what a live card says.
How long would it take to build battlecards from scratch?
The method sets no time. It sets an order: one dated profile per rival, then the card, then a review by someone other than the author. Our Battlecard tool asks for about 3 minutes of typing per card and runs the research step itself.
Sources
- Linear switch page, Linear, https://linear.app/switch, read 2026-10-14
- Google results for "what is a sales battlecard" (People also search for, Reddit result), https://www.google.com/search?q=what+is+a+sales+battlecard, read 2026-10-14
- r/ProductMarketing thread "Gonna make my first battlecards. What should I know about ...", as listed in Google results, https://www.google.com/search?q=%22Gonna+make+my+first+battlecards%22+reddit+ProductMarketing, read 2026-10-14
- Our battlecard method skill and the Battlecard tool on this site (ours, read 2026-10-14)
Build one with the Battlecard tool
Name one rival, or leave the name and website blank and the tool picks the closest competitor, or the standard product buyers compare you to. It asks for your positioning or messaging, and two or more objections buyers actually say, one per line. The buyer seat is optional; skip it and the card speaks to the person who picks the tool. You get a dated profile of the competitor and where each side wins. You also get three traps, the real objections, and questions to ask on the call. It takes about 3 minutes of typing.