MESAby BUZO

Order from the table. The kitchen sees it.

MESA is a BUZO product in development for receiving orders and coordinating service in local businesses. It starts with restaurants: guests can order without downloading an app, and the team sees each order on its screen.

Version 1 is in development. The product runs on a server with persistent data, but no authorized business is operating on it and no real payments have been verified.

Open MESA for guests

Opens in a new tab. No restaurant is operating on it yet.

Order from the phone and run the kitchen from the tablet: what one side does shows up on the other.Open full screen

Table 3

To start

  • Molcajete guacamoleAvocado, onion, cilantro, serrano and lime, with corn chips.$165
  • Fire-roasted esquitesCharred corn, mayonnaise, cotija cheese and piquín chili.$95
  • Nº 3 Grilled octopusCharred octopus, chipotle mayo and cucumber on blue corn.$185

From the fire

  • Wood-fire burger180 g beef over oak, Chihuahua cheese, butter bun and hand-cut fries.$189
  • Half chicken over charcoalMarinated and charcoal-grilled, with tortillas, green salsa and your side.$225

Dessert

  • Cajeta flanHouse flan with warm cajeta.$95

To drink

  • Hibiscus waterHibiscus infusion, lightly sweet.$55
  • Craft beer355 ml from a local brewery, lager or dark.$65
  • Mezcal espadínIn a veladora glass, with orange and worm salt.$95
  • AmericanoOaxacan coffee, medium roast.$45
Kitchen

Grill

—

Cold

—

Bar

—

No orders. Send one from the phone.

LÁMINA is MESA's test restaurant. No order leaves this page and nothing is charged.

At the table

A link on the table opens the menu, nothing to download. The table orders together.

LÁMINA is the test restaurant: its orders and payments aren't real. These are MESA's own screens, unedited.

Menu
MenuDiet filter, availability and photos, per table.
A dish
A dishEach option recalculates price, diet and allergens.
The table's order
The table's orderOne shared order, reviewed before it's sent.
Sent
SentIt only says “received” once the server has confirmed it.

Behind the counter

Team mode is tablet-first, with a screen for each role.

Today
TodayWhat needs attention first.
Orders
OrdersTickets by station.
Floor
FloorEvery table and its state.
Availability
AvailabilityA dish shows as sold out as soon as the kitchen says so.
Stock
StockTheoretical use by recipe, with counts entered by hand.

One system, three ways of serving

Between a restaurant and a pharmacy, what changes is how work reaches the team. So sign-up asks what you sell and how you serve.

  • At the table

    Restaurants, cafés, taquerias

    A QR per table, rounds, a waiter and split bills.

  • At the counter

    Cafés, bakeries, pizzerias, ice cream shops

    Every scan is an order with its own code. The team sees what's being made and what's ready.

  • For pickup

    Pharmacies, hardware stores, grocers, stationers

    The customer orders and the team checks off each product before handing it over.

The three service flows are implemented. Restaurant testing is pending an authorized business.

Where MESA is today

What already works, what's halfway, and what doesn't exist yet.

  • Already works

  • Guest web app and iOS app, on a local server
  • Team mode: kitchen, waiters, floor, availability
  • Shared server on Cloudflare, where orders, photos and accounts persist
  • Sign-up by trade: at the table, at the counter or for pickup
  • Options per product (a filling, paid extras) that the server validates and prices
  • Bills split in equal parts, by dish or by amount, with a tip the guest chooses
  • Cash-up with cash and the business's own terminal, recorded by staff
  • Use by recipe, deliveries and counts entered by hand
  • Orders waiting for a connection say so, and send themselves when it's back
  • Personal accounts with a password or a passkey; the owner opens the business from their account
  • Adding a dish in one tap and saying how many of you without typing
  • Paying only for what you ordered, without splitting the whole table first
  • Menu, booking and waitlist links for Google and Apple Maps
  • Halfway

  • App Clip: built, not yet opened from a real address
  • Visit card in Wallet: tested only with a test certificate
  • NFC table tags: written and checked from Chrome on Android, not yet tested with a physical tag
  • Working on a bad connection, beyond the web order queue
  • Card and SPEI payments through Stripe Connect: connected to BUZO's account, but no restaurant has finished signing up with Stripe
  • CFDI invoices through an authorized provider: built and tested against simulated responses, with no provider account yet
  • Bringing a menu from a spreadsheet, Loyverse or Fudo: tested against simulated responses, not with a real business
  • Sign-in codes by email, WhatsApp or SMS, and Google, Apple, Facebook or Microsoft: each one waits for its provider account
  • Doesn't exist yet

  • Real payments, including Apple Pay
  • A point-of-sale integration tested with a real business
  • MESA's own domain
  • Any business in operation

Checked against the current MESA main on November 13, 2026.

Why BUZO makes MESA

BUZO is building MESA around the work of running a restaurant: getting orders from table to kitchen, organizing the bill and seeing what sold. These workflows still need validation with an authorized business. Once a restaurant operates MESA, real service data can guide what BUZO builds next.

Want MESA in your business?

Tell us how you run things today. If what you need isn't a new system, we'll say so first.

I want MESA