Two sides, one system
Companies order; vendors cook. Employees browse the day's menu, place a single order, and add notes that travel to the kitchen — while the vendor gets a live manifest of exactly what's been sold.
Case Study · Product
Fudo
Corporate lunch, pre-ordered — so the kitchen cooks what's already sold.
The Brief
Fudo is a corporate lunch-ordering platform. Companies partner with food vendors; employees order the day's meal from their phone, managers approve, and the kitchen sees exactly what to cook and for whom. It replaces the usual mess of group chats, spreadsheets and someone walking round with a notepad — one place where lunch is ordered, approved and fulfilled. And it's ours: an in-house Jungle product, designed and built end to end.
"
Cook what's sold — Fudo's promise, and the shape of every screen.
The Product 01 02 03 04
What Fudo actually is.
One sign-in, many hats
One person can be an employee at their company and an owner at a vendor. Fudo asks which account you're using and reshapes the whole app around it — navigation, screens and permissions all follow the role.
Order for the whole table
A colleague in a meeting? Place their order for them. The one-order-a-day limit follows the person eating, not the one tapping, and Fudo shows who's already in so no one doubles up.
A locked manifest by cut-off
Ordering opens and closes on each company's schedule, and every order moves through clear states — placed, approved, completed. By the cut-off the kitchen has a final list, not a forecast.
Designed down to the empty state.
A food-first interface built in Figma and shipped to code — every flow, state and edge case drawn as a real screen.
The Process 01 02 03 04 05
From rules to a running product.
Discovery
We mapped the whole domain first: two organisations, five roles, and the rules that govern a day of ordering — one order per person, a timed window, prices locked at the moment of purchase.
UX architecture
Those rules became flows and states before any pixels — the ordering window, the approval queue, order-for-a-teammate, and every empty and error state treated as a real screen, not an afterthought.
UI & visual design
A calm, food-first interface in Figma: a warm purple system, generous cards that let the meals lead, and one component language shared across employee, manager and vendor views.
Build
Shipped as three real apps — an Astro + React ordering app, a TanStack admin console, and a NestJS API on MariaDB — with role-based access enforced end to end.
Ship & iterate
Fudo is in active development. New screens ship behind the same design system and the same API contract, so the product keeps growing without drifting apart.
Three apps, one contract.
A typed, container-ready stack — React on the front, NestJS and Prisma behind it, role-based access shared across all three.
Ordering app What employees and managers use
- Astro
- React
- TypeScript
- Tailwind CSS
- shadcn/ui · Radix
- React Hook Form · Zod
- Firebase Auth
Admin console Company & vendor administration
- TanStack Start
- TanStack Router
- Prisma
- Casbin (RBAC)
- Vite
Backend & data The API and the source of truth
- NestJS
- Prisma
- MariaDB
- Supabase
- Firebase Admin
- Swagger
- Docker
The Shape
A whole product, not a prototype.
3 Apps — ordering, admin, API
5 Roles the app reshapes around
6 States every order can move through
1 Active order per person, per day
Fudo is an in-house Jungle product — design and build, end to end. Currently in active development.
Up next Billin View case study
