Restaurant operating system
Suite ownership - Led design for the platform powering 10,000+ restaurants, and took AI tools from concept to launch.
At a glance
- Product
- Grubtech — restaurant OS connecting online sales channels, POS, kitchen, delivery, and analytics
- My role
- Led product design across the platform — strategy, roadmap, OKRs with product and engineering
- Scope
- Design framework for 22 products · 16 core products designed end-to-end
The challenge
I joined during COVID, when micro kitchens were popping up everywhere and a lot of restaurants had gone delivery-only overnight. Operators had more tools than ever, but they were drowning in disconnected systems, slow reporting, and data that was already out of date by the time they saw it.
Grubtech works with big F&B brands like Burger King and Domino’s, many of them running multiple branches across different locations. The job was to connect their online sales channels with everything behind the counter, so a brand could run every branch, wherever it was, from one place and make decisions on live data. Some of these chains were still on legacy systems, and their teams had processes they trusted. We had to keep those processes recognisable while making the kitchen and delivery side work far better.
Who it was for
Owners, managers, and operations teams at restaurant chains, multi-location brands, and micro kitchens. These were people juggling orders, menus, kitchens, and drivers, and they needed one clear picture instead of multiple systems.
My role
I led the product design team at Grubtech and shaped the design strategy and roadmap. I set OKRs with product and engineering, and set sprint priorities with the PM and Engineering Manager based on what the team could realistically ship. I worked with our AI engineers on where intelligence belonged in the product, and ran design operations from discovery through to delivery.
Grubtech had a lot of different users, and I wanted the team to hear from every one of them. We started with owners and managers, sat down with leading chains, and kept a close eye on competitors. Then we went further. Customer service tickets came back into the product, so whenever restaurants were struggling with something, we knew about it and could see what it was affecting. We spoke to the pickers and drivers too, about how the apps held up during a busy shift. Whoever was using a product, we talked to them.
Getting everyone working from the same map
When I arrived, the team had plenty of good ideas but no shared picture of where the product was going. So I started by mapping the critical end-to-end journeys for each type of user, with accessibility built in from the start, and used them to guide what we built next.
They stuck. Engineers and PMs started referencing the journeys in their PRDs, OKRs, and design docs, and I set up a weekly product sync where we could align on priorities and work through ideas together.
To bring the whole company closer to the people we were building for, I ran a series of customer empathy workshops with people from engineering, product, design, and sales. I organised the teams, recruited the participants, and set the agenda for each session. Everyone came away with a much clearer sense of what restaurant teams actually deal with day to day, and you could see it in the decisions we made afterwards.
The solution
One design framework for 22 products
With a suite this big, the design job was making it all feel like one product. I evolved grubtech’s design framework so all 22 products sat in a single ecosystem, and I owned end-to-end design for 16 core products: order, menu, and delivery management, POS, gKDS, gPicker, gGenie, gDiscover, fleet, aggregator integrations, routing, reporting, multi-location control, and many more.
Kitchens built for delivery
Delivery-only kitchens were being held together by workarounds. We redesigned the delivery flow and how micro and smart kitchens run day to day, with kitchen management at the centre, so orders moved from screen to bag without falling through the gaps.
AI, from concept to launch
I led three AI products from first idea to release: a digital menu ordering assistant that helped diners choose faster without endless scrolling; an operational dashboard that flagged problems early and forecast demand, inventory needs and sales; and gGenie, an AI assistant that let owners ask questions about any aspect of their business.
Data owners could act on
gDiscover pulled in competitor and market data so pricing and menu decisions weren’t guesses. Our analytics dashboards gave chains live views across branches, covering pricing, menu changes, promos, reviews, sales trends, store audits, and benchmarking, plus a map of nearby competitors.
The outcome
In testing, the kitchen and delivery redesign cut order failures by about 86% and made prep noticeably faster. Most of that came from smarter kitchen management, not more staff on the line.
Burger King moved off its legacy system while its teams kept a process they recognised, just faster and cleaner. Across the suite, launches landed on the timelines we agreed, all inside one design framework instead of 22 different looks. Today grubtech powers 10,000+ restaurants, including Burger King and Domino’s.