Industrial catering and events marketplace
Factories and event hosts were sourcing kitchens in chat. We shipped a bilingual storefront that presents catering capacity, daily meals, and a direct order path.
The situation
Yummi Go sits between kitchens and industrial / event demand. The offer was clear in conversation and invisible online.
The constraint
Arabic-first marketing site that still has to explain two different offers: event hospitality and daily factory meals.
What we refused
A restaurant theme with a PDF menu. A consumer food-delivery clone the operators would not run.
What we shipped
Bilingual marketing site, menu presentation, service lines, and a contact path that routes event vs daily-meal demand.
Stack, on purpose
TypeScript, Next.js, bilingual pages, WhatsApp / form intake.
What changed
The offer is now a public catalog instead of a forwarded price list.
What we would do next
Vendor kitchen roster and recurring factory-meal orders as first-class records.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell us where your current operational system is breaking.