Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

spin-selling旋转销售

Agent Skill

spin-selling 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

480

周安装

20

GitHub Stars

111

下载量

160
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:spin-selling(旋转销售)
来源仓库:https://github.com/getagentseal/founder-playbook
仓库路径:skills/spin-selling
安装命令:
npx skills add https://github.com/getagentseal/founder-playbook --skill spin-selling
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/getagentseal/founder-playbook --skill spin-selling

简介

spin-selling 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位目标内容。

  • 适用于基于关键词或任务场景的信息检索与筛选需求。
  • 通过 npx skills add 命令从 GitHub 仓库安装并调用。
  • 建议确认权限范围和维护状态,避免不必要的联网或文件访问。
  • 可结合原始文档进一步验证功能细节和使用方式。

SKILL.md

Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.

SPIN Selling

"The closing techniques that can be effective in smaller accounts will actually lose you business as the sales grow larger." - Neil Rackham

Core Insight

Sales techniques that work in small sales (closing, objection handling, feature pitching) tend to backfire in large sales.

DimensionSmall SaleLarge Sale
Selling cycleSingle callMulti-call (months/years)
Decision makerIndividualMultiple stakeholders
Customer's riskLow (personal $)High (career, public visibility)
Post-sale relationshipNoneOngoing
Need developmentInstantSlow, painful
Effective pressureYes (closing works)No (closing backfires)
Top behaviorClosing/FeaturesQuestioning/Need development

Decision rule: If you can't complete the sale in a single call, or if the customer must justify the decision to others, you're in a major sale. Use SPIN.


The 4 Stages of Every Sales Call

StageWhat HappensImportance in Major Sales
1. PreliminariesOpening, warming upLOW (≤20% of call time)
2. InvestigatingAsking questions to develop needsHIGHEST (this is where you win)
3. Demonstrating CapabilityShowing your solutionMedium (only after needs developed)
4. Obtaining CommitmentGetting next-step actionLow (good investigating makes this easy)

SPIN: The 4 Question Types

S - Situation Questions

Background facts about the customer's current situation.

  • "What equipment are you using now?"
  • "How long have you had it?"

Research finding: Negatively related to success. Inexperienced sellers ask too many.

Rule: Minimum needed. Do homework first - never ask what you could research. Each must have a specific purpose.

"There's a special place in hell reserved for wicked salespeople where they sit for all eternity being forced to answer their own Situation Questions."

P - Problem Questions

Probe for problems, difficulties, dissatisfactions.

  • "Are you satisfied with your present equipment?"
  • "What disadvantages does this approach have?"
  • "Is reliability an issue?"

Research finding: Strong predictor in small sales. Foundational in large sales but not sufficient alone.

Rule: Aim for 6+ Problem Questions per call. Plan 3+ problems your product can solve before each call. Inexperienced sellers don't ask enough because they fear offending the customer.

I - Implication Questions

Take a problem and explore its EFFECTS, CONSEQUENCES, IMPLICATIONS.

  • "What effect does that have on output?"
  • "What's the cost of doing nothing?"
  • "Could this affect your competitiveness?"

Research finding: Strongest predictor of success in major sales. Only 1 in 20 questions in average sales call is an Implication Question. Harder to ask. MUST be planned in advance.

Purpose: Take a problem the buyer perceives as small and build it large enough to justify expensive action.

"Even the smartest people we've studied find it hard to ask Implication Questions unless they've planned them in advance."

N - Need-Payoff Questions (NPQ)

Get the customer to articulate the VALUE/BENEFITS of solving the problem.

  • "How would solving this help you?"
  • "Why is that important?"
  • "Would it be useful if...?"
  • "What other ways could this help?"

Research finding: Top performers ask materially more NPQs than average reps (Rackham's "10x" figure is rhetorical, no published baseline). Calls with high NPQs are rated by customers as POSITIVE, CONSTRUCTIVE, HELPFUL.

Two effects:

  1. Shifts attention from problem (negative) to solution (positive)
  2. Customer tells YOU the benefits - far more persuasive

Critical: Don't ask NPQs about needs you CAN'T meet. Amplifies a need that benefits your competitor.

Quincy's Rule (Implication vs Need-payoff)

The hardest distinction. An 8-year-old solved it instantly:

"Implication Questions are always sad. Need-payoff Questions are always happy."
Question TypeFocusTone
ImplicationProblem-centeredSad (makes problem bigger)
Need-payoffSolution-centeredHappy (makes solution attractive)

The SPIN Logic Chain

Situation (background) → Problem (find difficulty) →
Implied Need ("we have this problem") →
Implication (make it bigger) → Need-payoff (build value of solving) →
Explicit Need ("I want X") → Benefit ("we deliver X") →
Order/Advance

SPIN is a guideline, not a rigid formula. Top performers use it flexibly. If the customer opens with an Explicit Need, jump to Need-payoff.


Implied vs Explicit Needs (The Key Distinction)

Two Categories Used in Practice

Need TypeDefinitionExample
ImpliedProblems, difficulties, dissatisfactions"Our system is unreliable"
ExplicitSpecific wants, desires, intentions"We need a more reliable system"

Buying Signals - Critical Distinction

In major sales, Implied Needs are NOT buying signals. Inexperienced reps misread "we have a problem with X" as a buy signal. It isn't.

The real buying signal in major sales is an Explicit Need:

  • "We're going to do something about X"
  • "We're looking for a system with these characteristics"

Research Statistics

Sales TypeImplied Needs Predict Success?Explicit Needs Predict Success?
Small (646 deals)YES (2x more in successful)Less critical
Large (1,406 deals, $27K avg)NO (no correlation)YES (2x more in successful)

The fundamental insight: In major sales, success comes from CONVERTING Implied Needs into Explicit Needs using Implication and NPQs.


FAB Redefined (Features / Advantages / Benefits)

Traditional FAB training is wrong for major sales.

BehaviorDefinitionSmall SalesLarge Sales
FeaturesFacts about the productSlightly positiveNeutral or negative
AdvantagesShow how product can be used or helpPositiveSlightly positive early, decreases over cycle
BenefitsShow how product meets an EXPLICIT NEED expressed by customerVery positiveVery positive

The Critical Definition Difference

Most sales training calls "Type A Benefits" what Rackham calls Advantages (showing how product helps). True Benefits require the customer to FIRST express an Explicit Need.

Wrong (Advantage): "Because our system uses high-reliability components, it solves your reliability problem."

  • Reliability problem is an Implied Need (not yet Explicit).

Right (Benefit): Customer says: "We need a more reliable system." → Seller: "Our system is built specifically for reliability and would meet that need."


Closing: The Counterintuitive Truth

StudyFinding
Office equipment (190 calls)High-close: 37% success. Low-close: 70% success
Photo store (cheap goods)Closing increased success: 72% → 76%
Photo store (expensive goods)Closing DECREASED success: 42% → 33%
Customer satisfaction (n=145)Closed customers: 5.8/10. Non-closed: 7.7/10
Professional buyer survey (n=54)34 of 54 said closing makes them LESS likely to buy

Pressure rule: Pressure helps with small decisions, hurts with large ones.

The American Airlines Counter-Finding (Important Caveat)

In a 575-call study (small-sale environment), success rates by closes per call:

  • 0 closes: 22% success
  • 1 close: 61% success (peak)
  • 2 closes: ~40%
  • 3+ closes: <20%

Zero closing also fails. Even in major sales, you must propose SOME commitment. The right number is one - propose a clear, realistic next step.

What Top Performers Do Instead (Obtaining Commitment)

  1. Concentrate Attention on Investigating - "You don't require closing techniques with a customer who wants to buy."
  2. Check That Key Concerns Are Covered - "Before we go further, could I check whether there are any areas you'd like me to tell you more about?"
  3. Summarize the Benefits - in long calls customers lose track
  4. Propose a Commitment (Don't Ask, Tell) - "Then the most logical next step would be for you and your accountant to come and see one of these systems in operation."

Two characteristics of good commitment proposals:

  1. The commitment ADVANCES the sale
  2. It's the HIGHEST realistic commitment the customer can give

The 4 Possible Call Outcomes

OutcomeDefinitionSuccess?
OrderFirm commitment to buyYES
AdvanceSpecific action moves sale forwardYES
ContinuationSale continues, no specific action agreedNO
No-saleCustomer actively refusesNO

Examples of Advances: demo attendance, intro to higher decision-maker, agreed trial, technical-team meeting, letter of intent.

Examples of Continuations (DEADLY): "Thank you, please visit again," "Fantastic presentation. Let's meet again sometime," "We liked it. We'll be in touch."

Decision rule: Judge call success by customer ACTIONS, not WORDS. Compliments are not a sign of success.

"In most major-account sales forces, fewer than 10% of calls result in an Order or No-sale."

Setting Call Objectives

Bad (Continuation)Good (Advance)
"Build the relationship""Get her to come to the demo"
"Collect information""Get a meeting with his boss"
"Make a good impression""Get an introduction to Planning"
"If a call's worth making, it's got to do something - to push the sale forward."

Objections: Prevention vs Handling

"Objections, contrary to common belief, are more often CREATED BY THE SELLER than the customer."

The Linda Marsh Correlation

Seller BehaviorMost Probable Customer Response
FeaturesPrice concerns
AdvantagesObjections
BenefitsApproval

Pattern: Problem Question → Implied Need → Advantage → Objection.

When you offer a solution before the customer feels the problem deeply, they push back. The cost feels too high relative to the developed need.

The Bold Experiment

Selected 8 salespeople with 10x average objection rates. Trained them in objection PREVENTION. Taught SPIN questioning to develop Explicit Needs and offer Benefits. Result: 55% reduction in objections.

Two Sure Signs You're Causing Objections

  1. Objections early in the call = talking solutions before developing needs
  2. Objections about value ("It's too expensive") = need not built strongly enough

Cure: Cut Features/Advantages. Add Problem, Implication, NPQ to build value.


Opening the Call (Preliminaries)

What Doesn't Work in Major Sales

  1. Relating to personal interests (golf trophy, family photo) - senior buyers don't care about your golf game
  2. Opening benefit statements ("Let me show you how to save thousands...") - traps you into early product details

What Works - Three Things to Establish

  1. Who you are
  2. Why you're there (NOT product details)
  3. Your right to ask questions

Three Rules

  1. Get down to business quickly - ≤20% of call time on Preliminaries
  2. Don't talk about solutions too soon - no products in the first half
  3. Concentrate on questions, not openings - plan questions, not opening lines

How to Implement: 4 Golden Rules of Skill Learning

Rule 1: Practice Only ONE Behavior at a Time

"Work on one thing at a time, and get it right." - Tom Landry

Rule 2: Try the New Behavior at Least 3 Times

200 golfers studied: 157 of 200 said they scored WORSE after their first lesson. The skill needs breaking in.

Rule 3: Quantity Before Quality

Don't worry about asking the perfect question. Ask LOTS of questions. Quality follows quantity.

Rule 4: Practice in SAFE Situations

"New skills go in SMALL accounts and well-known customers. Never in important sales."

Implementation Sequence

PhaseFocus
1Just ask MORE questions (mostly Situation, that's fine)
2Plan and ask Problem Questions (aim for 6+ per call)
3Move to Implication Questions (after PQs feel comfortable)
4Add Need-payoff Questions last

Decision Trees

"Is this a major sale?"

Will it complete in a single call?
├─ YES → Small sale. Use traditional techniques (close, features, etc.)
└─ NO  → Will customer need to justify to others?
        ├─ YES → Major sale. Use SPIN.
        └─ NO  → Is the spend significant ($) for the buyer?
                ├─ YES → Use SPIN-lite (PQ + needs)
                └─ NO  → Small sale techniques fine

"Why isn't this deal closing?"

Are you getting lots of objections?
├─ YES → Likely cause: too many Advantages too early
│        Cut Features/Advantages, add PQ/IQ/NPQ
└─ NO  → Are calls ending in Continuations (no specific next step)?
        ├─ YES → Call objectives are weak. Set Advance objectives.
        └─ NO  → Is customer not feeling enough urgency?
                └─ Add Implication Questions to develop the problem

"When to use which question type?"

Just met customer / new to account?
├─ Light on Situation Questions (do homework first)
└─ Started conversation?
   ├─ Customer aware of problems → Problem Questions
   ├─ Customer dismissive of severity → Implication Questions
   └─ Customer excited about solving → Need-payoff Questions

Critical Numbers & Rules of Thumb

NumberRule
27%Sales lift gap (Motorola, dollar value) - see cases.md for full breakdown and caveats
63%New-business order increase from SPIN training (Motorola) - see cases.md
6+Problem Questions per call - quantity target
20%Maximum % of call time spent on Preliminaries
3Minimum times to try a new behavior before judging
<10%Major-account calls that result in Order or No-sale (rest = Advances/Continuations)
7.8Average calls per major-sale cycle
55%Reduction in objections from objection-prevention training
1 in 20Average questions that are Implication Questions in typical sales calls
10xTop performers ask this many more NPQs (rhetorical, no published baseline)

Quick Reference Checklist

Before every major-sales call:

  • Researched enough to skip basic Situation Questions
  • Planned 3+ Problem Questions
  • Planned Implication Questions for each problem
  • Planned a few Need-payoff Questions
  • Set OBJECTIVE that requires customer action (Advance, not Continuation)
  • Planned how to summarize and propose commitment

During the call:

  • Preliminaries <20% of time
  • Asking questions, not telling
  • Building need with Implications before offering solutions
  • Converting Implied Needs into Explicit Needs
  • Asking NPQs to make customer articulate value

After the call:

  • Got an Order or Advance? (or just a Continuation?)
  • Which specific question had most impact?
  • What would I do differently next time?

The Big Idea

"Success rests on minute behavioral details. The hundreds of minute behavioral details in a call decide whether it succeeds."

The win isn't the close. It isn't the personality. It isn't the strategy. It's the questions you ask.


Supporting Files

  • frameworks.md - Full 3-stage need development model, value equation, FAB extended, BP buyer anecdote, "plan-do-review" loop, common mistakes (18-item list)
  • cases.md - Easiflo $120K canonical chained-Implication transcript; British Petroleum yacht photo; Tom Landry skill-learning case; Quincy's Rule origin; failed validation attempts (intellectual honesty)
  • examples.md - Question-planning templates; Implication Question generator; NPQ stock library; pre-call planning sheet; post-call review template
  • integration.md - Adaptation for B2C/SaaS/cultural contexts (Fuji Xerox 74% Japan study), competing methodologies (Challenger/MEDDPICC/Sandler/Gap Selling), conflicts with Mom Test/$100M Offers/Crossing the Chasm, evidence and limitations

When SPIN Fails (Don't Use Here)

ContextWhy SPIN FailsUse Instead
Cold call (<2 min)No time for chained questionsHook + value prop + meeting ask
RFP procurementBuyer wants price, not problemsDirect response + differentiation
PLG / freemium SaaSUser pre-qualified themselvesActivation + expansion playbook
Inbound MQL (read 4 assets)Already in solution modeSkip Investigating, fit/Benefit
Committee buyingSingle-call SPIN insufficientMEDDPICC + Champion enablement
Founder selling at $0-$1MOptimization prematureMom Test + offer iteration
Pure transactional <$50Small sales techniques workClosing/Features fine
Highly technical to expert buyer"Just show me the product"Lead with Features (the "Features appetite")

Full table and modern (post-1988) adaptations: see integration.md.


Note on Evidence

SPIN's empirical base is largely Huthwaite-internal: ~35,000 calls of broader research across 27 countries, but only n=42 (Motorola Canada) and n=55 (Multinational Business-Machines) are clean SPIN-specific validation studies. Both showed real productivity gains. No independent peer-reviewed replication. Treat SPIN as a strong prior for major sales, not gospel. Full evidence detail and Rackham's 6 failed validation attempts: see integration.md. For the Motorola validation study and its caveats, see cases.md.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

31.94%
按下载量换算51

Claude

31.49%
按下载量换算50

Cursor

18.37%
按下载量换算29

Gemini CLI

9.3%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills