Contend Guide 9 min read By the Contend team

How to Build a Competitor Battlecard That Sales Reps Actually Trust

The 4-Layer Battlecard framework — Snapshot, Strengths, Landmines, Plays — plus the data system that keeps the card current instead of stale within a quarter.

Framework: The 4-Layer Battlecard 7 steps 7 FAQs

TL;DR

Most battlecards rot within 30 days because the underlying data goes stale faster than the review cycle. The 4-Layer Battlecard separates the slow-changing parts from the fast-changing ones: Snapshot (ICP, pricing, funding, headcount), Strengths (where they actually win, sourced from G2 reviews and win/loss), Landmines (where you lose deals to them, sourced from CRM closed/lost analysis), and Plays (per-objection responses with proof points). The structure is the easy bit; keeping it current is the hard bit. Contend acts as the data layer — feeding pricing, funding, hiring, integration, and feature signals into the card continuously so the facts behind it never go three months old.

The playbook in 7 steps

High-level checklist. Detailed working method below.

  1. Pick competitors from CRM closed-lost data, not slide decks

    Pull twelve months of closed/lost opportunities and rank by deal value lost to each named competitor. Build cards for the top three to five. Aspirational competitors (the ones in your investor deck) almost never need cards; the ones reps actually lose to do.

  2. Build Layer 1 — Snapshot

    Capture ICP, public pricing, funding history, founding year, headcount, and a one-line positioning statement. Source from Crunchbase, the competitor pricing page, LinkedIn, and review-site buyer profiles. Roughly 30 minutes per competitor — do all five at once with the same tabs open.

  3. Build Layer 2 — Strengths from buyer behaviour, not marketing copy

    Read four- and five-star G2 and Capterra reviews, run two or three win/loss interviews with prospects you lost, and study which industries the competitor's case studies keep showcasing. A real strength is a place buyers chose them and were happy — not a homepage bullet.

  4. Build Layer 3 — Landmines from honest closed-lost analysis

    Filter your CRM to deals lost to this competitor. Read every note. Pull the recurring patterns — missing integration, lower-tier price, prior buyer relationship — and write each as a single sentence a rep can spot during qualification. This is the highest-value layer and the one most teams sanitise into uselessness.

  5. Build Layer 4 — Plays paired with current proof points

    For every landmine, write the prospect question, the one-sentence rebuttal, and a proof point (a customer name, a stat, a specific feature gap). Source rebuttals from the calls your top reps already win — listen to three calls a quarter and write the patterns down.

  6. Distribute where reps already work and assign per-card owners

    Ship as a single-page PDF in the sales enablement folder and as a structured page on opportunities in your CRM. Avoid buried Notion pages and shared Google Docs — reps don't open them mid-call. Assign one owner per card, usually the AE who wins most against that competitor.

  7. Trigger updates from competitor signals, not the calendar

    Wire the card to a continuous signal feed — Pulse, email digest, or Slack alerts — so a pricing drop, funding round, executive hire, or feature launch flags the card as stale within hours, not at the next quarterly review. Calendar-driven reviews catch monthly drift; signal-driven reviews protect rep trust.

Why battlecards rot

Most battlecards are dead on arrival. The PDF is uploaded to the sales wiki, opened twice in week one, and never touched again. By the end of the first quarter, the pricing on it is wrong, the integrations list is missing the two that shipped last month, and the "departing executive" landmine is about a person who has been at a different company for half a year. Reps stop trusting the card, fall back on instinct, and the sales enablement team quietly stops maintaining what nobody reads.

The decay is not a discipline problem. It is a structural one. A battlecard is a snapshot of a moving target — and the target moves. Competitors raise rounds, change pricing, ship features, lose VPs of Sales, sign partnerships, and quietly deprecate plans every week. A document built once and reviewed quarterly cannot keep up with a competitor whose product team ships every fortnight.

The teams who get battlecards right do two things differently. First, they pick a structure that separates the slow-changing parts (snapshot, deep strengths) from the fast-changing parts (recent landmines, current plays). Second, they wire the card into a continuous signal feed so the fast-changing parts update without a human remembering to check. Everything below is a working method for both halves — manual first, then where automation actually helps.

The 4-Layer Battlecard

A battlecard is not a competitor profile. A profile is for analysts. A battlecard is a tool a rep opens during a live deal — three minutes before a call, sometimes three seconds before a question — and needs an answer from. That constraint shapes the structure. Anything not directly used in a deal is overhead.

The 4-Layer Battlecard separates the four jobs a rep actually needs help with: knowing who the competitor is, knowing where they win, knowing where you lose to them, and knowing what to say when objections fire. Each layer is sourced from a different place and updates on a different cadence.

Layer 1 — Snapshot

The 30-second briefing. A rep glances at this when a prospect mentions the competitor for the first time on a discovery call. It contains: ICP (who they sell to — segment, geography, company size), public pricing (plan names, prices, billing model), funding history (rounds, investors, last raise date), founding year, headcount, and one-line positioning.

Where to source: Crunchbase for funding and headcount, the competitor's pricing page for plans and prices, LinkedIn for current employee count, the competitor's About page for founding year and ICP language, and review sites for who actually buys.

Update cadence: monthly is fine for most fields. Pricing and funding need to be flagged the moment they change — those are the two snapshot fields most likely to come up live in a deal.

Layer 2 — Strengths

Where the competitor genuinely wins. This is the layer most teams get wrong by listing what the competitor claims to do well — copy-pasted from their homepage. That is marketing, not a strength. A real strength is a place a buyer chose them over you and was happy with the choice.

Where to source: G2 and Capterra reviews (filter four and five stars, read the "what do you like best" field), win/loss interviews with prospects you lost to them, case studies on their site (read which industries and use cases they keep showcasing — that is where they are concentrating wins), and the integrations directory (deep integrations with tools your prospects already use are a structural strength).

Update cadence: quarterly. Strengths are slow-moving. A new flagship integration or a string of glowing reviews in a vertical you don't serve well is the trigger to update.

Layer 3 — Landmines

Where you lose deals to them, and what triggers that loss. This is the highest-value layer — and the hardest to build, because it requires honest analysis of your own losses. Most teams skip it or sanitise it. Don't.

Where to source: your CRM closed/lost notes, filtered to deals where the competitor was the named winner. Read every note. Pull the recurring patterns: "they had a native Salesforce integration we don't"; "their lower-tier plan is half ours"; "the buyer's CFO had used them at a previous company." Each pattern is a landmine. Write each one as a single sentence the rep can spot during qualification.

Update cadence: continuously. A pricing drop, a new integration, an executive hire from a customer of yours — any of these flips a new landmine into existence. This is the layer most likely to go stale and the one that hurts most when it does.

Layer 4 — Plays

Per-objection responses. For every landmine in Layer 3, write the play: the question the prospect will ask, the one-sentence answer, and a proof point (a customer name, a stat, a side-by-side feature comparison). No marketing prose — the rep is reading this on a Zoom call with their video off.

Where to source: the AEs themselves. The best plays are the ones top reps already use intuitively in deals they win. Sit on three calls a quarter, listen for the rebuttals that land, and write them down. Pair every play with a proof point — a customer logo, a benchmark, a specific feature gap on the competitor's side that you can point to.

Update cadence: monthly. Plays decay when proof points go stale (the customer churned), when the competitor closes the gap (they shipped the integration you were beating them with), or when the landmine itself shifts. A play without a current proof point is worse than no play — it makes the rep look unprepared.

The manual build process

Pick the right competitors

A battlecard for a competitor you don't actually lose deals to is wasted effort. Pull your closed/lost CRM data for the last twelve months and rank competitors by deal value lost. The top five — sometimes top three — are the only ones worth a card. Aspirational competitors (the ones in your slide deck) almost never need cards; the ones you tell investors you don't compete with often do. See How to find your real competitors for the discovery method.

Source the data

Build each layer from the sources above in parallel rather than card-by-card. It is faster to do all five Layer-1 snapshots in one sitting (same Crunchbase tab open, same pricing-page method) than to do one whole card end-to-end. A working pace: Layer 1 takes ~30 minutes per competitor, Layer 2 ~60 minutes (reading reviews is the slow bit), Layer 3 ~90 minutes (CRM mining), Layer 4 ~45 minutes if you can pull rebuttals from existing call recordings.

Distribute and review

Battlecards live where reps already are. The two formats that work are a single-page PDF in the sales enablement folder, and a structured page in your CRM (Salesforce, HubSpot) attached to opportunities tagged with the competitor. Avoid: shared Google Docs (nobody opens them mid-call) and Notion pages buried three folders deep. Set a calendar reminder to review every card monthly, with named owners — battlecards without an owner go stale within a quarter.

Where most battlecards die

Four failure modes account for almost every dead battlecard:

  1. Static PDF, never versioned. Someone built a beautiful PDF in Q1, emailed it round, and nobody touched it again. The PDF is on three different laptops with three different revision dates. By Q3 nobody knows which one is current.

  2. Quarterly review cycle. A 90-day refresh cadence is fine for the snapshot layer and disastrous for landmines and plays. The competitor's pricing changed in week two of the quarter and the card was wrong for eleven weeks.

  3. Reps trust gut over the card. When the card is wrong even once on a live call, a rep stops trusting it. They go back to instinct, the card stops getting opened, and the maintenance work feels pointless to whoever is doing it. The trust gap is hard to recover.

  4. No update trigger when the competitor moves. The card refreshes on a calendar, not on competitor activity. A new round of funding, a major hire, a feature launch — none of these automatically flag the card as stale. The team finds out from a prospect.

The first three are process problems. The fourth is the one tooling actually solves.

Or use Contend (as the data layer)

Most battlecards rot because the data behind them goes stale. Contend keeps the data current so you don't have to.

Contend does not generate battlecards for you. The team still owns the message — the plays, the tone, the rebuttals only your reps know how to land. What Contend does is feed the underlying facts into the document continuously, so when a rep opens the card the snapshot pricing is from this week, not last quarter, and the landmines reflect what the competitor actually did three days ago.

What Contend feeds into your battlecard:

  • Snapshot (Layer 1) ← pricing page changes, funding_round announcements, page updates (about/leadership), social_profile changes, headcount signals from job_posting volume.
  • Strengths (Layer 2) ← case_study and case_study_directory updates (which industries they're winning in), integration and integration_directory additions (structural moats forming), content_feed themes (where they're investing in thought leadership).
  • Landmines (Layer 3) ← pricing changes (especially plan additions or removals at lower price points), feature launches that close gaps you used to win on, job_posting for senior roles signalling strategy shifts (a new VP of Sales = aggressive motion incoming), news_article and press_release coverage of major customer wins in your segment.
  • Plays (Layer 4) ← updated feature comparison report views (differences, gaps, strengths) plug straight into per-objection responses; the pricing comparison report keeps the price-objection play current without anyone refreshing a spreadsheet.

How updates reach the team:

  • Pulse feed — every detected change lands in a single chronological stream at /app/{account}/pulse, filterable by competitor, signal type, and importance. Sales enablement scans it weekly to flag what needs cards updated.
  • Email digest — daily or weekly, configurable per recipient, filterable by competitor, signal type, and importance. Send it to AEs, sales engineering, product marketing, or whoever owns each card.
  • Slack alerts — real-time channel notifications the moment something material changes (Pro and Enterprise plans). Wire a #competitive-intel channel and the team finds out about a competitor's pricing drop within minutes, not at the next quarterly review.
  • MCP server — Claude Desktop, ChatGPT, Cursor or any MCP-compatible client can query competitors, pulse, pricing, and features conversationally. A rep can ask "what changed at Linebase in the last 30 days?" before a call and get a sourced answer.

What you still own:

The team writes the plays. The team writes the messaging. The team picks the proof points and the tone of voice. Contend just makes sure the underlying facts on the card — the prices, the headcount, the integrations, the recent moves — are not three months old. The card stays trusted because the data behind it stays trustworthy.

Get a free competitive landscape report →

Common mistakes

  • Building cards for competitors you don't actually lose to. The slide-deck competitor list and the CRM closed/lost list are rarely the same. Build cards from the second list.
  • Confusing strengths with claims. A homepage bullet is not a strength. A pattern of happy customers in a specific vertical is. Always source Layer 2 from buyer behaviour, not competitor marketing.
  • Skipping landmines because they feel uncomfortable. Sanitised landmines are worse than no landmines — they give reps false confidence and they get blindsided on calls.
  • Plays without proof points. "We have better integrations" is not a play. "We have a native Salesforce integration; their setup requires Zapier and a paid middleware tier — see the [customer name] case study" is a play.
  • One owner for all cards. Sales enablement owning every card means nothing gets updated when sales enablement is busy. Assign one owner per card — usually the AE who wins the most against that competitor.
  • Reviewing on a calendar, not on signals. A monthly review catches what changed in the last month. A signal-triggered review catches what changed in the last hour. The second one is what stops trust erosion.
  • Treating the card as a deliverable, not a system. The card is the artefact; the system is the data feed, the owners, the review cadence, and the trigger for updates. A beautiful artefact on top of a broken system rots in 30 days.

More guides in this series are coming. Working on a related problem — finding your real competitors, keeping pricing intel current, distributing landmines through Slack? Tell us what to write next.

Frequently asked

How often should you update a competitor battlecard?
It depends on the layer. Snapshot fields like ICP and headcount tolerate monthly review. Strengths are slow-moving and quarterly is fine. Landmines and Plays decay fastest — pricing changes, new integrations, executive hires, and feature launches all flip a landmine into existence overnight. The teams who get this right do not run on a single review cadence; they update the fast-changing layers continuously when signals fire and the slow layers on a calendar.
Who should own competitor battlecards — sales enablement or product marketing?
Both, with named owners per card. Sales enablement owns the format, distribution, and the review cadence. Product marketing owns the strategic narrative — Layer 4 plays especially. The card itself should have one named owner, usually the AE who wins most against that competitor, who is responsible for flagging when it goes stale. Diffuse ownership ("the team owns it") is the most reliable predictor of a dead battlecard.
How long should a battlecard be?
One page. A rep is opening the card mid-deal, sometimes mid-call. Anything that does not fit on one screen is overhead. The 4-Layer structure forces concision — Snapshot in five fields, Strengths in three to five bullets, Landmines as single-sentence triggers, Plays as question-rebuttal-proof point. Long-form competitor profiles are a different artefact for a different audience (analysts, leadership) and should not live alongside the card reps actually use.
What is the difference between a battlecard and a competitor profile?
A competitor profile is for analysts and leadership — a comprehensive document covering history, financials, strategy, and market position. A battlecard is for AEs in live deals — a one-page tactical reference optimised for being opened three minutes before a call. Profiles update quarterly. Battlecards update on signals. Mixing the two is the most common authoring mistake; reps stop opening profile-length battlecards within weeks.
How does Contend help with battlecards?
Contend does not generate battlecards — the team still authors the message, the plays, and the tone. What Contend does is keep the data behind the card current. It continuously monitors around twenty signal types per competitor (pricing, funding rounds, integrations, case studies, job postings, features, news, press releases) and routes detected changes to a Pulse feed, daily or weekly email digest, or real-time Slack alerts on Pro and Enterprise plans. Feature and pricing comparison reports plug into Layer 4 plays directly.
What's the difference between Contend and a battlecard tool like Klue or Crayon?
Klue and Crayon are battlecard authoring and distribution platforms — they help you write the card, version it, and surface it inside Salesforce or Slack. Contend is the data layer underneath. It captures the competitor signals (pricing changes, hires, launches, funding) that should trigger a card update in the first place. The two are complementary: many teams use Contend for the continuous intelligence feed and a dedicated battlecard tool for authoring and distribution. Smaller teams often run battlecards as PDFs or CRM pages and use Contend alone.
How do you build a battlecard for a competitor with hidden pricing?
Three workarounds. First, mine your own CRM — every prospect you talk to who is also evaluating that competitor mentions numbers; aggregate them quarterly. Second, watch ancillary signals — G2 reviewers often disclose negotiated pricing in numeric ranges, and conference talks sometimes leak pricing strategy verbatim. Third, request a quote yourself or via a third party every 60–90 days and log it. Hidden-pricing competitors are the hardest battlecards to keep current and the ones where signal-triggered updates matter most.

See it in action

Get a free competitive landscape report for your top 5 competitors.

Enter your website. Contend identifies your real competitors, captures their pricing surfaces, and shows you what's moved in the last 90 days — at no charge.

Get my free report