Core diner flow
The app and site already show the core flow: photo or QR menu input, one order suggestion, drink help, and reminders to confirm safety details with staff.
Pilot evidence
Earn trust with one small test.
MenuPilot is not asking restaurants to replace Toast, Clover, payments, tips, tables, or kitchen flow. The first test is one section, two live weeks, a written confirmation, and a report that shows whether guests used the help.
Status
Before the first pilot
We do not have public pilot results yet. The next useful proof is one named restaurant and a short summary.
Best audience
Owners, GMs, beverage leads
Especially Toast or Clover restaurants with wine, cocktail, beer, brunch, or long QR menus.
Boundary
Before checkout
Recommendations first. Existing order, payment, table, tip, and kitchen systems stay in charge.
Ready now
What we can show before the first pilot.
Setup guide
The setup call and confirmation sheet name the section, source, entry point, live dates, number to watch, responsibilities, and boundaries before launch.
End-of-pilot report
The report turns usage into a continue, expand, pause, or stop decision without promising extra drink sales.
Toast/Clover-friendly beginning
The first partner angle is menu reading and helping guests choose, not order creation, payment handling, or private admin access.
Pilot sequence
Turn one interested restaurant into a live test.
Each stage should leave a clearer record. Stop early if the menu source cannot stay current or the setup creates confusion.
- Choose one section Wine by the glass, cocktails, beer flights, brunch, or the menu area staff explains again and again.
- Confirm the source Public QR link, menu page, PDF, photo, or restaurant-provided export. No private admin access.
- Place the entry point Table card, menu insert, host stand, website link, or staff mention.
- Watch what guests do next Starts, finished recommendations, drink-guide taps, Toast/Clover order-flow clicks, feedback, and staff notes.
- Ask for partner support Only after the restaurant wants to continue or expand and approves a quote we can share.
Partner path
Start with menu help, not order creation.
This is the safer Toast/Clover story: restaurants get help before checkout, the POS keeps operational control, and partner access starts with menu accuracy instead of order writes.
Ask for read-only first
The first phases can use public menu sources or restaurant-approved menu and location access.
Keep card data out of scope
No cardholder data, payment tokens, tip adjustment, payroll, or kitchen routing changes. The POS safety packet is the public version of this boundary.
Handle support ourselves
MenuPilot owns setup, menu processing, recommendation quality, pilot reporting, and support notes.
How to use this page
Lead with what each person cares about.
Owner or GM
Start with the low-risk pilot: one section, two weeks, existing POS flow, and a written decision report.
Beverage director
Lead with the guest hesitation: plain pairing help that makes dense lists easier to choose from.
POS or hospitality partner
Lead with the sequence: menu reading first, attribution later, order creation only after certification and customer pull.
Next step
The next proof is one restaurant testing one section.
Use this page after outreach, before the setup call, and again when asking Toast or Clover for mutual-customer support.