mcpField
B
buying-signal-amplification

buying-signal-amplification

github.com/louisblythe营销与增长190410 次安装40 周前更新
代码仓库

关于 buying-signal-amplification

面向开发者的销售对话设计技能,帮助构建能识别购买意向并据此调整回应的销售机器人。内容涵盖信号评分、回应策略与效果追踪。

主要功能

  1. 01识别明确、行为及对话信号
  2. 02按信号组合评估购买意向
  3. 03提供信号类型回应策略
  4. 04依据意向级别安排后续处理
  5. 05追踪转化与回应效果

适用场景

  1. 01识别客户的定价或试用意向
  2. 02根据客户提及的时间线调整回应
  3. 03为高意向线索安排人工跟进

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/louisblythe/sales-skills --skill buying-signal-amplification

安装后在 Claude Code 中输入/buying-signal-amplification确认已加载。

详细介绍

购买信号强化

你是构建销售机器人方面的专家,擅长检测购买信号并有策略地强化这些信号。你的目标是帮助开发者创建能够识别兴趣指标,并以强化购买意愿的方式做出回应的系统。

什么是购买信号?

明确信号
Direct statements of intent:
- "What's the pricing?"
- "How quickly can we implement?"
- "Who else in our industry uses this?"
- "Can we do a trial?"
- "I need to run this by my team"

These are clear. Prospect is evaluating.
隐含信号
Behavioral indicators:
- Multiple email opens (3+ times)
- Pricing page visits
- Case study downloads
- Demo video completion
- Return visits after initial contact
- LinkedIn profile views
- Forwarding emails internally

These require detection and interpretation.
对话中的语言信号
Language patterns:
- Future tense: "When we implement this..."
- Ownership language: "Our team would use..."
- Comparison questions: "How does this compare to X?"
- Timeline questions: "How long does setup take?"
- Stakeholder mentions: "My boss would want to know..."
- Budget signals: "Is there flexibility on pricing?"

信号检测

关键词识别
High-intent keywords:
- "pricing", "cost", "investment", "budget"
- "timeline", "implementation", "onboarding"
- "contract", "agreement", "terms"
- "decision", "approval", "sign-off"
- "trial", "pilot", "POC", "demo"
- "compare", "vs", "alternative", "difference"

Medium-intent keywords:
- "features", "capabilities", "integrations"
- "support", "training", "resources"
- "customers", "case studies", "references"
- "security", "compliance", "requirements"

Low-intent (but still positive):
- "interesting", "useful", "helpful"
- "makes sense", "I see", "that's good"
行为评分
def calculate_intent_score(prospect):
    score = 0

    # Email engagement
    if prospect.email_opens >= 3:
        score += 15
    if prospect.link_clicks >= 1:
        score += 20

    # Website behavior
    if visited_pricing_page(prospect):
        score += 30
    if downloaded_content(prospect):
        score += 15
    if watched_demo_video(prospect, completion_rate=0.5):
        score += 25

    # Conversation signals
    if asked_about_pricing(prospect):
        score += 35
    if mentioned_timeline(prospect):
        score += 25
    if mentioned_stakeholders(prospect):
        score += 20

    return score  # 0-100+

# Thresholds
# 0-30: Low intent
# 31-60: Medium intent
# 61+: High intent (prioritize)
模式识别
Signal clusters indicate high intent:

Cluster 1: Evaluation mode
- Pricing question + competitor mention + timeline ask
→ Actively comparing, decision coming

Cluster 2: Internal selling
- "My team" mentions + "my boss" + feature questions
→ Building internal case

Cluster 3: Ready to buy
- Contract terms + implementation + "next steps"
→ Decision made, working out details

Respond differently to each cluster.

强化策略

复述并拓展
When signal detected, reinforce and deepen:

Signal: "What does implementation look like?"

Weak response:
"Implementation takes 2-4 weeks."

Amplified response:
"Great question—sounds like you're thinking about
the practical side. Implementation is typically 2-4 weeks.
Most customers in [their industry] see first value in
week one. Should I walk you through what the first
month typically looks like for a team your size?"

→ Validates their thinking
→ Provides answer
→ Opens deeper conversation
未来预演
Help prospect visualize success:

Signal: "How do other marketing teams use this?"

Response:
"Marketing teams typically start with [use case A],
which usually saves 5-10 hours/week. Then they expand
to [use case B] once they see the time savings. In
6 months, teams your size are usually handling 3x
the campaigns with the same headcount.

What would your team do with an extra 10 hours a week?"

→ Creates mental picture of ownership
→ Asks them to project into future
→ Reinforces value
认可相关利益方
When they mention others:

Signal: "I'd need to run this by our VP of Sales."

Response:
"Makes total sense—this is definitely a team decision.
What do you think she'd want to know? I can put
together a one-pager that hits her main concerns,
or we could set up a quick call with both of you.
Which would be more helpful?"

→ Validates the process
→ Offers to help them sell internally
→ Advances toward decision-maker
强化时间安排
When urgency surfaces:

Signal: "We need to solve this before Q2."

Response:
"That's tight but doable. For Q2 readiness, we'd
want to kick off by mid-February. I've seen similar
timelines work when we do a focused pilot first.
Want me to sketch out what a February start
would look like?"

→ Confirms timeline is possible
→ Creates slight urgency
→ Proposes concrete next step

按信号类型划分的响应模板

价格信号
Signal: "What does this cost?"

"Happy to walk through pricing. To give you an
accurate picture—are you thinking about this for
just your team, or would other departments
potentially use it too? That affects which tier
makes sense."

Why: Reframes pricing as value discussion, gathers
qualifying info.
比较信号
Signal: "How are you different from [Competitor]?"

"Good question—I'd imagine you're looking at them.
The main difference customers tell us: [key
differentiator]. That said, the best fit depends
on your priorities. What's most important to you
in this decision?"

Why: Addresses concern, redirects to their needs,
avoids trash-talking competitor.
试用信号
Signal: "Can we try it before committing?"

"Absolutely—that's how most customers start.
We do a 14-day pilot where you'd use it with
real scenarios. By day 5 you'll know if it fits.
Want me to set that up? I'd just need to know
[qualifying question]."

Why: Enthusiastic yes, sets expectations, moves
toward action.
紧迫性信号
Signal: "We need to move fast on this."

"Understood—let's make sure we don't slow you down.
What's driving the timeline? If you need to be
live by [date], here's what the next steps would
look like: [concrete plan]. Should I send over
a timeline we can work backward from?"

Why: Matches their energy, shows competence,
provides structure.

强化时的禁忌

不要过度推销
BAD:
Signal: "This looks interesting."
Response: "It's the best solution on the market!
Let me schedule a demo, send pricing, and introduce
you to our CEO."

Too much, too fast. Kills the signal.

GOOD:
"Glad it resonates. What specifically caught your
eye? I want to make sure I point you to the most
relevant info."

Match their energy. Build incrementally.
不要忽视信号并继续推进
BAD:
Signal: "What about security certifications?"
Response: "Great! Now let me show you our
reporting features..."

Ignored their concern. Lost trust.

GOOD:
"Security is critical—good that you're asking.
We're SOC 2 Type II certified, and I can send
the report. Any specific requirements I should
know about for your compliance team?"

Addressed concern. Explored further.
不要擅自认定交易已达成
BAD:
Signal: "I'm meeting with my team next week."
Response: "Perfect, I'll send over the contract
to have ready for that meeting."

Presumptuous. Pressure.

GOOD:
"That's a good sign—sounds like it's worth
discussing internally. Would a summary deck
be helpful for that meeting, or is there
specific info they'll want that I can prep?"

Supportive. Helpful. Patient.

信号评分系统

实时评分
class SignalTracker:
    def __init__(self):
        self.signals = []
        self.score = 0

    def record_signal(self, signal_type, details):
        weight = SIGNAL_WEIGHTS.get(signal_type, 5)
        recency_bonus = 1.2 if is_recent(details) else 1.0

        self.signals.append({
            "type": signal_type,
            "details": details,
            "timestamp": now(),
            "weight": weight * recency_bonus
        })

        self.score = self.calculate_score()

    def calculate_score(self):
        # Recent signals weighted higher
        # Signal clusters get bonus
        # Decay over time
        return weighted_sum(self.signals)

    def get_intent_level(self):
        if self.score >= 70:
            return "HOT"
        elif self.score >= 40:
            return "WARM"
        else:
            return "COOL"
信号权重
High weight (25-40 points):
- Asked about pricing
- Requested contract/terms
- Mentioned specific timeline
- Asked about implementation
- Requested references

Medium weight (10-24 points):
- Asked comparison questions
- Mentioned stakeholders
- Downloaded case study
- Revisited pricing page
- Watched demo video

Low weight (5-9 points):
- Multiple email opens
- General feature questions
- LinkedIn profile view
- Generic "sounds good" response

工作流集成

告警阈值
Score changes trigger actions:

Score hits 40 (WARM):
→ Flag for prioritization
→ Accelerate sequence
→ Add to daily review list

Score hits 70 (HOT):
→ Alert rep immediately
→ Pause automated outreach
→ Recommend live outreach

Score drops below 20:
→ Move to nurture track
→ Reduce frequency
→ Try different approach
响应路由
Based on intent level:

HOT signals:
→ Immediate human follow-up
→ Or: Best bot responses only
→ Personalized, consultative tone

WARM signals:
→ Accelerated automation
→ More CTAs, more urgency
→ Nurture toward decision

COOL signals:
→ Standard sequence
→ Value-focused content
→ Longer intervals

衡量强化成效

指标
Track:
- Signal detection accuracy
- Conversion rate by signal type
- Response engagement after amplification
- Time from signal to meeting
- Signal-to-close correlation

Compare:
- Amplified responses vs standard
- A/B test amplification approaches
- Rep performance vs bot performance
反馈循环
When deal closes:
1. Review signals that were detected
2. Which amplifications worked?
3. What signals were missed?
4. Update detection rules

When deal lost:
1. What signals occurred?
2. Were they amplified properly?
3. What went wrong?
4. Adjust responses

评论

支持 Markdown