SPIN
The output is questions. If your prompt produced statements, it was not SPIN.
What is SPIN?
SPIN is four kinds of question: Situation, Problem, Implication and Need-payoff. It is the only framework here that came out of a controlled study rather than somebody's experience, and the first thing to understand is that its output is a question sequence — not a pitch, not a script, not a set of talking points.
Ask a model to help with a sales call and it will write you things to say. SPIN produces things to ask, in an order where each question depends on the answer to the last one. That dependency is the whole mechanism: the point of the sequence is to get the buyer to state the problem's cost in their own words, because Rackham's research found that a need the buyer has said out loud behaves completely differently from one you have inferred. It is also the framework that makes FAB usable — FAB needs an explicitly stated need as an input, and SPIN is how you get one.
Where SPIN Came From
Twelve years, 35,000 sales calls, and a lot of overturned advice
SPIN comes from Neil Rackham and the Huthwaite research programme: observers sat in on roughly 35,000 recorded sales calls over about twelve years, at firms including IBM and Xerox, coding every behaviour and correlating it with outcomes. The results were published as SPIN Selling in 1988. It remains the largest study of its kind, and most of what it found contradicted what sales training was teaching at the time.
Situation questions correlate with inexperience, not success
The most useful finding for anyone writing a call plan. Situation questions — the ones that establish basic facts — are the easiest to ask, they are asked more often by less experienced salespeople, and they do not contribute to success. Buyers find them boring, because every one of them is a question the seller could have answered by doing their homework. The practical rule that falls out of this is the single best line to put in a SPIN prompt: here is what I already know from research, so do not spend the call establishing it.
Implication questions are the hard ones and the ones that work
Implication questions develop the consequences of a problem the buyer has already admitted — what it costs, what it knocks on to, what happens at the worst moment of the year. Rackham found buyers rate them the most thought-provoking, and they are the hardest to ask well because they cannot be written in advance without knowing which problem surfaced. They are the mechanism that turns an implicit need into an explicit one.
And closing techniques backfire in large sales
The finding that made the book controversial. The 1970s consensus was that more closing attempts meant more sales; the data said that holds for small transactions and reverses as the deal grows. With a professional buyer, pressure to close early reads as a reason for suspicion. Which is why a good SPIN prompt bans closing questions outright.
The 4 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
Cap the number explicitly, and supply everything your research already covers so the model cannot waste questions on it. Three is plenty. Every situation question you ask is a minute not spent on implication, and the research says buyers are actively bored by them.
These surface the implicit need. The craft is in the phrasing: a problem question can easily sound like an accusation that the buyer has managed badly, and a defensive buyer stops admitting things. Ask about the process, not about their judgement.
Give this section the most questions. Each one should extend a difficulty into its costs: partner time, missed timelines, what happens at year-end, what the open vacancy is doing to the people covering it. This is where a mildly annoying problem becomes a problem worth spending money on, and the buyer is the one who does the converting.
The inversion that makes SPIN work. Instead of telling them what solving it is worth, ask a question whose answer is that sentence. A buyer who says "we would get about a day a week back per partner" has made your argument in a way you never could, and will repeat it to their colleagues when you are not in the room.
One Task, Before and After
The task: A 40-minute discovery call with an accountancy practice running on spreadsheets. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Give me some questions to ask on a sales call.
Eight words. You get fifteen situation questions, two of which are "what are your biggest challenges?", and a closing question at the end.
Write the discovery call brief for a 40-minute first call - the questions I will ask, in the order I should ask them. This is a discovery call, not a pitch. What I already know from research, so I do not waste the call establishing it: 60-person accountancy practice, four partners, currently running client onboarding on a shared spreadsheet and a Dropbox folder. They hired two client managers last quarter. Their careers page has been advertising a third for eleven weeks. Situation - no more than three questions, and none that our research already answers. Every situation question spent is a minute not spent on implication. Problem - four questions that surface difficulties with the current spreadsheet process, phrased so they do not sound like accusations of poor management. Implication - six questions, and this is the section that decides whether the call works. Each one should develop the consequences of a problem they have just admitted: what it costs in partner time, what it does to onboarding timelines, what happens at year-end, what the eleven-week vacancy is doing to the existing team. Need-payoff - four questions that get them to state the value of solving it in their own words, rather than me asserting it. For each question, add one line: the answer that would tell me to keep going, and the answer that would tell me to stop. For example: ``` Q: When a client manager leaves, how do you hand over their in-flight onboardings? Keep going if: they describe a manual walkthrough or admit things get dropped. Stop if: they describe a documented process that already works. ``` Write 700 to 900 words, grouped under the four headings, questions numbered continuously. Reason through the research before you write the implication section: each implication question has to develop a difficulty the buyer will just have admitted, not introduce a new one. Ensure every implication question builds on a problem the earlier section would have surfaced, rather than introducing a new topic. Do not write any statement about our product - this call contains no pitch. Do not invent facts about their business beyond the research above, and do not use a closing question of any kind.
Ninety-two. The two lines carrying it are the research paragraph — which squeezes the situation questions down to three — and the keep-going/stop line under each question, which turns a list into something you can actually run a call from.
Ninety-two, and nothing checks whether the sequence is a sequence
One check is structurally unreachable, and the two things that decide whether a SPIN plan is any good are both invisible:
No persona slot, and here that is right: it is you on the call. A "veteran enterprise seller" persona produces questions in a register you would not use, and a buyer hears the seam immediately.
The mechanism, and nothing sees it. Six implication questions that each introduce a fresh topic score exactly as well as six that build on a problem just admitted — and only the second set does anything. Read them in order and check each one would make sense as a follow-up.
Models drift toward selling. A "question" that is really a product claim with a question mark on the end — "how much would it help if you could automate that?" — costs no points and wrecks the call.
The line worth stealing from this page whatever you sell: state what you already know from research, and forbid questions that re-establish it. Rackham measured that situation questions rise with inexperience and do not predict success; this one paragraph is what converts that finding into a better call.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
[The deliverable: the QUESTIONS I will ask, in order. This is a discovery call, not a pitch] [What I already know from research — so no question re-establishes it] Situation: [No more than three. None that the research above already answers] Problem: [Questions that surface difficulties, phrased so they are not accusations] Implication: [The MOST questions. Each develops the cost of a problem just admitted — time, timelines, what happens at the worst moment of the year] Need-payoff: [Questions whose answer is the buyer stating the value themselves] [For each question: the answer that means keep going, and the answer that means stop] [No product statements. No closing questions. No invented facts about their business]
When SPIN Fits — and When It Does Not
- Discovery calls, which is the job it was designed and measured for.
- Larger, considered B2B purchases with several people involved.
- Renewal conversations with an account that has gone quiet.
- Expansion into a second team, where the need has to be re-established from scratch.
- Qualifying an inbound lead, where the danger is assuming the need is already explicit.
- Preparing anyone junior for a call — the sequence is teachable in a way instinct is not.
- Small transactional sales. Rackham's own data says the advantage shrinks as the deal does.
- Self-serve and product-led motions, where nobody is having a conversation at all.
- Marketing copy of any kind. SPIN produces questions; copy has to make statements.
- Calls where you already have an explicit, stated need — go straight to FAB.
- Anything where you have not done the research. Without it, SPIN becomes fifteen situation questions.
10 Ready-Made SPIN Prompts
Every prompt below was produced by the Frompting generator with SPIN selected — not written by hand for this page. Each is scored by our prompt checker; the median is 87/100. Click one to open it, then copy.
Discovery questions for a mid-market prospect 68
You are a seasoned B2B sales consultant tasked with crafting a comprehensive list of discovery-call questions for a mid-market prospect. Your output should be a sequential set of question groups that naturally progress from gathering context, uncovering challenges, exploring consequences, identifying desired outcomes, and revealing the value of a solution. The questions must be tailored to the prospect’s situation, so include placeholders for any details you do not yet have: [INDUSTRY: specify the prospect’s industry] [PROSPECT_ROLE: specify the decision-maker’s title] [PRODUCT_OR_SERVICE: specify the seller’s offering] [CURRENT_CHALLENGE: specify any known pain point] If any of these placeholders are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the list. Deliver the questions in five concise sections, each containing 3-5 bullet-point questions, ordered to flow from context to value. Keep the total length under 495 words. Quality criteria: 1. Questions are open-ended and encourage detailed responses. 2. Each question builds logically on the previous ones to deepen insight. 3. Language is professional, clear, and appropriate for a mid-market B2B audience. Exclude any mention of frameworks, acronyms, or internal methodology.
A prospect still running on spreadsheets 96
You are a seasoned B2B sales strategist. Your task is to design a detailed conversation plan for a discovery call with a prospect who currently relies on spreadsheets for their workflow. The plan must guide the salesperson through a logical progression that uncovers the prospect’s current situation, identifies pain points, explores the broader impact of those pains, clarifies the prospect’s desired outcomes, and demonstrates how your solution delivers measurable value. Structure the output as a numbered outline (1‑5) where each step builds on the previous one, providing specific question prompts, listening cues, and suggested transition statements. The conversation plan should be concise enough to fit within a typical 30‑minute call and written in a natural, consultative tone. Include a brief “Key Objectives” summary (max 50 words) at the top, followed by the five‑step outline. Quality criteria: 1. Questions must be open‑ended and encourage the prospect to elaborate. 2. Each step should include at least one concrete example or data point the salesperson can reference. 3. Transitions must smoothly link each step to the next without abrupt jumps. [PROSPECT_INDUSTRY: specify the industry the prospect operates in] [PROSPECT_ROLE: specify the decision‑maker’s title (e.g., Operations Manager, CFO)] [YOUR_SOLUTION: specify the product or service you are selling] Assume any missing details are typical for a mid‑size B2B SaaS offering and state those assumptions before finalizing the plan. Deliver the plan in plain text, using markdown headings for the summary and each step. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Selling HR software to a people director 87
You are a seasoned B2B sales consultant specializing in HR technology solutions. Your task is to create a list of discovery questions that a salesperson can use when speaking with a People Director to uncover needs and position an HR software offering effectively. The questions should flow naturally from establishing the current context, identifying challenges, exploring the impact of those challenges, clarifying the desired outcomes, and highlighting the value of the solution. Structure the output as a numbered list of 12–15 concise questions, ordered to guide the conversation from context to value. Use clear, professional language appropriate for a senior HR leader. [COMPANY SIZE]: specify the approximate number of employees (e.g., “500‑1,000 employees”). [INDUSTRY SECTOR]: indicate the primary industry (e.g., “technology”, “manufacturing”). [CURRENT HR TOOLS]: name the primary HR system(s) currently in use, if known. Deliver the questions in plain text, each on its own line, without headings or sub‑headings. Quality criteria: 1. Questions should be open‑ended and encourage detailed responses. 2. Each question must logically lead to the next, building a coherent discovery flow. 3. The language should reflect a consultative tone, focusing on the People Director’s priorities and pain points. Exclude any mention of pricing, contract terms, or implementation timelines at this stage. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop. Unless a length is specified above, aim for roughly 600-900 words.
A renewal call with an at-risk account 83
You are a seasoned B2B sales consultant. Your task is to craft a concise list of discovery‑style questions that a salesperson can use during a renewal conversation with an at‑risk account. The questions must follow a logical progression that first gathers context, then uncovers challenges, explores the impact of those challenges, identifies the prospect’s desired outcome, and finally highlights the value of continuing the partnership. Produce the questions in the order described, grouping them under three short headings: 1. Context – understand the current situation. 2. Challenge – probe problems and their consequences. 3. Value – elicit the need and illustrate the payoff of renewal. Output format: a markdown list with each heading as a level‑2 heading (##) followed by bullet points. Limit the total to **12–15 questions** (approximately 200 words). Quality criteria: - Each question is open‑ended, encourages the prospect to elaborate, and avoids yes/no answers. - The flow naturally leads the prospect from factual context to deeper implications and finally to a vision of benefit. - Language is professional, concise, and tailored to a B2B renewal setting. Assume you have no specific details about the account. State any assumptions you make and ask up to three clarifying questions (e.g., industry, key decision‑maker’s role, renewal timeline) before finalizing the list. [ACCOUNT_NAME]: Provide the name of the at‑risk customer. [INDUSTRY]: Specify the industry or sector the account operates in. [KEY_STAKEHOLDER_ROLE]: Identify the primary contact’s job title or function. [CURRENT_CONTRACT_END]: Indicate the date the existing contract expires. Do not include any sales framework names or component labels in the output. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
A first call after a demo request 96
You are a seasoned B2B sales strategist. Your task is to design a concise, step-by-step agenda for the initial discovery call with a prospect who has requested a product demo. The agenda should flow naturally through the following logical phases: 1. Open with context-setting questions to understand the prospect’s current environment and objectives. 2. Identify specific challenges or pain points the prospect is experiencing. 3. Explore the broader business impact of those challenges if left unaddressed. 4. Clarify the prospect’s desired outcomes and criteria for a successful solution. 5. Outline how the upcoming demo will directly address those needs and demonstrate value. Deliver the agenda as a numbered list, each item limited to 1-2 short sentences. Keep the total length under 735 words. Quality criteria: - Each step must logically lead to the next, building a clear narrative. - Questions should be open-ended and tailored to uncover actionable insights. - The final step must clearly link the demo content to the prospect’s stated needs. Boundary: Do not include any script for the demo itself or pricing discussion. If any essential detail is unknown, insert a placeholder in the format **[PLACEHOLDER_LABEL: brief hint]** (e.g., [PROSPECT_INDUSTRY: specify industry]). State any assumptions you make and ask up to three clarifying questions before finalizing the agenda.
Uncovering the cost of a manual process 82
You are a seasoned B2B sales consultant tasked with creating a discovery‑question set that reveals the true cost of a manual process for a prospective client. Your output should be a list of concise, open‑ended questions organized in a logical flow that first establishes context, then uncovers challenges, explores the impact of those challenges, probes the client’s desired outcomes, and finally highlights the value of addressing the issue. Produce exactly **12–15 questions** total, grouped in the order described above, each on its own line. Use plain language but incorporate any relevant industry terminology only if it is supplied. **Quality criteria** 1. Each question must be open‑ended and encourage the client to elaborate. 2. The sequence should naturally lead the conversation from background to value realization without explicit headings. 3. Questions should avoid jargon unless it is essential to the process being examined. **Boundary** – Do not include any sales pitch, solution description, or pricing suggestion; focus solely on eliciting information about the current manual workflow and its costs. If any of the following details are unknown, insert a placeholder in the format **[PLACEHOLDER: brief hint]** and proceed: - [INDUSTRY: type of business] - [PROCESS: specific manual task or workflow] - [ROLE: decision‑maker or stakeholder being interviewed] State any assumptions you make about these placeholders, and ask up to three clarifying questions before finalizing the question set. Unless a length is specified above, aim for roughly 600-900 words.
Selling security to a finance director 87
You are a seasoned B2B sales strategist tasked with crafting a complete discovery‑call script for selling a cybersecurity solution to a finance director. The script should flow naturally through the following stages: begin by gathering context about the prospect’s current environment and financial oversight responsibilities; then uncover specific challenges the finance director faces regarding security and risk; explore the broader consequences of those challenges for the organization’s financial health and compliance; identify the finance director’s criteria for an effective security solution; and finally illustrate how the proposed cybersecurity offering delivers measurable value and mitigates the identified risks. [COMPANY NAME]: provide the name of the prospect’s organization. [CYBERSECURITY SOLUTION]: describe the specific product or service you will be positioning. [FINANCE DIRECTOR’S PRIMARY CONCERNS]: list the top security‑related worries (e.g., fraud, data breaches, regulatory penalties). [CALL DURATION]: indicate the intended length of the discovery call (e.g., 30 minutes). [REGULATORY FRAMEWORK]: specify any compliance regime relevant to the prospect (e.g., GDPR, PCI‑DSS). The output must be a ready‑to‑use script of approximately 350 words, formatted in clear paragraphs for each stage, with optional brief bullet points for key questions. Ensure the language is professional, consultative, and tailored to a finance executive’s perspective. Avoid jargon unless it is defined inline. If any of the placeholders above are unknown, state your assumption for that item and proceed. Otherwise, ask up to three clarifying questions before finalizing the script.
Expanding into a second team 89
You are a seasoned B2B sales strategist. Your task is to design a detailed conversation plan that helps a salesperson expand an existing client account into a second team. The plan should guide the dialogue from establishing the current context, uncovering challenges, exploring the impact of those challenges, identifying the true need for a broader solution, and illustrating the value of adding the second team. Structure the output as a sequential script with numbered sections, each containing concise talking points and suggested questions. Use a natural, consultative tone and keep the entire script to **approximately 555-735 words**. **Output format** 1. Opening - set the scene and confirm the current relationship. 2. Exploration - ask questions that reveal the client’s current situation and any pain points. 3. Impact - probe the consequences of those pain points for the client’s business. 4. Need - help the client articulate why expanding to a second team would address the impact. 5. Value - present the payoff of the expansion, linking it to the client’s goals. **Quality criteria** - Each section must contain at least one open-ended question that encourages the client to share specifics. - The script should flow logically, building on information gathered in the previous step. - Language must be clear, professional, and free of jargon unless a technical term is essential, in which case provide a brief definition. **Assumptions & clarifications** State any assumptions you make about the account and ask up to three clarifying questions (e.g., about the client’s industry, the products/services involved, or key stakeholders) before finalizing the script. **Placeholders for unknown details** - [ACCOUNT_NAME]: name of the existing client - [CURRENT_TEAM]: description of the team currently using your solution - [TARGET_TEAM]: description of the second team you aim to engage - [KEY_DECISION_MAKER]: name/role of the person who can approve the expansion - [PRODUCT_OR_SERVICE]: brief description of what you are selling Do not include any content outside the script, placeholders, or the brief instructions. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Qualifying an inbound enterprise lead 74
You are a seasoned B2B sales strategist tasked with creating a concise list of qualifying questions for an inbound enterprise lead. Your output should be a series of open‑ended questions organized in a logical discovery flow: begin with context‑setting inquiries, then explore the prospect’s challenges, uncover the broader impact of those challenges, identify the specific need they are trying to address, and finally surface the value they would gain from a solution. Produce exactly **10 questions**, each no longer than two sentences, formatted as a numbered list. **Quality criteria** 1. Each question must be open‑ended and encourage the prospect to elaborate. 2. The sequence should naturally guide the conversation from understanding the current situation to revealing the desired outcome. 3. Questions should be relevant to an enterprise buyer and avoid technical jargon unless it is essential to the industry. **Assumptions & Clarifications** If any of the following details are unknown, state your assumption and proceed, or ask up to three brief clarifying questions before finalizing the list: - [INDUSTRY]: the sector the prospect operates in. - [PRODUCT_OR_SERVICE]: the solution you are qualifying. - [TARGET_ROLE]: the typical decision‑maker or influencer you will be speaking with. - [BUDGET_RANGE]: the approximate budget the prospect might allocate. - [DECISION_TIMELINE]: the expected timeframe for a purchasing decision. **Boundary** Do not include any yes/no questions or statements that could be interpreted as a sales pitch. Deliver the numbered list of questions only.
A prospect happy with their current vendor 88
You are a seasoned B2B sales strategist. Your task is to craft a concise, persuasive call script for a sales representative who is speaking with a prospect that claims they are satisfied with their current vendor. The script should flow naturally through the following progression: begin by gathering essential context about the prospect’s current situation, then subtly reveal any underlying challenges, explore the broader impact of those challenges, highlight the prospect’s true needs, and finally illustrate the unique value your solution can deliver. Structure the output as a single, continuous script (no headings or labels), keeping the total length between 340-450 words. Include at least three specific, open-ended questions that elicit useful information at each stage of the conversation. Quality criteria: 1. Questions must be open-ended and encourage the prospect to elaborate. 2. The transition between stages should feel natural and not forced. 3. The payoff portion must clearly differentiate your offering from the prospect’s current vendor without disparaging the competitor. Assume the prospect’s industry, decision-maker title, and the product/service you sell are unknown; insert placeholders in the format **[PLACEHOLDER: description]** (e.g., **[INDUSTRY: specify the prospect’s industry]**). Before finalizing the script, state any assumptions you are making and ask up to three clarifying questions needed to tailor the conversation more precisely. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
Scores range from 68 to 96. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
SPIN vs the Alternatives
The pair that completes each other. FAB cannot produce a genuine benefit without an explicitly stated need; SPIN is the sequence that produces one. Run SPIN on the call, FAB on the follow-up.
The written cousin, and the roles reverse. PAS agitates the problem for the reader; SPIN asks questions until the buyer agitates it themselves — which is far stronger and only works live.
A model of a stranger's attention. SPIN assumes you already have a meeting and the job is to find out whether there is anything worth selling.
What to write once the call has told you what the Before actually is. SPIN gathers the material BAB needs.
The neutral fact-finding checklist. 5W1H establishes what is true; SPIN is designed to make the buyer care about it.
Five Ways People Get SPIN Wrong
The defining SPIN failure. Ask for help with a sales call and a model writes a pitch. Say explicitly that the deliverable is the questions you will ask, and ban product claims outright — otherwise half your "questions" are assertions with a question mark attached.
The behaviour the research specifically associates with inexperience. Cap them at three and supply your research, or the model will happily generate fifteen and the buyer will be bored before you reach anything that matters.
An implication question has to develop something the buyer just admitted. If it opens a fresh subject it is a problem question in the wrong section, and the sequence stops compounding.
"So if I could solve that, would you buy?" is a close wearing a question mark. A real need-payoff question invites the buyer to describe the value, not to commit.
Every question should change what you do next. Attaching a keep-going and a stop condition to each one is the cheapest way to find the questions that were only there for symmetry.
The research is specific: pressure to close early works in small sales and backfires in large ones. Ban closing questions in the prompt and decide about them afterwards, with a clear head.
SPIN Questions
What does SPIN stand for?
Situation, Problem, Implication, Need-payoff — four types of question, asked in that order, designed to move a buyer from an unexamined difficulty to an explicitly stated need.
Where does SPIN come from?
Neil Rackham and the Huthwaite research programme: roughly 35,000 recorded sales calls observed over about twelve years, published as SPIN Selling in 1988. It is the largest study of selling behaviour ever conducted.
Why are situation questions discouraged?
Because the research found they are asked more by less experienced salespeople and do not correlate with success. Every one is a question you could have answered with research, and buyers experience them as wasted time.
What makes implication questions different?
They develop the consequences of a problem the buyer has already admitted, which is what turns an implicit need into an explicit one. Buyers rate them the most thought-provoking, and they are the hardest to prepare because they depend on what surfaced a moment earlier.
Does SPIN work for small sales?
Less well, and Rackham said so. The behaviours that predict success in large sales differ from those in small ones — including closing, which helps in small transactions and backfires with professional buyers on large ones.
How do I stop the AI turning my SPIN prompt into a pitch?
Say the deliverable is questions, ban statements about the product explicitly, and ban closing questions. Without all three, a model will drift into selling, because that is what most of its sales training data looks like.
Generate a SPIN Prompt Instantly
Skip the manual template — Frompting applies SPIN to your topic in one click.
Try it FreeFramework Details
| Name | SPIN |
| Stands for | Situation-Problem-Implication-Need-Payoff |
| Domain | Persuasion & Conversion |
| Steps | 5 |
| Access | Pro |