Every hotel software demo goes well. The demo is a controlled environment with clean data, one property, one currency, no OTA mappings and nobody standing at the desk waiting. The questions below are designed to find out what happens outside it.
Quick answer (for the impatient)
Ask about exit before entry. How you get your data out is the most revealing question available.
Ask what it can't do. A vendor with no honest answer is a vendor you'll discover the gaps from later.
Ask for a trial with your own data, not a demo with theirs.
On your data
Can I export all my data, in a usable format, whenever I want? Ask now, while you have leverage.
Who owns the data? It should be you, unambiguously, in writing.
How is my data separated from other properties on the platform? See what to listen for in the answer.
Are guest identity documents stored encrypted? A hotel holds passports and IDs; this is a fair question.
What's the backup and recovery position, and has it been tested? Untested backups are a common and expensive discovery.
On money and billing
Does it handle GST slabs that vary by what the room actually sold for? A single hardcoded rate is a real limitation — see why.
Can it produce a compliant tax invoice, including correct HSN/SAC?
Does it support e-invoicing if I'm in scope, or will I be in scope soon? See applicability.
Can F&B charges post to the guest folio? If you have a restaurant, this decides whether you lose revenue to chits.
Does it post to real double-entry accounting, or export a file someone re-enters?
Can one stay ever produce two invoices? Ask directly; see why it matters.
On distribution and rates
Which channels can I actually connect, on my plan? "Integrates with all major OTAs" is a marketing sentence, not an answer.
How are channel rooms mapped to my rooms, and what happens when I add a room type?
Can I set rates by date and by plan? See rate plans and calendars.
Is there a booking engine for my own website, and what does it cost per booking? Some are free; some carry a per-booking fee that recreates the commission you were escaping.
On the parts vendors don't volunteer
What does this software not do well? The single most informative question on this list. An honest gap is worth more than a feature list.
What's your support model, and what are the hours? A hotel runs at 2am; ask what happens then.
What's the total first-year cost — licence, setup, training, migration, per-booking fees, payment processing, and any per-user charges?
Can I speak to a property of my size and type using this today? Not a testimonial — an actual conversation.
What's the notice period, and what happens to my data at the end?
What to do with the answers
Ask every vendor the same questions and write the answers down side by side. Two things emerge that never emerge from demos: which vendors answer directly versus deflect, and where the real cost differences sit — which is usually in setup, per-booking fees and payment processing rather than the headline subscription.
Then run a trial on your own data, with your own rate structure and at least one channel connected. Software that handles your actual rate complexity is a different question from software that handles a demo property's.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind Twenty Questions to Ask Before You Sign a Hotel Software Contract does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Ask about exit before entry. How you get your data out is the most revealing question available. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: Ask what it can't do. A vendor with no honest answer is a vendor you'll discover the gaps from later. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: Ask for a trial with your own data , not a demo with theirs. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Is the cheapest option ever right?
Sometimes, for a small property with simple needs. Just compute total first-year cost, not monthly subscription.
How long should evaluation take?
Long enough to trial two shortlisted options properly. Rushing this costs far more than the weeks saved.
Should I pick software with features I don't need yet?
Only if the growth is genuinely planned. Paying today for a maybe is how hotels end up on expensive systems they use a fifth of.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
Demos are designed to impress and every vendor's does. These questions are designed to surface what the demo omits — starting with how you'd leave.
See how migration actually works, what PMS versus business OS means, or pricing.
Ask the hard questions first. Start free →
Comments