360 Secure SkillHub
360 安全技能中心

Discovery Calls with SPIN — Let the Buyer Sell Themselves

该 Skill 提供 SPIN Selling 探索电话框架，按情境、问题、影响、需求回报顺序提问，帮助买方说出痛点与价值，并附带使用场景、注意事项和验证清单。

deciqai
deciqai
热度 25.63
最近更新 2026-07-17 01:57:43
分类：营销依赖：纯提示词应用场景：工作流 / 模板

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add discovery-call-spin
Metadata
name
discovery-call-spin
description
Activate when: running sales discovery calls; deals stall because the buyer doesn't feel the pain; 'how do I run a sales call', 'my demos don't convert', qualifying a prospect. Do NOT activate when: the deal is transactional/self-serve with no call, or it's post-sale support. More: deciqai.com/c/discovery-call-spin

Discovery Calls with SPIN — Let the Buyer Sell Themselves

Overview

SPIN Selling (Neil Rackham, from large-sale research) structures a discovery call around four question types in order — Situation, Problem, Implication, Need-payoff — so the buyer articulates the cost of their problem and the value of solving it, rather than being pitched. Implication questions (what the problem costs) are the ones that move complex deals. Talking less and questioning better outperforms feature-dumping.

The Process

  1. Situation (briefly) — enough context to be relevant; don't interrogate on facts you could research. Gate: too many situation questions bore the buyer — keep them minimal.
  2. Problem — surface real difficulties/dissatisfactions ("where does the current approach break down?").
  3. Implication — quantify the cost/ripple of that problem ("what does that delay cost per month? who else does it hurt?"). This is where urgency is built.
  4. Need-payoff — let them state the value of a solution ("if that were solved, what would it be worth?").
  5. Only then map your capability to their stated need — solve, don't pitch.
  6. Confirm next step / advance. Gate: no agreed next action = the call didn't progress the deal.

When to Use

  • Consultative / considered-purchase sales
  • Demos that show features but don't create urgency
  • Qualifying whether pain is worth the buyer's spend

Applying It Well

  • Talk <40%; the buyer should voice the pain and the payoff.
  • Implication questions create urgency without pressure — invest there.
  • Research situation facts beforehand; spend live time on problem/implication.

Red Flags

  • Jumping to demo before implications are felt.
  • Feature-dumping when the buyer hasn't quantified pain.
  • Ending with "I'll follow up" instead of a scheduled advance.

Verification

  • Situation kept minimal; researched in advance
  • Problems surfaced in the buyer's words
  • Implications quantified (cost of inaction)
  • Buyer stated the payoff; concrete next step set

Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/discovery-call-spin · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/discovery-call-spin.json