Product · Hospitality
The till already owns the money. This owns the guest.
Dish names, prices and stock come from the accounting system. The cheque closes in the point of sale. What no system owned was the guest — the booking, the table, the allergy, the occasion, and the memory of every visit across all the venues.
Open SIDRA
Opens in a new tab. Switch between the guest side and the restaurant side in the control bar.
What it is
A guest-experience platform for a multi-venue restaurant group, sitting on top of the systems already in place rather than replacing them. Booking, waitlist, the table session, ordering by course and seat, the bill and its splits, the tax invoice, and the feedback loop — with a floor plan, an arrivals desk and a shift handover on the restaurant side.
- 4
- venues in one group
- 26
- tables laid out to scale on the floor plan
- 2
- sides: guest and restaurant
- 3
- bill-splitting modes that each produce a real list
These describe the product and its seeded demonstration world. They are not a client's operating figures.
Who it is built for
The guest on a phone, and the floor team who cannot stop moving.
Every screen on these pages is redrawn in the browser from the product itself. None of it is a captured image.
The guest
Books through real availability, records an allergen passport that travels between venues, scans the table, orders by course and seat, splits the bill and receives a tax invoice.
Table 14
Allergen passport applied
- First course2 guestsSent
- Shellfish dishBlockedAllergy
- BillSplit by seat3 ways
Send the next courseThe floor
A floor plan coloured by service state with turn timing and a bussing clock, arrivals against the service clock, a three-tap walk-in with a live quote, and the coursing board.
The floor
Service state and turn timing
- Table 9DessertTurns in 12 min
- Table 21Bussing4 min
- Walk-in quote2 guests25 min
Seat the walk-inThe back office
Menu availability and guest-facing copy only, with the provenance of every field stated, plus a live view of every system link with retries that actually retry.
System links
What this product does not own
- Menu and pricePulled from accountingRead-only
- The chequeClosed in the tillRead-only
- Failed pushes2 queuedRetry
Retry the queue
Three decisions that shaped it
- 01
Availability is structural
A table is only offered if no other booking overlaps its turn. Overbooking to look available is the fastest way to lose a fine-dining guest.
- 02
The allergy blocks, it does not warn
A conflicting dish is greyed out with the reason inline and the chef's substitute underneath. A basket with a conflict cannot be sent.
- 03
The product states what it does not own
Every field pulled from the accounting system is marked read-only with its source. Being explicit about the boundary is what makes an operator trust the parts you do own.
How it is built
- Integration state is a first-class screen: heartbeat per connector, queued and failed counts, payload preview, and a retry that works.
- The menu is typographic, with no photography — a deliberate choice for the segment.
- Feedback routes by score: high goes public, low goes privately to the floor manager and offers no review link.
- Arabic first with right-to-left throughout, complete English, Latin numerals, and a QR rendered inline rather than fetched.
Next product
Running more than one venue?
If a guest's allergy does not travel between your branches, that is the first thing worth fixing.
Our WhatsApp line is being connected. Email reaches us today.