[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EE6RN31MP5WJ80BRZ7S7CV":3,"skill-same:01M6EE6RN31MP5WJ80BRZ7S7CV":91},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6EE6RN31MP5WJ80BRZ7S7CV","competitive-battlecard-generator",null,"ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fcompetitive-battlecard-generator\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25],"competitive","battlecard generator","competitive battlecard generator","2026-11-10 10:12:30",false,"# Competitive Battlecard Generator\n\n> A sequential system for building, maintaining, and deploying competitive\n> intelligence as battlecards. Each phase produces a defined output that feeds\n> the next. Phase 6 captures field intel that keeps battlecards current rather\n> than letting them decay into shelf-ware.\n\n## Why This Skill Exists\n\nCompetitive battlecards at most B2B SaaS companies are one of two things:\n\n1. **A feature comparison matrix that nobody reads.** Marketing builds a table\n   comparing 40 features. Checkmarks everywhere. Sales never opens it because\n   it doesn't tell them what to say when a prospect mentions the competitor\n   on a live call.\n\n2. **Tribal knowledge in the heads of 2-3 senior reps.** They know what to\n   say because they've lost deals to this competitor before. Nobody else on\n   the team has that context. When those reps leave, the intel leaves with\n   them.\n\nBoth fail because they confuse information with enablement. A battlecard\nisn't a data sheet. It's a decision aid that tells a rep exactly what to\nsay, what to ask, and what to avoid in a competitive deal, specific to\nthe persona they're talking to.\n\nThis skill builds battlecards that sales and BDRs actually use, keeps them\ncurrent with field feedback, and connects them to the rest of your go-to-market\nstack.\n\n## When to Use This Skill\n\n- Building a battlecard for a specific competitor from scratch\n- Updating an existing battlecard with new competitive intel\n- Responding to a competitor's product launch, pricing change, or acquisition\n- Preparing a BDR or AE for a deal where a specific competitor is involved\n- Analyzing win\u002Floss data to identify competitive patterns\n- Building persona-specific competitive talk tracks\n- Reviewing competitive positioning as part of quarterly planning\n- Onboarding new sales\u002FBDR team members on competitive landscape\n\n## When NOT to Use This Skill\n\n- General market research or industry analysis (this is competitor-specific)\n- Product roadmap planning (competitive intel informs it, but this isn't a\n  product management skill)\n- Pricing strategy (this skill covers how to handle competitor pricing\n  objections, not how to set your own prices)\n- Content creation for comparison\u002Falternative pages (use SEO or content skills\n  for that; this skill produces internal enablement, not external content)\n- Evaluating potential acquisition targets (different analysis framework)\n\n---\n\n## The Battlecard Pipeline: 6 Sequential Phases\n\n```\nPHASE 1              PHASE 2              PHASE 3\nCompetitor       →   Positioning &    →   Persona-Specific\nIntelligence          Differentiation      Battlecard\nGathering             Analysis             Assembly\n\n     ↓                                         ↓\n\nPHASE 6              PHASE 5              PHASE 4\nRefresh Cycle    ←   Win\u002FLoss         ←   Deployment &\n& Decay               Analysis             Enablement\nPrevention\n\n     ↓\n     └──→ PHASE 1 (next refresh cycle)\n```\n\n**The closed loop:** Phase 6 runs on a fixed cadence. Field intel from sales,\nnew competitor moves, and win\u002Floss patterns feed back into Phase 1. Battlecards\nthat aren't refreshed every 90 days get flagged for review or retirement.\n\n---\n\n## Phase 1: Competitor Intelligence Gathering\n\n**Input:** Competitor name, your product context, existing intel (if any)\n**Output:** Structured competitor intelligence brief\n\n### Intelligence Source Matrix\n\nGather from multiple sources. No single source gives you the full picture.\n\n| Source | Signal Quality | What to Extract | Update Frequency |\n|--------|---------------|-----------------|-----------------|\n| **Competitor website** | Medium | Pricing (if public), messaging, feature claims, customer logos, positioning changes | Monthly |\n| **G2\u002FTrustRadius reviews** | High | What their customers praise, what they complain about, switching reasons, comparison mentions | Monthly |\n| **Your win\u002Floss interviews** | Very High | Why you won, why you lost, what the buyer compared, what mattered most | After every closed deal |\n| **Sales call recordings** | High | What prospects say about the competitor unprompted, specific objections, feature comparisons mentioned | Ongoing |\n| **Competitor job postings** | Medium | Product direction signals (hiring for a new category = building it), tech stack, growth signals | Quarterly |\n| **Competitor blog\u002Fchangelog** | Medium | Feature launches, messaging shifts, vertical focus changes | Monthly |\n| **Industry analyst reports** | Medium | Market positioning, quadrant placement, analyst perspective on strengths\u002Fweaknesses | Annually or when published |\n| **Social media \u002F LinkedIn** | Low-Medium | Executive messaging, thought leadership themes, customer engagement, employee sentiment | Monthly |\n| **Patent\u002Ftechnical filings** | Low | Long-term product direction. Useful for enterprise competitors. | Quarterly |\n| **Former competitor employees** | Very High (if available) | Internal roadmap, culture, sales process, known weaknesses | Opportunistic |\n\n### Competitor Intelligence Brief Template\n\n```\nCOMPETITOR INTELLIGENCE BRIEF\n\nCompetitor: ________________________\nLast updated: ________________________\nUpdated by: ________________________\nNext review date: ________________________ (max 90 days)\n\nCOMPANY OVERVIEW\n- Founded: ________\n- HQ: ________\n- Funding \u002F public status: ________\n- Estimated revenue \u002F ARR: ________\n- Employee count: ________ (growth trend: ________)\n- Key investors \u002F parent company: ________\n\nPRODUCT OVERVIEW\n- Core product: [One sentence description]\n- Primary use case: [What most customers buy it for]\n- Secondary use cases: [What else it does]\n- Platform \u002F architecture: [Cloud-native, on-prem, hybrid]\n- Key integrations: [Tech stack dependencies]\n\nPRICING (as known)\n- Model: [Per user \u002F per asset \u002F per framework \u002F flat rate \u002F usage-based]\n- Entry price: $________ [source: ________]\n- Mid-market price: $________ [source: ________]\n- Enterprise price: $________ [source: ________]\n- Free tier \u002F trial: [Yes\u002FNo, details]\n- Contract terms: [Annual only, monthly available, multi-year discounts]\n- Known discounting behavior: [Aggressive, standard, rigid]\n\nTARGET MARKET\n- Primary segment: [SMB \u002F Mid-market \u002F Enterprise]\n- Key verticals: [Industries they focus on]\n- Geo focus: [Where they sell most]\n- ICP overlap with us: [High \u002F Medium \u002F Low, specifics]\n\nMESSAGING & POSITIONING\n- Primary value prop: [How they describe themselves]\n- Key differentiators (their claimed): [What they say makes them different]\n- Messaging themes: [Risk, speed, cost, compliance, developer experience, etc.]\n- Recent messaging shifts: [Any changes in how they position]\n\nKNOWN STRENGTHS (evidence-based, not assumed)\n1. [Strength] — Evidence: [G2 reviews, win\u002Floss data, customer quotes]\n2. [Strength] — Evidence: ________\n3. [Strength] — Evidence: ________\n\nKNOWN WEAKNESSES (evidence-based, not assumed)\n1. [Weakness] — Evidence: [G2 complaints, lost deals to us, technical gaps]\n2. [Weakness] — Evidence: ________\n3. [Weakness] — Evidence: ________\n\nRECENT MOVES (last 90 days)\n- Product: [New features, acquisitions, partnerships]\n- Pricing: [Changes, new tiers, discounting patterns]\n- Go-to-market: [New campaigns, verticals, channels]\n- People: [Key hires, departures, leadership changes]\n\nWHAT THEIR CUSTOMERS SAY (verbatim from G2\u002Freviews)\n- Positive: \"[Quote]\" — [Source]\n- Positive: \"[Quote]\" — [Source]\n- Negative: \"[Quote]\" — [Source]\n- Negative: \"[Quote]\" — [Source]\n\nWHAT OUR PROSPECTS SAY ABOUT THEM (from sales calls)\n- \"[Quote]\" — [Persona, deal stage, outcome]\n- \"[Quote]\" — [Persona, deal stage, outcome]\n```\n\n### Intelligence Quality Rules\n\n1. **Cite everything.** Every strength and weakness needs a source. \"We think\n   they're weak at X\" is an opinion. \"Three G2 reviews from mid-market CISOs\n   mention X as a limitation\" is intel.\n\n2. **Separate what they claim from what customers say.** Their website says\n   \"seamless integration.\" Their G2 reviews say \"integration took 3 months.\"\n   Both matter. The gap between the two is your ammunition.\n\n3. **Date everything.** Intel from 12 months ago is unreliable. Pricing from\n   6 months ago may have changed. Mark the date on every data point.\n\n4. **Don't invent weaknesses.** If you don't have evidence of a weakness,\n   don't list it. Reps who use unverified claims in deals lose credibility\n   when the prospect checks.\n\n---\n\n## Phase 2: Positioning & Differentiation Analysis\n\n**Input:** Competitor intelligence brief (Phase 1), your product context\n**Output:** Differentiation map with positioning strategy\n\n### Differentiation Framework\n\nDon't list 40 features. Identify the 3-5 dimensions that actually decide deals.\n\n```\nDIFFERENTIATION MAP\n\nCompetitor: ________________________\nAnalysis date: ________________________\n\nDIMENSION 1: ________________________\nUs: [Our position on this dimension, with evidence]\nThem: [Their position, with evidence]\nBuyer impact: [Why this matters to the buyer, not why it matters to us]\nVerdict: [Advantage us \u002F Advantage them \u002F Parity]\n\nDIMENSION 2: ________________________\nUs: ________\nThem: ________\nBuyer impact: ________\nVerdict: ________\n\nDIMENSION 3: ________________________\nUs: ________\nThem: ________\nBuyer impact: ________\nVerdict: ________\n\nDIMENSION 4: ________________________\nUs: ________\nThem: ________\nBuyer impact: ________\nVerdict: ________\n\nDIMENSION 5: ________________________\nUs: ________\nThem: ________\nBuyer impact: ________\nVerdict: ________\n\nSUMMARY\nDimensions where we win: ________\nDimensions where they win: ________\nDimensions at parity: ________\nOur best competitive angle: [The 1-2 dimensions where we have the\nstrongest advantage AND the buyer cares the most]\n```\n\n### How to Pick the Right Dimensions\n\nThe dimensions should come from deal data, not from your product team's\nfeature list.\n\n| Good Dimensions (decide deals) | Bad Dimensions (don't decide deals) |\n|-------------------------------|-------------------------------------|\n| Time to value \u002F implementation speed | Number of features |\n| Framework coverage depth | UI aesthetics |\n| Evidence collection automation | Company founding date |\n| Multi-framework overlap handling | Number of employees |\n| Integration with buyer's existing stack | Number of customers (unless dramatically different) |\n| Support quality and responsiveness | Awards or analyst mentions |\n| Total cost of ownership (not just license) | Technology stack choice |\n\n**The test:** Ask your last 5 closed-won and 5 closed-lost reps: \"What was the\ndeciding factor?\" If a dimension doesn't appear in those answers, it doesn't\nbelong on the battlecard.\n\n### Positioning Strategy\n\nBased on the differentiation map, pick one of three competitive strategies:\n\n| Strategy | When to Use | How It Sounds |\n|----------|------------|---------------|\n| **Head-to-head** | You win on the same dimensions they compete on | \"We do what they do, but [faster \u002F deeper \u002F cheaper \u002F with better support].\" |\n| **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.\" |\n| **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.\" |\n\nMost competitive deals are won by reframing, not by head-to-head comparison.\nIf you're competing on their best dimension, you've already lost the\npositioning battle.\n\n---\n\n## Phase 3: Persona-Specific Battlecard Assembly\n\n**Input:** Differentiation map (Phase 2), competitor intel (Phase 1)\n**Output:** Battlecards formatted for each persona in the buying committee\n\n### Why Persona-Specific Matters\n\nA CISO evaluating your product against a competitor asks different questions\nthan a CTO evaluating the same comparison. The CISO wants to know about risk\ncoverage and audit readiness. The CTO wants to know about engineering burden\nand integration overhead. Same competitor, different battlecard.\n\n### Battlecard Template (Per Persona)\n\n```\nCOMPETITIVE BATTLECARD\n\nCompetitor: ________________________\nPersona: ________________________ [CISO \u002F CTO \u002F Compliance Mgr \u002F etc.]\nVersion: ________________________\nLast updated: ________________________\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nQUICK REFERENCE (for live calls)\n\nWhen the prospect mentions [Competitor], say:\n\"[One sentence acknowledgment that doesn't trash the competitor.\nExample: 'They're a solid option. A lot of our customers evaluated\nthem too. What specifically appealed to you about their approach?']\"\n\nThen ask:\n\"[One diagnostic question that exposes the competitor's weakness\nwithout naming it. Example: 'How important is [dimension where\nwe win] for your team?']\"\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nOUR 3 ADVANTAGES FOR THIS PERSONA\n\n1. [Advantage]: [One sentence. Why this persona cares.]\n   Proof: [Customer quote, metric, case study specific to this persona]\n\n2. [Advantage]: [One sentence.]\n   Proof: ________\n\n3. [Advantage]: [One sentence.]\n   Proof: ________\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTHEIR 2 ADVANTAGES (be honest)\n\n1. [Advantage]: [One sentence. Acknowledge it.]\n   Our counter: [How to reframe this so it's less decisive.\n   Not \"that doesn't matter\" but \"here's the tradeoff they made\n   to get that advantage.\"]\n\n2. [Advantage]: ________\n   Our counter: ________\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nLANDMINES TO SET\n\nQuestions to ask the prospect BEFORE they evaluate the competitor.\nThese seed criteria that favor you.\n\n1. \"How does your team handle [process where we're strong]?\"\n2. \"What's your timeline for [outcome where we're faster]?\"\n3. \"Have you thought about [dimension they'll struggle with]?\"\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nOBJECTION RESPONSES (persona-specific)\n\n\"[Competitor] is cheaper.\"\n→ [Response framework. Not \"we're worth more.\" Instead: \"What's\nincluded in that price? When our customers compared total cost\nincluding [implementation \u002F maintenance \u002F FTE time], the gap\n[narrowed \u002F reversed].\"]\n\n\"[Competitor] has [feature we don't have].\"\n→ [Response. Acknowledge, then redirect: \"That's true. The\ntradeoff is [what they sacrificed to build that]. For teams\nthat prioritize [your strength], that tradeoff matters.\"]\n\n\"We're already using [Competitor].\"\n→ [Response. Don't pitch a rip-and-replace. Instead: \"What's\nworking well? What do you wish was different?\" Find the gap.\nIf no gap exists, this isn't your deal right now.]\n\n\"[Competitor] has more customers \u002F is bigger.\"\n→ [Response. \"They do. For teams in [your niche \u002F segment \u002F\nuse case], we have [X] customers including [names if allowed].\nThe question is whether a bigger company optimizes for your\nspecific needs or for the average of all their customers.\"]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTRAP QUESTIONS TO WATCH FOR\n\nThings the competitor may have coached the prospect to ask you.\n\n1. \"[Question]\" — Why they ask: [What the competitor wants to expose]\n   How to respond: [Honest answer that doesn't concede the deal]\n\n2. \"[Question]\" — Why they ask: ________\n   How to respond: ________\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nPROOF POINTS FOR THIS PERSONA\n\n| Customer | Similar to Prospect? | Key Metric | Quote |\n|----------|---------------------|------------|-------|\n| | [Industry, size, use case] | | |\n| | | | |\n| | | | |\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nDO NOT SAY\n\n1. [Specific claim about competitor that is unverified or legally risky]\n2. [Trash talk or subjective insults about competitor quality]\n3. [Outdated information that has been corrected]\n```\n\n### Battlecard Honesty Rules\n\n1. **Always include their advantages.** A battlecard that says you win on\n   every dimension is a battlecard nobody trusts. Sales reps know when\n   you're hiding the competitor's strengths. Include them and teach reps\n   how to handle them.\n\n2. **Never fabricate weaknesses.** If you don't have evidence, don't include\n   it. A rep who claims \"their platform goes down constantly\" and the\n   prospect says \"actually we've had zero downtime issues\" just destroyed\n   your credibility.\n\n3. **Never instruct reps to trash the competitor.** The framing is always\n   \"here's the tradeoff\" not \"they're bad.\" Prospects respect sellers who\n   acknowledge competitor strengths. They distrust sellers who only attack.\n\n4. **Include a \"Do Not Say\" section.** Legal risks, outdated claims, and\n   unverified rumors go here. Protect reps from themselves.\n\n---\n\n## Phase 4: Deployment & Enablement\n\n**Input:** Persona-specific battlecards (Phase 3)\n**Output:** Trained sales\u002FBDR team with accessible battlecards\n\n### Deployment Checklist\n\nBuilding the battlecard is half the work. Getting reps to actually use it is\nthe other half.\n\n| Step | Action | Owner | Timeline |\n|------|--------|-------|----------|\n| 1 | Store battlecards in a single, searchable location (not buried in Google Drive) | Marketing ops | Before enablement session |\n| 2 | Run a 30-minute enablement session per competitor (not a deck review; a live roleplay) | Product marketing \u002F demand gen lead | Within 1 week of battlecard release |\n| 3 | Roleplay the top 3 objection scenarios with BDRs and AEs | Sales manager | During enablement session |\n| 4 | Share the \"Quick Reference\" section as a Slack-accessible snippet | Marketing ops | Same day as enablement |\n| 5 | Add battlecard link to CRM deal record template (so reps see it when a competitor is tagged) | Marketing ops | Within 1 week |\n| 6 | Collect initial feedback from reps after first 2 weeks of use | Product marketing | 2 weeks post-launch |\n\n### Enablement Session Structure (30 minutes per competitor)\n\n```\nCOMPETITIVE ENABLEMENT SESSION\n\nCompetitor: ________________________\nDuration: 30 minutes\nAttendees: BDR team, AEs, sales leadership\n\nSECTION 1: CONTEXT (5 minutes)\n- Who is this competitor (1 minute)\n- Where we see them in deals: which segments, which personas,\n  how often (2 minutes)\n- Our win rate against them and what decides it (2 minutes)\n\nSECTION 2: THE BATTLECARD (10 minutes)\n- Walk through the 3 advantages (with proof points)\n- Walk through their 2 advantages (with counters)\n- Show the landmine questions\n\nSECTION 3: LIVE ROLEPLAY (15 minutes)\n- Scenario 1: Prospect says \"We're also looking at [Competitor]\"\n  One rep plays prospect, another plays seller. Group gives feedback.\n- Scenario 2: Prospect says \"[Competitor] is cheaper\"\n  Same format.\n- Scenario 3: Prospect says \"We're already using [Competitor]\"\n  Same format.\n\nOUTPUT: Reps leave with the Quick Reference card and confidence\nto handle the top 3 competitive scenarios.\n```\n\n### Accessibility Rules\n\n| Rule | Rationale |\n|------|-----------|\n| Battlecards must be accessible in under 10 seconds during a live call | If a rep can't find it fast, they won't use it |\n| Store in the tool reps already use (Slack, CRM, Notion, Guru, Gong) | Don't create a new destination. Embed in existing workflow. |\n| Mobile-friendly format | Reps take calls on their phones. A PDF that requires pinch-to-zoom is useless. |\n| Searchable by competitor name | \"How do we beat [X]\" should return the right battlecard instantly |\n| Version-dated | Reps need to know if they're looking at current intel or 6-month-old data |\n\n---\n\n## Phase 5: Win\u002FLoss Analysis\n\n**Input:** Closed deal data (won and lost), sales feedback\n**Output:** Competitive win\u002Floss patterns that update battlecards\n\n### Win\u002FLoss Data Collection\n\nCapture this for every competitive deal, not just the ones you lost.\n\n```\nWIN\u002FLOSS COMPETITIVE DATA\n\nDeal: ________________________\nOutcome: Won \u002F Lost\nCompetitor(s) in deal: ________________________\nDecision-maker persona: ________________________\nSegment: [C1 \u002F C2 \u002F Enterprise]\nACV: $________\nSales cycle length: ________ days\n\nPRIMARY REASON FOR OUTCOME (pick one):\n[ ] Price \u002F total cost\n[ ] Product capability \u002F feature gap\n[ ] Integration \u002F technical fit\n[ ] Ease of use \u002F user experience\n[ ] Implementation speed \u002F time to value\n[ ] Support \u002F customer success quality\n[ ] Brand \u002F trust \u002F market presence\n[ ] Existing relationship with competitor\n[ ] Champion influence\n[ ] Procurement \u002F legal \u002F security requirements\n[ ] Other: ________________________\n\nDETAILS (from rep or buyer interview):\nWhat did the buyer say was most important? ________________________\nWhat did they say about us vs. competitor? ________________________\nIf lost: What would have changed the outcome? ________________________\nIf won: What almost made them choose the competitor? ________________________\n\nQUOTE (if available):\n\"________________________\" — [Buyer persona, anonymous company description]\n```\n\n### Win\u002FLoss Pattern Analysis\n\nRun quarterly. Look for patterns, not anecdotes.\n\n```\nWIN\u002FLOSS COMPETITIVE ANALYSIS\n\nCompetitor: ________________________\nPeriod: Q__ 20__\nDeals analyzed: __ won, __ lost\n\nWIN RATE VS. THIS COMPETITOR: __%\n\nTOP 3 REASONS WE WON:\n1. [Reason] — appeared in __% of wins\n2. [Reason] — appeared in __% of wins\n3. [Reason] — appeared in __% of wins\n\nTOP 3 REASONS WE LOST:\n1. [Reason] — appeared in __% of losses\n2. [Reason] — appeared in __% of losses\n3. [Reason] — appeared in __% of losses\n\nPATTERNS BY PERSONA:\n- When decision-maker is [Persona A]: win rate __% (we win because ________)\n- When decision-maker is [Persona B]: win rate __% (we lose because ________)\n\nPATTERNS BY SEGMENT:\n- C1 (SMB) deals: win rate __%\n- C2 (Mid-market) deals: win rate __%\n\nPATTERNS BY DEAL SIZE:\n- Deals under $__K ACV: win rate __%\n- Deals over $__K ACV: win rate __%\n\nBATTLECARD UPDATES NEEDED:\n1. [What to add\u002Fchange based on this data]\n2. [What to add\u002Fchange]\n3. [What to remove because it's no longer accurate]\n```\n\n### Win\u002FLoss Interview Guide\n\nThe best competitive intel comes from buyers who chose the competitor, not from\nyour own team's speculation. Run these interviews within 30 days of a lost deal.\n\n```\nWIN\u002FLOSS INTERVIEW GUIDE (15-20 minutes)\n\nConducted by: [Someone other than the rep who owned the deal.\nBuyers are more honest with a neutral party.]\n\nOPENING:\n\"Thanks for taking the time. We're trying to improve our product and\nour process. Your honest feedback helps, and there are no wrong answers.\"\n\nQUESTIONS:\n\n1. \"Walk me through your evaluation process. How did you decide which\n   vendors to look at?\"\n   [Understand how they found you and the competitor]\n\n2. \"What were the 2-3 criteria that mattered most in your decision?\"\n   [Don't suggest criteria. Let them name them unprompted.]\n\n3. \"How did [Competitor] perform against those criteria vs. us?\"\n   [Get the specific comparison on their terms, not yours]\n\n4. \"Was there a moment in the evaluation where you felt one option\n   pulled ahead? What was it?\"\n   [Identify the tipping point. This is the most valuable insight.]\n\n5. \"How did pricing factor into the decision?\"\n   [If price was the decider, dig into whether it was license cost\n   or total cost including implementation and maintenance]\n\n6. \"If you could change one thing about our product or our process\n   during the evaluation, what would it be?\"\n   [Product feedback AND sales process feedback in one question]\n\n7. \"Anything else you'd want us to know?\"\n   [Open-ended. Sometimes the most useful insight comes here.]\n```\n\n---\n\n## Phase 6: Refresh Cycle & Decay Prevention\n\n**Input:** Field intel (Phase 5), competitor monitoring (Phase 1 sources)\n**Output:** Updated battlecards on a fixed cadence\n\n### Refresh Cadence\n\n| Trigger | Action | Timeline |\n|---------|--------|----------|\n| **Scheduled refresh** | Full battlecard review against latest intel | Every 90 days, non-negotiable |\n| **Competitor product launch** | Update product overview, assess impact on differentiation map, update objection responses | Within 1 week of announcement |\n| **Competitor pricing change** | Update pricing section, recalculate TCO comparison, update pricing objection response | Within 1 week of confirmation |\n| **Competitor acquisition \u002F merger** | Reassess entire competitive landscape. May require new battlecard or retirement of old one. | Within 2 weeks |\n| **Win\u002Floss pattern shift** | If win rate against a competitor changes by >10% in a quarter, investigate and update | Within 2 weeks of quarterly analysis |\n| **New evidence from sales** | Update specific sections (quotes, objection responses, proof points) as intel arrives | Within 1 week of receiving intel |\n| **Competitor messaging shift** | Update positioning analysis, check if your landmine questions still work | Within 2 weeks |\n\n### Decay Prevention Rules\n\nBattlecards without maintenance become liabilities. A rep using 6-month-old\npricing data or a discontinued feature comparison in a live deal does more\ndamage than having no battlecard at all.\n\n```\nBATTLECARD HEALTH CHECK (run quarterly)\n\nFor each active battlecard:\n\n[ ] Last updated date is within 90 days\n    If not: schedule immediate refresh or retire\n\n[ ] Pricing data verified within 60 days\n    If not: check competitor website, G2, recent deal intel\n\n[ ] All customer quotes and proof points are from current customers\n    (not churned accounts)\n    If not: replace with current references\n\n[ ] Win\u002Floss data reflects the last 2 quarters, not historical averages\n    If not: rerun win\u002Floss analysis\n\n[ ] At least 2 reps have given feedback on battlecard accuracy\n    in the last quarter\n    If not: collect feedback before next refresh\n\n[ ] No items in \"Do Not Say\" section that should now be in the\n    main battlecard (competitor fixed a weakness, or claim is\n    now verified)\n    If not: update accordingly\n\nHEALTH STATUS:\n[ ] Green: all checks pass. Schedule next review in 90 days.\n[ ] Yellow: 1-2 checks failed. Fix within 2 weeks.\n[ ] Red: 3+ checks failed. Battlecard unreliable. Pull from\n    circulation until refreshed.\n```\n\n### Competitor Monitoring Automation\n\nWhere possible, automate the intel gathering so refreshes are data-informed,\nnot memory-dependent.\n\n| Source | Automation | Tool Options |\n|--------|-----------|-------------|\n| Competitor website changes | Page change monitoring | Visualping, ChangeTower, or manual monthly screenshot |\n| G2 new reviews | Alert on new reviews for competitor | G2 alerts (if available on your plan) |\n| Job postings | Track new roles with keywords | LinkedIn alerts, Otta, or manual quarterly check |\n| News \u002F press | Google Alerts for competitor name | Google Alerts, Feedly |\n| Pricing page changes | Page change monitoring on pricing URL | Visualping on their pricing page specifically |\n| Social media \u002F LinkedIn | Track competitor company page and key execs | LinkedIn notifications, manual monthly check |\n\n---\n\n## Integration Notes\n\n### With Other Skills in This Repo\n\n- **BDR Enablement Generator:** Phase 6 objection handling and Phase 4 message\n  templates should reference battlecard content. When a BDR encounters a\n  competitive deal, they pull from the battlecard's Quick Reference and\n  persona-specific objection responses. The BDR skill's monthly performance\n  review (Phase 7) captures competitor mentions that feed back into\n  battlecard updates here.\n\n- **ABM Program Orchestrator:** Phase 2 account selection includes competitive\n  displacement opportunities. The battlecard's intel on competitor weaknesses\n  and contract renewal timing directly informs which accounts to target for\n  ABM and what messaging angle to lead with.\n\n- **GRC Messaging Guardrails:** All competitive claims referencing compliance\n  frameworks must be validated. Saying \"[Competitor] doesn't support HIPAA\"\n  when they actually do, or saying \"we're SOC 2 certified\" (attestation, not\n  certification) in a competitive context, is a credibility-destroying error\n  in front of the exact buyer you're trying to win.\n\n- **Pipeline Attribution Narrator:** Competitive deal outcomes should be\n  trackable in attribution data. Tag competitive deals in CRM so you can\n  measure whether your win rate differs by channel source. If ABM-sourced\n  competitive deals have a higher win rate than inbound competitive deals,\n  that informs both battlecard deployment and channel allocation.\n\n- **Marketing Ops SOP Generator:** Battlecard distribution and version control\n  follow the change management process from Phase 7. Updates to battlecards\n  should be logged and communicated through the same channels as other\n  marketing ops changes.\n\n### With Your Tech Stack\n\n- **HubSpot \u002F CRM:** Create a custom deal property for \"Competitor in Deal\"\n  (dropdown). This enables win\u002Floss analysis by competitor in Phase 5. Add\n  a required field for competitive loss reason on closed-lost deals.\n\n- **Gong \u002F Chorus \u002F call recording:** Keyword alerts for competitor names\n  surface competitive mentions automatically. Use these as a continuous\n  intel source for Phase 6 refreshes.\n\n- **Slack:** Create a #competitive-intel channel. Reps post competitor\n  mentions and buyer quotes in real-time. Marketing aggregates these\n  during refresh cycles. Pin the current battlecard Quick Reference in\n  the channel.\n\n- **Guru \u002F Notion \u002F internal wiki:** Store full battlecards here. The Quick\n  Reference cards go in Slack. Link CRM deal records to the relevant\n  battlecard so reps can access it from the deal they're working.\n\n---\n\n## Common Battlecard Mistakes\n\n| Mistake | What Happens | How to Avoid |\n|---------|-------------|--------------|\n| **Feature comparison matrix instead of battlecard** | 40-row table nobody reads. Reps still wing it on calls. | Focus on 3 advantages, 2 honest disadvantages, and specific talk tracks. Less is more. |\n| **Same battlecard for every persona** | CISO gets CTO talking points. CTO gets compliance language. Neither resonates. | Build persona-specific cards. At minimum: technical evaluator, economic buyer, day-to-day user. |\n| **Only listing your advantages** | Reps get blindsided when prospects mention competitor strengths. Credibility lost. | Always include their advantages with honest counters. Reps who acknowledge competitor strengths build more trust. |\n| **Building it and never updating it** | Pricing is 8 months old. Feature they \"lacked\" was shipped 3 months ago. Rep uses outdated claim, prospect corrects them. | 90-day refresh cycle. Phase 6. Non-negotiable. |\n| **No field validation** | Battlecard is built from marketing's assumptions, not from what buyers actually say. | Win\u002Floss interviews (Phase 5) are the ground truth. Build from deal data, not product marketing's positioning deck. |\n| **Storing it somewhere nobody looks** | Beautiful battlecard in a Google Drive folder with 200 other docs. Usage rate: 0%. | Embed in the tools reps already use: Slack, CRM, Gong, Guru. If they have to go find it, they won't. |\n| **Trashing the competitor** | Prospect respects the competitor. Your rep insults them. Prospect disqualifies you on trust. | Never trash. Always reframe. \"They optimize for X, which makes sense for some teams. We optimize for Y, which matters more when [prospect's situation].\" |\n| **No enablement session** | Battlecard emailed to the team with \"please review.\" Nobody reviews it. | 30-minute enablement session with live roleplay. Phase 4. It's the difference between a document and a capability. |\n\n---\n\n## Validation Checklist\n\nRun this before deploying any new or refreshed battlecard.\n\n### Intelligence Quality\n- [ ] All strengths and weaknesses have cited evidence (not assumptions)\n- [ ] Pricing data sourced and dated within 60 days\n- [ ] At least 3 G2\u002Freview data points included\n- [ ] At least 2 win\u002Floss data points from your own deals\n- [ ] \"Recent Moves\" section current within 30 days\n- [ ] No unverified claims in the battlecard\n\n### Battlecard Structure\n- [ ] Quick Reference section is usable in under 10 seconds on a live call\n- [ ] 3 advantages with proof points per persona\n- [ ] 2 honest competitor advantages with counters\n- [ ] Landmine questions test well (ask a rep if they'd use them)\n- [ ] Objection responses cover the top 3-4 competitive objections\n- [ ] \"Do Not Say\" section included\n- [ ] Persona-specific versions for at least 2 key personas\n\n### Deployment Readiness\n- [ ] Stored in accessible, searchable location\n- [ ] Enablement session scheduled within 1 week\n- [ ] Roleplay scenarios prepared for session\n- [ ] Quick Reference shared in Slack \u002F team channel\n- [ ] CRM deal template links to battlecard\n- [ ] Feedback collection planned for 2 weeks post-launch\n\n### Maintenance\n- [ ] Next refresh date set (max 90 days)\n- [ ] Competitor monitoring alerts configured\n- [ ] Win\u002Floss data collection process active for competitive deals\n- [ ] Decay prevention health check scheduled quarterly\n\n---\n\n## Changelog\n\n- **v1.0** (March 2026): Initial release. 6-phase sequential pipeline, intelligence gathering framework, differentiation analysis, persona-specific battlecard templates, deployment and enablement playbook, win\u002Floss analysis system, refresh cycle with decay prevention.\n",{},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fcompetitive-battlecard-generator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":7,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill competitive-battlecard-generator",{"tool":45,"command":46},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill competitive-battlecard-generator",{"tool":48,"command":49},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill competitive-battlecard-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FStallin-Sanamandra\u002Fb2b-saas-marketing-skills\u002Fcompetitive-battlecard-generator\u002FSKILL.md",true,[53,59,63,67,71,75,79,83,87],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",16471,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002FREADME.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Farchitecture.md",33004,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Farchitecture.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fcomposition.md",34942,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Fcomposition.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Feffects.md",72928,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Feffects.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Finputs.md",24586,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Finputs.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Foptimization.md",24265,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Foptimization.md",{"path":80,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fscenes.md",37487,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Fscenes.md",{"path":84,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fshaders.md",50435,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Fshaders.md",{"path":88,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ftroubleshooting.md",13246,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002FWORM_V2_SOVEREIGN\u002Fblob\u002Fmain\u002Fcore\u002Fhermes-agent\u002Fskills\u002Fcreative\u002Fascii-video\u002Freferences\u002Ftroubleshooting.md",[92,102,112,121,127,134],{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":26},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[97],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[99,100,101],"model","model hierarchy","model hierarchy skill",{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":26},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[107],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[109,110,111],"MCP","zoom","zoom mcp",{"skillNo":113,"name":114,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":26},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[118,119,120,110],"sdk","zoom apps sdk","apps",{"skillNo":122,"name":123,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":26},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[123],{"skillNo":128,"name":129,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":26},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[132],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[129],{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":26},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[136]]