Discovery Calls with SPIN — Let the Buyer Sell Themselves

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', qua...

deciqAI

@deciqai

What This Skill Does

Guides sales discovery calls using the SPIN questioning framework (Situation, Problem, Implication, Need-payoff) so the buyer articulates their pain and the value of a solution, rather than being pitched. The agent prompts the seller through each stage and flags when to advance or avoid feature-dumping.

Replaces unstructured discovery calls and feature-dumping demos by forcing the buyer to quantify the cost of their problem and the payoff of solving it.

When to Use It

  • Run a discovery call for a complex B2B deal that needs urgency
  • Qualify a prospect who seems interested but won't commit to next steps
  • Prepare questions for a call where the buyer hasn't voiced their pain
  • Debrief a stalled deal to identify missing implication questions
  • Structure a demo so it only shows features tied to buyer-stated needs
  • Train new sales reps on consultative questioning techniques

Install

$ openclaw skills install @deciqai/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

Top skills in this category