Discovery call spin

Skill deciqAI/knowledge-skills/discovery-call-spin

Open-source thinking-framework skills that make rigorous reasoning executable for AI agents — first-principles, inversion, second-order thinking, Occam's razor, Bayesian reasoning. Built by deciqAI.

Install

npx -y skills add deciqAI/knowledge-skills --skill discovery-call-spin

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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/s/discovery-call-spin

SKILL.md

2.8 KB, as published. Nobody here has run it

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

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.
Problem — surface real difficulties/dissatisfactions ("where does the current approach break down?").
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.
Need-payoff — let them state the value of a solution ("if that were solved, what would it be worth?").
Only then map your capability to their stated need — solve, don't pitch.
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 — 233 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/s/discovery-call-spin · Built by deciqAI · github.com/deciqAI · Contributions welcome.

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