sandler-system
について
このスキルは、クロードがサンドラー販売システムの原則を適用し、コンサルティング型セールス会話を実現するものです。発見通話や反論対応において、課題の掘り下げ、予算要件の確認、相互の意思決定フレームワークの確立に重点を置いています。開発者はこのスキルを活用して、機能本位の提案から協調的な問題解決対話へと変換するセールス支援機能を構築できます。
クイックインストール
Claude Code
推奨npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/sandler-systemこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Sandler Selling System
Apply Sandler's consultative selling methodology focusing on pain discovery, upfront contracts, and mutual commitment to transform sales conversations.
When to Use This Skill
- Discovery conversations
- Handling sales resistance
- Budget qualification
- Creating mutual commitments
- Dealing with objections
Methodology Foundation
Based on David Sandler's Selling System, built on:
- Pain discovery (not feature selling)
- Upfront contracts (mutual agreements)
- Budget qualification (money conversation early)
- Decision framework (clear next steps)
- Equal business stature (not subservient selling)
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Structures discovery questions | When to use techniques |
| Creates upfront contract templates | How aggressive to be |
| Designs pain funneling | Relationship balance |
| Suggests budget qualification | Deal-specific judgment |
| Provides objection frameworks | Walking away decisions |
Instructions
Step 1: Understand the Sandler Submarine
Seven Stages:
┌─────────────────────────────────────────────────────────────┐
│ THE SANDLER SUBMARINE │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. Bonding & Rapport ──► 2. Upfront Contract │
│ │ │ │
│ └────────────────────────┘ │
│ │ │
│ 3. Pain ◄──┘ │
│ │ │
│ ▼ │
│ 4. Budget │
│ │ │
│ ▼ │
│ 5. Decision │
│ │ │
│ ▼ │
│ 6. Fulfillment (Present Solution) │
│ │ │
│ ▼ │
│ 7. Post-Sell (Reinforce Decision) │
│ │
└─────────────────────────────────────────────────────────────┘
Step 2: Master Pain Discovery
Pain Funnel Technique:
| Level | Question Type | Example |
|---|---|---|
| Surface | Open | "Tell me more about that" |
| Deeper | Clarifying | "Can you be more specific?" |
| Impact | Business | "How is that affecting the business?" |
| Personal | Individual | "How does that affect you personally?" |
| Commitment | Action | "What have you tried to fix it?" |
Step 3: Create Upfront Contracts
Upfront Contract Elements:
- Time - How long do we have?
- Agenda - What will we cover?
- Outcome - What's the possible result?
- Permission - Can we have honest conversation?
Step 4: Qualify Budget
Money Questions (Progressive):
| Timing | Question |
|---|---|
| Early | "Is there a budget for this?" |
| Middle | "What range are you thinking?" |
| Direct | "If we could solve this, what's it worth?" |
| Test | "Our solution is typically $X. Does that fit?" |
Step 5: Establish Decision Process
Decision Questions:
- "How do decisions like this typically get made?"
- "Who else needs to be involved?"
- "What could stop this from happening?"
- "What's the timeline for a decision?"
Examples
Example 1: Discovery Call with Sandler Framework
Input:
Structure a discovery call using Sandler principles.
Context: First meeting with VP of Marketing, inbound lead.
Output:
## Sandler Discovery Call Structure
### Pre-Call Preparation
**Mindset:**
- You're interviewing them as much as they're interviewing you
- No need to convince—focus on uncovering fit
- Comfortable walking away if not right
- Equal business stature, not supplicant
---
### 1. Bonding & Rapport (5 minutes)
**Goal:** Establish equal footing, build trust
**Opening:**
"Thanks for making time, [Name]. Before we dive in, I have to admit—
I did some homework on [Company] and have some questions, but I'm
also curious about what prompted you to reach out in the first place."
**Techniques:**
- Match their energy and pace
- Find common ground (naturally)
- Demonstrate you've done research
- Be genuinely curious, not performative
---
### 2. Upfront Contract (3 minutes)
**Goal:** Mutual agreement on meeting structure
**Script:**
"[Name], to make sure we both get value from this conversation,
can I suggest how this might go?
We have about 30 minutes. I'd like to understand what's going on
in your world that made you want to talk. I'll share a bit about
what we do—but honestly, I'm not sure if we're the right fit yet.
At the end, one of three things will happen:
1. We both see enough potential to keep talking
2. You decide it's not right—and that's totally fine
3. I tell you we're not the right fit—and I promise I will
Does that work for you? And can we agree to be straight with
each other?"
**Why this works:**
- Sets expectation you might say no
- Gets permission for honest conversation
- Reduces buyer's defense mechanisms
- Establishes equal stature
---
### 3. Pain Discovery (15 minutes)
**Goal:** Uncover real pain, not surface problems
**Opening Question:**
"So, tell me—what's happening that made you want to have this
conversation now?"
**Pain Funnel in Action:**
| Their Response | Your Follow-Up |
|----------------|----------------|
| "We need better marketing automation" | "Tell me more about that" |
| "Our campaigns aren't performing" | "What does 'not performing' mean specifically?" |
| "Our open rates dropped 30%" | "How is that affecting the business?" |
| "We're missing revenue targets" | "By how much?" |
| "$2M behind this quarter" | "How does that affect you personally?" |
| "I'm on the hot seat with the CEO" | "What have you tried to fix this?" |
**Key Questions:**
1. "Tell me more about that"
2. "What do you mean by [vague term]?"
3. "How long has this been going on?"
4. "What's it costing the business?"
5. "How is this affecting you personally?"
6. "What have you tried already?"
7. "Why didn't that work?"
8. "What happens if you don't solve this?"
**Reverse Technique (when they ask about your solution early):**
> Them: "Can you just tell me how your platform works?"
> You: "I could, but honestly, I'm not sure if it's even relevant yet.
> Help me understand what you're actually trying to solve first."
---
### 4. Budget Qualification (5 minutes)
**Goal:** Understand if money is available and in what range
**Progressive Approach:**
**Level 1 (Soft):**
"If we could solve [pain you uncovered], would there be budget
for something like this?"
**Level 2 (Range):**
"When you've invested in solutions like this before, what kind
of investment was typical?"
**Level 3 (Direct):**
"I want to be respectful of your time. Solutions like ours
typically range from $X to $Y depending on scope. Does that
match what you were thinking, or are we in different universes?"
**If they resist:**
> "Look, I get it—budget conversations can be uncomfortable.
> But here's my concern: if I spend our time showing you
> something you can't afford, I've wasted both our time.
> What would be helpful here?"
---
### 5. Decision Process (3-5 minutes)
**Goal:** Map the buying process
**Questions:**
- "Walk me through how decisions like this typically get made at [Company]"
- "Who else would need to weigh in?"
- "Is there anyone who could stop this from happening?"
- "Have you bought anything like this before? How did that go?"
- "What's driving your timeline?"
**Red Flag Questions:**
- "What could make you decide NOT to move forward?"
- "What would make you go with a competitor instead of us?"
---
### 6. Upfront Contract for Next Step
**Goal:** Clear mutual commitment or clear no
**If positive indicators:**
"Based on what you've shared, I think there might be something
here. Here's what I'd suggest for next steps:
I'll put together [specific thing] that addresses [their pain].
We'd meet again with [whoever they mentioned], and at the end of
that meeting, you'll be in a position to tell me yes, no, or
'we need more information.'
Does that work? And can you commit to giving me a decision at
that meeting?"
**If unclear fit:**
"I appreciate your honesty. Based on what you've shared, I'm
not sure we're the best fit, and here's why: [reason].
What I'd suggest is [alternative or referral]. Does that help?"
---
### Sandler-isms to Remember
| Situation | Sandler Response |
|-----------|------------------|
| They want a proposal too fast | "I could send something over, but I'd just be guessing. Can we slow down?" |
| They won't discuss budget | "If we can't talk about money, how will we know if this makes sense?" |
| They ask for discount | "What is it about the value that you're questioning?" |
| They go silent after proposal | "Sounds like something's changed. Should I assume this is a no?" |
| They say "let me think about it" | "When people say that, it usually means no. Is that what's happening here?" |
Example 2: Handling "Let Me Think About It"
Input:
Prospect says "let me think about it" after a demo.
How do I respond using Sandler?
Output:
## Sandler Response: "Let Me Think About It"
### The Principle
In Sandler, "let me think about it" is often a polite no. Rather
than chase, you surface what's really going on.
---
### Response Script
**Option 1: Direct Reversal**
> "I appreciate that. When people tell me they need to think about
> it, usually it means something's not quite right. Can you help me
> understand—is this a no, or is there something specific you're
> trying to figure out?"
**Option 2: Permission to Be Honest**
> "[Name], I want to be straight with you. In my experience, 'let
> me think about it' often means 'no, but I don't want to say it.'
> I'd rather know now. Is this something you're genuinely considering,
> or are we done here?"
**Option 3: Negative Reverse**
> "Honestly, that sounds like a no. And that's okay—I'd rather
> know now than chase you for weeks. What's the real hesitation?"
---
### What Usually Happens
**Scenario 1: They admit it's a no**
- Thank them for honesty
- Ask what was missing
- Ask for referral or future timing
- Move on without burning bridge
**Scenario 2: They share real objection**
- Now you can actually address it
- Likely price, authority, timing, or feature gap
- Engage with real problem, not phantom
**Scenario 3: They commit to timeline**
- Great—make it an upfront contract
- "OK, so you need to think about [X]. Let's set a call for
Thursday. At that point, you'll give me a yes or no. Fair?"
---
### What NOT to Do (Traditional Sales)
| Don't | Why It Fails |
|-------|--------------|
| "When can I follow up?" | Endless chase begins |
| "What questions do you have?" | They already said they're done |
| "Let me send more info" | They didn't ask for more info |
| "I'll check back next week" | You become a pest |
---
### The Sandler Mindset
You're not desperate for this deal. If it's not right, you'd
rather know now. This confidence paradoxically makes them more
likely to engage honestly—and often reveals they were just
testing to see if you'd chase.
Skill Boundaries
What This Skill Does Well
- Structuring consultative conversations
- Creating discovery frameworks
- Handling objections non-defensively
- Qualifying opportunities honestly
What This Skill Cannot Do
- Replace genuine curiosity
- Work without relationship skills
- Override poor product-market fit
- Guarantee closed deals
Iteration Guide
Follow-up Prompts:
- "Create pain funnel questions for [industry]"
- "How do I handle [specific objection]?"
- "Design upfront contract for [scenario]"
- "What if they won't discuss budget?"
References
- David Sandler - Sandler Selling System
- "You Can't Teach a Kid to Ride a Bike at a Seminar"
- Sandler Rules - 49 Timeless Selling Principles
- Sandler Training Institute
Related Skills
never-split-difference- Negotiation tacticsspin-selling- Question-based sellingchallenger-sale- Teaching-based selling
Skill Metadata
- Domain: Sales
- Complexity: Intermediate-Advanced
- Mode: centaur
- Time to Value: Apply in next conversation
- Prerequisites: Consultative selling context
GitHub リポジトリ
関連スキル
llamaguard
その他LlamaGuardは、暴力やヘイトスピーチなど6つの安全性カテゴリーにおいて、LLMの入力と出力をモデレートするMetaの70-80億パラメータモデルです。94〜95%の精度を提供し、vLLM、Hugging Face、Amazon SageMakerを使用してデプロイ可能です。このスキルを使用して、AIアプリケーションにコンテンツフィルタリングと安全策を簡単に統合できます。
cost-optimization
その他このClaudeスキルは、リソースの適正サイジング、タグ付け戦略、支出分析を通じて、開発者がクラウドコストを最適化することを支援します。AWS、Azure、GCPにわたるクラウド支出の削減とコストガバナンスの実施のためのフレームワークを提供します。インフラコストの分析、リソースの適正サイジング、または予算制約への対応が必要な際にご利用ください。
quantizing-models-bitsandbytes
その他このスキルは、bitsandbytesを使用してLLMを8ビットまたは4ビット精度に量子化し、精度の低下を最小限に抑えつつ50〜75%のメモリ削減を実現します。限られたGPUメモリでより大規模なモデルを実行したり、推論を高速化するのに理想的で、INT8、NF4、FP4などのフォーマットをサポートしています。HuggingFace Transformersと統合され、QLoRAトレーニングや8ビットオプティマイザーを可能にします。
dispatching-parallel-agents
その他このClaudeスキルは、複数のエージェントを配備し、3つ以上の独立した問題を並行して調査・修正します。共有状態や依存関係がなく解決可能な、無関係な障害が発生するシナリオ向けに設計されています。中核となる機能は並列問題解決であり、効率を最大化するために独立した問題領域ごとに1つのエージェントを割り当てます。
