Sales Enablement

Sales Battlecards: How to Build Competitive Enablement That Sales Actually Uses

By James Doman-Pipe | Published February 2026 | Sales Enablement

Most battlecards get ignored because they are written for the person who made them, not for the rep who needs to win a deal in the next 30 minutes.

The average B2B sales rep has access to dozens of battlecards. Most of them are useless in the moment that matters.

They are too long to skim. They are written in product language rather than buyer language. They describe features instead of objection responses. They were accurate when they were written six months ago but nobody has updated them since the competitor released a new pricing tier.

The result: reps do not use them. They fall back on instinct, hearsay, and whatever they picked up in the last deal review. Competitive positioning becomes inconsistent, and PMM loses credibility with sales because the tools they built are not being used.

Fixing this is not complicated. It requires building battlecards from the ground up around how reps actually need to use them - quickly, mid-deal, under pressure.

The Design Principle

A battlecard is not a competitive analysis. It is a decision tool. It should give a rep everything they need to handle a specific competitor in a specific moment - and nothing else. If it takes more than 90 seconds to find the answer to an objection, it will not get used.

When Battlecards Get Used - and When They Do Not

Understanding when reps reach for a battlecard tells you exactly how to build one.

Reps consult battlecards in three situations: before a call with a known competitive deal, mid-deal when a competitor gets mentioned unexpectedly, and during prep for a presentation where the buyer has disclosed they are evaluating alternatives.

In all three cases, the rep needs one thing fast: what to say. Not a product comparison. Not a feature matrix. Not a history of the competitor. What to say when the buyer raises a specific concern about price, a specific capability gap, or a specific claim the competitor made.

Battlecards that fail are written like research documents. They list everything that is known about the competitor. They are thorough and impressive and completely useless at 8:45am before a demo call.

The Five-Section Battlecard Structure

Section What It Contains Max Length
The 30-Second Summary Who they are, who they target, how to think about them 3-4 sentences
Where We Win 3-4 specific situations where we have a clear advantage Bullet list, one line each
Where They Win 2-3 honest situations where they have an advantage - and how to respond Bullet list with responses
Top Objections and Responses 5-7 specific objections with word-for-word response starters Q+A format, 2-3 sentences per response
Discovery Questions 3-4 questions to ask early that expose competitor weaknesses naturally Questions only, one line each

Section 1: The 30-Second Summary

This is not a company biography. It is a positioning read - how to think about this competitor in relation to your product and your ICP.

A good 30-second summary tells the rep:

  • Who the competitor is strongest with (the profile of buyer who buys them over you)
  • Their core positioning claim (the story they tell)
  • Their biggest structural weakness (what they consistently cannot do)

Example for a competing hiring platform:

"Greenhouse is the category leader for enterprise talent teams (500+ employees) who want deep ATS customisation. Their strength is workflow flexibility and integration breadth. Their weakness is complexity - implementation takes months, and smaller teams without a dedicated HRIS admin struggle to get value. If the buyer is a 150-person company without a dedicated ops team, this is a winnable deal."

Section 2: Where We Win

Be specific. "Better product" and "stronger customer support" are not useful. They tell the rep nothing they can use in a conversation.

Good "where we win" entries describe a situation, not an attribute:

  • "Companies hiring 15-100 people per year who need to get value in weeks, not months"
  • "Hiring managers who want to run interviews themselves without HRIS training"
  • "Teams replacing spreadsheet-based tracking for the first time - our onboarding is built for this transition"
  • "Deals where time-to-hire is a board-level metric - we have the data to prove velocity improvement"

Each entry gives the rep a signal to listen for in discovery that tells them they are in favorable territory.

Section 3: Where They Win - and How to Respond

This is the section most battlecards get wrong. They either omit it entirely (making the battlecard feel dishonest to reps who know the reality) or they frame every competitor weakness as an opportunity for spin.

Honest acknowledgement of where the competitor wins builds rep trust in the card. If reps believe the card is accurate, they use it. If they think PMM is papering over real gaps, they ignore it.

The format that works: acknowledge the advantage, then pivot to the question that changes the context.

Example:

"Where they win: Large enterprise deals (1,000+ employees) that need Workday/SAP integration on day one. We do not have that integration yet.
Response: 'That is a fair point. When is that integration a must-have versus a nice-to-have? Most teams we talk to at your stage are not using Workday at full depth yet - are you?'"

The response does not deny the weakness. It asks a question that surfaces whether the weakness is actually relevant to this buyer's situation.

Section 4: Top Objections and Responses

This is the highest-value section of any battlecard. Build it from real conversations, not hypotheticals.

The sourcing process:

  • Pull the last 20 competitive deals from your CRM. For losses, look at the stated reason. For wins, look at the objections that were raised and overcome.
  • Interview 3-5 reps who regularly face this competitor. Ask: "What is the hardest thing this competitor says about us that you have to overcome?"
  • Review Gartner Peer Insights, G2, and Capterra reviews of the competitor. Their positive reviews tell you what buyers value about them - which is what reps will hear as objections.

Format each objection as a direct quote in buyer language, followed by a response starter:

Objection: "Greenhouse has way more integrations than you."
Response: "That is true - they have been building their integration library for longer. Which specific integrations are critical for how your team works today? In our experience, most teams use three or four actively - let me check which ones matter most for you and we can be specific about our coverage."

The response starter does not have to be the entire script. It just has to give the rep a direction and a first sentence they can deliver confidently.

Section 5: Discovery Questions

These are questions the rep asks early in the deal - ideally before the competitor is even mentioned - that surface information favouring your positioning.

Good discovery questions feel like genuine curiosity to the buyer. They are not leading or manipulative. They are legitimate questions that happen to reveal dimensions where your product has an advantage.

Examples:

  • "How long has your current system been in place, and who manages it day-to-day?" (Surfaces complexity and admin dependency)
  • "When you last went through an implementation with a new HR tool, what was the hardest part of the rollout?" (Surfaces implementation pain)
  • "If you could see your time-to-hire data right now, what would you expect it to show?" (Opens the velocity conversation)

Sourcing Competitive Intelligence

Battlecards are only as good as the intelligence behind them. Build a repeatable intel-gathering process rather than doing one big research project every year.

Source What It Gives You Cadence
Win/loss interviews Buyer perception of competitor vs you; actual decision criteria Every competitive loss, monthly review
G2 / Capterra reviews What buyers praise and criticise; language they use Quarterly
Competitor website + pricing page Positioning changes, new features, ICP shifts Monthly
Sales team Slack / deal reviews Real-time objections and competitor claims in active deals Ongoing - set up a #competitive channel
New hire interviews Deep internal knowledge from people who just left a competitor Every relevant hire

Getting Adoption

Build the card with sales input, not after the fact. A rep who contributed to a battlecard is far more likely to use it. A rep who received it by email as a PDF is not.

The process that drives adoption:

  • Interview 3-4 reps before writing anything. Use their language, their objections, their real-deal situations.
  • Share a draft with the same reps before publishing. Ask: "Would you use this? What is missing?"
  • Run a 20-minute live session to walk through the card - not a training deck, a conversation. How would you use this? When does it come up?
  • Embed it where reps actually work. A PDF on Confluence is invisible. A card in Salesforce, Gong, or Highspot next to the deal record gets used.
  • Review and update quarterly. Nothing kills trust in a battlecard faster than a rep finding outdated information mid-deal.

How to Source Intelligence That Makes Battlecards Actually Useful

A battlecard is only as good as the intelligence behind it. The difference between a battlecard that reps trust and one they ignore is usually the specificity of the competitive intelligence — whether it reflects what buyers are actually hearing from competitors today, or what PMM believed to be true six months ago.

The best battlecard intelligence comes from four sources, ranked by reliability:

Source 1: Win/loss interview verbatims

Buyers who chose a competitor — or who chose you over a competitor — will tell you exactly what the competitor said and how it landed. This is the highest-quality input for battlecard content because it is unfiltered buyer perception, not your interpretation of a competitor's website. Pull five to eight relevant quotes per competitor per quarter from your win/loss interviews. The objections and claims that appear in more than half of them belong in the battlecard. The rest are deal-specific noise.

Source 2: Sales rep intel from the field

Reps hear competitive claims in every deal cycle. The problem is that this intelligence is usually trapped in individual rep memory, anecdote, or the occasional Slack message. Build a structured input channel — a #competitive Slack channel with a standard format, or a CRM field that captures competitor mentioned and specific claim made. Review this monthly. Patterns in rep-reported intel update battlecards faster than any other source because they reflect what is happening in live deals this week, not what was happening last quarter.

Source 3: Competitor public positioning signals

Review competitor websites, G2 review responses, LinkedIn posts from their leadership, and recent case studies on a quarterly basis. What claims are they leading with? What have they recently changed? If a competitor has updated their homepage hero from feature-centric to outcome-centric in the last 90 days, they have repositioned. Your battlecard needs to reflect the new story, not the old one.

Source 4: Third-party review site intelligence

G2, Capterra, and Trustpilot reviews of your top two to three competitors surface what real buyers valued and where they experienced gaps. Read the three-star and four-star reviews — not the five-stars (too promotional) and not the one-stars (often outliers). The middle-range reviews describe what the product actually does for most buyers and where they experienced friction. This is excellent source material for the "Where They Win" and "Top Objections" sections of your battlecard.

The intelligence assembly cadence

Do not try to update all battlecards simultaneously every quarter. Instead, rotate: prioritise the competitor that appears most frequently in current deals and run a full intelligence refresh on that one. The following quarter, move to the next. A single battlecard updated with current, specific intelligence is worth more than three battlecards updated superficially.

FAQ: Sales Battlecards

How many competitors should you have battlecards for?
Focus on the three to five competitors you encounter in at least 20% of your deals. Building a battlecard for every competitor in the market is wasted effort. Build for frequency and impact, not comprehensiveness.

How long should a battlecard be?
One page is the target. Two pages maximum. If it cannot fit on one page, you have not made the hard editorial decisions. Reps will not read past page two under any circumstances.

Should battlecards be visible to buyers?
No. Battlecards are internal tools. They contain strategic framing and honest assessments of your weaknesses that should not be in the buyer's hands. Keep them behind login in your CRM or enablement platform.

How do you keep battlecards current without it becoming a full-time job?
Build a lightweight update process: a #competitive Slack channel where reps post real-time intel, a quarterly 30-minute review with two or three reps to check accuracy, and a clear owner (usually PMM) who is responsible for integrating updates. The quarterly review catches 90% of meaningful changes.

About the Author

James Doman-Pipe

James is a B2B SaaS positioning and GTM specialist, co-founder of Inflection Studio, and a PMA Top 100 Product Marketing Influencer. He previously led product marketing at Remote, where he helped build the engine that powered 12x growth. He writes the Building Momentum newsletter for 2,000+ PMMs and operators.

Connect: LinkedIn | Building Momentum | Inflection Studio