Build a competitor battlecard
One dated page per competitor from public pricing, docs, changelogs and reviews, with an honest when they win and when you win.
competitor-battlecard/SKILL.mdDownload- name
competitor-battlecard- description
- Use this skill when a competitor keeps showing up in your deals and sellers need a fair, current answer. It builds a one-page battlecard from public sources only (pricing pages, docs, changelogs, reviews, filings), dates every fact, and states honestly when they win and when you win, with questions and answers a seller can use on a call.
- license
- CC-BY-4.0
Build a competitor battlecard
A battlecard is only useful if sellers trust it, and they stop trusting it the first time a prospect corrects them. This skill builds one page on one competitor from what the competitor publishes and what its customers say in public, dates every fact, and is honest about where the competitor is the better choice. Use it when a competitor appears in three or more deals, or before a seller's first call against it.
Inputs
- The competitor: name and website.
- Your product: what you sell, and the segment where you meet this competitor most.
- Your evidence, optional: notes from deals won or lost against them, call notes, or what prospects said about them. Kept apart from public facts.
- Who will use the card: new sellers need more context than a team that knows the market.
Steps
- Fix the scope. One competitor, one segment, today's date at the top. A card that covers every segment says nothing useful about any of them.
- Read their own pages. Open and date each one:
- Homepage: their one-line claim, quoted in their words.
- Pricing page: plans, prices, limits and what each plan includes. If it says "contact sales", write that.
- Docs or help center: setup steps, integrations, limits, requirements.
- Changelog or release notes: what shipped in the last six months.
- Customer stories: which industries and company sizes they show.
- Careers page: what they are hiring for, which shows where they invest.
- Check what changed. Look up older copies of the pricing page in the Wayback Machine. Its availability API (
https://archive.org/wayback/available?url=[page]×tamp=[YYYYMMDD]) returns the closest archived snapshot to a date. Note any price or plan change with both dates. - Read what customers say. On the review sites of your category, sort by most recent and read at least 20 reviews from the last 12 months. Count recurring praise and complaints. A pattern needs at least three reviews; one review is an anecdote. Quote short phrases with the link and date.
- Public company? Read its latest annual report in SEC EDGAR for its segments, strategy and stated risks.
- Add your evidence, labeled. Put deal notes in their own column, marked internal. Never mix them with public facts.
- Write when they win. From their strengths in the sources and from the deals you lost. If you cannot find a real case where they are the better choice, you have not looked hard enough.
- Write when you win. Only where your product does something they do not, or does it under conditions they cannot meet, with the proof a seller can show.
- Write the call kit. Their likely claims with a factual answer and a source; discovery questions that surface a fit gap fairly; the one thing never to say.
- Set a review date, 90 days out, because pricing pages and changelogs move.
Without web access, ask the user to paste the pricing page, two help articles, the changelog and a handful of reviews, and build the card from those.
Output
# Battlecard: [competitor] in [segment], [date]
Review again by: [date + 90 days]
## In their words
"[homepage claim]" ([link], opened [date])
## Pricing, as published on [date]
| Plan | Price | Includes | Limits |
|---|---|---|---|
Changes seen: [old price or plan] on [date] to [new] on [date]
## What shipped recently
- [date]: [release], [link]
## What customers say (review sites, last 12 months)
| Pattern | Reviews | Example quote, link, date |
|---|---|---|
## When they win
- [situation], because [fact], [source]
## When we win
- [situation], because [fact], [proof to show]
## Call kit
| They say | Our factual answer | Source |
|---|---|---|
Questions to ask: ...
Never say: ...
## Internal evidence (not public)
- [deal, date, what happened]Guardrails
- Reads: the competitor's public pages, public reviews, public filings, and the deal notes the user shares.
- Writes: nothing outside the conversation unless the user asks for a file.
- Asks before: sharing the card outside the sales team, and using any deal note that names a prospect.
- MUST date every fact and link its source.
- MUST quote the competitor's claims in their own words, not paraphrase them into something easier to attack.
- MUST include a real "when they win" section.
- NEVER use confidential material: leaked decks, a former employee's knowledge, or anything shared under NDA.
- NEVER sign up for a trial or ask for a demo under a false identity.
- NEVER state a price, limit or feature you did not read on a source today, and never disparage the competitor or its people.
Sources
- Wayback Availability JSON API, Internet Archive: the closest archived snapshot of a page.
- EDGAR full text search, US Securities and Exchange Commission: annual reports and other filings of public companies.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit