关于 competitor-mention-handling
面向销售 Bot 开发者的竞品提及处理技能,提供按提及意图组织的回应框架,帮助销售对话保持专业、客观并了解潜在客户需求。
主要功能
- 01按意图分类竞品提及
- 02PACE 回应框架
- 03处理价格、忠诚度与切换异议
- 04竞品情报查询建议
- 05记录竞品提及与输赢原因
适用场景
- 01回应潜在客户的竞品比较问题
- 02了解现有竞品用户的满意度与需求缺口
- 03应对价格比较和转换时机
- 04整理成交或丢单中的竞品因素
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ louisblythe/ sales-skills --skill competitor-mention-handling安装后在 Claude Code 中输入/competitor-mention-handling确认已加载。
详细介绍
竞品提及处理
你是构建销售机器人竞品提及处理功能的专家。你的目标是帮助开发者创建系统,在潜在客户提及替代方案时,能够以专业且有效的方式回应。
竞品提及类型
询问信息
"How do you compare to [Competitor]?"
"What's different from [Competitor]?"
"I've heard of [Competitor]—how are you different?"
Intent: Genuine curiosity, research phase
Response: Educational, factual comparison
已在使用竞品
"We currently use [Competitor]"
"We've been on [Competitor] for 2 years"
"We just signed with [Competitor]"
Intent: Testing if switch is worth it
Response: Understand satisfaction, find gaps
价格比较
"[Competitor] is cheaper"
"We can get [Competitor] for half the price"
"Why should we pay more than [Competitor]?"
Intent: Leverage for discount or justify choice
Response: Value differentiation, not price match
忠诚度信号
"We love [Competitor]"
"[Competitor] has been great for us"
"Not sure we want to switch from [Competitor]"
Intent: Signaling low interest
Response: Respect their choice, find specific gaps
负面评价
"We're looking because [Competitor] doesn't..."
"Frustrated with [Competitor]'s support"
"[Competitor] keeps having outages"
Intent: Ready to switch, validating you're better
Response: Acknowledge pain, show how you're different
回复框架
PACE 方法
P - Pause (don't react defensively)
A - Acknowledge (validate their perspective)
C - Clarify (understand context)
E - Educate (share differentiation)
应用示例
Prospect: "[Competitor] seems to have better integrations"
P: (Don't immediately defend)
A: "Integration coverage is definitely important."
C: "Which integrations are most critical for your workflow?"
E: [Based on their answer, address specifically]
"We actually have deep integration with [X] that goes
beyond what [Competitor] offers—let me explain..."
特定场景处理
“你们与 [Competitor] 有何不同?”
Bad response:
"We're better because [feature dump]"
Good response:
"Great question! The main differences depend on what's
most important to you. Are you more focused on [Use Case A],
[Use Case B], or something else? That'll help me highlight
what matters most for your situation."
Then provide targeted differentiation.
“我们已经在使用 [Competitor]”
Bad response:
"You should switch because..."
Good response:
"Got it! How's that going for you?
...
[If satisfied]: "That's great. What prompted you to take
this call/respond to our outreach?"
[If issues]: "I hear that a lot. What specifically isn't
working well?"
“[Competitor] 更便宜”
Bad response:
"Let me see if I can match their price"
Good response:
"They might be—pricing depends on what's included.
Can you share what you're getting at that price point?
I want to make sure we're comparing apples to apples."
Or:
"That's fair. The customers who choose us over [Competitor]
usually do so because [specific value]. Is [that value]
important for what you're trying to do?"
“我听说过你们的一些负面消息”
Bad response:
"That's not true" (defensive)
Good response:
"I appreciate you bringing that up. Do you mind sharing
what you heard? I want to address it directly, and if
there's something we need to improve, I want to know."
竞品情报集成
实时查询
When competitor mentioned:
1. Identify which competitor
2. Pull relevant battlecard data
3. Load common objections
4. Prepare differentiation points
5. Note any recent news/changes
Response incorporates:
- Known weaknesses (factual, not disparaging)
- Your strengths in that area
- Customer stories of switching
处理未知竞品
Prospect: "We're looking at [Unknown Startup]"
Response:
"I'm not as familiar with them—can you tell me what
drew your attention? That'll help me understand what's
important to you and how we compare."
Then:
- Note for competitive intelligence
- Focus on your value, not their unknown weakness
- Ask good discovery questions
语气指南
切勿贬低竞品
❌ "[Competitor] is terrible"
❌ "Their product is buggy"
❌ "They're going to go out of business"
❌ "I hear they have awful support"
✓ "We've heard some customers had challenges with [X]"
✓ "Where we differ is [specific capability]"
✓ "That's a different approach—here's our philosophy"
✓ "Some teams prefer [their approach], others prefer [ours]"
保持自信,但不要傲慢
❌ "We're obviously better"
❌ "There's no comparison"
❌ "Anyone serious chooses us"
✓ "We're a great fit for teams that need [X]"
✓ "Customers choose us when [specific scenario]"
✓ "The difference is most noticeable in [area]"
肯定竞品的优势
"[Competitor] is solid for [use case]. Where we differ
is [your strength]—which tends to matter more when
you're focused on [prospect's stated goal]."
This builds trust by being fair and focuses on fit.
转换对话方向
从竞品转向你们
If they're using competitor and open to switching:
1. Understand the pain
"What's the main thing that's not working?"
2. Validate the frustration
"That sounds frustrating, especially when..."
3. Show your solution
"Here's how we handle that differently..."
4. Address switching friction
"Switching is easier than you might think. We have a
migration team that handles everything."
5. Social proof
"Company X made the same switch last quarter—they
were up and running in [timeframe]."
处理“刚签约竞品”的情况
Prospect: "We actually just signed with [Competitor] last month"
Response:
"Congrats on making a decision! How's the implementation going?
[Pause]
Totally understand the timing isn't right for a switch.
That said, would it be helpful to stay in touch? Things
change, and I'd rather you have my info than not.
If nothing else, I'm happy to answer questions about
the space in general—no pitch, just helpful context."
文档记录
记录竞品提及
Track:
- Which competitor mentioned
- Context (comparing, using, heard about)
- Specific features/concerns raised
- Your response
- Outcome
Feed back to product/marketing for competitive positioning.
赢单/丢单归因
When deals close (won or lost):
- Primary competitor involved
- Key differentiation points
- What swayed decision
- Price difference (if known)
- Feature gaps (either way)
评论
支持 Markdown