Case studyProduct and platform
Mensa
Reimagining restaurant ordering and payments.
A restaurant management ecosystem built around QR ordering and split payments.

The work, the thinking and the value behind it.
Mensa is a connected restaurant operating system spanning the guest, the waiter and the restaurant manager. A QR-led web experience handles ordering and payment while two staff-facing applications keep tables, orders and payment status aligned in real time.
The work was shaped as one service rather than three isolated interfaces. Each person sees only the controls they need, but every action updates the same operational picture behind the scenes.
Restaurant guests, floor staff and venue operators
Product and platform
- Guest ordering web app
- Waiter dashboard
- Restaurant control app
- Split-payment flow
The problem
Dining should feel effortless for both guests and staff. In most restaurants, ordering, splitting bills, and handling payments still involve waiting, confusion, and manual work.
The friction compounds during busy service: guests depend on staff for every step, staff re-enter information across tools, and the restaurant has no single live view of what has been ordered or paid.
A system with three views
A real-time ecosystem of three connected apps — a visitor web app, a waiter dashboard, and a restaurant control app — that work as one.
Guests scan a QR code to order and pay instantly. Staff manage tables, add or edit orders, and track payments as they happen. No downloads, no delays.
The division of responsibility is intentional: the guest flow stays lightweight, the waiter view prioritises active tables and service actions, and the restaurant app provides the broader operational controls.
The payment moment
Splitting a bill is treated as a first-class part of the experience rather than an exception at the end. Guests can see what remains, choose what they are paying for and complete payment from their own device.
Because payment status returns to the staff-facing views, the convenience for the guest does not create a reconciliation problem for the restaurant.
The result
For restaurants this means faster turnover, fewer errors, and a fully digital service flow that feels natural to staff and guests alike — traditional dining turned into a live, connected system.
The product removes avoidable hand-offs while keeping staff in the service loop, allowing technology to absorb administration without making the dining experience feel automated for its own sake.




What the work puts in place.
What changed
- Faster table turnover
- Fewer ordering errors
- Split payments without the maths
- A service flow that is digital end to end
Project surface
- Guest ordering web app
- Waiter dashboard
- Restaurant control app
- Split-payment flow
Built with
- Next.js
- React
- Node.js
- PostgreSQL
- Keepz Payments
Something here look like the problem you have?
Start a project