# Free Sales Battlecard Template (and How to Keep It Current) Source: PageCrawl.io Blog URL: https://pagecrawl.io/blog/sales-battlecard-template --- A senior account executive is forty minutes into the most important call of her quarter. The prospect leans back and says, "We're also looking at Rival A. Honestly, their new pricing looks hard to beat." She opens the battlecard her enablement team built, scans to the pricing section, and reads numbers that are eight months old. Rival A changed its tiers in March. The card never caught up. She improvises, the answer lands flat, and the deal slips into a "we'll circle back" that never circles back. The battlecard was not the problem. A battlecard is one of the highest-leverage documents a revenue team owns. The problem was that nobody kept it current. Competitors do not freeze their websites so your enablement team can catch up. They quietly add tiers, reword homepages, retire features, and publish case studies, and every one of those edits ages your battlecards a little more. This guide gives you a complete, copy-paste sales battlecard template you can use today, explains what belongs in each section and why, and then solves the hard part: wiring your battlecards to automated competitor monitoring so the facts update themselves instead of rotting in a slide deck. By the end you will have a structure your reps actually trust during live calls, because the numbers on it are never stale. 📄 Free download: Grab the editable Competitive Sales Battlecard Template to fill in and put to work. Open it in your browser, customize the placeholders, and print or save it as a PDF. No signup required. Get the template → ### What is a sales battlecard, and why do most of them go stale? A sales battlecard is a one-page reference that arms a rep to win a deal against a specific competitor. It compresses everything a seller needs in the moment: who the competitor is, where they are strong, where they are weak, what objections to expect, and how to respond. Most go stale because they are built once and never refreshed against the competitor's live website. The staleness is structural, not lazy. A battlecard is a snapshot of a moving target. The day you publish it, it is accurate. A few weeks later the competitor reworks their pricing page, and your pricing section is wrong. A month after that they launch a feature that erases a weakness you told reps to exploit, and now your card is actively dangerous, because it teaches sellers to attack a gap that no longer exists. Stale battlecards are worse than no battlecards. A rep with no card knows they are improvising. A rep with a confidently wrong card walks into the call believing bad information, repeats it to the prospect, and gets corrected in real time. That destroys credibility faster than admitting you do not know. The fix is not better writing. It is a system that tells you the instant the underlying facts change, which is exactly what continuous [competitor website tracking](/blog/how-to-track-competitor-websites-guide) provides. ### What should a sales battlecard include? The free template A strong battlecard has six sections: overview, strengths, weaknesses, traps to set, objection handling, and a pricing comparison. Keep the whole thing to a single page. Reps glance at battlecards mid-call, so density and scannability beat completeness. Below is the full template you can paste into a doc, a wiki, or your enablement platform. #### The overview block ``` COMPETITOR: [Name] ONE-LINER: [What they sell and to whom, in one sentence] TARGET BUYER: [The segment where you meet them most] WHEN WE WIN: [The 2-3 conditions that predict our wins] WHEN WE LOSE: [The 2-3 conditions that predict our losses] LAST UPDATED: [Date] | OWNER: [Name] ``` The overview gives a rep instant orientation. The "when we win / when we lose" lines come straight from win/loss data and are the single most valuable rows on the card. Always stamp a date and an owner so anyone can see at a glance whether the card is fresh and who to ping when it is not. #### Strengths and weaknesses ``` THEIR STRENGTHS (acknowledge, do not deny): - [Strength] -> reframe: [how we neutralize or contextualize it] - [Strength] -> reframe: [how we neutralize or contextualize it] THEIR WEAKNESSES (with evidence): - [Weakness] -> proof: [review quote, analyst note, or doc gap] - [Weakness] -> proof: [review quote, analyst note, or doc gap] ``` List real strengths honestly. Reps lose trust in a card that pretends the competitor is hopeless, because prospects praise those strengths out loud. Pair every weakness with evidence, ideally a verbatim customer quote, so the seller cites a fact rather than a claim. Public review pages are a goldmine here, which is why teams [monitor G2, Capterra, and comparison pages](/blog/monitor-g2-reviews-software-comparison-pages) for fresh, quotable complaints. #### Traps to set and objection handling ``` TRAPS TO SET (questions that expose their gaps): - "[Question that surfaces a known limitation]" - "[Question that surfaces a known limitation]" OBJECTION HANDLING: OBJECTION: "[What the prospect says]" RESPONSE: "[Conversational reply a rep can say out loud]" PROOF POINT: "[Specific evidence or customer example]" ``` Traps are discovery questions that lead a prospect to find the competitor's gap themselves, which is far more persuasive than you asserting it. Objection handling should be written in spoken language a rep can use verbatim, not corporate prose. Each objection gets a response and a proof point so the answer has teeth. #### The pricing comparison ``` THEIR PRICING (verified [date]): - [Tier]: [Price] - [what's included / notable limits] - [Tier]: [Price] - [what's included / notable limits] HIDDEN COSTS: [onboarding, overages, add-ons, seat minimums] OUR POSITION: [how we frame value against this structure] ``` Pricing is the section that ages fastest and burns reps hardest, so it carries its own verification date. Capture structure and hidden costs, not just headline numbers, because total cost of ownership is where deals are actually won. This section is the one most worth wiring to automated [SaaS pricing page monitoring](/blog/saas-pricing-page-monitoring-competitor-changes) so a tier change pings you the same day it ships. ### How do you fill each section with real evidence instead of guesses? Fill every claim with a dated, attributable source: a customer quote, an analyst report, a screenshot of the competitor's own page, or a win/loss interview. A battlecard built on opinions collapses the first time a prospect pushes back. A battlecard built on evidence holds up because the rep is quoting reality, not your marketing team's wishful thinking. Pull strengths and weaknesses from public review platforms, where customers describe in their own words what frustrates them. Pull pricing and feature claims directly from the competitor's live pages, never from memory or a six-month-old deck. Pull objections from your own reps: run a fifteen-minute session asking "what does the prospect say when they mention this competitor?" and you will fill the objection section in one sitting. The discipline that separates a trusted battlecard from a decorative one is attribution. Every line should answer "how do we know this?" with a source and a date. That habit also makes the card maintainable, because when a source changes, you know exactly which line to revisit. For a fuller catalog of where this evidence lives, see our guide to [competitive intelligence sources and tactics](/blog/competitive-intelligence-sources-tactics), and the broader primer on [what competitive intelligence is](/blog/what-is-competitive-intelligence-guide). ### Why do battlecards go stale, and which sections break first? Battlecards go stale because competitors edit their public surfaces constantly and nobody is watching those edits. The sections that break first, in order, are pricing, positioning and messaging, and feature claims. These are precisely the surfaces a competitor touches most often, which is why a card built in January is materially wrong by spring. Pricing breaks first because it is the most strategically active page a competitor owns. New tiers, renamed plans, changed seat minimums, and quietly removed free trials all land here, and each one invalidates your pricing comparison. Positioning breaks next: a competitor reworks a homepage headline or a category claim, and suddenly your "they don't even talk about X" line is false. Feature claims break third, as the competitor ships something that closes a gap you told reps to exploit. Tracking these shifts is the core of [competitive marketing intelligence](/blog/competitive-marketing-intelligence-guide). The common thread is that all three live on the competitor's public website, the one surface you can watch automatically. You do not need insider access or expensive data. You need a system that notices the day a page changes and tells the battlecard owner to update one specific line. ### How do you keep a battlecard current with automated monitoring? You keep a battlecard current by monitoring the exact competitor pages that feed each section, so the moment a page changes you get an alert and update the matching line. PageCrawl checks your chosen pages on a schedule, detects what changed, and pushes that change to your team, turning battlecard maintenance from a quarterly scramble into a steady trickle of small edits. Here is the setup, start to finish. [Image: PageCrawl change diff for Rival A - Pricing and Positioning Page, highlighting the added and removed text] **Step 1: List the pages behind each battlecard section.** For one competitor, that is usually their pricing page, homepage, main product or features page, a comparison or "alternatives" page if they run one, and their blog or news section. Five pages per competitor is a realistic baseline. **Step 2: Create a free PageCrawl account.** The free tier includes 6 monitors and 220 checks per month, which is enough to cover your single most important competitor's core pages end to end and prove the workflow before you scale. **Step 3: Add a monitor for each page.** Paste the competitor's pricing page URL first, since it is the section that breaks soonest. Repeat for the homepage, product page, and blog. Each monitor watches one page for changes. **Step 4: Choose what to track per page.** For pricing pages, track the pricing region so you catch tier and number changes. For homepages and product pages, track the main text so headline and positioning edits surface. PageCrawl detects the meaningful change and shows you a clean before-and-after diff rather than raw noise. **Step 5: Set the checking frequency.** Free monitors check every 60 minutes, which is more than fast enough for competitive intelligence, where a same-day catch already beats the weeks-late discovery most teams live with. Paid tiers tighten this to 15, 5, or 2 minutes when timing matters. **Step 6: Route alerts to where your team already works.** Send change notifications to [a dedicated Slack channel](/blog/website-change-alerts-slack) or to email so the battlecard owner sees edits without logging in anywhere. The battlecard becomes a living document fed by a steady stream of small, specific updates. **Step 7: Update the matching line and re-stamp the date.** When a pricing alert fires, open the diff, copy the new number into the pricing section, and update the "verified" date. The whole maintenance loop is now minutes per change instead of a quarterly rebuild. This is the same monitoring backbone described in our guide to building a [competitive intelligence program](/blog/competitive-intelligence-strategy-program), applied to the deliverable sales reps touch every day. ### Which competitor pages should feed your battlecard? Monitor the five pages that map directly to your battlecard sections: pricing, homepage, product or features, comparison pages, and the blog or newsroom. Each page feeds a specific part of the card, so a change on any one tells you exactly which line to revisit. This page-to-section mapping is what makes the whole system maintainable rather than a vague "watch the competitor" goal. The pricing page feeds your pricing comparison. The homepage and any category page feed your positioning and the "their strengths" reframes. The product or features page feeds both strengths and weaknesses, since shipped features can close a gap or open a new one. A competitor's own comparison or "alternatives" page is pure gold, because it shows exactly how they position against you and what objections they are coaching their own reps to raise. The blog and newsroom feed proof points and signal strategic direction. For Tier 1 competitors, the ones your reps meet in nearly every deal, watch all five pages. For Tier 2 competitors you see occasionally, watching just the pricing page and homepage is enough to keep their card from going dangerously stale. This tiering keeps you inside the free or Standard plan limits while still covering what matters. ### How do you route changes to the right battlecard owner? Assign one owner per competitor card and route that competitor's monitoring alerts straight to them, so every change lands with the person responsible for acting on it. Ownership plus targeted routing is what turns raw change alerts into updated battlecards. Without an owner, alerts get seen by everyone and acted on by no one. Give each Tier 1 competitor a named owner, usually a product marketer or a sales enablement lead. Route that competitor's PageCrawl alerts to a channel or inbox that owner watches, and tag changes by competitor so the right person is pinged. When a pricing alert fires for Rival A, Rival A's owner updates the pricing line and re-stamps the date. The loop closes in minutes. For higher-volume programs, push changes through [webhook automation](/blog/webhook-automation-website-changes) so an alert can open a task in your project tracker, post to a battlecard channel, or trigger a "review this card" reminder automatically. PageCrawl's review boards also give the whole team a shared, visual queue of every detected change across all competitors, so owners can mark items reviewed, flag the significant ones, and leave notes, instead of each person checking pages independently. ### How often should you update a battlecard? Update the facts on a battlecard the day the underlying page changes, and review the whole card on a fixed cadence: monthly for Tier 1 competitors, quarterly for Tier 2. Continuous monitoring handles the urgent, day-of edits like a pricing change, while the scheduled review catches the slower drift in narrative, objections, and win/loss patterns that no single page edit captures. The two cadences work together. Monitoring keeps the volatile sections, pricing, positioning, and feature claims, accurate in near real time, so a rep never quotes an eight-month-old number again. The scheduled review is where the owner asks the questions a diff cannot answer: are these still the right objections, do the win/loss conditions still hold, has the competitive frame shifted? A monthly thirty-minute review per Tier 1 card, fed by a month of accumulated change alerts, keeps the card both factually current and strategically sharp. ### Choosing your PageCrawl plan PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough to keep one Tier 1 competitor's core pages fully current and prove the battlecard workflow before you scale. Most teams upgrade once they are tracking three or more competitors. | Plan | Price | Pages | Checks / month | Frequency | |------|-------|-------|----------------|-----------| | Free | $0 | 6 | 220 | every 60 min | | Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min | | Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min | | Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min | Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access. Standard at $80 per year is the natural home for a real battlecard program. Five pages per competitor across five Tier 1 competitors and ten Tier 2 competitors is 75 monitors, comfortably inside 100 pages, with 15-minute checks that make same-hour pricing catches routine. Enterprise at $300 per year fits sales orgs tracking large competitive sets, with 500 pages, SSO for team access, and the full API for piping change data into your enablement stack. Measured against a single deal lost to a stale pricing line, the math is not close. All plans include the **PageCrawl MCP Server**, which lets enablement leads and reps ask Claude to pull a change summary for any competitor over any time window directly from the monitoring archive. A rep prepping for a call can ask "what changed on Rival A's pricing and product pages in the last 30 days?" and get an answer drawn from live data. AI assistants can create monitors through conversation on every plan, including Free. ### Getting Started Pick your single most dangerous competitor, the one your reps meet in nearly every deal. Open the template above, fill the six sections with dated evidence, and stamp it with today's date and an owner. Then set up free monitoring for that competitor's pricing page, homepage, and product page, and route the alerts to a Slack channel your team already watches. In under an hour you will have a battlecard that is both accurate and self-correcting. A battlecard is only as good as its freshest fact. Stop rebuilding cards from scratch every quarter, wire them to the competitor's live pages, and let the updates come to you. --- Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.