Dieture Operations Platform

Kitchen, packing, delivery and support each ran on their own spreadsheets, chat threads and printed sheets, and the numbers never matched. Past 10,000 active customers, those gaps became the limit on growth.

One microservices backend owns the business logic. Every app above it is a thin client built for one role, so no business rule is re-implemented in an app. About 30 staff work in the dashboard, and each field app has 10+ daily users.

• Kitchen app: production requirements per service, derived from live subscriptions
• Packer app: the packing queue, item by item, with built-in checks
• Driver app: the day's route and stops, built for one-handed use
• Backoffice dashboard: the control centre for all of it

A custom ERP and CRM in one, with role-based access so each department sees only its own modules. It replaced more tools than any other part of the platform.

• Subscriptions, leads, customer progress and full history
• Menu catalogue: dishes, ingredients, allergens and programs
• Kitchen, packing and delivery workflows, plus B2B retail orders
• Complaints and feedback captured internally
• Delivery coverage drawn as editable map zones, covering almost all of Qatar
• Theming and configuration pushed out to every field app
• Multi-country configuration, ready for expansion into Saudi Arabia
• Structured logging and real-time operational insight

I contributed heavily to the backend and owned the complex parts of the dashboard: coverage mapping, the configuration layer, subscription state and the logging that made everything else debuggable. Here a bug has a physical cost: a wrong kitchen number means wasted food, and a wrong route means a customer goes without a meal.