spin-selling

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 5015fcf4cde3 · 29 Oct 2026Report an issue or request a re-scan

• Publishergetagentseal GitHub organizationOwner of the repository this skill is read from
• Source foldergetagentseal/founder-playbook/skills/spin-sellingThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict5015fcf4cde3A new audit runs when the source changes
• Repository statusNot archivedLast push 22 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to…

---
name: spin-selling
description: "Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching', 'discovery call structure', 'stuck in the middle of the sale'. Not for transactional sub-$50 sales, pure consumer impulse, or PLG self-serve products."
---

> **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.**

| Dimension | Small Sale | Large Sale |
|-----------|-----------|------------|
| Selling cycle | Single call | Multi-call (months/years) |
| Decision maker | Individual | Multiple stakeholders |
| Customer's risk | Low (personal $) | High (career, public visibility) |
| Post-sale relationship | None | Ongoing |
| Need development | Instant | Slow, painful |
| Effective pressure | Yes (closing works) | No (closing backfires) |
| Top behavior | Closing/Features | Questioning/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

| Stage | What Happens | Importance in Major Sales |
|-------|--------------|---------------------------|
| **1. Preliminaries** | Opening, warming up | LOW (≤20% of call time) |
| **2. Investigating** | Asking questions to develop needs | **HIGHEST** (this is where you win) |
| **3. Demonstrating Capability** | Showing your solution | Medium (only after needs developed) |
| **4. Obtaining Commitment** | Getting next-step action | Low (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 Type | Focus | Tone |
|---------------|-------|------|
| Implication | Problem-centered | Sad (makes problem bigger) |
| Need-payoff | Solution-centered | Happy (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 Type | Definition | Example |
|-----------|------------|---------|
| **Implied** | Problems, difficulties, dissatisfact

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/getagentseal/founder-playbook
git -C founder-playbook checkout 5015fcf4cde3

Works in

1. 2026-10-29
   ✓SAFE B 89 / 100

   first audit · source 5015fcf4cde3

Questions about spin-selling

• github.com/getagentseal/founder-playbook/tree/main/skills/spin-s — the audited source at commit 5015fcf4cde3 and every finding aboveObserved · 29 Oct 2026

Spotted something wrong? Report a correction · Methodology