Restaurant TechMulti-surface DesignSaaSDesign System
MenuMitra
Complete restaurant operating system, built around the QR code
Scroll
TheProblem
Indian restaurants, from neighbourhood cafes to multi-outlet chains, were running on paper and memory. Physical menus cost thousands to reprint every time a price changed. Orders went by voice from table to kitchen, arriving wrong or not at all. Owners had no visibility into which dishes were profitable. Post-pandemic, handing customers laminated menus felt like a liability. But the deeper problem wasn't the lack of digital tools. It was that the table, the waiter, the kitchen, and the billing counter each operated as islands with zero real-time connection.
Menu updates required costly reprints. Owners updated menus 3-4 times per year minimum, losing revenue during the gap
Kitchen order communication was verbal or paper-based. Errors and delays happened daily with no audit trail
Owners had zero item-level data. No way to tell which dishes drove margins and which ones quietly lost money
Existing digital solutions required customers to download an app, which killed adoption before it started
Enterprise POS systems were priced way beyond what small and mid-size restaurants could afford
02
TheTransformation
Restaurants didn't need a digital menu. They needed an operating system. The QR code was just the entry point. The real change was connecting six isolated parts (table, waiter, kitchen, billing, manager, owner) into one real-time system. Complexity lives at the platform level, not on any individual screen.
The Problem
Paper menus reprinted 3-4 times a year. Orders communicated verbally from table to kitchen, with errors and delays daily. Zero item-level data. No real-time connection between any part of the operation.
The Insight
“A chef under Saturday-night rush and a customer casually browsing lunch are touching the same data, but they need completely different interfaces. Pressure level changes everything about what works on screen.”
New Direction
The QR-first digital menu. No app download, works on any smartphone. Customer scans, browses, orders, and that order flows instantly to the right kitchen station, the waiter's app, and the billing system.
Research & Discovery
I spent two weeks in restaurants across Pune and Mumbai, from single-outlet dhabas to multi-outlet food courts, watching the full cycle from prep to close. Interviewed 35 stakeholders: owners, head waiters, kitchen staff, billing operators, and customers. The research showed that restaurant owners didn't just need a digital menu. They needed every part of the operation connected: the customer's order flowing to the kitchen display, the kitchen display feeding the billing system, and all of it reporting to an analytics layer so owners could see what was actually happening in real time.
01
Field observations at 20+ restaurants across Pune and Mumbai, from single outlet to 4-outlet chains
02
35 stakeholder interviews: owners, head waiters, kitchen staff, billing operators, and dine-in customers
03
Competitive audit of 12 tools: Zomato/Swiggy (delivery-only), LimeTray (expensive, complex), basic QR PDF menus (no interactivity), enterprise POS (unaffordable)
04
Customers were already used to zero-friction from UPI and web apps. Any solution requiring an app download was dead on arrival
05
Multi-outlet management was severely underserved. Chain owners coordinated across outlets via WhatsApp groups and shared spreadsheets
Design Exploration
How do you serve six different user types from one system? A customer who wants to order in seconds, a waiter managing 8 tables, a chef who needs zero ambiguity under pressure, a billing operator in a rush, a manager tracking daily numbers, and an owner monitoring remotely. Early explorations treated these as separate apps with shared data. What worked was the modular surface model: each user type gets a purpose-built interface for their context and pressure level, while a single sync layer connects everything underneath.
05
TheSolution
MenuMitra is a restaurant operating system built around the QR code. A customer scans the code on their table and instantly sees a full interactive digital menu on their phone, no app required. They add items and place the order directly. That order routes to the correct kitchen station (hot, cold, or beverages) and appears on the Kitchen Display System with timing and priority. The waiter app handles table assignment, order changes, and bill requests. The Captain App manages table status and floor overview. The billing POS handles payment with integrated gateway support. The owner dashboard provides real-time revenue, item-level sales analytics, inventory alerts, and staff performance across single outlets and multi-location chains.
Key Screens
My Contribution
AsLeadProductDesigner,Iowneddesignacrossall6surfaces:customerQRmenu,KitchenDisplaySystem,WaiterApp,CaptainApp,OwnerAnalyticsDashboard,andBillingPOS.Iranthefieldresearch,mappeduserjourneyflows,builttheIA,setupthedesignsystem,andproducedhigh-fidelityprototypesforeverysurface.Ialsodesignedtherestaurantonboardingexperience,whichwascriticalbecausethefirst30minutesdeterminedwhetheranownerwouldstayorchurn.Thetrickiestdesignproblemwasthereal-timestatuslayer:howdoesawaiterknowtheirorderwasacceptedwithoutcheckingtheirscreenconstantly?Wesolveditwithambientstatusindicatorsinthetableview.Nointerruption,justapersistentvisualtruth.
Impact & Outcomes
Launched with a pilot of 50 restaurants in Maharashtra and scaled from there. MenuMitra now serves 2500+ restaurants across India, spanning 12 outlet types from single-outlet cafes and cloud kitchens to multi-location chains.
2500+
Restaurants on platform
25%
Avg. revenue growth reported
4.8/5
Customer satisfaction rating
6
Interface surfaces designed
08
Reflection
ThebiggestthingItookfromMenuMitraisthatinformationtimingmattersmorethaninformationlayout.Whichscreenshowsthedataislessimportantthanwheninsomeone'sworkflowtheyneeditandhowmuchattentionyoucanaskforatthatmoment.AchefonaSaturdaynightandacustomerbrowsinglunchareusingthesamedata,buteverydesigndecisionforeachofthemhastobemadeasiftheotherdoesn'texist.Designingfor6usersat6differentpressurelevelsforcedmetothinkaboutcontextmorecarefullythananyotherproject.