Limited Kitchen Pilot Program

Help shape the AI ordering system built for independent restaurants.

Run FoodOrders.ai in your real restaurant for 90 days with guided setup, direct support, the Kitchen screen and eligible printer integration. Start with the equipment you already own, keep your existing fallback during validation, and receive founding-participant benefits if you continue.

Places are limited and awarded by application. Open to eligible restaurants anywhere in the United States and Canada. Application and readiness review required. No long-term commitment.

Why now

The ordering problems independents actually have

Calls ring out during the rush

Phones go unanswered exactly when orders are worth the most, and nobody knows how many were lost.

Handwritten tickets get misread

Modifiers, allergy notes and substitutions live on paper and in memory, and the kitchen pays for it.

Online orders arrive in three places

A tablet here, an email there, a phone in a pocket — with no single acknowledged queue.

Nothing tells you what actually failed

When an order goes wrong there is no record of when it arrived, who saw it, or whether it printed.

Two ways to run it

Start with the equipment you already own

Screen-only is a complete pilot path. Printing is added only where a specific model and connection has been assessed and tested.

Screen-only

Run the pilot entirely from the Kitchen screen on a tablet, laptop or desktop you already have. No printer, no agent install, no new hardware.

  • Orders appear, alert and are acknowledged on screen
  • Works on Windows, macOS, Linux, iOS, iPadOS, Android and ChromeOS browsers
  • Suitable for many takeout, café and catering operations

Printer-assisted

Add the FoodOrders Windows Agent on an existing Windows computer and print to a compatible printer already installed in Windows.

  • Requires a Windows computer that stays powered on
  • Compatibility is assessed and tested per model — never assumed
  • The Kitchen screen stays live as the fallback when printing fails

Unsure about your printer? Check the compatibility list.

Scope

What the pilot includes — and what it does not

Included

  • FoodOrders web ordering and conversational ordering, where enabled
  • Configured AI telephone ordering, where enabled and production-ready
  • The tenant Orders workspace
  • The FoodOrders Kitchen screen
  • Browser notifications and kitchen alerts that are production-ready
  • The FoodOrders Windows Agent for approved pilot locations
  • One validated Windows printer, or an approved network-printer path
  • Guided menu, hours, modifier, tax and fulfillment setup
  • Direct founder and pilot support
  • Structured testing, weekly check-ins and feedback

Not included

  • A promise to replace every POS function
  • A cash drawer, payroll, accounting, inventory or card-terminal replacement
  • A generally available Square, Toast, Clover, Lightspeed, Deliverect or Otter integration — those are planned
  • Compatibility with every kitchen printer
  • Unlimited AI telephone usage
  • New restaurant hardware at no cost
  • Guaranteed uninterrupted service
  • Permission to remove your existing fallback during controlled validation

90 days

How the pilot runs

Nothing is switched on all at once. Each stage has to earn the next one.

  1. Days 1–14

    Configuration and simulation

    Complete onboarding, run scripted tests, correct menu and workflow defects, establish your baseline. You do not rely on FoodOrders yet.

  2. Days 15–45

    Limited live operation

    Enable a limited set of channels, hours or volume. Your existing fallback stays in place. Weekly check-ins, fast incident review.

  3. Days 46–75

    Representative operation

    Real rush periods, more staff involved, deliberate recovery testing. We measure value and support burden together.

  4. Days 76–90

    Evaluation and decision

    We present results and unresolved risks. You choose a subscription, a bounded extension, or a clean exit. Exact terms in writing.

Fit

Apply if this sounds like you

Apply now if…

  • You miss calls or lose orders during your busiest hours
  • Handwritten tickets or shouted modifiers cause kitchen mistakes
  • You handle pickup, takeout, delivery, catering or future orders
  • You can keep a phone, tablet, laptop or desktop available in the kitchen
  • An owner or manager will personally take part
  • You can keep your existing process running as a fallback during rollout
  • You would consider continuing as a paying customer if the pilot works

Wait for general release if…

  • You need a certified POS integration in place before you begin
  • You need guaranteed compatibility with hardware nobody has tested
  • You cannot maintain a fallback process during validation
  • There is no responsible owner or manager contact for the location
  • You expect FoodOrders to replace accounting, payroll, inventory or payment-terminal management immediately
  • A pilot failure could not be safely handled manually at your location

Commitments

Who does what

Your restaurant

  • Nominate an owner or manager who takes part throughout
  • Attend kickoff and a 15–20 minute weekly review
  • Keep your existing fallback process available during controlled rollout
  • Run the scripted simulated orders before going live
  • Report incidents promptly with enough detail to reproduce them
  • Approve your menu snapshot before live orders
  • Complete the day-75 evaluation and give an explicit decision

FoodOrders

  • Guided setup of menu, hours, modifiers, taxes and fulfillment rules
  • Kitchen screen, notification and audio configuration and testing
  • Printer assessment, agent pairing and documented test evidence where applicable
  • Named support contact with agreed channels and hours
  • Weekly review of your check-ins and incidents
  • A written day-75 evaluation with measured results, not opinions
  • A clean exit: export, agent unpair, uninstall guidance, retention and deletion

Safety

Your service keeps running

A pilot must never put a shift at risk.

  • Your existing fallback stays available for the whole controlled rollout — we will not ask you to remove it.
  • Live channels are enabled gradually, not on day one.
  • If the Kitchen screen or a printer fails, staff fall back to the documented manual process and we log the incident.
  • Compatibility is never claimed because an install succeeded — only because a real ticket printed and was verified.
  • You can leave the pilot. Exit revokes paired agents, stops any scheduled billing and gives you your export.

Trial vs pilot

This is not the 14-day trial

The public 14-day trial stays available. The Kitchen Pilot Program is a different, application-based commitment.

14-day trialKitchen Pilot Program
Open signupApplication and approval
14 days90 days
Standard evaluationReal operational deployment
No formal feedback commitmentScheduled feedback and evaluation
Standard public termsPilot participation agreement
No guaranteed founding incentiveDefined conversion incentive

The 14-day trial stays available and is separate from the pilot. The two are not automatically stacked; FoodOrders.ai can approve exceptions individually.

Pilot terms

Pilot fee: USD $199 per location, plus applicable taxes

For 90 days. If you start an annual subscription within 30 days of completing the pilot, the pilot fee is credited once against your first annual invoice, onboarding is waived and you receive 25% off the first 12 months. The credit is not available on monthly billing.

Kitchen Pilot Program terms — subject to written acceptance. Final pricing, currency, taxes and inclusions are confirmed in writing before any acceptance or payment. Nothing is charged when you apply, and the pilot never converts to a subscription on its own. Read the draft participation terms.

Support

What support looks like during the pilot

Pilot support runs Monday–Friday, 9:00 a.m.–6:00 p.m. Eastern Time, at pilot@foodorders.ai. These are response targets, not resolution guarantees.

  • Ordering or printing unavailable during an active service period: Initial response within 1 hour during support hours
  • Significant but non-blocking issue: Response within 4 business hours
  • General questions and cosmetic issues: Response within 1 business day

During service, the required fallback is always the Kitchen/Orders screen together with your existing manual process.

Questions

Kitchen Pilot FAQ

Put your restaurant forward

About 10 minutes. Tell us how you operate today and what equipment you already have — we will be straight with you about fit.

Security, Privacy & Responsible AI

Our application is built using Lovable, a platform that maintains SOC 2 Type II compliance and ISO 27001:2022 certification. We combine this security-focused infrastructure with privacy-conscious data practices, GDPR-supporting safeguards, and responsible AI governance informed by ISO/IEC 42001 principles.

Platform certifications apply to Lovable and its defined systems and controls. They do not constitute independent SOC 2 or ISO certification of our company or this application. Compliance responsibilities are shared across our platform providers, application controls, connected services and internal operating practices.

  • SOC 2 Type II

    Built using a platform subject to independent security-control assessment.

  • ISO 27001:2022

    Supported by an information-security management framework certified at the platform level.

  • GDPR

    Designed with privacy, transparency, data minimization and user rights in mind.

  • Responsible AI

    AI practices informed by ISO/IEC 42001 principles for accountable AI management.