Competitive Battlecard Generator

Competitive Battlecard Generator

> A sequential system for building, maintaining, and deploying competitive > intelligence as battlecards. Each phase produces a defined output that feeds > the next. Phase 6 captures field intel that keeps battlecards current rather > than letting them decay into shelf-ware.

Why This Skill Exists

Competitive battlecards at most B2B SaaS companies are one of two things:

1. A feature comparison matrix that nobody reads. Marketing builds a table

comparing 40 features. Checkmarks everywhere. Sales never opens it because it doesn't tell them what to say when a prospect mentions the competitor on a live call.

1. Tribal knowledge in the heads of 2-3 senior reps. They know what to

say because they've lost deals to this competitor before. Nobody else on the team has that context. When those reps leave, the intel leaves with them.

Both fail because they confuse information with enablement. A battlecard isn't a data sheet. It's a decision aid that tells a rep exactly what to say, what to ask, and what to avoid in a competitive deal, specific to the persona they're talking to.

This skill builds battlecards that sales and BDRs actually use, keeps them current with field feedback, and connects them to the rest of your go-to-market stack.

When to Use This Skill

• Building a battlecard for a specific competitor from scratch
• Updating an existing battlecard with new competitive intel
• Responding to a competitor's product launch, pricing change, or acquisition
• Preparing a BDR or AE for a deal where a specific competitor is involved
• Analyzing win/loss data to identify competitive patterns
• Building persona-specific competitive talk tracks
• Reviewing competitive positioning as part of quarterly planning
• Onboarding new sales/BDR team members on competitive landscape

When NOT to Use This Skill

• General market research or industry analysis (this is competitor-specific)
• Product roadmap planning (competitive intel informs it, but this isn't a

product management skill)

• Pricing strategy (this skill covers how to handle competitor pricing

objections, not how to set your own prices)

• Content creation for comparison/alternative pages (use SEO or content skills

for that; this skill produces internal enablement, not external content)

• Evaluating potential acquisition targets (different analysis framework)

---

The Battlecard Pipeline: 6 Sequential Phases

PHASE 1              PHASE 2              PHASE 3
Competitor       →   Positioning &    →   Persona-Specific
Intelligence          Differentiation      Battlecard
Gathering             Analysis             Assembly

     ↓                                         ↓

PHASE 6              PHASE 5              PHASE 4
Refresh Cycle    ←   Win/Loss         ←   Deployment &
& Decay               Analysis             Enablement
Prevention

     ↓
     └──→ PHASE 1 (next refresh cycle)

The closed loop: Phase 6 runs on a fixed cadence. Field intel from sales, new competitor moves, and win/loss patterns feed back into Phase 1. Battlecards that aren't refreshed every 90 days get flagged for review or retirement.

---

Phase 1: Competitor Intelligence Gathering

Input: Competitor name, your product context, existing intel (if any) Output: Structured competitor intelligence brief

Intelligence Source Matrix

Gather from multiple sources. No single source gives you the full picture.

| Source | Signal Quality | What to Extract | Update Frequency | |--------|---------------|-----------------|-----------------| | Competitor website | Medium | Pricing (if public), messaging, feature claims, customer logos, positioning changes | Monthly | | G2/TrustRadius reviews | High | What their customers praise, what they complain about, switching reasons, comparison mentions | Monthly | | Your win/loss interviews | Very High | Why you won, why you lost, what the buyer compared, what mattered most | After every closed deal | | Sales call recordings | High | What prospects say about the competitor unprompted, specific objections, feature comparisons mentioned | Ongoing | | Competitor job postings | Medium | Product direction signals (hiring for a new category = building it), tech stack, growth signals | Quarterly | | Competitor blog/changelog | Medium | Feature launches, messaging shifts, vertical focus changes | Monthly | | Industry analyst reports | Medium | Market positioning, quadrant placement, analyst perspective on strengths/weaknesses | Annually or when published | | Social media / LinkedIn | Low-Medium | Executive messaging, thought leadership themes, customer engagement, employee sentiment | Monthly | | Patent/technical filings | Low | Long-term product direction. Useful for enterprise competitors. | Quarterly | | Former competitor employees | Very High (if available) | Internal roadmap, culture, sales process, known weaknesses | Opportunistic |

Competitor Intelligence Brief Template

COMPETITOR INTELLIGENCE BRIEF

Competitor: ________________________
Last updated: ________________________
Updated by: ________________________
Next review date: ________________________ (max 90 days)

COMPANY OVERVIEW
- Founded: ________
- HQ: ________
- Funding / public status: ________
- Estimated revenue / ARR: ________
- Employee count: ________ (growth trend: ________)
- Key investors / parent company: ________

PRODUCT OVERVIEW
- Core product: [One sentence description]
- Primary use case: [What most customers buy it for]
- Secondary use cases: [What else it does]
- Platform / architecture: [Cloud-native, on-prem, hybrid]
- Key integrations: [Tech stack dependencies]

PRICING (as known)
- Model: [Per user / per asset / per framework / flat rate / usage-based]
- Entry price: $________ [source: ________]
- Mid-market price: $________ [source: ________]
- Enterprise price: $________ [source: ________]
- Free tier / trial: [Yes/No, details]
- Contract terms: [Annual only, monthly available, multi-year discounts]
- Known discounting behavior: [Aggressive, standard, rigid]

TARGET MARKET
- Primary segment: [SMB / Mid-market / Enterprise]
- Key verticals: [Industries they focus on]
- Geo focus: [Where they sell most]
- ICP overlap with us: [High / Medium / Low, specifics]

MESSAGING & POSITIONING
- Primary value prop: [How they describe themselves]
- Key differentiators (their claimed): [What they say makes them different]
- Messaging themes: [Risk, speed, cost, compliance, developer experience, etc.]
- Recent messaging shifts: [Any changes in how they position]

KNOWN STRENGTHS (evidence-based, not assumed)
1. [Strength] — Evidence: [G2 reviews, win/loss data, customer quotes]
2. [Strength] — Evidence: ________
3. [Strength] — Evidence: ________

KNOWN WEAKNESSES (evidence-based, not assumed)
1. [Weakness] — Evidence: [G2 complaints, lost deals to us, technical gaps]
2. [Weakness] — Evidence: ________
3. [Weakness] — Evidence: ________

RECENT MOVES (last 90 days)
- Product: [New features, acquisitions, partnerships]
- Pricing: [Changes, new tiers, discounting patterns]
- Go-to-market: [New campaigns, verticals, channels]
- People: [Key hires, departures, leadership changes]

WHAT THEIR CUSTOMERS SAY (verbatim from G2/reviews)
- Positive: "[Quote]" — [Source]
- Positive: "[Quote]" — [Source]
- Negative: "[Quote]" — [Source]
- Negative: "[Quote]" — [Source]

WHAT OUR PROSPECTS SAY ABOUT THEM (from sales calls)
- "[Quote]" — [Persona, deal stage, outcome]
- "[Quote]" — [Persona, deal stage, outcome]

Intelligence Quality Rules

1. Cite everything. Every strength and weakness needs a source. "We think

they're weak at X" is an opinion. "Three G2 reviews from mid-market CISOs mention X as a limitation" is intel.

1. Separate what they claim from what customers say. Their website says

"seamless integration." Their G2 reviews say "integration took 3 months." Both matter. The gap between the two is your ammunition.

1. Date everything. Intel from 12 months ago is unreliable. Pricing from

6 months ago may have changed. Mark the date on every data point.

1. Don't invent weaknesses. If you don't have evidence of a weakness,

don't list it. Reps who use unverified claims in deals lose credibility when the prospect checks.

Battlecard Evidence Controls

Every claim about a competitor must be evidence-tagged before inclusion in a battlecard.

| Field | Required | |-------|----------| | Claim | The specific statement about the competitor | | Source | Where this information comes from (G2 review, website, analyst report, win/loss interview, product test) | | Date verified | When this was last confirmed. Claims older than 90 days must be re-verified. | | Confidence | Verified (directly confirmed) / Inferred (reasonable conclusion) / Stale (>90 days, unverified) | | Can sales say this live? | Yes (verified, non-confidential, defensible) / No (unverified, potentially confidential, or legally risky) |

Evidence Rules

1. Never state a competitor limitation as fact unless verified within 90 days.

Products change. A feature gap from 6 months ago may be closed. Mark stale claims and prioritize re-verification.

1. Never use confidential, non-public, or insider information.

Only use publicly shareable, non-confidential sources. Do not solicit or include confidential roadmap, pricing, customer, or internal strategy information from former competitor employees or other non-public channels.

1. Every "They can't do X" claim must have a fallback.

If the competitor closes the gap, what's the next differentiator? Include a "If they fix this" contingency for every limitation you cite.

1. Price claims are the most dangerous.

Competitor pricing changes without notice. Never state exact competitor pricing unless sourced from their current public pricing page with a verification date. Use ranges or relative positioning instead: "typically 20-30% higher" with source.

Live Deal Quick Card

For sales reps who need a 10-second reference during a call, generate a condensed version alongside the full battlecard:

QUICK CARD: [Competitor Name]
Updated: [Date]
SAY: [1-2 sentence positioning against this competitor]
ASK: [The question that exposes their weakness]
DON'T SAY: [The claim that will backfire or can't be defended]
PROOF: [One verified customer quote or metric]
ESCALATE IF: [Trigger to bring in SE, leadership, or specialist]

---

Phase 2: Positioning & Differentiation Analysis

Input: Competitor intelligence brief (Phase 1), your product context Output: Differentiation map with positioning strategy

Differentiation Framework

Don't list 40 features. Identify the 3-5 dimensions that actually decide deals.

DIFFERENTIATION MAP

Competitor: ________________________
Analysis date: ________________________

DIMENSION 1: ________________________
Us: [Our position on this dimension, with evidence]
Them: [Their position, with evidence]
Buyer impact: [Why this matters to the buyer, not why it matters to us]
Verdict: [Advantage us / Advantage them / Parity]

DIMENSION 2: ________________________
Us: ________
Them: ________
Buyer impact: ________
Verdict: ________

DIMENSION 3: ________________________
Us: ________
Them: ________
Buyer impact: ________
Verdict: ________

DIMENSION 4: ________________________
Us: ________
Them: ________
Buyer impact: ________
Verdict: ________

DIMENSION 5: ________________________
Us: ________
Them: ________
Buyer impact: ________
Verdict: ________

SUMMARY
Dimensions where we win: ________
Dimensions where they win: ________
Dimensions at parity: ________
Our best competitive angle: [The 1-2 dimensions where we have the
strongest advantage AND the buyer cares the most]

How to Pick the Right Dimensions

The dimensions should come from deal data, not from your product team's feature list.

| Good Dimensions (decide deals) | Bad Dimensions (don't decide deals) | |-------------------------------|-------------------------------------| | Time to value / implementation speed | Number of features | | Framework coverage depth | UI aesthetics | | Evidence collection automation | Company founding date | | Multi-framework overlap handling | Number of employees | | Integration with buyer's existing stack | Number of customers (unless dramatically different) | | Support quality and responsiveness | Awards or analyst mentions | | Total cost of ownership (not just license) | Technology stack choice |

The test: Ask your last 5 closed-won and 5 closed-lost reps: "What was the deciding factor?" If a dimension doesn't appear in those answers, it doesn't belong on the battlecard.

Positioning Strategy

Based on the differentiation map, pick one of three competitive strategies:

| Strategy | When to Use | How It Sounds | |----------|------------|---------------| | Head-to-head | You win on the same dimensions they compete on | "We do what they do, but [faster / deeper / cheaper / with better support]." | | Reframe | You lose on their dimension but win on a different one that matters more | "They optimize for [X]. We optimize for [Y]. Here's why [Y] matters more for your situation." | | Niche | You dominate a specific segment or use case they don't serve well | "For [your specific situation], we're purpose-built. They're a general tool being used for a specific job." |

Most competitive deals are won by reframing, not by head-to-head comparison. If you're competing on their best dimension, you've already lost the positioning battle.

---

Phase 3: Persona-Specific Battlecard Assembly

Input: Differentiation map (Phase 2), competitor intel (Phase 1) Output: Battlecards formatted for each persona in the buying committee

Why Persona-Specific Matters

A CISO evaluating your product against a competitor asks different questions than a CTO evaluating the same comparison. The CISO wants to know about risk coverage and audit readiness. The CTO wants to know about engineering burden and integration overhead. Same competitor, different battlecard.

Battlecard Template (Per Persona)

COMPETITIVE BATTLECARD

Competitor: ________________________
Persona: ________________________ [CISO / CTO / Compliance Mgr / etc.]
Version: ________________________
Last updated: ________________________

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

QUICK REFERENCE (for live calls)

When the prospect mentions [Competitor], say:
"[One sentence acknowledgment that doesn't trash the competitor.
Example: 'They're a solid option. A lot of our customers evaluated
them too. What specifically appealed to you about their approach?']"

Then ask:
"[One diagnostic question that exposes the competitor's weakness
without naming it. Example: 'How important is [dimension where
we win] for your team?']"

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

OUR 3 ADVANTAGES FOR THIS PERSONA

1. [Advantage]: [One sentence. Why this persona cares.]
   Proof: [Customer quote, metric, case study specific to this persona]

2. [Advantage]: [One sentence.]
   Proof: ________

3. [Advantage]: [One sentence.]
   Proof: ________

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

THEIR 2 ADVANTAGES (be honest)

1. [Advantage]: [One sentence. Acknowledge it.]
   Our counter: [How to reframe this so it's less decisive.
   Not "that doesn't matter" but "here's the tradeoff they made
   to get that advantage."]

2. [Advantage]: ________
   Our counter: ________

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

LANDMINES TO SET

Questions to ask the prospect BEFORE they evaluate the competitor.
These seed criteria that favor you.

1. "How does your team handle [process where we're strong]?"
2. "What's your timeline for [outcome where we're faster]?"
3. "Have you thought about [dimension they'll struggle with]?"

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Stallin-Sanamandra](https://github.com/Stallin-Sanamandra)
- **Source:** [Stallin-Sanamandra/b2b-saas-marketing-skills](https://github.com/Stallin-Sanamandra/b2b-saas-marketing-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.