03 / 07, Restaurant technology
Restaurant Operating System
Ikkyu's approach turned into templates by cuisine and region, so any restaurant can get a system that fits.
- Role
- Founder
- Stage
- Building
- Sector
- Restaurant technology
- Market
- Mexico first
- Started
- 27 October 2026
(01)
What it is
The Restaurant Operating System takes what I built for Ikkyu and makes it repeatable. Each restaurant starts from a template for its cuisine and region, then gets tailored to how it actually runs.
The second deployment is for a bar and nightclub in Monterrey, a very different business: door passes by QR, bar inventory by the milliliter, and a guest app. Same code, a different brand file.
(02)
The problem
Restaurants in Mexico pay high fees to a few dominant platforms and still get software that wasn't designed for them.
(03)
What it does
Five steps to launch
Pick a template, run discovery, tailor it, launch and train the team, then keep improving.
Everything in one place
Orders, inventory, reports and staff in one system the restaurant owns its data in.
Simple pricing
A setup fee plus a monthly subscription, and it works with any payment provider.
BeYou Restaurants
A planned reservations layer that competes with the dominant platforms in Mexico at a much lower cost.
(04)
Timeline
The second deployment starts from the Ikkyu template, for a bar and nightclub in Monterrey.
Bar inventory and drink recipes loaded from the club's own menu.
Nightclub hours: the business day rolls over at 6 a.m., spirits are counted by the bottle, night reservations and bar reports.
A guest app on the same database: reserve, join your table by QR, order bottles, call your waiter and split the bill.
The staff side: door entry with pass scanning and ID check, a promoter role, and guest payments validated into the till.
A one-command demo that runs a full night from start to finish.
- Today
Building
- Next
Sign the next restaurants after Ikkyu, starting with Sushi IWA.