Battlecard vs competitor profile
In our method, a competitor profile is the dated research file on one rival: how it describes itself in its own words, its claims, its pricing, the buyers its copy reveals and where it beats you. A battlecard is the one-page card a seller opens on a live call, built from that profile. The profile comes first.
Last updated by Omair Dawood.
The difference, side by side
The table compares the two as our own competitor-profile and battlecard methods define them. Both run inside the Battlecard tool on this site.
| Competitor profile | Battlecard | |
|---|---|---|
| Its job | Say what is true about one rival right now, in a form that stays useful for a month | Help a seller on a live call against that rival |
| Who uses it | Whoever builds on the evidence: a battlecard, a positioning argument, a pricing call | A seller, mid-call |
| Starts from | The rival's public pages, fetched live and dated | A verified profile no older than 30 days |
| Refuses to run without | One named rival, its public site reachable that session, the question the profile answers, today's date, and who you sell to and how you position | A current profile, your current messaging, real objections from calls that happened |
| Their positioning | Quoted word for word, never paraphrased | A one-line read of who they are and when they show up in deals |
| Where they beat you | At least two places, each with evidence a buyer would act on | Where they win, plus at least one honest weakness on your own side |
| Objections and traps | None. That is the card's job | Three traps, and real objections with a when-to-walk line |
| Length | No page limit in the method | One page |
| Shelf life | Review-by date 30 days out | Review-by date 30 days out, plus a refresh log |
Both methods share one sourcing rule. Every claim about the rival carries a public source and a check date. Anything unverifiable is labelled UNVERIFIED, and the card may cut it instead.
How a profile turns into a card
These are the first five steps of our battlecard method, the one the Battlecard tool runs (read 2026-10-14). The method calls the card "a rendering of verified intel, not a fresh research pass". Each step below reads from the profile.
- Check the profile's date first. Read its review-by date and the rival's recent moves. If they launched, changed pricing or repositioned since it was written, refresh the profile before you start the card.
- Write the one-line read. Say who the rival is and when it shows up in deals, in one sentence. The method's test: if you need two, the profile has not answered its question yet.
- Copy where they win. Take it from the profile's section on where they genuinely beat you. Each line is something a buyer would choose them for, with a dated public source.
- Hold your side to the same standard. Each win needs evidence and maps to a claim already in your messaging. A win you cannot prove moves to "claims cut for lack of proof".
- Name at least one honest weakness. Write it in the same plain type as theirs. The method calls this the point of the card.
Steps 6 to 8 add what a profile does not hold: three traps, honest answers to real objections, and discovery questions. Steps 9 to 11 check sources, cut to one page and save with a refresh log. The full walk-through is on our battlecard how-to guide.
Worked sample: one Atlassian page, read for both
In our view, a vendor's public comparison page is the closest public copy to either document, since real profiles and cards stay inside companies. Say you sell against Jira. Atlassian's Jira vs. Asana page opens with this:
"Jira vs. Asana"
"Jira is a project management tool built for every team – from Marketing to Operations to Engineering – to plan and track work. See how it stacks up against Asana."
Read on . Source: Atlassian, Jira vs. Asana. Above the H1, a line reads "Last updated January 2025" (shown in capitals on screen).
Further down, a section headed "Bring context to your projects" says:
"Jira integrates with Confluence and Loom to connect everything in one place."
"These first-party integrations are only available in Jira, not Asana."
Read on . Source: Atlassian, Jira vs. Asana
What the copy does well. The hero names a category, "project management tool", and the rival in its first two sentences. That is the self-description profile step 2 asks you to quote. "Built for every team" with three named teams gives the profile's section on who their copy targets its first piece of evidence. In our reading, the integrations line is the strongest claim on the page for a profile, because it names two products and says which side lacks them. A reader can check it. The page also dates itself.
What each document can take, and what it cannot. The profile takes the integrations line as claimed differentiation, with the two named products as its evidence. The profile method takes headline quotes from the homepage and about page, so this hero is a supporting quote. Its section on who they target needs three pieces of evidence, and this page gives one. The card can take nothing until that profile exists. Even then, no Atlassian page can tell you your own weakness, your traps or what your buyers say on calls.
The fix: both read-outs, filled from the page. Each slot uses the page's words or stays a question.
# Competitor profile: Atlassian (Jira)
Date: 2026-10-14 Review by: 2026-11-13 (30 days)
Question this answers: [the commissioning question: needs an owner]
## Identity and positioning, in their words
> "Jira is a project management tool built for every team – from
> Marketing to Operations to Engineering – to plan and track work."
Source: atlassian.com/software/jira/comparison/jira-vs-asana
Fetched: 2026-10-14. Page says "Last updated January 2025".
Category they claim: project management tool
[homepage headline: fetch Jira's homepage and quote it]
## Claimed differentiation
| Their claim (quoted) | Evidence they attach | Source | Fetched |
|---|---|---|---|
| "These first-party integrations are only available in Jira,
not Asana." | Names Confluence and Loom | same page | 2026-10-14 |
# Battlecard: Jira
Last reviewed: 2026-10-14 Review by: 2026-11-13 (30 days)
Built from: [the profile above, once every section is filled]
## One-line read
[when Jira shows up in your deals: needs deal evidence]
## Where they win
- First-party Confluence and Loom integrations. Source: the Jira vs.
Asana page, checked 2026-10-14. [Check against your own product.]
## Our honest weaknesses against them
- [needs your own product's facts]
## The real objections
| [buyer's words: needs real calls] | [honest answer] | [when to walk] |The open slots show the order. The profile fills from public pages. The card fills from the profile, your messaging and your calls.
Common mistakes
- Building the card first. The card method refuses to run without a profile no older than 30 days. Build or refresh the profile, then the card.
- Profiling from memory. If the rival's site cannot be fetched live, the profile method stops. The method's reason: a profile from memory is worse than none, because it looks sourced.
- Paraphrasing their positioning. Quote the headline and category line exactly. The method's reason: a paraphrase turns their positioning into your reading of it.
- Putting three rivals in one file. Both methods cover one named competitor. Three rivals means three profiles and three cards.
- Loading objections into the profile. The profile feeds the card and does not replace it. Real objections and their when-to-walk lines live on the card.
- Smoothing a conflict. Both methods ban "reportedly" and "some users say" as cover for sources that disagree. Escalate it and mark it with the date.
Questions people ask
What is the difference between a competitor profile and a battlecard?
In our method, the profile is the evidence and the card is what a seller uses. The profile quotes the rival's positioning, records its claims, pricing and buyers, and names where it beats you. The card turns that into one page for a live call: where each side wins, your honest weakness, three traps and real objections.
What is a competitor profile?
In our method, a competitor profile is a sourced file on one named rival that answers one question someone asked. It quotes how they describe themselves, lists their claimed differentiation with the evidence attached, and records public pricing or says it is not public. It reads who they sell to from their own copy, dates their recent moves and names at least two places they genuinely beat you.
Is a battlecard the same as a competitor analysis?
No, in our method. Our profile method treats a comparison across several vendors as a different deliverable, and covers one rival per file. The battlecard comes after the profile, for one rival and one buyer seat. For a cross-vendor view, run one profile per name.
Sources
- Atlassian, Jira vs. Asana, https://www.atlassian.com/software/jira/comparison/jira-vs-asana, read 2026-10-14
- Google results for "battlecard vs competitor profile" (People also ask), https://www.google.com/search?q=battlecard+vs+competitor+profile, read 2026-10-14
- Our battlecard and competitor-profile method skills and the Battlecard tool on this site (ours, read 2026-10-14)
Get a profile and a card from the Battlecard tool
Name one rival, or leave both fields blank and the tool picks the closest competitor, or the standard product buyers compare you to. It researches them first and writes a dated profile before it starts the card. It asks what you say about yourselves, and for 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, where they win and where you win, three traps and the real objections, and questions to ask on the call. It takes about 3 minutes of typing.