Discovery Call Questions for Hotel Tech Sales

Discovery Call Questions for Hotel Tech Sales

Published on:

Published on:

Reading time:

Reading time:

7

7

min read

min read

Table of contents:

TL;DR

  • Gong's research links 11 to 14 discovery questions and 3 to 4 business problems per call with the best outcomes, so choose questions rather than reading a list.

  • Hotel discovery has to cover the current stack and contract dates, the operational problem, the cost of that problem, who approves, and timing.

  • Ebsta found well qualified deals are 6.3x more likely to close, so log every answer in the CRM straight after the call.

  • End every call with a specific next step agreed with the buyer, or disqualify the hotel politely.

Most hotel tech discovery calls go wrong in one of two ways. Either the seller talks for forty minutes and calls it discovery, or they run through a long checklist that feels like an audit to a general manager who stepped away from the front desk to take the call. Both end with a demo that misses what the hotel actually cares about.

This post gives you copyable scripts for each part of the call, written for selling PMS, channel managers, booking engines, revenue management and guest tech to hotels. Use them as a bank to choose from, not a script to read top to bottom.

What the data says about discovery calls

Gong's analysis of 519,000 recorded discovery calls found that the most effective calls uncover three to four business problems, and that asking 11 to 14 questions correlated with the greatest success. Fewer, and discovery was not deep enough. More, and the call started to feel like an interrogation. Top sellers spread their questions through the call rather than front-loading them.

Gong's 2025 update, based on 326K sales calls, found the same pattern. Sellers who won deals asked 15 to 16 questions per call, while sellers who lost asked about 20. Reps talked for 57% of the time on closed-won deals and 62% on lost deals. In short: fewer, better questions, and more listening.

The calls also need to be recorded properly. Ebsta's 2025 Sales Qualification Report, covering over 655,000 B2B opportunities, found that well-qualified deals are 6.3x more likely to close than poorly qualified ones, yet only 36% of deals passing discovery had both a qualification score and supporting notes.

The call structure

Part

Minutes

Goal

Questions to use

Opener

2 to 3

Agree the agenda and the time

None, just the opener script

Current stack

5

Know what they run and when contracts end

2 to 3

The problem

10 to 15

Find 3 to 4 real problems

3 to 4

The cost

5

Put a number on the problem

2

Decision and timing

5 to 10

Know who approves and when

3 to 4

Close

3

Agree a dated next step

1

That adds up to between 11 and 14 questions, inside the range Gong found works best.

Script 1: The opener

"Thanks for making time, I know mornings at the hotel are busy. I'd like to spend most of our 30 minutes understanding how you run things today and where it hurts. If it looks like we can help, I'll suggest a next step. If not, I'll tell you. Does that work?"

The last line matters. Telling a hotelier up front that you may say no lowers their guard and makes the rest of the call more honest.

Script 2: The current stack

"Can you walk me through the systems your team uses from booking to check-out?"

"Which of those are you happy with, and which ones does the team work around?"

"When is your contract with your current [PMS / channel manager / booking engine] up for renewal, and what notice does it need?"

The renewal date is the single most useful fact on the call. If the current contract runs well past your selling window, you are building a relationship, not a deal, and your forecast should say so. Gong's research also found that phrases like "Can you walk me through" and "Talk to me about" draw longer answers, which is what you want here.

Script 3: The problem

"Talk to me about the last week your team had a problem with [rate updates / overbookings / check-in queues]. What happened?"

"Who notices first when that goes wrong: the guest, the front desk or the revenue manager?"

"What have you already tried to fix it?"

"If you could fix one thing about how the hotel runs today, what would it be?"

Ask about a specific recent event, not a general opinion. "Last week" questions produce stories with details you can use in the demo. If the hotel cannot name a recent example, the problem may not be painful enough to act on.

Script 4: The cost

"Roughly how many hours a week does the team spend on that?"

"Has it cost you bookings, reviews or a guest complaint you can point to?"

You need a number the general manager can repeat to the owner. Hours, lost bookings and complaints are all fine. Do not invent the number for them: write down their estimate and use their words in the follow-up. Our guide to building a business case the hotel owner approves shows how to turn these answers into a one-page case.

Script 5: Decision process and timing

"Apart from you, who would need to be comfortable with a change like this? The owner, the management company, the brand?"

"What would each of them want to see before they said yes?"

"How was the last software purchase at the hotel decided, and how long did it take?"

"Is there a budget set for this year, or would this go into next year's budget?"

Hotel decisions often involve people who are never on the call. The owner signs, the management company sets standards, and the brand may have an approved vendor list. Our post on the hidden approvers in hotel software deals covers how to reach them. Budget questions matter too: a Canary Technologies survey of 404 hospitality IT decision-makers, reported by Hotel Dive in March 2026, found that nearly all hoteliers planned to increase IT budgets in the next year, but listed integration barriers, data and privacy issues, limited training bandwidth and a lack of technical expertise among the top challenges to adopting AI. Expect those concerns to come up in your call, AI product or not.

Script 6: The close

"Based on what you've told me, the two things worth looking at are [problem one] and [problem two]. I'd suggest a 45-minute session next Tuesday where I show you exactly how we handle those, with your front office manager on the call. Shall I send an invite?"

Name the problems back in their words, propose a specific date and ask who else should join. A vague "I'll send some information" is how deals drift into silence.

What the answers tell you

Answer

Signal

What to do

Contract ends within your sales cycle

Real window

Qualify in and plan the migration conversation

Contract runs well past your selling window

No near-term deal

Nurture, set a reminder before notice date

Specific recent problem with a cost

Real pain

Build the demo around it

Only general complaints

Weak pain

Ask one more "last week" question or disqualify

Owner or brand approval needed and unknown

Hidden approver risk

Ask for an introduction before the demo

No budget this year

Timing risk

Ask when the next budget is set and who sets it

Mistakes to avoid

  • Reading every question. Losing sellers in Gong's 2025 data asked more questions, not fewer. Pick the ones that fit this hotel.

  • Running full discovery with the owner. Gong found that asking too many discovery questions greatly harms calls with C-suite executives. Do detailed discovery with operators and bring insight to the owner.

  • Pitching in the middle. Hold the product until the problem is clear. See why hospitality SaaS demos fail when they start too early.

  • Not writing it down. If the answers are not in the CRM within the hour, the qualification did not happen.

Turning answers into the next stage

After the call, log the stack, contract dates, three to four problems, the cost estimate, approvers and timing in the CRM. Then build the demo around the problems you heard, using the hotel's own words. Our guide to a demo that survives operator scrutiny picks up from there, and the full sales motion sits inside our hotel tech GTM strategy.

The takeaway

Good hotel tech discovery is short, specific and written down. Ask 11 to 14 questions across the stack, the problem, its cost, the decision process and timing. Listen more than you talk, close on a dated next step and disqualify hotels that cannot buy this year.

If your discovery calls produce demos but not deals, a free revenue leak audit will show where qualification is leaking.

Frequently Asked Questions

How many questions should a hotel tech discovery call include?

Who should be on a hotel software discovery call?

What is the most important question to ask a hotel buyer?

When should you disqualify a hotel prospect?

Should you demo on the first call?

FREE DOWNLOAD

The Hotel Deal Kit: 7 templates for winning and keeping hotel deals

Discovery script, owner business case, pilot criteria, migration plan, RFP checklist, account plan and QBR. PDF and editable Word.

Get the free kit

Where is your revenue actually leaking?

Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.

Get the free leak audit

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.