The Stale Battlecard: Auditing a Competitor Brief Against Fresh Signals
Objective: Given an 8-month-old one-page battlecard and 6 fresh competitive signals (a pricing change, 2 G2 review themes, a job-posting cluster, a press release, a funding announcement), audit which sections are stale and rewrite the 'how we win' section.
You're the PMM at Snowflake covering a data-warehousing competitor. Sales keeps citing an 8-month-old battlecard in live deals, and two reps just lost objection-handling on a pricing point the competitor changed months ago.
Tag each new signal by type and confidence per the lesson's Stage 2 framework, then decide which battlecard sections it invalidates.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, fast to filter and sort a small signal set
Free, easy to track version history on a living document
The process
2 steps
Step 01 of 02
The lesson's Stage 2 requires tagging each raw signal with competitor name, signal type (pricing, product, hiring, messaging, partnership), confidence level (confirmed vs. inferred), and date before it can be acted on.
One signal is 'a Reddit thread claims the competitor is raising prices next quarter.' What confidence tag does that get, and does it belong in the battlecard yet?
Procedure
- Import fresh-signals.csv (6 rows: signal description, source, date)
- Tag each row's Type (pricing, product, hiring, messaging, partnership)
- Tag each row's Confidence as confirmed (verified on the competitor's own site or filing) or inferred (secondhand, e.g. a forum post)
- Exclude any inferred-confidence row from the battlecard rewrite, flag it for monitoring only
Row 3: 'Reddit thread claims competitor raising prices next quarter' Type: pricing Confidence: inferred (unverified secondhand claim) Action: monitor only, do not update battlecard yet
Healthy
The battlecard only changes on confirmed signals; inferred signals go to a watch list.
Unhealthy
Rewriting a battlecard's pricing objection-handling off a single unverified forum post.
What this means
Confidence tagging is what keeps a battlecard from thrashing every time a rumor surfaces.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| The battlecard has been rewritten 4 times this month on conflicting rumors | Require confirmed-tier confidence before any battlecard section changes | 5 min |
Step 02 of 02
The lesson's Stage 4 explains that a battlecard's value comes from timing: delivering the right insight to a rep within minutes of a competitive mention, not from having the most exhaustive document.
Of the 4 confirmed signals from Step 1, which one directly changes the 'how we win' section reps read during a live objection, versus which one only updates background context?
Procedure
- For each confirmed signal, name the exact battlecard section it changes (Positioning, Strengths, Weaknesses, Objections, How We Win)
- Rewrite the 'How We Win' section using only the confirmed signals that map to it
- Leave background sections (company overview, funding) unchanged if no confirmed signal touches them
Confirmed signal: 'Competitor removed free tier from pricing page, effective this month' Battlecard Section: Objections + How We Win Rewrite: Add counter-move 'Their free tier is gone as of [date] -- lead with our still-free starter plan'
Healthy
The rewritten section is one that a rep would actually open mid-call, not a paragraph nobody reads.
Unhealthy
A 12-paragraph rewrite that buries the one sentence a rep needs during an objection.
What this means
Activation means the section a rep opens under time pressure gets the update first.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Reps say the battlecard is 'too long to use on a call' | Cut the How We Win section to 3 bullets max, move everything else to an appendix | 30 min |
Final deliverable
A tagged 6-row signal log (type, confidence, action) plus a rewritten 3-bullet 'How We Win' battlecard section using only confirmed signals.
See a reference example
Lenskart competitor battlecard, How We Win (rewritten excerpt) 1. Their in-store try-on wait time averages 12 min per G2 reviews (Aug 2026) -- lead with our 15-min home try-on delivery 2. They dropped their student discount last quarter -- we still offer 20% off with valid ID 3. Hiring 4 'AR try-on engineers' since June -- expect a virtual try-on launch within 2 quarters, do not promise this feature as our exclusive
Success criteria
You're done when you can:
- Excludes inferred-confidence signals from the battlecard rewrite
- Rewritten How We Win section stays to 3 bullets a rep could use live on a call