--- 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" - "They have more customers like us" RISK OBJECTIONS: - "They're a bigger, safer company" - "What if you get acquired?" - "We're already using them and switching is risky" RELATIONSHIP OBJECTIONS: - "We already have a contract with them" - "Our team is trained on their platform" - "Our exec has a personal relationship there" ``` ## Win Theme Templates ### Discovery Questions That Favor Us ``` QUESTION DESIGN PRINCIPLE: Ask questions whose honest answers reveal competitor weaknesses without mentioning the competitor by name. FORMAT: Question → Expected Answer → Bridge to Our Strength EXAMPLES: Q: "How important is [our strength area] to your workflow?" A: [Prospect describes importance] B: "That's exactly where we've invested most deeply..." Q: "What's your experience been with [pain our product solves]?" A: [Prospect describes pain] B: "We hear that a lot from teams who've used [category]. Here's how we approach it differently..." Q: "When you evaluated solutions before, what fell short?" A: [Prospect describes gaps] B: "Those are the exact gaps we were built to fill..." ``` ### Landmine Questions ``` LANDMINE STRATEGY: Plant questions the prospect will ask the competitor that expose their weaknesses. TEMPLATE: "When you're evaluating [Competitor], you might want to ask them about [specific weakness area]. Specifically: 1. [Question about their known limitation] 2. [Question about their pricing gotcha] 3. [Question about their support gap] These are areas where we've seen prospects get surprised during implementation, and it's worth clarifying upfront." RULES: - Never lie or exaggerate competitor weaknesses - Base landmines on documented, verified issues - Keep it professional — attack the product, not the people - Be prepared for the competitor to do the same to you ``` ## Pricing Comparison Framework ### Pricing Analysis Template ``` PRICING COMPARISON: US COMPETITOR ────────────────────────────────────────────────── Model: [per seat] [per usage] Entry Price: $___/mo $___/mo Mid-Market: $___/mo $___/mo Enterprise: $___/mo $___/mo HIDDEN COSTS: - Implementation: [included] [$X extra] - Support: [included] [paid tier] - Integrations: [included] [add-on] - Storage/Usage: [included] [overage fees] TRUE TCO (3-year, 100 users): Us: $______ Competitor: $______ Savings: $______ (__%) WIN NARRATIVE: "While their list price appears [lower/similar], when you factor in [hidden cost 1] and [hidden cost 2], the total cost of ownership over 3 years is actually [X%] higher." ``` ## Battle Card Maintenance ### Update Cadence | Component | Update Frequency | Owner | | --- | --- | --- | | Competitor snapshot | Quarterly | Competitive Intel | | Feature comparison | Monthly | Product Marketing | | Pricing comparison | Quarterly (or on change) | Pricing Team | | Objection handling | Monthly (from win/loss) | Sales Enablement | | Win themes | Quarterly | Product Marketing | | Customer proof points | Monthly | Customer Marketing | | Recent intel | Weekly | Competitive Intel | ### Staleness Indicators ``` BATTLE CARD IS STALE WHEN: RED FLAGS: - Last updated > 90 days ago - Competitor released major product update since last refresh - Win rate against competitor dropped > 5% QoQ - Sales reps report card is "not useful" - Pricing information is outdated HEALTH CHECK QUESTIONS: - When was this last updated? [date] - Has competitor launched anything since? [Y/N] - Have we validated with recent win/loss data? [Y/N] - Do sales reps actively use this card? [Y/N] - Is our proof point data current? [Y/N] ``` ### Win/Loss Integration ``` WIN/LOSS DATA COLLECTION: AFTER EVERY COMPETITIVE DEAL: 1. Record outcome (win/loss) 2. Document primary reasons (top 3) 3. Note competitor strengths that resonated 4. Note our strengths that resonated 5. Capture any new objections heard 6. Flag any pricing intelligence QUARTERLY ANALYSIS: - Win rate by competitor (trending) - Top reasons for wins (reinforce in card) - Top reasons for losses (address in card) - New objections to add - Proof points to update ``` ## Battle Card Quality Checklist | Check | Status | | --- | --- | | Competitor info verified within last 30 days | [ ] | | Pricing data confirmed (not assumed) | [ ] | | At least 3 customer proof points per strength | [ ] | | Objection responses tested with top reps | [ ] | | Win themes validated by recent win/loss data | [ ] | | Honest about competitor strengths (credibility) | [ ] | | No unverified claims or speculation | [ ] | | Formatting is scannable (not wall of text) | [ ] | | Card fits on 2 pages (front and back) | [ ] | | Last updated date is visible | [ ] | ## See Also - [Sales](../sales/SKILL.md) - [Marketing](../marketing/SKILL.md) - [Document Skills: DOCX](../document-skills/docx/SKILL.md) - [Product Management](../product-management/SKILL.md)