MenuPilot Request pilot

Pilot confirmation

Confirm the two-week test.

Use this after the setup call so nobody is guessing about the section, source, order path, number to watch, or review date. It is a worksheet, not a substitute for the restaurant's normal contract or legal review.

Email details Read POS safety
Scope
One section
Live window
Two weeks
If it continues
$89/month/location
Boundary
Before checkout

Pilot scope

Fill this in before the first QR goes live.

This sheet keeps the pilot narrow enough to approve. Every blank should have a plain answer before guests see the QR entry.

Restaurant ________________________________________
Menu section Wine by the glass / cocktails / beer flights / brunch / other
Menu source Public QR link, menu page, PDF, photo, or export
Entry point Table card / host stand / menu insert / staff mention / website link
Live dates Start ____________ End ____________ Review ____________
Success signal Scans / finished recommendations / order-flow clicks / staff feedback

Responsibilities

Each side has one clear job.

MenuPilot provides

  • Guest-facing recommendation flow for the confirmed section.
  • Plain food and drink help before checkout.
  • QR or link entry guidance for the restaurant's preferred placement.
  • Weekly usage notes and a short end-of-pilot decision summary.

The restaurant provides

  • A current public menu source for the chosen section.
  • A staff owner who can confirm menu changes and safety notes.
  • A visible pilot entry point and a simple staff mention.
  • Feedback on whether the pilot helped guest decisions.

Data and operations

MenuPilot stays out of the systems that run the floor.

The first pilot is menu help before checkout. The restaurant keeps the systems that already handle orders, payments, tips, table routing, kitchen operations, availability, and allergy checks.

No payment or card data MenuPilot does not collect cardholder data or replace payment flow.
No POS write access The pilot does not create orders, route kitchen tickets, or change POS records. The POS safety packet gives the longer version.
No allergy-safety claims Guests must confirm ingredients, prep, and cross-contact risks with staff.

Decision date

End with continue, expand, or stop.

Hold the decision meeting after two live weeks. Weak pilots stop cleanly. Useful pilots continue at the FluteOS Companion price or expand to one more section.

Continue Keep the same section live at $89/month/location.
Expand Add one adjacent beverage or food section after the summary.
Stop Pause if usage, source quality, staff fit, or guest behavior is not strong enough.

Written confirmation

Approve the pilot by email or through your normal agreement tool.

Restaurant contact
MenuPilot contact
Date

Use this sheet as the approval brief. If either side needs formal terms, attach them before the pilot goes live.

Next step

Do not go live until the section, source, and number to watch are named.

A short written confirmation keeps the test useful, bounded, and easy to stop if guests do not use it.

Back to pilot kit See demo agenda Read POS safety