mcpField
P
pricing-discussion-logic

pricing-discussion-logic

github.com/louisblytheマーケティング・グロース190410 回インストール40 週間前に更新
リポジトリ

pricing-discussion-logic について

営業ボット開発者向けの価格交渉スキルで、見積もり、追加確認、人へのエスカレーションの判断を支援します。異議への対応、値引き権限、営業への引き継ぎを扱います。

主な機能

  1. 01見積もりか保留かの判断
  2. 02人へのエスカレーションの判定
  3. 03価格への異議や値引き要求への対応
  4. 04値引き権限ルールの適用
  5. 05価格交渉の記録と引き継ぎ

活用シーン

  1. 01見積もり前にニーズと予算を確認
  2. 02価格が高いという反応に対応
  3. 03ボットの権限を超える値引き要求を引き継ぐ
  4. 04企業案件の情報を営業向けに整理

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/louisblythe/sales-skills --skill pricing-discussion-logic

インストール後、Claude Code で/pricing-discussion-logicを入力して読み込まれたか確認します。

詳細

価格に関する会話のロジック

営業ボットの価格に関する会話ロジックの構築に精通しています。目標は、価格を提示する、いったんかわす、担当者にエスカレーションするタイミングを判断し、価格に関する質問に戦略的に対応するシステムを開発者が作成できるよう支援することです。

価格に関する会話の目標

  1. まず適合性を確認する:ニーズに合うかを把握する前に、価格の話から始めないでください
  2. 価値を伝える:価値について話し合ってから、価格を提示してください
  3. 適切な透明性を保つ:価格を隠すのではなく、背景を踏まえて説明してください
  4. 利益率を守る:早まって値引きしないでください
  5. 対応できる範囲を把握する:必要に応じてエスカレーションしてください

判断フレームワーク

価格を直接提示する場合
Quote when:
✓ Prospect is qualified
✓ Value has been established
✓ They have explicit budget authority
✓ Pricing is simple/standard
✓ You have published pricing
✓ They've seen a demo or understand the product

Example:
"For a team of 50, you're looking at $500/month on our
Professional plan. That includes [key features]. Would
you like me to walk through what's included?"
(一時的に)回答をかわす場合
Deflect when:
- Too early in conversation (no qualification)
- Prospect doesn't understand value yet
- Need more info to quote accurately
- Complex pricing requires configuration

How to deflect:
"I'd love to get you accurate pricing. First, let me
understand your needs so I don't quote the wrong thing.
Are you looking for [Option A] or [Option B]?"
エスカレーションする場合
Escalate when:
- Request exceeds bot's discount authority
- Complex enterprise deal
- Custom pricing required
- Prospect is frustrated/insistent
- Strategic account
- Legal/contract questions

"For custom pricing at your scale, let me connect you
with our enterprise team. They can structure something
that fits your needs. Can I have them reach out?"

よくある状況への対応

「費用はいくらですか?」
Early in conversation:
"Great question! Pricing depends on a few factors.
To give you an accurate range—roughly how many people
would be using this?"

After qualification:
"Based on what you've shared—50 users, need for [features]—
you're looking at approximately $X/month. Does that
align with what you had in mind?"
「高すぎます」
Step 1: Understand the objection
"I hear you. Too expensive compared to what you budgeted,
or compared to an alternative you're considering?"

Step 2: Based on answer...

Budget issue:
"What were you hoping to spend? Let me see if we have
an option that fits."

Competitor comparison:
"Can you share what they're offering at that price?
I want to make sure we're comparing similar things."

Value issue:
"If the ROI was clear—let's say 10x return—would
the price still feel too high?"
「値引きしてもらえますか?」
Don't immediately discount. Explore first:

"I may be able to help with that. Can you share more
about what you're working with? Is it a budget constraint,
or are you comparing to another option?"

Then based on authority:

Within authority:
"I can do [X discount] if you're ready to move forward
by [date]. Does that work?"

Beyond authority:
"Let me check with my manager on what's possible.
What discount would make this work for you?"

No discount available:
"Our pricing is set, but I can explore if there's a
different package that fits your budget better."
「最も安いプランは何ですか?」
"Our starter plan is $X/month. But let me make sure
that's actually the right fit—what are you mainly
trying to accomplish? Sometimes the starter plan
is missing key features that matter."
「承認を得るために見積もりが必要です」
"Absolutely—I'll put together a formal quote. To make
sure it's accurate, let me confirm:
- [Number] users
- [Specific plan/features]
- [Billing preference: monthly/annual]
- [Implementation needs]

And who else will be reviewing this? I want to make
sure the quote addresses their questions too."

価格決定権に関するルール

ボットが値引きできる範囲
Define clear rules:

Standard discounts (auto-approve):
- Annual payment: 10-15% off
- Multi-year: Up to 20% off
- Volume (100+ users): Up to 15% off
- Nonprofit/education: 25% off

Maximum bot authority:
- Total discount: 20%
- Can't combine multiple discounts
- Can't modify contract terms
- Can't promise future pricing

Beyond these → Escalate
エスカレーションの条件
Escalate pricing to human when:
- Requested discount > 20%
- Custom contract terms requested
- Enterprise deal (>$50k ARR)
- Request for pilot/trial pricing
- Competitive displacement deal
- Multi-product bundle
- Government/public sector

戦略的な価格の話し合い

アンカリング
Before revealing price, establish value:

"So just to recap: this would eliminate 10 hours/week
of manual work for your team, give you real-time
visibility you don't have today, and integrate with
your existing tools. For a team your size, that's
typically worth $50-100k/year in efficiency gains.

The investment is $24k annually. Does that feel
proportionate to the value?"
選択肢の提示方法
Don't just give one price—offer context:

"We have three tiers:
- Starter at $X: Best for small teams getting started
- Professional at $Y: Most popular—includes [key features]
- Enterprise at $Z: For larger orgs needing [advanced features]

Based on what you've described, Professional is probably
the sweet spot. What do you think?"
トレードオフ
If they want discount, get something:

"I can get you 15% off if you:
- Sign an annual contract (vs monthly)
- Commit to a case study after implementation
- Start this quarter
- Add the integration package

Which of those would work for you?"

価格への強い抵抗への対応

「[Competitor]ならもっと安くできます」
"They might be lower upfront. Can you share what's
included at that price? Our customers who've compared
usually find that [Competitor] charges extra for
[features we include], so the total cost ends up similar.
But let me make sure we're comparing the same things."
「予算がありません」
"Understood. Is it a matter of no budget at all, or
the budget existing but not enough? Sometimes there's
flexibility when ROI is clear, or we can look at a
smaller starting point."
「上司が承認するはずがありません」
"What would your boss need to see to approve? If it's
ROI, I can help build that case. If it's about comparing
options, I can provide a competitive analysis. What
would be most helpful?"

記録と引き継ぎ

価格に関する会話の記録
Record:
- Price quoted
- Discount given (if any)
- Discount reason
- Prospect's reaction
- Objections raised
- Next steps
- Authority level needed
営業担当者への引き継ぎ
When escalating:

"[Name] from [Company] is interested in our Enterprise plan.
Here's what I know:
- Team size: 500+
- Budget mentioned: ~$100k
- Key need: [Feature]
- Competitor comparison: [Name]
- Requested: 25% discount
- Timeline: Q2 decision

They're expecting a call to discuss custom pricing."

コメント