Level 17 min
Curious
Sofia admits the summer overbooking after one good problem question and answers implication questions in detail.
- One hidden problem
- Gives examples freely
A discovery call for SPIN selling training. Sofia, an AI operations director at a hotel group, says her booking system works and asks what problem you think she has. Ask the situation, problem, implication and need-payoff questions that let her find the problem herself and say what fixing it is worth.

The situation
Sofia’s group runs 12 hotels in Spain and Portugal on a booking system she chose six years ago. You sell a central reservation system for hotel groups: one room inventory for every channel, including group blocks and corporate rates. She agreed to a 30-minute call because her commercial director asked her to, and she opens by asking what problem you think she has.
The AI character

Polite and guarded. She expects you to criticize a system she chose.
What is scored
In SPIN the questions do the work, so the questions are what gets quoted. Under each criterion you see the situation, problem, implication or need-payoff questions that opened Sofia up or shut her down, with timestamped comments. If your team runs discovery its own way, score the call on your own checklist.
Asks only what research can’t tell you, such as how group bookings reach the system, and shows the rest is already known.
Opens with a list of questions about hotel count, room numbers and software.
Asks where the current process is slow, manual or risky until Sofia describes a problem herself.
Tells her what her problem is, or accepts “it works” and moves to the demo.
Explores what selling a room twice costs: guests moved to other hotels, reviews, evening work at the front desk, the two new hotels.
Jumps from the first problem straight to the product.
Asks what a fix would change, so Sofia, not the rep, says what it’s worth to her hotels.
Describes the benefits instead of asking her.
Ends with a meeting on a set date that includes the commercial director, who shares the decision.
Closes with “I’ll send you a deck.”
How the conversation can go

Our booking system works. What problem do you think we have?
Maybe none. That’s what I’d like to find out. I know you run 12 hotels on one central system. How do group and corporate bookings get into it today?

By email. Each front desk enters the block by hand, usually in the evening.
Where does that get hard for your front desk teams?

In summer. A block goes in late, the online channels still show the rooms, and we sell them twice.
What happens to the guest when a hotel sells the same room twice in July?

We move them to another hotel and pay for the night. It happened at four of our hotels last summer.
And with two new hotels opening in April, does that risk grow?

It does. Two new front desk teams learning the same manual process in their first season.
If a group block closed online availability the moment it was entered, what would that change for you next summer?

No guests moved on arrival, and my front desk managers get their evenings back. My commercial director should hear this.
Could the three of us talk on Tuesday? I’ll show how one group block would move through a single hotel, start to finish.

Tuesday at ten. Send the invite to both of us.
Strong implication work, but only one need-payoff question. Next run, ask what the fix would mean for the two new hotels.
Difficulty
Level 17 min
Sofia admits the summer overbooking after one good problem question and answers implication questions in detail.
Level 210 min
The default version. She defends the system she chose and names a problem only after a specific question about group bookings.
Level 314 min
Her commercial director joins halfway, cares about direct bookings more than front desk workload and pushes you to skip to a demo.
FAQ
A discovery method from Neil Rackham’s book SPIN Selling (1988). Situation questions establish the facts, problem questions find what isn’t working, implication questions explore what that costs, and need-payoff questions let the buyer say what a solution would be worth.
It gives reps a buyer who won’t volunteer a problem, so each question type has work to do. Run it after reps learn the four types, and repeat it until implication and need-payoff questions come without a script.
Yes. One person plays Sofia from the profile above and gives up a hidden problem only when asked a well-aimed question. A second person runs the call, and a third tallies questions by type and scores the five criteria. Swap roles after each round.
The criteria are the question types themselves, so each score quotes the situation, problem, implication or need-payoff questions the rep actually asked. What counts is what the rep asks and says, not their voice or feelings. The mood bar is Sofia’s alone: she is the character, and she warms or cools with the questions she hears.
Yes. Describe your product, the buyers your reps call on and the problems they usually have to dig for in the scenario builder. Keep SPIN as the criteria, or score against MEDDIC or your own discovery checklist.
Ask Sofia your own discovery questions in a short live demo, or name the buyer your reps can’t get past “it works.”
Cookies and tags
With your consent, Microsoft Clarity records how you use our pages, and tags from Google, LinkedIn and Lemon Squeezy measure our ads and partner links. Nothing loads until you choose. Read the cookie policy