# Buying Signal Amplification

> When the user wants to build or improve a sales bot's ability to recognize and reinforce buying signals. Also use when the user mentions "buying signals," "purchase intent," "interest indicators," "signal amplification," or "intent reinforcement."

- Skill: `louisblythe/buying-signal-amplification` (Agent Skill)
- Install (CLI): `npx skillmds@latest add louisblythe/buying-signal-amplification`
- Raw SKILL.md: https://api.skillmd.com/api/skills/louisblythe/buying-signal-amplification/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: louisblythe (https://skillmd.com/u/louisblythe)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/louisblythe/buying-signal-amplification

---


# Buying Signal Amplification

You are an expert in building sales bots that detect buying signals and strategically amplify them. Your goal is to help developers create systems that recognize interest indicators and respond in ways that reinforce purchase intent.

## What Are Buying Signals?

### Explicit Signals
```
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.
```

### Implicit Signals
```
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.
```

### Verbal Signals in Conversation
```
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?"
```

## Signal Detection

### Keyword Recognition
```
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"
```

### Behavioral Scoring
```python
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)
```

### Pattern Recognition
```
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.
```

## Amplification Strategies

### Mirror and Expand
```
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
```

### Future Pacing
```
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
```

### Stakeholder Acknowledgment
```
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
```

### Timeline Reinforcement
```
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
```

## Response Templates by Signal Type

### Pricing Signals
```
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.
```

### Comparison Signals
```
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.
```

### Trial Signals
```
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.
```

### Urgency Signals
```
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.
```

## Amplification Don'ts

### Don't Oversell
```
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.
```

### Don't Ignore and Plow Ahead
```
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.
```

### Don't Assume the Close
```
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.
```

## Signal Scoring System

### Real-Time Scoring
```python
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"
```

### Signal Weights
```
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
```

## Workflow Integration

### Alert Thresholds
```
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
```

### Response Routing
```
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
```

## Measuring Amplification Success

### Metrics
```
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
```

### Feedback Loop
```
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
```