Hotel technology

A software demo script for hoteliers: ten tasks to ask the vendor to perform live

Replace the vendor's prepared tour with a fixed script of ten tasks from your own week. Score each vendor on the same sheet to see what the software actually does.

  • 9 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

A software demo script for hoteliers: ten tasks to ask the vendor to perform live
Contents

Key takeaways

  1. A demo shows the vendor's best screens; a script shows what happens on your worst day, so make the vendor perform tasks from your own week.
  2. Send the ten tasks in writing before the session and keep the exact order and one awkward case back, so you see the system working rather than a rehearsal.
  3. Score every vendor on the same sheet with the same people, and write "not shown" instead of guessing.
  4. A task the vendor will not perform live is not a feature you have seen, and a promise made out loud belongs in the offer in writing.

A hotel software demo checklist is a fixed list of tasks taken from your own daily work that the vendor performs live while your team scores each one. It replaces the vendor's prepared tour with evidence: ten tasks, one sheet for every vendor, and a written list of what was not shown.

The screen share opens on a clean reservation: two nights, one room, one rate, one payment. Your own Tuesday has a tour group picking up eleven of its fifteen rooms, a company paying for two rooms, and a guest who wants the minibar from room 214 moved onto the bill for 312. After reading this, you will have a script, a scoring sheet and a follow-up email you can send to any vendor, this week.

Why does a scripted demo beat the vendor's own tour?

Because a tour is built to show the screens that work, and you are buying the days that do not. A script makes the vendor perform your work in your order, so every vendor is judged on the same evidence.

A prepared tour follows the product's happy path: one reservation, one rate, one payment, one report. A hotel's week rarely looks like that. The vendor knows its own demo by heart; the person who will use the system does not. The gap between those two people is what you are measuring.

A fixed script also makes two vendors comparable: same tasks, same order, same sheet, so the difference you see comes from the software, not from the presenter. Time each task. A check-in that takes the vendor four minutes with a mouse and no keyboard tells you what the same check-in feels like at 23:00 with a queue. Ask for one task to be done with the keyboard only, and watch whether the screen keeps up with the typing.

Listen for the sentence "that is better shown in a training session". It is information about the task, not about the training. For the questions to ask before you even book a session, see our guide to questions to ask hotel PMS vendors in Türkiye.

Key pointThe rule of the session

The vendor drives, your team scores, and nothing counts as done because someone said "we can do that". If it was not performed on screen, it goes in the notes as not shown.

What should you send the vendor beforehand, and what should you keep back?

Send the ten tasks and the shape of your operation at least three working days ahead; keep back the exact order and one awkward case, so you see the system working rather than a rehearsal.

Tell the vendor which tasks are must-pass and which are nice to have, so the hour cannot disappear into the easy half of the list. Ask for a demo property with data in it, not slides, and ask who will drive: the salesperson or someone who uses the system every day. Keep back the order of the tasks, one deliberately awkward case such as a guest who moves rooms mid-stay or a group that shrinks by four rooms, and the question about who can undo a change.

Ask for the session to be recorded, or record it with permission, so the colleague who was on the desk that afternoon sees exactly what the others saw. State the length in the invitation: ninety minutes, ten tasks, questions at the end. A demo with no end time becomes a feature tour.

ChecklistSend ahead, in one email

  • The ten tasks, one line each
  • Room types and rate structure in outline
  • How many outlets post charges to rooms
  • How many user types you need
  • The must-pass tasks marked
  • A request for a demo property with data
  • A request to record
  • The ninety-minute limit and the name of the person driving

To turn the same preparation into a document you can attach to a tender, use a requirements document that makes vendor offers comparable.

What are the ten tasks to ask the vendor to perform live?

Ten tasks drawn from a normal week: a group booking, a split bill, a room move, an outlet charge, the day close, a report, a new user, a rate change, a deliberate mistake and an oversell attempt.

Each task should take five to eight minutes. If one takes twenty, that is your answer for that task. Ask the vendor to narrate what the system is doing, not what it could do with configuration. When a task needs a workaround, ask the vendor to say the workaround out loud and write it down. Keep the same order for every vendor, so a slow start is visible in the same place each time. If a task fails, ask what the hotel would have to change in its own process to make it work, and note that too.

TaskWhat you ask the vendor to doWhat a good answer looks like
Group bookingBlock 15 rooms for 3 nights, take a rooming list, pick up 11, bill the group for rooms and guests for extrasBlock, pick-up and individual bills visible without re-entering data
Split a billTwo rooms under one company account, move one night's charge from room A to room B, show both billsThe move is recorded and both bills still balance
Move a guestMove a guest to another room on the second night, keeping the rate and the billOne stay, two rooms, no new reservation created
Outlet chargePost a restaurant charge to a room, void it, post it againThe void leaves a trace and the bill shows one charge
Day closeRun the day close and show what it locks and what it refuses to closeThe system names what is unresolved instead of closing over it
ReportProduce the in-house list and one weekly revenue report, then export bothThe numbers match the screen and the export opens
Add a userCreate a front desk user who cannot see rates or void a charge, then log in as that userThe restriction holds on screen, not only on a settings page
Change a rateChange one room type for a date range and show where the change appearsOld value, new value and the person who changed it are all visible
Make a mistakeDelete a reservation, undo a change, then find who did itNothing disappears silently; the record shows the change and the person
OversellTry to sell the last room twiceThe second sale is stopped and the system says why

Who from the hotel should sit in, and what does each person watch?

Three people at most: whoever owns the money, whoever runs the front desk, and whoever will administer the system. Each watches a different thing and each scores the same sheet.

The owner or general manager watches how the vendor answers: with a screen or with a promise, and whether the price covers what was actually shown. The front office manager watches keystrokes and screen changes, and asks the questions a receptionist asks with a guest standing in front of them. The person who will administer users, rates and reports watches the settings screens and asks how a change is undone.

Bring one receptionist who has not read the script. Their confusion is data, not a problem to be managed. Nobody scores a task they did not see, and nobody scores from memory two days later. Keep the salesperson from answering for the person driving; the driver's hesitation is the honest part of the session. For setting up those users and permissions after you buy, see our PMS user roles and permissions setup checklist.

TipHand over the mouse

For at least two of the ten tasks, ask the vendor to hand the mouse to whoever would use the system daily, and watch how much help is needed from the other side of the call.

How do you score two vendors on the same sheet?

One sheet, ten rows, a score of 0 to 2 per task and a written note of what you saw. The total matters less than the rows where the two vendors differ.

Score 0 for not shown or refused, 1 for shown with help or with a workaround, 2 for done in front of you without a caveat. Add a column for the time the task took and a column for who had to help. Score separately and immediately after each session, then compare. A discussion before scoring turns three opinions into one.

Mark the three tasks you cannot live without. A vendor that fails a must-pass fails, whatever the total says. Keep the notes factual: "the void left no trace on the bill" is worth more than "felt clunky". Add a column for the whole cost of the change, not the subscription alone: data migration, training hours and the weeks when two systems run side by side.

TaskScore (0-2)MinutesWho helpedNote
Group booking
Split a bill
Move a guest
Outlet charge
Day close
Report
Add a user
Change a rate
Make a mistake
Oversell
Must-pass result
Open questions

What should you send in writing after the demo?

A short list: every task that was not shown, every promise made out loud, and the questions the session raised, sent to the vendor the same week.

Ask for answers in writing with a date, so a spoken "yes, we do that" becomes something you can hold later. Ask what happens when the system is unavailable, and what the contract says about it. Ask who can undo a change, and whether the record of who did what can be edited afterwards. Ask what the vendor needs from you at cutover: which data, how many training hours, whose time and for how long.

Ask for a sandbox or trial for the two finalists, and run the same ten tasks in it without the vendor driving. Anything still unanswered goes into the contract as an open item, not into someone's memory. For the contract side of availability and response promises, see support and uptime terms in hotel software contracts.

Watch outNot shown is not done

A task the vendor will not perform live is not a feature you have seen. Record it as not shown, ask for it in the trial, and treat it as a risk you are choosing to carry.

What to do next

Write your ten tasks this week from last week's actual work, not from a feature list: the group that shrank, the bill that had to be split, the charge that went to the wrong room. Send the same list to two vendors, score both on one sheet, and let the rows where they differ decide the shortlist. The script is the cheapest part of the purchase and the part that shows you the software you will live with. Our hotel operating system is built and working, ahead of launch, and covers the areas your ten tasks come from: reservations, front desk, billing, restaurant sales, reports and compliance; read how we handle trust, records and undo before you trust any vendor's word for it.

Frequently asked questions

How long should a hotel software demo take?

Ninety minutes for ten tasks and questions, or two sessions of forty-five minutes if the list is long. A session with no end time drifts into a feature tour, and the tasks you cared about get the last ten minutes.

Should the vendor use our own hotel data in the demo?

Use a demo property with realistic data, or an anonymized export of your room types and rates. Do not hand over live guest data for a sales session, and do not accept screenshots in place of a working screen.

What if the vendor refuses one of the ten tasks?

Write it down as not shown, ask why, and ask for it in the trial instead. A refusal is information about the product or about the vendor's confidence in it, and it belongs in the score, not in the conversation afterwards.

Is a free trial better than a demo?

They answer different questions. The demo shortlists two or three vendors quickly on the same tasks; the trial tests the final two with your own people driving. Do both, in that order, and run the same ten tasks in each.

Can we record the demo?

Ask first, and record with permission. A recording lets the colleague who was not in the room see the same screen, and it settles later disagreements about what the vendor actually showed.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

We can brief you on this topic.

If this topic touches your work, we can walk you through what is built and what is designed.

Request a briefing