Hotel software is a long commitment bought in a short demo. The vendor controls the screen, the data is fake, and everything looks effortless. Then the contract starts, the real property loads in, and you discover what the demo never showed. The fix is not cynicism — it is a better set of questions, asked in a fixed order, scored the same way for every vendor.
In short
- Judge systems by how little re-keying they force, not by feature-list length.
- Count the total cost: per-module licences, integrations, training and the hours your team spends feeding it.
- Run every demo on your own numbers — your room count, your rate plans, your messiest week.
Start with the problem, not the demo
Before you look at a single product, write down the three things that cost you the most time or money today. For most independent hotels it is some mix of: numbers that do not match between systems, hours lost to manual work (night audit, reconciliation, reporting), and revenue leaking through no-shows, fake bookings or flat pricing. A demo is only useful if it is forced to answer your three problems. Otherwise it answers the vendor’s.
The 10-point checklist
- One data model or many? Ask where the restaurant charge lives, where the ledger lives, and how they meet. If the answer involves a nightly sync, you are buying a patchwork.
- How much re-keying survives? Follow one booking from OTA to folio to ledger in the demo. Count every place a human re-types a number.
- What happens at the edges? Ask to see a refund, a room move mid-stay, a group block and a split folio. Weak systems fall apart in exactly these places.
- Is the room status live? Housekeeping marking a room clean should be visible at the front desk in seconds, not after a refresh ritual.
- How does pricing work? A rate calendar is table stakes. Demand-based recommendations you can read and approve are the difference — see our revenue management guide.
- What does reporting cost you? Ask for last month’s occupancy, ADR and RevPAR during the demo. If producing them takes more than a minute, imagine month-end.
- Who does the setup? Hands-on onboarding with your data beats a documentation portal. Ask exactly who migrates reservations and history, and how long it takes.
- How is your data protected — and isolated? Multi-property or not, ask how tenant data is separated, who can access it, and what is logged.
- What is the exit? Ask how you get your data out — full export, standard formats — before you put it in.
- Can the team actually run it? The best system is the one your busiest front-desk shift uses correctly at 6 pm on a Friday.
Count the total cost, not the licence
The licence is rarely the biggest number. Per-module pricing multiplies: PMS plus channel manager plus POS plus accounting integration plus booking engine, each with its own invoice and support queue. Then add the quiet costs — training every new hire on four tools, the hours spent reconciling systems that disagree, the consultant who glues it together. A single-platform bill is easier to compare honestly against that full stack, not against one line of it.
Red flags that should end a demo early
- The vendor cannot show your scenario and offers a follow-up video instead.
- “Integration” is the answer to every hard question.
- No straight answer on data export, ownership or deletion.
- The AI story is a chatbot bolted to the side rather than work happening inside the workflow.
- Implementation is quoted in months for a property that should take days.
Making the call
Score every vendor against the same ten points, weight the three problems you wrote down at the start, and ignore the rest of the feature war. A system that solves your top three problems and forces no re-keying will beat a longer feature list every time. Then take the reference call — and ask that hotelier only one question: what do you still do by hand?