Choosing a system
Restaurant software demo: what to bring, what to test live, and red flags
Get real value from a 20 to 30 minute restaurant software demo: bring your menu and three hard orders, ask for 10 live tests, watch for red flags, score each vendor.
WaiterPilot Operations
Updated , 9 min read
The short answer
Bring your own menu, three hard orders from a real night and your busiest-hour numbers. Then ask the vendor to run live tests in front of you: a dish with choices, an allergy question, a sold-out dish, a split bill, a question in another language, several tables at once, and the staff screens. Score each vendor on the same sheet.
Key points
- A demo on the vendor's own sample menu shows the screens; a demo on your menu and your hard orders shows whether the tool fits your restaurant.
- Ask the vendor to run each test live, not to describe it, and write down who makes the decision at each step, especially for allergies.
- Red flags include no staff screens shown, no published price, a long term, and promises of 30% bigger checks; the peer-reviewed effect of tabletop ordering was about 1% per check.
- Ask every vendor what happens when the internet or a phone fails, and get the answer in writing, because published answers differ.
- You can try a sample order yourself before any demo, so the call is spent on your hard cases instead of a tour.
On this page
To get real value from a restaurant software demo, bring your own menu, three hard orders from a real night and your busiest-hour numbers. Then ask the vendor to run live tests in front of you: a dish with choices, an allergy question, a sold-out dish, a split bill, a question in another language, several tables at once and every staff screen. Write down what you saw on one scorecard per vendor, so you compare what happened, not what was promised.
This guide is the product side of the decision. For the paperwork side, the term, renewal, exit fees and data, see 12 contract questions to ask before you sign; we don’t repeat them here.
What should you get out of a 20 to 30 minute demo?
Short answer: proof that the tool handles your hardest moments, a look at every screen your staff will use, and the full price in writing.
A typical vendor demo is a tour: the nicest screens, a sample menu, a smooth order. That tells you the product exists. It doesn’t tell you what happens when table 7 orders a steak medium-rare with no sauce, asks whether the fries share a fryer with the shrimp, and wants to split the bill four ways. Those are the moments that decide whether your servers love or hate the tool.
So set the agenda yourself. Send it ahead, and spend the time on three things:
- Your hard cases, run live. On your menu if the vendor can load it, or on theirs if not.
- The staff side. Every screen a server, cook or manager will touch.
- The numbers. Price, fees and what isn’t included, in writing after the call.
What should you prepare before the demo?
Short answer: your menu, three hard real orders, your busiest-hour numbers and a list of the languages your guests speak.
- Your menu, as a PDF or photos, sent a few days before. Ask whether they can load it for the demo.
- Three hard orders from a real night. Pick ones that caused trouble: a dish with several required choices and a change (“no onions, sauce on the side”), an allergy question, a big table that orders in rounds.
- Your busiest hour. How many tables are seated, how many servers are on the floor, roughly how many orders and how many check requests. You’ll use these to judge the rush test.
- Your guests’ languages. Which ones you hear at the table, so you can ask for a test in one of them.
- What you already run. Your till, card terminal and kitchen printer or screen, so the vendor can’t skip the question of how orders get into them.
- One server and one cook, if they can join. They will spot problems you won’t.
Diners notice these moments too. In the National Restaurant Association’s 2024 survey, full-service diners most wanted technology to make paying easier and faster (30%) and ordering easier and faster (28%), followed by food details such as allergens (21%) (NRA, 2024).
Which live tests should you ask the vendor to run?
Short answer: these ten, run in front of you, with the guest view and the staff view on screen at the same time.
Ask for both views side by side. For each test, write down what the guest saw, what staff saw, and who made the decision.
- A dish with required choices and a change. Can the guest confirm without picking the side? Where does “no onions” appear for the cook, and in what language?
- An allergy question. Ask “does this contain nuts?” Who answers: the software, the menu, or a person? Is staff alerted, or does the guest have to ask? The answer you want is that staff have the final word.
- A question the menu doesn’t answer. Does the tool guess, or send the guest to a person?
- A sold-out dish. Mark a dish sold out mid-service. How fast does it disappear for guests, and who can do it? Then mark a dish already in the kitchen out of stock: does it come off the bill?
- A correction. The guest ordered the wrong thing. Can they cancel? Can staff reject or change it? Toast’s own FAQ, for example, says “guests cannot edit a Toast Mobile Order & Pay® order after they submit it” (Toast, updated 17 Sep 2026). Find out the equivalent for every tool.
- A split bill. Four guests, one pays for two. What does each phone or the check show? Where does payment happen, and who pays the processing fee?
- A question in another language. Type one in Spanish, Arabic or a language your guests use. Does it answer in that language? What does the kitchen ticket show?
- A rush. Ask the vendor to open several tables at once and send orders from each. Watch the staff board. How do you tell what has waited too long?
- What staff see. Ask to see the kitchen screen or ticket, the floor screen for calls and checks, and the manager view. Does the kitchen see prices? Do alerts reach a phone in a pocket?
- When something fails. Ask what happens if the internet drops, a staff phone dies, or a guest’s phone loses signal. Published answers differ: Toast’s FAQ says that during an internet outage “order and payment processing through Toast Mobile Order & Pay® is not supported” and servers should take orders directly. Square’s handheld page says offline payments can keep running “for up to 24 hours” (Square Handheld). Ask for the vendor’s answer in writing.
What are the red flags?
Short answer: anything the vendor won’t show, won’t price or won’t put in writing.
- Won’t show the staff screens. Your staff spend more time on them than guests spend on theirs.
- Won’t run your menu or your hard orders, even a few dishes.
- No published price, or a price that only appears after a second call.
- A long term or automatic renewal pushed in the demo. Read the contract questions linked above before you agree to anything.
- “It increases checks 30%.” The peer-reviewed study of tabletop ordering at a US casual chain found about 1% more per check and about 10% shorter meals (Restaurant Technology News, 2019, reporting Tan and Netessine in Management Science). A vendor that promises far more should show its method.
- “It handles all languages” or “it never makes mistakes.” Ask which languages were tested and what happens when it gets one wrong.
- “We integrate with everything.” Ask for the named POS, the setup steps and who supports it.
How do you score each vendor?
Short answer: the same ten tests, scored 0 to 2, plus price and terms, on one sheet per vendor.
Score 2 if the vendor ran the test live and it worked, 1 if it was described or partly shown, and 0 if it failed or was skipped. Copy this table for each vendor:
| Test | What good looks like | Score (0 to 2) | Notes |
|---|---|---|---|
| Required choices and a change | Can’t confirm without the choice; note readable in the kitchen | ||
| Allergy question | Staff make the final call; the guest is told so | ||
| Question not on the menu | Sends the guest to a person, doesn’t guess | ||
| Sold-out dish | Gone for guests right away; comes off the bill | ||
| Correction | Guest or staff can fix it before the kitchen starts | ||
| Split bill | Each guest sees their share; payment path is clear | ||
| Another language | Answers in the guest’s language; ticket readable by staff | ||
| Rush of tables | Waiting orders stand out; nothing lost | ||
| Staff screens | Shown live: kitchen, floor, manager | ||
| Failure plan | Answer given, in writing | ||
| Price and terms | Full price, fees and term in writing |
A tool that scores well here earns a trial, not a signature. To judge a trial on real nights, use our 30-day trial plan and scorecard. For the wider product questions, see the restaurant QR buyer’s checklist.
How does WaiterPilot’s demo answer each test?
Short answer: here is what WaiterPilot does on each test, from our published product facts; where we haven’t published something, we say so.
Ask us to run each one in the demo. This is what to look for:
| Test | WaiterPilot |
|---|---|
| Required choices and a change | Required choices (size, side, flavor) must be picked before an order can be confirmed. Special requests go on the ticket as a short note; notes are not translated for staff. |
| Allergy question | WaiterPilot gives what the menu says and asks the guest to confirm with staff; staff always have the final word. Staff are not alerted automatically. |
| Question not on the menu | Answers come from your menu; when the menu doesn’t say, WaiterPilot tells the guest to ask a staff member. |
| Sold-out dish | Mark a dish sold out from your phone (owner or manager PIN) and WaiterPilot stops offering it right away. A dish already in the kitchen can be marked out of stock; it comes off the bill and the guest sees a note. |
| Correction | A guest can cancel an order while it is still awaiting staff. The first order at each table waits for staff to confirm, and staff can reject one that looks wrong. |
| Split bill | The bill stays live on every phone at the table, with tax and any service charge or gratuity you set. Guests split it evenly or see just their share. Payment happens with staff; WaiterPilot takes no payments. |
| Another language | Guests chat in their own language; tested in English, Arabic (several dialects) and Spanish. In our 15 Oct 2026 test, a Spanish question was answered in Spanish with dish names as written on the menu. Guest buttons are English or Arabic. |
| Rush of tables | Waiting orders and calls change color at 1, 5 and 10 minutes. Our published timing covers 4 test orders at one table on 15 Oct 2026 (0.8 to 2.7 seconds from guest Confirm to the staff board), so it says nothing about a full room. Ask us to send orders from several tables in the demo. |
| Staff screens | Staff use their own phones or tablets: a main board with every ticket, a kitchen screen with dishes, choices and notes but no prices, and a floor screen for calls and check requests answered with Ack. On iPhone, lock-screen alerts need the board added to the Home Screen. |
| Failure plan | Ask us in the demo and get the answer in writing, as you would from any vendor. |
| Price and terms | $200 per location per month after 30 days free, or $2,000 per location per year; 0% commission; no contract; free setup, training and QR cards. |
Some things we haven’t published yet. As of 15 Oct 2026 WaiterPilot has not published a data retention period, a data export or deletion process, a data processing agreement, security certifications, a support response time, or customer references. If you need any of these, ask in the demo and ask for the answer in writing. And if you want to see what happens when the AI misreads a guest, what happens when the AI waiter gets it wrong walks through every check.
You can do part of this before we ever talk. Our sample order page lets you order at an example restaurant as a guest, then confirm the ticket and mark it served as staff. Nothing is sent to a restaurant, and it frees the demo for your hard cases. How it works shows the staff screens in more detail.
When is WaiterPilot not the right pick?
Short answer: when you need orders in your POS automatically, or payment on the guest’s phone.
WaiterPilot has no POS or kitchen-printer connection, so staff ring orders into your till by hand if you use one. It takes no payments. If either of those is a must, a POS-based ordering tool or a pay-at-table product will score better on your sheet, and our comparisons show where.
What to do next
Send every vendor on your list the same agenda: your menu, three hard orders, your busiest-hour numbers and the ten tests. Score each one on the same sheet, then trial the best one on real nights. WaiterPilot’s full offer is on the pricing page.
- Book a demo and bring this list: ask us to run each test in front of you.
- Or start 30 days free and test it on your own floor.
Questions readers ask
What should I ask in a restaurant software demo?
Ask the vendor to run your hard cases live: a dish with required choices, an allergy question, a sold-out dish, a split bill, a question in another language and several tables ordering at once. Ask to see every staff screen, the full price in writing, the contract term, and what happens when the internet or a phone fails.
How long is a restaurant POS demo?
Plan for 20 to 30 minutes and ask for that much time on your own cases. Send your menu and three hard orders beforehand, so the vendor can load them and the call isn't spent on a general tour. If a test needs longer, book a second session or a trial.
Is a free trial better than a demo for restaurant software?
You need both. A demo shows whether the tool can handle your hard cases and what the terms are; a trial shows whether your staff and guests use it on busy nights. Use the demo to decide whether a trial is worth running, then judge the trial against written goals.
What are red flags in a software demo?
A vendor that won't show the staff or kitchen screens, won't run your menu, has no published price, pushes a long contract, or promises check increases of 20 to 30%. Peer-reviewed research on tabletop ordering found about 1% more per check, with the gain mostly in shorter meals.
Should my staff attend the restaurant software demo?
Yes, bring one server and one cook if you can. The server will spot what slows down the floor, and the cook will tell you within a minute whether the kitchen screen or ticket is readable. They are also the people who will use it every night.
Can I try WaiterPilot before booking a demo?
Yes. The sample order page lets you order at an example restaurant as a guest, then confirm the ticket and mark it served as staff. Nothing is sent to a restaurant. Then book a demo to run the tests in this guide with us.
Sources
- Research: Tabletop technology improves sales 1% per check, reducing meal duration 10%, Restaurant Technology News, 2019-07 (checked 2026-11-14)
- Toast Mobile Order & Pay FAQs, Toast, 2026-09-17 (checked 2026-11-14)
- Square Handheld, Square, 2026 (checked 2026-11-14)
- Restaurant Technology Landscape Report 2024, National Restaurant Association, 2024 (checked 2026-10-15)