Senyu Fine Dining
This is self-initiated concept work. No client engagement, no production deployment. The problem, structure, and execution are mine.
Senyu Fine Dining needed a website that matched the prestige of dining in person. Opulent dark aesthetic, full menu architecture, and an inline reservation system, the digital experience earning every table booking before the door opens.
Given: a fine dining restaurant, its menu and its reservation process. Designed: the website, from menu architecture to the inline reservation flow.
Built withHTML/CSS/JS
Fine dining is sold on atmosphere before a single dish is served. This restaurant's food and ambiance were exceptional, but a generic website would send prospective guests straight to a competitor who could communicate that prestige digitally. Every pixel needed to justify the reservation.
Most restaurant websites default to generic templates: stock photography, OpenTable embeds, and menus buried as PDF downloads. For a restaurant at this price point, that gap between digital experience and in-person experience doesn't just underperform. It actively erodes the brand before the guest arrives.
Build a website that communicates luxury instantly, makes menu browsing an act of anticipation, and closes the reservation in a single seamless flow. No redirects off the site, no phone calls required.
Competitive analysis
I audited four restaurant website archetypes, from global luxury chains to independents fully reliant on OpenTable, to map where the fine dining digital experience consistently fails its audience.
Nobu
Strong brand presence and photography. But reservation flows split across markets and a fragmented menu structure dilute the luxury experience at the critical conversion point.
Zuma
Excellent visual staging and atmosphere. Navigation is confident. However the menu is PDF-gated and reservations route out to SevenRooms, breaking immersion at the moment that matters most.
Typical independent
Template sites dominate: a page builder with a restaurant theme, stock photos, and an OpenTable widget. Nothing signals exclusivity. Nothing earns the table.
OpenTable profile
Frictionless booking for the guest, zero brand control for the restaurant. The digital impression belongs to OpenTable, not the chef, a brand liability for a restaurant competing on atmosphere.
| Criteria | Nobu | Zuma | Independent | OpenTable | This site |
|---|---|---|---|---|---|
| Brand atmosphere | Strong | Excellent | Weak | None | Immersive |
| Menu experience | Moderate | PDF only | PDF / hidden | None | Full inline |
| Reservation flow | Fragmented | Redirects out | OpenTable | Off-site | Inline · 1 page |
| Mobile experience | Good | Moderate | Poor | Generic | Optimised |
| Custom-built | Yes | Yes | No | No | Yes |
User personas
Two people use this website with fundamentally different intentions. Every design decision was tested against both: does this earn the diner's trust? Does this reduce the owner's dependency on phone calls?
Plans special occasions with research. Visits 3 to 5 restaurant websites before choosing. Expects the website to validate the decision: if the site feels cheap, the experience probably is. Has booked online for 8 years and won't pick up the phone if an online option exists.
Primary goalConfirm the restaurant is worth the price before committing. Menu, atmosphere cues, and a frictionless booking flow are the deciding factors. She wants to feel the occasion before she arrives.
Pain points- PDF menus are inaccessible on mobile and kill the browsing experience
- Redirecting to OpenTable or calling a phone number breaks immersion
- Generic template sites signal a restaurant that doesn't care about presentation
"If the website looks like a template, I assume the attention to detail in the kitchen is the same."
18 years in fine dining, opened his own restaurant three years ago. The kitchen is his domain; the phone and the reservation spreadsheet are not. Loses 4 to 6 hours a week to phone calls that could be self-serve. Has no technical staff.
Primary goalA website that handles reservations without him. No monthly OpenTable fee, no phone calls during service, no spreadsheet at the end of the night. The brand should feel as considered as the food he plates.
Pain points- 4 to 6 hours weekly lost to phone reservation calls that interrupt service
- OpenTable fees compound monthly and brand control is surrendered
- Existing site doesn't reflect the calibre of the food or years of craft behind it
"I built this restaurant with my hands. The website should feel like I built that too."
The diner's journey
Aiko's path from restaurant discovery to confirmed reservation, mapped against the friction points this site was designed to eliminate at each step.
Searches "best sushi restaurant [city]". Scans 3 to 5 results. First impression from the thumbnail and meta description. Clicks the most compelling.
Most restaurant sites load slowly, display stock photography, and provide no immediate signal of quality. Bounce rate is high at this stage.
Hero section: full-bleed food photography, clear name and positioning statement. The atmosphere is communicated in under 3 seconds.
Navigates to the menu to check for options they'll enjoy and to validate price expectations before committing.
PDF menus require download, can't be read comfortably on mobile, and have no design continuity with the brand. No pricing creates anxiety.
Four inline menu categories with descriptions and pricing, browsable on any device. A "Today's special" section adds urgency and delight.
Wants to know who is behind the food. Looks for a chef profile, the restaurant's story, any signal of craft and intention.
Generic "About" pages with no personality. Stock chef photography. No visual connection between the food and the person who creates it.
Master chef profile section with narrative biography beneath the reservation block. The chef becomes part of the reason to book.
Ready to book. Needs to select date, time, and party size. Expects the process to take under two minutes and stay within the same visual environment.
Redirected off-site to OpenTable or SevenRooms. The luxury aesthetic collapses the moment the third-party widget appears.
Inline calendar-based reservation, all on one page, no redirect. Confirmation stays on-brand. The entire flow takes under 90 seconds.
From brief to build
01 · Information architecture
Homepage hero
Full-bleed dining room photography, gold-tinted headline, and a single CTA above the fold. Atmosphere is communicated before a word is read.
Menu page
Four categories with photography, descriptions, and pricing. Browsable on any device without a PDF in sight.
Fine dining experience Core
Our Story, four brand values, and the master chef profile. The emotional case for booking before the reservation form is reached.
High-fidelity screens
9 screens covering the full site experience, from the first impression on the homepage to reservation confirmation. Each screen is built around a specific guest or owner need.
Four choices that shaped the site
Dark luxury palette
The decision to go jet black with antique gold wasn't aesthetic preference, it was competitive positioning. Every restaurant website in the reference set defaulted to white or cream. A full dark canvas made the photography the subject and signalled a level of craft in the design itself that translated directly onto the food. Gold was selected for its warmth over cooler yellows; it reads as earned, not decorative.
Inline reservation. No redirect.
Every third-party reservation widget (OpenTable, SevenRooms, Resy) breaks immersion. The guest spends 4 minutes inside a crafted atmosphere, then clicks "Reserve" and lands on a generic white widget with corporate branding. The solution was a custom inline booking block, date picker, time slots, party size, and contact fields, all within the site's own design system. The reservation completes without the guest ever leaving the page.
- Click "Reserve" on branded site
- Redirect to OpenTable / SevenRooms
- Generic corporate interface loads
- Fill out generic form
- Confirmation email from 3rd party
- Scroll to reservation block
- Pick date, time, party size
- Enter name and contact
- Confirm, stays on the site
Menu as experience, not information dump
A PDF menu is a failure mode. It requires a download, renders poorly on mobile, carries no brand continuity, and cannot be updated without re-uploading a file. The inline menu was designed as a content section, four tabbed categories, each with item names, descriptions, and pricing displayed as a browsable grid. A "Today's special" rotator sits above the menu to surface the freshest offering. The menu is the product catalogue and the closing argument simultaneously.
Chef profile as the conversion trigger
Placing the master chef's profile immediately beneath the reservation block was deliberate. At that point in the page, the guest has browsed the menu, considered the price, and is on the edge of committing. The chef's portrait, biography, and culinary philosophy turn a transaction into an occasion. A table reservation is partly a reservation with the person who made the food, the site makes that explicit.
Delivered outcomes
Nigiri, Sashimi, Specialty Rolls, and Appetizers with names, descriptions, and pricing. No PDF, browsable on any screen.
The entire reservation flow completes on a single page with no redirect to OpenTable or any external service.
Responsive across all breakpoints, gold-on-black aesthetic, a complete reservation-to-confirmation flow with no third-party dependencies.
The owner's 4 to 6 hours weekly of reservation calls during service shifted to a self-serve booking system, including during peak service hours.
Every pixel of the guest's digital journey, from landing to confirmation, is inside a consistent luxury aesthetic. The site became part of the restaurant's identity.
The "Today's special" rotator gives existing guests a reason to return between visits, converting a one-visit utility page into a lightweight engagement loop.
What I would do differently
I would add a backend reservation management dashboard for the owner: a simple admin view showing upcoming bookings, party sizes, and contact details without spreadsheet maintenance. A confirmation email system with the same visual language as the site would also reinforce the brand post-booking.
Luxury digital design is not decoration, it's the systematic elimination of anything that contradicts the brand promise. Every redirect, every generic widget, every stock photograph is a micro-contradiction. The discipline of this project was resisting the convenient solution in favour of the consistent one.
Botanikos →
A structured product grid that signals price tier before a word is read.