Gamma sales battlecards that stay current: competitor moves and reviews in, one card per rival out

Avoma's guide defines a battle card as a one page reference with competitor intelligence, objection responses, pricing comparisons and product differentiators, and cites Crayon's figure that 68% of sales opportunities are competitive. Its list of contents: a competitor overview, three to five differentiators framed as buyer outcomes, a pricing comparison, five to seven objection responses written as talk tracks, trap-setting discovery questions, one or two proof points and next steps.

Avoma's advice on building one is blunt: write for scannability, since a card a rep cannot use in ten seconds goes unused, and assign an owner with a monthly or quarterly review.

Gamma ships a competitive battlecards template, and Google ranks it first for this query. A template gives the layout. The competitor facts and the review quotes are what go stale.

Battlecards fail for reasons other than missing facts. A competitive intelligence founder on Reddit wrote: "The problem was never a lack of information. It was a lack of decision ownership." The card is only useful when someone owns keeping it current, and the facts on it can be checked.

Two Linkeddit sources. The weekly brief grades each rival's moves by priority, with a category, why it matters and a source link. In the test run for 26 October to 1 November, Fathom's high priority move was an AI assistant launch and Matomo's was security guidance.

The second source is the stored customer reviews. Linkeddit fetches reviews from G2, Capterra, TrustRadius and Trustpilot, stores them as the sites show them, and does not summarise or score them. The test run shows what that means in practice: 20 Matomo reviews read from G2 and 7 from Trustpilot, one tracked site returning an error and others returning none. A card should say so rather than imply full coverage.

Word for word, with the review site and date named, and never a paraphrase. The test project's own stored reviews show why. One Trustpilot reviewer gave plausible.io one star over a subscription upgrade dispute, and another gave it five stars for helpful support. A card that quoted only one would mislead the rep either way.

Use textMode preserve in Gamma's generate tool so the quote survives layout, then check the finished card against the stored text. Quote only text you have read in the review, and cite its URL.

Review quotes about a rival are marketing material. Check how your company permits their use before you put one in front of customers.

Avoma recommends a monthly or quarterly review and an immediate update when a competitor changes pricing or launches a feature. A weekly brief lets you do the second part without watching every changelog yourself.

Refresh only the block that changed. Ask Claude to compare the new brief with the date on the card and rewrite what they just did, leaving how we answer untouched. Gamma's edit_gamma tool can change an existing document when editing is enabled on your account.

A battlecard is read mid-conversation, so it must be short. Avoma's rule of thumb is that a rep who cannot find an answer in ten seconds will not use the card. One page per competitor, one week of moves, and the review quotes limited to two or three lines.

Distribution matters as much as content. Avoma advises placing cards where reps already work, such as the CRM or a pinned Slack channel, instead of a shared drive. Ask Claude to export the Gamma document as PDF, then post it where your team looks.