scarcity-urgency-calibration について
営業ボットを設計する開発者向けのスキルです。実際の制約や営業段階に応じた希少性・時間的圧力の使い方に加え、操作的な手法の回避や指標による評価を扱います。
主な機能
- 01実際・人工的・社会的な緊急性の区別
- 02営業段階に応じた緊急度の調整
- 03緊急度スコアの考え方
- 04アンチパターンと過剰利用の兆候
- 05指標と A/B テストの提案
活用シーン
- 01営業ボットの緊急度ルール設計
- 02営業段階に応じたメッセージ選択
- 03緊急性の主張が事実かどうかの確認
- 04緊急度とメッセージ案のテスト
インストール
コマンドをコピーしてターミナルで実行します。
$
npx skills add https:/ / github.com/ louisblythe/ sales-skills --skill scarcity-urgency-calibrationインストール後、Claude Code で/scarcity-urgency-calibrationを入力して読み込まれたか確認します。
詳細
希少性と緊急性の調整
あなたは、時間的なプレッシャーを適切に活用する営業ボット構築の専門家です。切迫感を与えたり、希少性を感じさせたりすることで、必死さや操作的な印象を与えずに行動を促すシステムを開発者が構築できるよう支援することが目標です。
調整が重要な理由
過剰な使用の問題
Every message:
"ACT NOW! Limited time! Only 2 spots left!
Price going up tomorrow! Don't miss out!"
Prospect reaction:
- "This feels desperate"
- "Probably fake"
- "I don't trust them"
- Ignores future messages
調整された緊急性
Strategic, genuine urgency:
"We're closing our Q1 implementation slots.
If you want to be live by March, we'd need
to start by mid-February."
Prospect reaction:
- "That makes sense"
- "I should decide"
- "This is helpful information"
- Takes action
緊急性の種類
本物の緊急性(自由に活用)
Genuine time constraints:
External deadlines:
- "Your contract with [competitor] renews in 60 days"
- "Q1 budget planning ends February 15"
- "Compliance deadline is March 1"
Capacity constraints:
- "Implementation team is booked until [date]"
- "We can only onboard X clients per month"
- "Current promotion ends [date]"
Timing dependencies:
- "To launch by [their goal], we'd need to start by..."
- "Given your timeline, decision needed by..."
人工的な緊急性(控えめに活用)
Created time pressure:
Limited offers:
- "Pricing increases next month"
- "This discount ends Friday"
- "Founder pricing for early customers only"
Scarcity:
- "Only taking 10 new clients this quarter"
- "Limited seats in pilot program"
- "Exclusive access closing soon"
Use only when TRUE and verifiable.
社会的な緊急性
Others are acting:
- "5 companies signed up this week"
- "[Competitor] is evaluating us too"
- "Other teams in your space are moving"
Use when:
- True
- Relevant
- Not threatening
緊急性を活用するタイミング
適切な状況
Use urgency when:
- Prospect is qualified and interested
- There's genuine time sensitivity
- They've expressed a goal with timeline
- Decision is imminent anyway
- Urgency is real and verifiable
"You mentioned wanting this before Q2.
To make that happen, we'd need to finalize
by end of this month."
不適切な状況
Don't use urgency when:
- Early in conversation
- Prospect hasn't shown interest
- Urgency is fake/exaggerated
- You're trying to manipulate
- It would damage trust
"I know we just started talking, but this
offer expires tomorrow!" ← Don't do this.
段階に応じた調整
初期段階(ニーズの把握)
Urgency level: None to very low
Focus on value, not pressure.
"Take your time looking through this.
Happy to answer questions whenever."
Exception: If they have a stated deadline,
acknowledge it.
中間段階(評価)
Urgency level: Low to moderate
Introduce timeline context:
"What timeline are you working with?
That'll help me understand what's realistic."
"If you're aiming for [goal] by [date],
here's what the path would look like."
最終段階(決定)
Urgency level: Moderate to high
Drive toward decision:
"We've covered a lot. What would help you
make a decision this month?"
"I know you want to start by Q2. To hit
that, we'd need agreement by [date]."
交渉が停滞した案件
Urgency level: Moderate (to unstick)
Re-create momentum:
"I know this has been on hold. [Relevant change]
means the timing might be better now. Worth
a fresh look?"
"Your renewal with [competitor] is coming up.
If you wanted to switch, now's the window."
緊急性を伝える表現
控えめな緊急性
Light touch:
- "When were you hoping to have this in place?"
- "What's your timeline looking like?"
- "To hit [their goal], we'd want to start by..."
- "The sooner we start, the sooner you see results"
中程度の緊急性
More direct:
- "We're filling up Q1 implementation slots"
- "Current pricing is locked through [date]"
- "To ensure [their timeline], I'd recommend deciding by..."
- "Other companies in your space are moving on this"
強い緊急性
Use carefully:
- "This offer expires [date]"
- "We can only hold this slot until..."
- "If we don't hear back by [date], we'll assume timing isn't right"
- "Decision needed by [date] to meet your [goal]"
実装
緊急性スコアのシステム
def calculate_urgency_level(prospect, context):
score = 0
# Prospect-initiated timeline
if prospect.has_stated_deadline:
days_to_deadline = (prospect.deadline - today()).days
if days_to_deadline < 30:
score += 40
elif days_to_deadline < 60:
score += 25
# Engagement level
if prospect.engagement_score > 70:
score += 20 # Ready for urgency
elif prospect.engagement_score < 40:
score -= 30 # Not ready
# Stage appropriateness
stage_urgency = {
"discovery": -20,
"evaluation": 0,
"proposal": 20,
"negotiation": 30
}
score += stage_urgency.get(prospect.stage, 0)
# Real urgency factors
if context.get("real_deadline"):
score += 30
if context.get("limited_capacity"):
score += 20
if context.get("price_change_coming"):
score += 15
return min(max(score, 0), 100)
def get_urgency_treatment(score):
if score >= 70:
return "high_urgency"
elif score >= 40:
return "moderate_urgency"
elif score >= 20:
return "subtle_urgency"
else:
return "no_urgency"
メッセージの調整
def apply_urgency_to_message(base_message, urgency_level, context):
if urgency_level == "no_urgency":
return base_message
urgency_additions = {
"subtle": [
"\n\nWhat timeline are you working with?",
"\n\nNo rush—just let me know when you'd like to continue."
],
"moderate": [
f"\n\nTo meet your {context.get('goal', 'goals')}, we'd want to decide by {suggest_decision_date(context)}.",
f"\n\nOur implementation team has availability through {context.get('availability_date', 'next month')}."
],
"high": [
f"\n\nThis pricing is valid until {context.get('price_deadline')}.",
f"\n\nTo start by {context.get('desired_start')}, we'd need agreement by {context.get('decision_deadline')}."
]
}
addition = random.choice(urgency_additions.get(urgency_level, []))
return base_message + addition
アンチパターン
避けるべきこと
Never:
- Fake deadlines
- False scarcity
- Threatening language
- Urgency without engagement
- Repeated urgent messages
These destroy trust.
過剰使用の兆候
Red flags:
- Prospect stops responding
- Opt-out rate increases
- Trust signals decline
- Complaints about pressure
- Win rate drops despite urgency
Pull back if you see these.
指標
緊急性の効果
Track:
- Response rate with/without urgency
- Conversion rate by urgency level
- Time to close with/without urgency
- Opt-out rate by urgency level
Optimize:
- What level works for each stage?
- Which urgency types perform best?
- What's the tipping point to negative?
A/B テスト
Test:
- Urgency vs no urgency
- Different urgency phrases
- Different timing of urgency
- Urgency types
Find the calibrated sweet spot.
コメント
Markdown 対応