Why Generic SPIN Training Fails the Moment a Hotel GM Picks Up
Most sales training programs that cover SPIN treat it as a four-stage framework. Situation, Problem, Implication, Need-Payoff — learn them in order, apply them to every call, convert more prospects. For horizontal software sales this approach works reasonably well. For hotel SDR work, it collapses fast.
Hotel General Managers and Revenue Managers are commercial operators. They manage P&L under ownership pressure, navigate multiple revenue streams simultaneously, and have been pitched by software vendors every week for years. The moment they detect a scripted framework being applied to them — the slightly too-rehearsed Situation question, the pivot to Implication that arrives before a real problem has been established — they disengage. The call ends politely and the calendar never opens.
What separates the hotel SDRs who consistently book demos from those who burn through call lists is not whether they know SPIN. It is whether they execute it correctly across all seven stages, in the right order, with the right content at each step. The four-stage model you learned in training is missing three stages that hotel buyers specifically require. Understanding all seven is the foundation of every call that converts.
The Seven-Stage SPIN Arc Built for Hotel Selling
The full framework used by elite hotel SDRs has seven stages, not four: Greeting, Situation, Problem, Implication, Need Payoff, Close, and Complete. Each stage has a specific function. Rushing any one of them — or skipping stages because the call is going well — is how deals get lost at the one-yard line.
Stage 1 — Greeting: This stage is underestimated by almost every SDR. The Greeting is not small talk. It is a 60-to-90-second credibility window where the hotel GM decides whether you understand their world or whether you are another vendor who is about to waste their time. The opening needs to demonstrate market awareness — a reference to what is happening in their corridor right now, a demand observation that signals you have looked at their specific market before calling — without launching into a pitch. The Greeting sets the entire tone of what follows.
Stage 2 — Situation: Once the GM is engaged, Situation questions establish the hotel's current commercial setup. How does the property currently manage pricing decisions? Who is involved in rate changes? How frequently are rates reviewed? What does the process look like when the market moves unexpectedly? These questions are not interrogation — they are professional mapping. And critically: if you have prior notes or context about this property from a previous call or email, you do not ask open discovery questions. You confirm what you already know and move faster.
Stage 3 — Problem: With the pricing process established, Problem questions surface the operational gap. Not invented pain — real gaps the GM or Revenue Manager has already been living with. What happens when a demand event lands mid-week and the next rate review is three days away? What happens when the comp set adjusts during the weekend and the hotel's rate does not follow until Monday? Problem questions work best when they are specific to the market conditions visible in that hotel's corridor right now, not generic hypotheticals.
Stage 4 — Implication: This is the stage that separates conversations from conversions. Implication questions ask the GM to calculate the downstream commercial consequence of the problem they just confirmed. Not "what if things were better" — but "when that rate review misses a market movement, what does that cost you in occupancy or RevPAR across a typical week?" The goal is a specific number, produced by the GM, in their own language. When that number exists, the commercial case for the meeting has been built entirely by the prospect. The SDR did not manufacture it.
One critical rule for the Implication stage: the framing must match the market reality. If the hotel's market is flat or showing distressed indicators, the Implication question should not manufacture urgency that the data does not support. Intellectually honest implication — anchored in what the market is actually doing — builds far more trust than an inflated opportunity claim that the GM will immediately recognise as inaccurate.
Stage 5 — Need Payoff: With the Implication number on the table, Need Payoff questions invite the GM to describe the benefit of solving the problem in their own words. "If you could respond to a rate movement inside the same trading day rather than waiting for the next scheduled review — what would that change for your weekday occupancy in Q4?" When the GM answers that question with a specific scenario or number, the SDR stops selling and starts confirming. The prospect has already decided.
Stage 6 — Close: The Close stage is singular in its purpose: booking a 20-minute demo or securing a 14-day trial commitment. Every script in the Close stage is designed to arc toward one of those two outcomes. Not "I'll send you more information." Not "let me know when you want to chat further." A specific calendar invite for a specific 20-minute window. That is the only acceptable advance from a hotel SPIN call.
Stage 7 — Complete: The call has reached its conclusion. Notes are captured, next steps are confirmed, and the follow-up is prepared while the conversation is still fresh.
An APAC Scenario: A Phuket Resort SDR Call That Goes the Full Arc
Consider an SDR calling the General Manager of a mid-scale beachfront property in Phuket during late January. The forward demand picture for the resort's corridor shows a compression window building for Songkran in April — pace is running ahead of prior year and the comp set has already begun moving weekend rates upward. The SDR has this intelligence loaded before the call connects.
The Greeting references the Songkran demand picture without naming the data source: "I've been looking at what's building in the Phuket market for April — there's a significant compression window forming and I wanted to understand how your team is positioned for it." The GM stays on the call because that sentence is about their market, not a product.
Situation: "Can you walk me through how the team is currently handling rate decisions — who's involved and roughly how often you're reviewing?" The GM describes a weekly process managed by the Revenue Manager with occasional input from the GM during peak periods.
Problem: "When the compression builds fast — like Songkran typically does in the final six weeks — does your weekly review cycle catch the full uplift opportunity, or does the market move ahead of your next scheduled update?" The GM pauses. The honest answer is that the rate usually follows the market by three to five days.
Implication: "If the comp set is capturing full compression ADR for five to seven days before your rate catches up — across a 120-room property in a peak window — what does that three-to-five-day lag represent in revenue?" The GM does the math. She quotes a number. That number is now the commercial case for the next conversation.
Need Payoff: "If your rate moved inside the same window as your comp set during those compression days — without adding anything to the team's existing workflow — what would that change for your Q2 RevPAR position?" The GM describes the outcome in her own words. The SDR confirms. The Close follows immediately.
The seven-stage arc is not a script — it is a sequence of permissions. Each stage earns the right to ask the next question. Rush any one of them and the GM stops giving permission. Complete all seven and the demo books itself.
The Most Common Stage That Gets Skipped — and Why It Kills the Deal
Across every failed hotel SDR call, the missing stage is almost always Implication. The SDR establishes a problem — the GM confirms a rate review lag — and the instinct fires immediately to pivot: "That's exactly what we solve." The product pitch arrives. The tension of the problem disappears. And so does the urgency.
The Implication question exists to hold the problem open long enough for the GM to feel its commercial weight. That feeling — not the product feature list that follows — is what creates the motivation to find 20 minutes on the calendar. SDRs who have been trained to skip Implication because the conversation is already going well are the same SDRs who have strong call quality scores and weak demo conversion rates. The two problems are directly related.
What Changes When You Have Market Intelligence on the Call
The seven-stage arc becomes significantly more precise when the SDR has live market data loaded before the call starts. In the Situation stage, the comp-set picture tells you what kind of pricing process question will be most revealing. In the Implication stage, the revenue opportunity calculation — property room count, current market ADR, the estimated underpricing gap — gives the SDR a specific dollar figure to anchor the question rather than a vague directional estimate.
Instead of "what do you think that lag costs you?" the SDR can frame it as: "Based on what your corridor is trading at right now, a five-day lag across your room count represents roughly $X in the window before Songkran. Does that match what you'd expect, or is it higher than you thought?" The GM responds to a number. The number produces an answer. The answer produces a meeting.
That specificity — rooted in live data, shaped by seven disciplined stages — is the difference between a hotel SDR who is good at their job and one who is exceptional at it. The framework is the same. The precision is what separates them.