# SPIN Question Templates — Stock Patterns by Type

**Source:** SPIN Selling, Neil Rackham. Chapter 4 (The SPIN Strategy).

Use these patterns as starting points when planning questions for a specific deal. Adapt to the actual context — these are structural templates, not word-for-word scripts. Specificity beats generality: "Are you finding that approval cycles are slowing your contract close times?" is far more powerful than "Are there any process challenges you're facing?"

---

## Situation Questions

**Purpose:** Establish factual background about the customer's current state. Use sparingly — they serve the seller, not the buyer. Do your homework first; ask only what you couldn't find out in advance.

| Template | Example |
|---|---|
| "What does your current [process/system] look like?" | "What does your current approval workflow look like?" |
| "How are you currently handling [area]?" | "How are you currently handling production scheduling?" |
| "How many [people/systems/locations] are involved in [function]?" | "How many operators use the system currently?" |
| "What [tool/vendor/approach] are you using for [function]?" | "What system are you using for demand forecasting?" |
| "How long have you been using [current approach]?" | "How long have you had this setup?" |
| "Who is involved in [process/decision]?" | "Who else is involved in the procurement decision?" |

**Situation Question limit:**
- New account, first call: 5-8 maximum
- Follow-up call: 2-3 maximum (context already established)
- Executive call: 1-2 maximum (they expect you to have done your homework)

---

## Problem Questions

**Purpose:** Probe for problems, difficulties, and dissatisfactions. Invite the customer to express Implied Needs. More effective than Situation Questions. In large sales, they provide the raw material for Implication chains.

| Template | Example |
|---|---|
| "Are you finding [situation] creates [difficulty]?" | "Are you finding that manual reporting creates delays for your team?" |
| "What difficulties do you run into when [situation]?" | "What difficulties do you run into when scheduling around last-minute orders?" |
| "Is it difficult to [task] with your current [system/approach]?" | "Is it difficult to track accountability with your current phone system?" |
| "How satisfied are you with [current approach]?" | "How satisfied are you with the speed of your current approval process?" |
| "Does [current situation] give you any [reliability/quality/cost] problems?" | "Does your current setup give you any visibility problems across regions?" |
| "Are there any bottlenecks or slowdowns in [process]?" | "Are there any bottlenecks in how work gets assigned to operators?" |
| "What would you change about your current [approach], if you could?" | "What would you change about your scheduling process if you could?" |

---

## Implication Questions

**Purpose:** Develop the seriousness of an Implied Need. Make the problem feel larger — not by exaggerating, but by helping the customer connect the problem to its downstream consequences. Problem-centered ("sad" per Quincy's Rule).

**Best used with:** Decision-makers (who think in consequences); high-value, multi-stakeholder deals; any situation where the cost of the solution needs to feel justified.

**Planning requirement:** Do NOT improvise these. Use the 3-step sub-workflow (Step 5 of the skill body) to generate them from specific consequences before the call.

| Template | Example |
|---|---|
| "What effect does [problem] have on [downstream area]?" | "What effect does the bottleneck have on your production schedule?" |
| "If [problem] occurs, what happens to [related process]?" | "If an operator leaves, how long before a replacement is fully trained?" |
| "[Problem] seems to lead to [consequence A]. Does it also affect [consequence B]?" | "Turnover leads to retraining costs. Does it also cause bottlenecks during the gap?" |
| "What does [problem] mean in terms of [cost/time/quality/risk]?" | "What does the overtime situation mean in terms of your annual labor costs?" |
| "When [problem occurs], how does that affect [stakeholder/team]?" | "When a shipment is late, how does that affect your relationship with the customer?" |
| "Is [problem] also affecting [adjacent area you've noticed]?" | "Is the turnover also making it harder to maintain quality on specialized jobs?" |
| "Does [problem] put you at risk of [specific negative outcome]?" | "Does sending work outside put you at the mercy of other people's delivery schedules?" |

---

## Need-Payoff Questions

**Purpose:** Shift the conversation from problem-centered to solution-centered. Get the buyer articulating benefits. "Happy" per Quincy's Rule. Only deploy these after the need has been developed.

**Critical constraint:** Only ask Need-payoff Questions for capabilities you can deliver. Asking "why would that be important?" for a need you cannot meet strengthens a need that becomes an objection.

| Template | Example |
|---|---|
| "Why is [solving this problem] important to you?" | "Why is controlling unauthorized long-distance calls important to you?" |
| "How would [capability] help you?" | "How would automated scheduling help your team?" |
| "Would it be useful if you could [specific capability]?" | "Would it help if you could restrict long-distance calling to authorized users?" |
| "Is there any other way [solving this] could help you?" | "Is there any other way having faster reports would help your team?" |
| "If you could [solve the problem], what would that mean for [outcome]?" | "If you could cut approval time from days to hours, what would that mean for your close rate?" |
| "How significant would it be if [positive change occurred]?" | "How significant would it be if you could catch a bottleneck 24 hours in advance?" |
| "Would [solving this] also help with [related area]?" | "Would better cost tracking also help you with your department accountability reporting?" |
| "What would be the value to you of [specific improvement]?" | "What would be the value to you of having operators up to speed in weeks rather than months?" |

---

## Sequence and Balance Notes

**Top performer benchmarks (from Rackham's research):**
- Top performers ask approximately **10× more Need-payoff Questions** than average performers
- Only **1 in 20 questions** in an average call is an Implication Question — despite being the most powerful type
- In failed calls: more Situation Questions, far fewer Implication and Need-payoff Questions

**Practical balance for a 45-minute discovery call:**
- Situation Questions: 4-6 (or fewer if you've done homework)
- Problem Questions: 6-10 (primary exploration phase)
- Implication Questions: 4-8 per confirmed problem (the chain)
- Need-payoff Questions: 3-5 per confirmed Implication chain (conversion phase)

**Transition signals — when to move to the next type:**
- S → P: Once you have the background context you need (don't wait until you have everything)
- P → I: Once the customer confirms a problem ("yes, that is a difficulty for us")
- I → N: Once the customer's language shifts from "it's minor" to "actually, this is significant" OR once you have 3+ consequences developed
- N → present: Once the buyer has expressed a specific want or desire (Explicit Need) in their own words