Orquesta Labs: operational software for restaurants

A restaurant coordinates guests, reservations, staff, tasks and timing while service keeps moving. When tools do not talk to each other, teams fill the gaps with messages, separate sheets and knowledge held by only a few people.

Orquesta Labs begins there. We build modular tools to organize that work without asking a restaurant to change everything at once or bend every process around a rigid system.

I worked as a waiter at La Piemontesa and La Tagliatella and as a crew member at McDonald's. I experienced demand peaks, shift handovers, late information and the difference a clear process can make.

That experience does not replace user research; it gives me better starting questions. It also helps me spot features that look elegant in a demo but would add steps when the team has the least time.

I lead product and technology: prioritization, architecture, frontend, backend, APIs, authentication, databases, integrations and deployment. Working across the journey forces me to connect each technical decision to a specific need.

I structure the system in modules so it can grow without mixing responsibilities. In the interface, repeated actions must be fast and predictable because they compete with physical work, noise and guest attention.

AI is useful when it organizes information, finds a priority or removes repetitive work. If the process itself is still unclear, adding a model only hides the problem for a while.

Any recommendation should be reviewable and leave the final decision with the team. In a restaurant it also has to arrive on time: a brilliant answer that comes too late is useless.

Orquesta Labs lets me combine two experiences that are often kept apart: working in restaurants and building a full-stack product. It is not a weekend prototype, but a product I continue to review and develop.

This page explains my role and the decisions behind the work. The official Orquesta Labs website shows the latest public state of the product.