Skip to content
Concept Study
Restaurant

EMBER

Ember · Wood-Fire Kitchen

A 32-seat restaurant with an open wood-fire kitchen and a menu that rotates every two weeks. The brief: fewer no-shows — and make what sets you apart actually visible.

Restaurant
/01
EMBER

Wood-Fire Kitchen · Seasonal Menu

Palette
Char
#1a1a1a
Ember
#c44d20
Cream
#f5f0e6
Aa Bb
Inter · 900
Tracking −0.04em
EMBER Wood-Fire Kitchen · Seasonal Menu
02 · Situation

How the business runs today.

A 32-seat downtown restaurant with an open wood-fire kitchen and a seasonal menu that rotates every two weeks. Reservations come in by phone and through a third-party booking service. The no-show rate sits where the industry sits — somewhere between twelve and fifteen percent. At 32 seats, that means an empty four-top per service, week after week. The menu rotates faster than the static PDF on the website is updated — guests arrive with photos that haven't been current for three weeks. And the wood-fire method, the one thing that sets this restaurant apart from seven others on the same street, is nowhere on the site.

03 · Problem

What's actually going wrong.

01

The phone is frictionless. Cancelling is not.

A phone reservation takes thirty seconds. Cancelling means calling during service, maybe twice, and talking to someone who is in the middle of setting a table. Most guests do not call twice. They simply don't show up.

02

The menu changes. The website doesn't.

Every new seasonal menu starts with a gap: the printed card swaps on Monday, the website card the weekend after — if at all. Guests book on the basis of photos that no longer exist. Expectation and reality drift apart before the first course hits the table.

03

What sets you apart isn't on the site.

Wood-fire kitchen, chef portrait, method — none of it appears on the current site. Instead: a stock pasta shot, opening hours, phone number. The same as every other restaurant on the same block.

04 · Goal

What we are working toward.

01

Reservation with commitment

A form that turns into a confirmed reservation in thirty seconds — with a small card hold that brings no-shows down meaningfully.

02

Seasonal menu without delay

A menu workflow the chef can update in ten minutes themselves. No web appointment, no weekend update.

03

Difference made visible

Wood-fire method, sommelier pairing, seasonal sourcing — surfaced as the asset they are, not buried as a footnote.

05 · Solution

The decisions we make.

01

Reservation with a card hold.

A one-euro card hold meaningfully reduces no-shows — well-documented industry standard. The form does not break the reservation friction; it shifts it to where it belongs: the cancellation.

02

Above-the-fold: chef and wood fire.

The differentiating asset belongs above the fold. Whoever scrolls is looking for the menu — whoever does not scroll should at least know what makes this place different. Three seconds, one statement.

03

Menu as a markdown drop.

No backend login, no CMS training session. The chef types the new menu into a notes app and sends it as a file — the site picks it up on the next update. Menu maintenance is a ten-minute task, not a calendar invite.

04

Sommelier note per dish.

Wine pairing is the high-margin anchor buried in most restaurant menus. One line per course — instead of a separate card at the back — moves attention to where the margin lives.

05

Bilingual from day one.

Downtown means thirty percent international guests. An English version that feels machine-translated signals the opposite of premium. Translated properly, with separate URL paths.

06 · Features

What the site can do.

Reservation with card hold

Binding reservation in thirty seconds — cancellation in the same.

Seasonal menu as a markdown drop

Chef's note becomes the web menu. No CMS login, no training.

Sommelier pairing per dish

Wine recommendation next to each course — one line, not a separate card.

Chef portrait & method

Wood-fire detail, chef bio, source references — visible in the hero.

Bilingual frontend

Properly translated with a URL per language.

Local search presence

Structured data so reservation buttons appear directly in search results.

Data stays with the restaurant

Reservations go straight to the house inbox — no external CRM siphoning the data.

Standalone mobile reservation

Mobile is its own layout. Thumb reach, not mouse reach.

Next step

Solve problems like these for you?

If your business shows one of these patterns, let's talk — no upfront contract, no pressure.