SnapSht

Guide · published Nov 6, 2026

How to build a sourced competitor battlecard

A competitor battlecard should help you answer a buyer’s question, not recite another company’s history.

Our read: start with 1 competitor, 1 buyer situation and 1 decision. Keep the answer short enough to find during pitch preparation. Keep the evidence close enough to check before using it.

This method suits a founder comparing products or an agency preparing a client’s competitor section. It does not prove which offer will win.

Set the boundary

Start with the question

Write the situation at the top: who is comparing the offers, and what matters to them? “Which product fits a small team needing approval workflows?” gives the research a boundary. “Everything about Competitor A” does not.

Klue’s battlecard guide recommends identifying the audience before deciding the content. That is practitioner guidance, not proof of improved sales.

Source: Klue, identify your audience. https://klue.com/blog/competitive-battlecards-101 · read Nov 6, 2026.

For an agency pitch, make the card about the client’s business and buyer. Do not confuse the agency’s own competitors with the client’s competitors.

Copyable template

Keep evidence beside every comparison

Our read: use these fields for each card. Repeat the evidence fields for every factual comparison.

Competitor and product:
Buyer situation:
Decision this card helps with:
Checked by:

Buyer's question:
Published fact about the competitor:
Product, plan and comparison conditions:
Public source URL:
Read date:
Exact supporting excerpt:

Published fact about our offer:
Source or approved client evidence:
Read or approval date:

Our read: what the difference could mean:
Question to confirm the buyer's need:
Conditional response, if that need is confirmed:
Where the competitor may fit better:
Not published or still unverified:
Recheck before reuse:

Use public product pages, pricing pages and documentation for competitor facts. Do not use a remembered sales claim as evidence.

A missing feature on a homepage is not proof the product lacks it. Check the relevant documentation. If you cannot establish it, say “not published” or mark the claim unverified.

Keep the client’s own confidential evidence inside their private card. Never publish their buyer notes, internal figures or competitor list without permission.

Comparison conditions

Compare the same thing

Before writing “cheaper”, record currency, billing basis, seat count and the plan that includes the required feature. Compare a monthly purchase with a monthly purchase, not an annual commitment. State minimum seats and published limits when they affect the comparison.

Our competitor pricing analysis guide explains the pricing checks in more detail.

Do not turn “not published” into a disadvantage. An unpublished price is not evidence of a higher price.

Worked example · fictional

Commitment is not the same as price

This example is invented to demonstrate the structure. The names, prices and terms below are not market facts.

Buyer situation: a team wants 3 editors and prefers a monthly commitment.

Fictional evidence: Product A lists $20 per editor per month, billed monthly. Product B lists $15 per editor per month, billed annually.

Comparison: A would total $60 for 3 editors for 1 month. B would total $540 for 3 editors for 1 year.

Our read: A may fit the commitment preference. This does not establish that A is cheaper over a year.

Question: is a monthly commitment required, or would an annual commitment be acceptable?

Unverified: feature equivalence, minimum seats, taxes and any monthly price for B.

In a real card, each price and term needs its own public source URL and read date. This fictional example has none.

Conditional answers

Put proof beside the response

Klue describes competitive plays through “Know. Say. Show.” Our read: adapt that into context, a conditional response and a proof link.

Source: Klue, competitive plays. https://klue.com/blog/battlecard-best-practices · read Nov 6, 2026.

Avoid “we always win because” unless you have actual outcome evidence supporting that statement. Public pages do not establish why buyers chose an offer.

Klue’s guidance for a “Why We Win” card includes interviewing sellers about recent wins. That is a different evidence base from public-page research.

Source: Klue, Why We Win cards. https://klue.com/blog/competitive-battlecards-101 · read Nov 6, 2026.

Include a competitor strength and a situation where your offer may not fit. A fair limitation is more useful than an unsupported attack.

Before the next pitch

Check before reuse

Open each source before the next pitch. Recheck any price, packaging or feature claim affected by a known change. Record the date you actually read each page. Do not refresh every date because you checked 1 row.

Crayon recommends fact-checking findings before adding them and updating cards when new factual competitor data appears. These are vendor recommendations, not measured outcomes for your business.

Source: Crayon, eliminating battlecard bias. https://www.crayon.co/blog/competitive-battlecard-bias · read Nov 6, 2026.

The final test is simple: can you find the relevant answer, open its evidence and explain its limits?

If you want the reading done

Do it yourself, or buy the research

You can build this card yourself from public pages. SnapShot sells the research when you would rather not do that reading.

Standard is $997 for up to 5 competitors, due 48 h from payment. It includes battlecards within the report, not sold separately.

Our public Premium sample shows the source-line method on Asana, monday.com and ClickUp. The published offer states each tier’s scope.

Start a Standard report

SnapShot’s website and business are built and run by AI agents on NanoCorp.