No card data
MenuPilot does not collect card numbers, payment tokens, receipts, tips, or checkout credentials.
POS safety packet
Guests choose first. Your POS still runs the order.
A guest scans a QR code or photographs a menu, gets one useful food-and-drink suggestion, then returns to Toast, Clover, staff, or the QR flow the restaurant already uses.
First pilot
Public menu, QR, PDF, photo, or export
No private Toast or Clover admin access is needed to start.
Operational line
Recommendation only
Orders, payments, tips, tables, and kitchen work stay with the restaurant's current systems.
Partner ask
Earn the first yes
Use one named restaurant pilot and one clear report before asking for deeper POS access.
The boundary
What MenuPilot will not touch in the first pilot.
No tickets
The app does not send items to the kitchen, change prep notes, route courses, or alter printer flow.
No table control
Seats, tabs, table numbers, service pacing, and staff assignments stay exactly where they are today.
No allergy promises
MenuPilot can flag questions. The restaurant still confirms ingredients, prep, and cross-contact risk.
Guest flow
How a table actually uses it.
The product only works if the guest understands it in the moment. No new staff script, no new checkout, and no hidden operational dependency.
- Open the menu source The guest scans a MenuPilot QR, opens a restaurant menu link, photographs a printed menu, or uses a menu section the restaurant shared.
- Say what they want tonight Safe choice, lighter food, a splurge, no alcohol, a pairing, or help with a wine or cocktail list.
- Get one plain order MenuPilot gives a food-and-drink suggestion plus a sentence the guest can say to staff.
- Return to the current flow The guest orders through Toast, Clover, the server, or the restaurant's existing QR page.
- Review the pilot report The restaurant sees starts, finished recommendations, order-flow clicks, drink-guide taps, guest feedback, and staff notes.
Toast and Clover
This should make Toast and Clover conversations calmer.
The first story is modest on purpose: guests need help deciding before they reach checkout. Toast, Clover, and the restaurant's staff remain the source of operational truth.
Phase 0: menu source
Use a public menu, QR page, PDF, photo, or restaurant export. No partner status required.
Phase 1: restaurant-approved access
Ask only for menu or location data when the restaurant has the right plan and permission.
Phase 2: attribution
Connect recommendations to order behavior only if the restaurant and POS partner approve it.
Phase 3: order creation
Leave this out until certification, support readiness, and mutual customer demand justify it.
Proof needed
What the first restaurant gives us.
A named use case
Which section causes hesitation: wine by the glass, cocktails, beer flights, brunch, or the page staff explains again and again.
A current menu source
A QR page, public menu link, PDF, printed menu photo, or restaurant export that can stay current during the pilot.
A clean summary
Two weeks of scans, recommendation starts, order-flow clicks, drink-guide taps, guest replies, and staff notes.
Forward this
A short note for a restaurant or POS contact.
Use this when someone asks the fair question: "Does this mess with our POS?" The answer is no. The first pilot stays before checkout.
Subject: MenuPilot POS-safe menu pilot
Hi [Name],
MenuPilot helps guests decide what to order before they enter the restaurant's checkout flow.
For the first pilot, it does not create orders, touch payments, change tips, route tables, send kitchen tickets, or require private Toast/Clover admin access.
The test is one menu section for two weeks. Guests get plain food-and-drink help, then order through Toast, Clover, staff, or the QR flow already in place.
If the pilot works, the next step is a report and a written restaurant request for more accurate menu access.
George
Next step
Start where guests already get stuck.
One menu section, one menu source, two live weeks, and no operational rewrite. That is enough to learn whether MenuPilot earns the next conversation.