关于 battle-card-builder
为销售团队制作针对特定竞争对手的作战卡提供结构化框架,涵盖竞争情报、定位、异议应对、价格比较和持续更新。
主要功能
- 01竞争情报来源与收集周期框架
- 02定位与差异化模板
- 03异议回应和制胜主题模板
- 04价格比较与更新指南
适用场景
- 01为针对竞争对手的销售机会做准备
- 02整理定位和异议回应所需的证据
- 03依据输赢分析反馈更新作战卡
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ travisjneuman/ .claude --skill battle-card-builder安装后在 Claude Code 中输入/battle-card-builder确认已加载。
详细介绍
竞争对战卡构建器
用于创建结构化竞争对战卡的框架,帮助销售团队在与特定竞争对手的竞争中胜出。
对战卡结构
标准对战卡章节
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
竞争情报收集
情报来源
| 来源 | 数据类型 | 更新频率 | 可靠性 |
|---|---|---|---|
| 竞争对手网站 | 定价、功能、信息传达 | 每月 | 高 |
| G2/Capterra 评论 | 用户情绪、投诉 | 每月 | 中高 |
| 招聘信息 | 战略方向、技术栈 | 每季度 | 中 |
| SEC 文件/投资者演示文稿 | 收入、战略、风险 | 每季度 | 高 |
| 专利申请 | 未来产品方向 | 每季度 | 中 |
| 赢单/丢单访谈 | 买家的真实决策理由 | 持续进行 | 高 |
| 销售通话录音 | 异议、竞争对手提及情况 | 持续进行 | 高 |
| 行业分析师报告 | 市场定位 | 每年 | 高 |
| 社交媒体/论坛 | 产品问题、用户情绪 | 每周 | 低至中 |
| 会议演讲 | 路线图、愿景 | 有资料时 | 中 |
情报收集框架
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 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]."
差异化类别
| 类别 | 我们的定位 | 竞争对手的定位 | 介绍要点 |
|---|---|---|---|
| 产品 | [具体功能/能力] | [他们的做法] | [我们的优势为何重要] |
| 技术 | [架构/方法] | [他们的架构] | [技术优势] |
| 服务 | [支持模式] | [他们的支持模式] | [对客户的影响] |
| 价格 | [定价模式] | [他们的定价模式] | [价值说明] |
| 市场重点 | [我们的 ICP] | [他们的 ICP] | [专业化优势] |
| 集成 | [生态系统适配度] | [他们的生态系统] | [工作流优势] |
| 安全 | [认证/方法] | [他们的安全态势] | [信任因素] |
异议处理模板
异议回应框架
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."
常见异议类别
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"
赢单主题模板
有利于我们的探索问题
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 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:
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 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 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
对战卡质量检查清单
| 检查项 | 状态 |
|---|---|
| 竞争对手信息已在过去 30 天内核实 | [ ] |
| 定价数据已确认(而非假设) | [ ] |
| 每项优势至少有 3 个客户证明材料 | [ ] |
| 已与顶尖销售代表测试异议回应 | [ ] |
| 赢单主题已由近期赢单/丢单数据验证 | [ ] |
| 如实说明竞争对手的优势(保持可信度) | [ ] |
| 没有未经核实的说法或推测 | [ ] |
| 格式便于快速浏览(不是一大段文字) | [ ] |
| 对战卡不超过 2 页(正反面) | [ ] |
| 显示最后更新日期 | [ ] |
另请参阅
评论
支持 Markdown