# A three-line battlecard format for live sales calls Use one concise card per objection: a one-sentence answer, one dated proof point and the likely rebuttal. Then test the format with sellers. URL: https://www.hiresteve.ai/blog/battlecards-sales-actually-uses Updated: 2026-10-12 For a battlecard meant for use during a live call, start with one objection and three lines: an answer, dated proof and the likely rebuttal. Test the format with the sellers who will use it. **Key takeaways** - For live-call use, fit the answer on one screen and test how quickly sellers can find it. - Write one card per objection, not one card per competitor. - Every claim needs a date and source so the rep can check whether it is current. - Refresh the card when its supporting evidence changes. ## Why a long card can be slow to use A comprehensive battlecard may answer many questions and still be slow to use during a live call. A rep may need one answer to an objection that just arrived while the prospect waits. ### Organize the card by objection The unit of a battlecard is not the competitor. It is the objection. "They are cheaper" and "they have a SOC 2 and you do not" need different responses and different cards, even when they name the same competitor. **The three-line test** Read the card from the top in a timed test with sellers. If the answer is hard to find, shorten the card or split it by objection. ## A starting shape to test with sellers **Name the objection in the prospect's words** Not "pricing differentiation" — "they quoted us half". Using the prospect's words makes the card easier to find during the call. **Answer in one sentence** The whole answer, first. If the rest of the card vanished, the sentence still works on its own. **Add the proof, with a date** An undated claim gives the rep no visible freshness cue. Add the source and the date you checked it so the rep can judge whether to use it. **Add the trap** One line on what the competitor may say next. This prepares the rep for a likely follow-up and keeps the response tied to the deal. Here is the same card in both shapes: | Section | Long card | Three-line card | | --- | --- | --- | | Opening | Company overview, funding, positioning | "They quoted us half" | | Body | Feature matrix, 40 rows | One sentence: what the price excludes | | Proof | Links to five sources | One dated line | | Close | Discovery questions | What they say next | --- **The other half of the problem** ## Freshness beats polish A card is not a document, it is a claim about the present tense. When a competitor changes its pricing page, any card that cites the old price is wrong, and sellers may not be told. **Holds up** - Positioning against a category - Your own customer proof - Objection patterns, which change slowly **Rots** - Named pricing and packaging - Feature gaps, which can change with every release - Named customers, which move both ways - Security and compliance posture **When a feature-gap claim is stale** A feature gap that closed two months ago can make a card worse than having no card. If a prospect corrects the claim during a call, the rest of the card may become harder to trust. ### What to monitor, and how often [Compato's battlecard guide](https://compato.app/blog/battlecard-creation-and-update-workflow) varies review timing by field, while [Content Camel](https://www.contentcamel.io/blog/sales-battlecard-examples/) recommends periodic and change-triggered review. The schedule below is our editorial starting point; adapt it to the sources you rely on. - Pricing and packaging pages — weekly - Changelog and release notes — weekly - Security and trust pages — monthly - Customer logo walls — monthly - Job postings, which can hint at roadmap direction — monthly ## Where this leaves product marketing Writing gets faster. Maintaining does not, and maintenance is the whole job. The teams that get this right stop treating a battlecard as a deliverable and start treating it as a feed with a review step. - **One card per objection** — Focused objection cards can be easier to search than one long document. - **Dated claims only** — Every line carries the date it was verified. Undated lines get cut at review. - **A rep edits it** — A lack of rep edits is a reason to check usage, not proof that nobody opened the card. - **Change drives the refresh** — The competitor's page changing is what triggers the edit — not the calendar. Steve tracks competitor pages and news and drafts battlecard updates when something changes. Updates wait for your review before they apply. [Review Steve's competitive-intelligence product](/products/competitive-intel) or ask how the current workflow applies to your sources. ## The part nobody automates Judgement. What a change *means* for your deal is not on the competitor's website, it is in the calls you lost. That is a different pipeline, and it is the subject of the other post. ## Frequently asked ### How long should a battlecard be? Start with one screen. For this template, use three lines: one answer, one dated proof point and the likely rebuttal. Treat that as a starting format and test it with the sellers who use the card. ### How often should battlecards be updated? Update a card when its supporting evidence changes. Review fields at a cadence that matches how quickly their sources change; the schedule below is an editorial starting point, not a universal interval. ### Who should own battlecards? Product marketing can write the first version, and sales should have a way to correct it. A lack of rep edits is a reason to check usage, not proof that nobody opened the card. ### Do battlecards work for AI-native competitors? The format works; the sourcing changes. Use the competitor's actual release, pricing and packaging changes as triggers, then test the review schedule with the team. ## Go deeper - [A battlecard template you can fill in during one call](https://www.hiresteve.ai/blog/battlecards-sales-actually-uses/battlecard-template) — A four-part battlecard format with an objection, one-sentence answer, dated proof, next response, and a clearly fictional worked example. - [How often should you update a battlecard?](https://www.hiresteve.ai/blog/battlecards-sales-actually-uses/how-often-to-update-battlecards) — Refresh each battlecard field when its source changes, using a field-specific review cadence instead of one quarterly sweep.