For restaurants & bars · Midlands
Appetite does the selling: the menu, the photography, the room at golden hour. Then the booking has to be one tap, and protected, so a table for eight can't vanish without a word.
Long before anyone tastes a thing, the site has done its selling or lost the table. Three ways it goes wrong, and every one is fixable.
No scare figures here. If you run a dining room you've lived all three of these this month, and each one is a build, not a fact of life.
This is Ember & Oak, a restaurant concept I built to show the standard. Hover it and it walks through itself.
Browsable on a phone, readable by Google. Your dishes turn up when someone searches for dinner near them, which a PDF never will.
Card capture on the sixes and eights, so a no-show costs them something instead of only you.
Hours, address, parking, dogs or not. The boring questions, settled before anyone has to ring mid-service.
Appetite does the selling. One evening with a decent photographer outworks a page of adjectives.
Ember & Oak is a concept, not a real restaurant. Yours gets built on your menu, your room, your prices.
A site fills the book. These three run between services, and every one is a small build.
Today
The menu changes, so someone retypes it: print, the website, the PDF, Google, the specials board. Miss one and a diner orders something you stopped serving in March.
What I'd build
One menu source that pushes everywhere at once: the site, a print stylesheet for the table copy, and Google. Change the fish, everything changes with it.
Ask about thisToday
It lives in a folder by the pass, always one edit behind whatever the kitchen changed on Tuesday. Everyone trusts it slightly less than they should have to.
What I'd build
An allergen list linked to the same menu source, so it updates once, with the dish. The folder becomes a printout of something that's actually current.
Ask about thisToday
Sold on paper, logged in a notebook, redeemed on trust. Nobody knows how many are out there, and December's voucher admin lands in the middle of December.
What I'd build
Vouchers sold on your own site that track themselves: numbered, dated, redeemed with a tap at the till. The money lands upfront and the drawer retires.
Ask about thisEvery one is a small build that connects to the booking system and till you already run. If you want the numbers for your own setup, I'll build you a proper ROI on the jobs worth doing.
Most places leave the site as it is because service eats every week. Here's the whole of it.
Twenty minutes, between services. I look at your current site and how bookings and the menu actually run, then tell you honestly where the quick win is and where there isn't one.
You see a real, clickable version of the site on your name, your menu and your room, not a slide deck of what it might become.
It connects to the booking system you already run and the till you already trust. Nothing that works gets rebuilt.
Menus change weekly, so the site keeps up. That's the part other builders hand over and forget.
Most restaurants take the subscription: nothing upfront, one monthly amount, and the website stops being the thing you do after close.
The restaurant site done properly. Menu as a real page, booking, hours, find-us, hosting, changes and care, bundled.
Start with StarterThe site plus the admin killers. Single-source menu, the allergen list and vouchers: the jobs above, built in. We'll agree the exact mix on the call.
Start with StandardFifteen minutes on the phone and I'll tell you what I'd build, what it costs, and whether it's worth doing at all. If your current site just needs its menu unsticking, I'll say so.