Battlecard Effectiveness Scorecard
A 100-point rubric that scores every competitive battlecard on accuracy, usage, and measured win-rate impact: so retiring, rebuilding, or promoting a battlecard is a data call, not a guess.
How to use it
Run this quarterly across every active competitive battlecard, scoring with an enablement lead plus reps who've used the card in a live deal; use the band and decision log to force an explicit retire/rebuild/maintain/promote call.
What's inside
- Accuracy scoring criteria (40 pts): positioning, pricing, features, rebuttal currency
- Usage scoring criteria (30 pts): findability, CRM reference rate, update recency, rep confidence delta
- Impact scoring criteria (30 pts): win-rate lift, cycle-time delta, anecdotal behavior change, loss-reason leak check
- Four scoring bands, Promote / Maintain / Rebuild / Retire, with a required action for each
- Fill-in scoring worksheet with an evidence-source column per criterion
- Recommended quarterly cadence and a named scorer panel (enablement + reps + loss-review)
- Decision log template for tracking retire/rebuild calls over time
Purpose: Score every competitive battlecard on a 100-point scale across Accuracy, Usage, and Impact so you know, with evidence, which battlecards to promote, refresh, or retire, instead of guessing from gut feel or how recently someone remembers updating one.
Cadence: Score every battlecard quarterly, or immediately after a competitor makes a material product/pricing move.
Who scores: Enablement/product marketing lead + 2 quota-carrying reps who've used the battlecard in a live deal in the last 90 days + 1 person who coded a recent loss involving that competitor.
Scoring Worksheet
Battlecard: ______________________ Competitor: ______________________ Owner: ______________________ Last updated: ______________________
Section A: Accuracy (40 pts)
| # | Criterion | Points available | Score | Evidence source |
|---|---|---|---|---|
| A1 | Positioning claims match the competitor's current real-world pitch (verify against a recent competitive-deal call or their own website/pricing page) | 10 | ___ | Call recording / competitor site |
| A2 | Pricing & packaging info is current within the last 90 days | 10 | ___ | Win/loss interviews, public pricing |
| A3 | Feature/capability comparison reflects the competitor's current product, not a version 12+ months old | 10 | ___ | Product marketing, recent losses |
| A4 | Suggested rebuttals still land: reps report buyers aren't pushing back with something the card doesn't cover | 10 | ___ | Rep pulse survey |
Section A subtotal: ___ / 40
Section B: Usage (30 pts)
| # | Criterion | Points available | Score | Evidence source |
|---|---|---|---|---|
| B1 | Reps can locate the correct card in under 30 seconds (timed test, min. 5 reps) | 5 | ___ | Live timed test |
| B2 | % of CRM-flagged competitive deals where the card was opened/referenced this quarter (5 pts if ≥70%, 3 pts if 40-69%, 0 pts if <40%) | 10 | ___ | CRM engagement/content-tool logs |
| B3 | Card was updated within one review cycle of the competitor's last known product or pricing change | 5 | ___ | Update log vs. competitor change log |
| B4 | Rep self-reported confidence going into a competitive deal, before vs. after reviewing the card (survey, 1-5 scale delta) | 10 | ___ | Pre/post rep survey |
Section B subtotal: ___ / 30
Section C, Impact (30 pts)
| # | Criterion | Points available | Score | Evidence source |
|---|---|---|---|---|
| C1 | Win rate on flagged deals where the card was used vs. flagged deals where it wasn't (5 pts per 10-point win-rate lift, capped at 15) | 15 | ___ | CRM win/loss by competitor tag |
| C2 | Average sales-cycle length is shorter on flagged deals where the card was used | 5 | ___ | CRM cycle-time report |
| C3 | Reps report at least one instance this quarter of the card directly changing how they ran a call (specific anecdote required, not a rating) | 5 | ___ | Rep survey free-text, manager 1:1 notes |
| C4 | Loss-reason coding does NOT show reps still losing to messaging the card was built to counter (inverse: full points if the leak has stopped) | 5 | ___ | Win/loss loss-reason tags |
Section C subtotal: ___ / 30
TOTAL SCORE: ___ / 100
Scoring Bands & Required Action
| Band | Score | Action |
|---|---|---|
| Promote | 80-100 | Feature as the gold-standard template in enablement training; no changes needed this cycle |
| Maintain | 60-79 | Keep live; assign a light refresh (pricing/feature currency only) before next quarter |
| Rebuild | 40-59 | Structure is fine, content is stale or unused, assign an owner and a 2-week rebuild sprint |
| Retire | 0-39 | Archive immediately. If the competitor is still active in deals, replace the card entirely: do not cosmetically patch a card scoring this low |
Decision Log (fill in per battlecard, per cycle)
| Battlecard | Competitor | Score | Band | Decision | Owner | Next review date |
|---|---|---|---|---|---|---|
Rule of thumb: A battlecard nobody can find (low B1) will always score low on impact (C1-C4) regardless of how accurate it is, fix distribution before you rewrite content.