Jorge Gasca
Ver en español
Menu
Selected work

Live pilotPrivate source

OrdenAI — Restaurant orders without the channel gaps

OrdenAI connects orders from web and messaging channels with the restaurant’s kitchen, catalog, inventory, customer records, and daily operations.

Open live productPrivate source
OrdenAI homepage with a restaurant order workflow across customer channels and operations.
Public product page2026-08-09This public pilot view is not an authenticated restaurant account or a claim of general availability.

30-second brief

RoleIndependent product builder
StageLive pilot
What I owned

I designed the product domain, mapped the customer-to-kitchen journey, built the responsive workflows and channel connections, and handled security boundaries, monitoring, and release checks.

Current result

The limited pilot uses one server-controlled order record across the public menu, messaging intake, kitchen status, inventory changes, and customer follow-up.

What I noticed

An order can arrive through the web, WhatsApp, or Telegram, but the kitchen still needs one reliable version of what was ordered. Separate systems create duplicate work and make status changes hard to trust.

What I worked on

  1. 01

    I defined how organizations, locations, team membership, catalogs, and orders fit together.

  2. 02

    I connected channel intake to a shared order model and the kitchen’s working view.

  3. 03

    I added localization, responsive behavior, release checks, and monitoring around the operational flow.

One decision that mattered

I made order changes repeat-safe and kept an audit trail because messaging providers can retry a webhook. The restaurant should not receive a duplicate order because the network repeated a request.

What I learned

OrdenAI made the difference between a feature and an operation very concrete: a button is easy; a trustworthy order needs history, ownership, and a safe response when another system retries.

Current status

OrdenAI is a live, limited pilot with private source. It is not presented as a generally available enterprise platform.

See it in action

OrdenAI

Public, synthetic, or simulated screens only. Customer and account data stay out of the portfolio.

01

I defined how organizations, locations, team membership, catalogs, and orders fit together.

02

I connected channel intake to a shared order model and the kitchen’s working view.

03

I added localization, responsive behavior, release checks, and monitoring around the operational flow.

OrdenAI homepage showing a restaurant order workflow across customer channels and operations.
Public product pageOrdenAI on desktop.This public pilot view is not an authenticated restaurant account or a claim of general availability.
OrdenAI homepage showing a restaurant order workflow across customer channels and operations.
Public product pageOrdenAI on mobile.This public pilot view is not an authenticated restaurant account or a claim of general availability.

A short path from menu and channel setup to an order and its restaurant operations view.

Read the visual transcript

The walkthrough begins with the OrdenAI menu and channel setup, follows a synthetic order into the shared order flow, and finishes on the restaurant operations view. No customer or restaurant account information is shown.

Public product pageShort walkthrough of OrdenAI.This public pilot view is not an authenticated restaurant account or a claim of general availability.

Technology

Next case studyZentix Office — Showing an AI-team idea without faking activity