Serve the house. Keep both lists true.
Two audiences. One house. Honest lists.
Members, guests, private dining, events. A public restaurant site leaks the wrong things; a members’ PDF leaks allergens. The house needs a digital system that knows who is looking.
Leading restaurant websites and Quiteful live menus for this room — London, the South, the North, Scotland, Ireland and nationwide.
What usually goes wrong
- The public site looks like a restaurant. Members expected a house.
- Guest menus, members’ menus and event menus are three Word docs.
- Private dining allergen duty is real and still “speak to the office”.
- Events sell out on email. The site finds out later.
why Lemon Octopus
Lemon Octopus builds club sites with a dual audience: the house story, events, private dining, gated bits if you need them. Custom when members and guests should not see the same pages. Not a high-street restaurant template with a crest.
- Members vs public journeys without maintaining two entire websites.
- Events and private dining as first-class paths.
- Gated areas or member tools when the house actually needs them.
- A tone that can carry a club without looking like a hotel brand.
why Quiteful
Members’ menus, guest menus and event menus diverge. Allergen duty on private dining is not optional. Quiteful holds those lists as live records: publish per audience, QR in the room, last-updated, dietary filters so the office is not translating a PDF during service.
- Separate lists where the house actually serves different food.
- Event and private-dining menus with full allergen logic.
- QR in the room so “ask the office” is not the allergen policy.
- Staff publishing that a club kitchen will use.
Why both together *
The club site knows who you are. Quiteful knows which list you are allowed to see. Lemon Octopus builds the house and wires the live menus so members, guests and private dining are not three incompatible documents.
Quiteful, in this room
Not every Quiteful capability belongs on every lander. These are the ones that earn their keep for clubs.
Live menus
Update once. Publish to QR, web, embeds and signage.
Allergens
All 14 UK/EU regulated allergens, with contains, may-contain and cross-contact logic.
Multi-location management
One source of truth across venues, without cloning every dish by hand.
QR / web access
Table-side QR and website embeds from the same live menu.
Staff workflows
Publishing designed for busy kitchens, not a CMS tutorial.
Last-updated information
Diners deserve to know when the menu was last true.
proof, without a fake quote
Private dining does not get a pass on allergens.
We built Quiteful so allergen information is current, clear and traceable — including rooms that are not on the public website. Lemon Octopus puts that behind a club site that can tell members from guests.
“Clear scope, fast staging links and no calendar theatre. The site launched looking like the product we actually sell.”
“Pricing was honest, the brief turned into a real plan, and the build held up under real traffic.”
Food consultants
Recommend a stack you do not have to babysit. A studio behind the consultant: Lemon Octopus ships the client’s site and software; Quiteful is the live menu product you specify.