Marketing & sales
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.
travisjneuman · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add travisjneuman/.claude --skill battle-card-builderAbout this skill
name: battle-card-builder description: Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.
Battle Card Builder
Structured frameworks for creating competitive battle cards that help sales teams win against specific competitors.
Battle Card Structure
Standard Battle Card Sections
BATTLE CARD LAYOUT:
1. COMPETITOR SNAPSHOT (top of page)
- Company name, logo, tagline
- Founded, HQ, headcount, funding/revenue
- Target market and primary use case
- Threat level: HIGH / MEDIUM / LOW
2. QUICK COMPARISON TABLE
- Feature-by-feature comparison
- Pricing comparison
- Target customer comparison
3. OUR STRENGTHS (vs. this competitor)
- 3-5 key advantages with proof points
- Customer quotes that validate each strength
4. THEIR STRENGTHS (honest assessment)
- 2-3 areas where competitor excels
- How to acknowledge without conceding
5. OBJECTION HANDLING
- Top 5-7 objections prospects raise
- Recommended responses for each
6. WIN THEMES
- 3-4 messaging themes that resonate
- Discovery questions to surface our advantages
7. LANDMINES
- Questions to plant that expose competitor weaknesses
- Features to demo that highlight differentiation
8. RECENT INTEL
- Latest product releases or changes
- Pricing changes
- Key wins/losses
- Last updated date
Competitive Intelligence Gathering
Intelligence Sources
| Source | Data Type | Refresh Frequency | Reliability |
|---|---|---|---|
| Competitor website | Pricing, features, messaging | Monthly | High |
| G2/Capterra reviews | User sentiment, complaints | Monthly | Medium-High |
| Job postings | Strategic direction, tech stack | Quarterly | Medium |
| SEC filings / investor decks | Revenue, strategy, risks | Quarterly | High |
| Patent filings | Future product direction | Quarterly | Medium |
| Win/loss interviews | Real buyer reasoning | Ongoing | High |
| Sales call recordings | Objections, competitor mentions | Ongoing | High |
| Industry analyst reports | Market positioning | Annually | High |
| Social media / forums | Product issues, sentiment | Weekly | Low-Medium |
| Conference presentations | Roadmap, vision | As available | Medium |
Intelligence Collection Framework
COLLECTION CADENCE:
WEEKLY:
- Social listening for competitor mentions
- Review new G2/Capterra reviews
- Check competitor blog/news for announcements
MONTHLY:
- Full website and pricing page review
- Feature comparison audit
- Gong/Chorus analysis of competitor mentions in calls
- Win/loss interview synthesis
QUARTERLY:
- Deep competitive analysis refresh
- Battle card full update
- Sales team feedback collection
- Market positioning reassessment
ANNUALLY:
- Comprehensive competitive landscape review
- Strategic differentiation audit
- Battle card rebuild from scratch
Positioning Frameworks
Competitive Positioning Matrix
POSITIONING MAP:
HIGH CAPABILITY
|
|
NICHE LEADER | MARKET LEADER
(deep in segment) | (broad + deep)
|
─────────────────────+──────────────────────
LOW REACH | HIGH REACH
|
EMERGING PLAYER | BROAD PLAYER
(limited scope) | (wide but shallow)
|
LOW CAPABILITY
POSITION US: [where we sit]
POSITION COMPETITOR: [where they sit]
NARRATIVE: "While [Competitor] covers more ground, we go deeper
in [our segment] where it matters most for [buyer]."
Differentiation Categories
| Category | Our Position | Competitor Position | Talking Point |
|---|---|---|---|
| Product | [specific feature/capability] | [their approach] | [why ours matters] |
| Technology | [architecture/approach] | [their architecture] | [technical advantage] |
| Service | [support model] | [their support model] | [customer impact] |
| Price | [pricing model] | [their pricing model] | [value story] |
| Market Focus | [our ICP] | [their ICP] | [specialization benefit] |
| Integration | [ecosystem fit] | [their ecosystem] | [workflow advantage] |
| Security | [certifications/approach] | [their posture] | [trust factor] |
Objection Handling Templates
Objection Response Framework
STRUCTURE FOR EVERY OBJECTION:
ACKNOWLEDGE: Validate the concern without agreeing
BRIDGE: Transition to your perspective
RESPOND: Address with evidence and specifics
EVIDENCE: Proof point (customer, data, demo)
EXAMPLE:
OBJECTION: "[Competitor] has more integrations than you."
ACKNOWLEDGE: "Integration breadth is important — I understand
why that's a factor in your evaluation."
BRIDGE: "What we've found with customers in your space is that
it's less about the total number and more about depth
of the integrations you actually use."
RESPOND: "We have 40+ integrations focused on [their stack],
with bi-directional sync and real-time data flow.
[Competitor]'s integrations are often one-directional
or require manual configuration."
EVIDENCE: "[Customer X] evaluated both and chose us specifically
because our [specific integration] saved their team
12 hours per week vs. the manual workaround with
[Competitor]'s connector."
Common Objection Categories
PRICING OBJECTIONS:
- "They're cheaper"
- "We can't justify the premium"
- "Their free tier is sufficient"
FEATURE OBJECTIONS:
- "They have [feature] that you don't"
- "Their product does more"
- "We need [specific capability]"
MARKET OBJECTIONS:
- "They're the market leader"
- "Everyone in our industry uses them"
Read the complete source ↗