Current source
QR page, public menu link, PDF, photo, or export. We need the source guests actually see.
Restaurant demo call
Use 20 minutes to choose the first section.
The first call should not feel like a systems project. Bring the menu guests already see, name where they hesitate, and leave with a small pilot you can approve or decline.
Time
20 minutes
Enough to see the guest flow and decide whether a pilot is worth the next step.
Bring
One menu source
A QR page, public menu link, PDF, printed menu photo, or restaurant export is enough.
Leave with
Section, source, next step
If the fit is real, we send a written pilot confirmation sheet.
Call agenda
What happens on the call.
This is a working call, not a pitch deck. The point is to decide whether one menu section is worth two live weeks.
- Minutes 0-3: name the hesitation Which part of the menu makes guests pause, ask staff to translate, or order the safe default?
- Minutes 3-8: show the guest flow Scan, photograph, or open the menu source, then show the plain food-and-drink order script.
- Minutes 8-14: choose the first section Pick wine by the glass, cocktails, beer flights, brunch, or the page that staff explains most.
- Minutes 14-18: choose the proof Use scans, finished recommendations, order-flow clicks, drink questions, guest replies, or staff notes.
- Minutes 18-20: decide the next step Stop, send the menu source for review, or approve a two-week pilot confirmation sheet.
What to bring
No prep deck. Just the real menu.
Current order path
Toast, Clover, staff-led ordering, or another QR flow. MenuPilot should hand back to what already works.
One stuck section
Name the section where guests hesitate or staff repeats the same explanations.
One staff contact
Someone who can confirm menu changes, availability notes, and the review date.
What we decide
The call should end with a plain answer.
Not a fit
The menu changes too often, the first section is not clear, or the restaurant needs direct order creation before seeing value.
Review the menu
The section looks promising, but we need to check the source and send back a tighter recommendation.
Confirm the pilot
The section, source, staff owner, entry point, number to watch, and review date are clear enough for a written confirmation.
Boundaries
We will not ask for private POS access on the demo call.
The first call is about menu help before checkout. Restaurants keep their order, payment, tip, table, and kitchen systems in place.
No payment details
Do not send card data, receipts, or tip records.
No admin credentials
A public menu source is enough for the first review.
No allergy guarantees
Guests still confirm ingredients, prep, and cross-contact risks with staff.
Send this
A short note for an owner, GM, or beverage lead.
Use this when someone is interested but wants to know whether the first call is worth the time.
Subject: 20-minute MenuPilot demo for [Restaurant]
Hi [Name],
I think MenuPilot may be useful for [Restaurant] because guests have to choose from [wine/cocktails/beer/brunch/section] before they know what fits.
The first call is simple: we look at your current menu source, show the guest flow, pick one section, and decide whether a two-week pilot is worth trying.
No private POS access, payment changes, table routing, or kitchen changes on the call.
Worth 20 minutes this week?
George
Request the demo
Send the menu source and the section guests ask about.
The best first call starts with the real menu. If you are not sure which section to test, send the source and the current ordering setup.
Best first section
Wine by the glass, cocktails, beer flights, brunch, or anything staff explains repeatedly.
Good source
A Toast or Clover QR page, public menu link, PDF, photo, or current menu export.
Clear ending
The call ends with stop, menu review, or pilot confirmation.