All industries
Restaurants & hospitality
Your restaurant site isn't losing diners to the food.
It's leaking the reservation.
A hungry local lands on their phone, can't see the food, can't read the menu without pinching a PDF, can't book a table in two taps, and orders through a delivery app that eats your margin. This is exactly where the reservations and direct orders leak out, and what each leak costs you a month.
what you actually lie awake about
You're not asking for a fancier site.
A hungry local picking where to eat tonight decides in seconds, on their phone, off the photos and the recent reviews. These are the real questions behind "maybe the site needs a refresh."
the cover question
"Why is the dining room half empty on a good night?"
People find you on Google and Instagram. The reservation book stays light and the bar covers don't show.
the margin question
"Why is every order coming through the delivery apps?"
Orders come in, but a third of each one goes to commission. You're busy and barely keeping it.
the trust question
"Why does the newer spot down the street look busier?"
Their photos are mouthwatering and their reviews are recent, so the hungry local picks them first.
A hungry local doesn't want a website. They want to know the food's good and they can book right now.
follow a hungry local through your site
Where your restaurant site leaks diners
Same hungry local on their phone, four moments. Each one a quiet leak. None look broken. All of them cost you covers. (Percentages illustrative, the pattern is real.)
1 · Lands · 0 to 5 seconds
~100% still here
"Does this place look good, and is it my kind of food?"
No mouthwatering food photos up top, no sense of the vibe. A stock hero and a logo. Nothing that says eat here tonight.
They swipe back to the spot whose food they can already see.
2 · Sizes you up · next 10 sec
~50% still here
"Is it actually good, and is it still open and busy?"
No recent reviews, no fresh photos, hours that don't match Google. The menu is a PDF they can't read on a phone.
The place with recent five-star reviews wins the hungry vote.
3 · Wants to act · the decision
~30% still here
"Can I book a table or order right now, in two taps?"
No sticky reserve or order button. Booking buried, ordering pushed to a delivery app. The one action that counts has friction.
Ready diners book the place that let them do it on the spot.
4 · Leaves · gone
~15% still here
"I'll come back next time." (orders from the app instead)
No email or SMS capture, no reason to return, no offer to come back direct. The regular-to-be never hears from you again.
A diner worth thousands a year defaults to the delivery app that owns them now.
You don't need more foot traffic. You need to stop losing the hungry locals already on your site.
what the leaks actually cost
100 hungry locals in. 5 booked direct.
Watch where 100 visitors go when every leak is open. This is the math you never see, because the diners who leak out never tell you, they just eat somewhere else.
100 hungry locals, every leak open
100 land from Google / Instagram
↓ 5-second leak
50 still think the food looks good
↓ trust leak
30 want to book or order tonight
↓ the booking wall
15 would act, if it took two taps
↓ follow-up leak
5 actually reserve or order direct
Every direct order keeps the 30% you hand the delivery apps, and a captured diner who comes back monthly is worth far more than a one-off commission order.
A prettier restaurant site with the same leaks is just a more expensive way to feed the delivery apps your margin.
how I find the leaks before touching the build
The 4-question diagnosis
Before I build anything, I walk your site like a first-time buyer and ask four questions at every step. The answers are the whole job. The build is just what happens after.
1
What's visibly broken?
The leak a stranger feels in five seconds, before they could ever explain it.
2
What is it costing you?
Every leak has a price in lost quotes, calls, or bookings. We name it in your numbers, not mine.
3
What proof can I show in 30 seconds?
Trust is built fast or not at all. If proof isn't near the top, the cheaper competitor wins.
4
What action should the fix create?
Every change points at one thing: the next step you actually want the visitor to take.
AI lets you build 10x faster. It also lets you build the wrong thing 10x faster. Diagnose first. Build second.
same site, two completely different sales
Why "I'll rebuild it" never lands
A stranger emailing "I made you a better website" sounds like homework, on a night with a full pass, a server out, and the walk-ins backing up. The fix has to name a leak the owner feels every service. Here's the difference.
sells a rebuild
"I rebuilt your restaurant site. Here's the preview, looks way better."
Reads as homework and an expense they didn't ask for, on a service that's already on fire. Ignored, the way most owners ignore the stranger pitching a redesign mid-rush.
sells a leak they're already bleeding from
"Your menu is a PDF nobody can read on a phone, there's no sticky book-a-table button, and every order routes through the delivery app. You're paying 30% on orders you could own and losing the diners who'd rather book direct."
Reads as found money. A leak they feel every single service. Same site, completely different conversation.
I don't sell restaurants a rebuild. I find the leaks and seal them.
straight answers
Questions owners actually ask
Why is my restaurant website getting visitors but no reservations?
Usually it's a leak, not traffic. Hungry locals can't see the food or the vibe in five seconds, the menu is a PDF they can't read on a phone, or there's no easy way to book a table. Add real food photos up top, a mobile-friendly menu, and a sticky reserve button, and the same visitors start booking direct.
How do I get more direct orders instead of paying delivery app commissions?
Put your own ordering front and center with a sticky order button, not buried behind a third-party app that takes 20 to 30% of every ticket. Then give people a reason to come back direct, an email or SMS list and the occasional offer, so a one-time order turns into a regular who orders from you, not the app.
Should my restaurant menu be a PDF?
No. A PDF menu is brutal on mobile, where almost all your diners are, and search engines can't read it, so it's invisible on Google. Use a real web menu that loads fast, reads cleanly on a phone, and shows up in search. It's one of the biggest quiet leaks on restaurant sites.
How do I find out where my restaurant site is losing customers?
Walk it on your phone like a hungry local at 7pm: in five seconds, does the food look good; can you read the menu and trust the recent reviews; can you book a table or order in two taps. Each no is a leak. That's the free 15-minute audit I run, and you keep the findings whether we work together or not.
the whiteboard, pointed at your restaurant site
Want to know where your restaurant site leaks?
Book 15 minutes. I'll walk your live site on a phone like a hungry local picking where to eat tonight and show you the exact leaks costing you reservations and direct orders, free, whether we work together or not.