A restaurant website you change
by sending a message.
Wes rebuilds the restaurant website you already have, then keeps it yours. New price, new photo, closed on Monday: one message and it is live, in every language your site speaks.
1msg
to change anything on your siteThe reason restaurant websites go stale is never the website. It is the asking.
A price changed in March, the terrace opened in April, the Monday closure started in June. Each one needed an email to someone who would get to it next week. So none of them happened, and the site quietly started lying about you.
A Tuesday in March
The fish went up. The site knew before service.
Nothing about this morning is special. That is rather the point.
Your supplier calls. The sea bass is two euros more this week, and you are not eating that.
You send Wes one message: put the sea bass at 26,50.
He shows you the line exactly as it will read on the menu, and asks whether to publish it.
Live. On your site, and in every language your site speaks, without you writing any of them.
The old way was an email to a web person, a reminder on Thursday, and a wrong price all weekend.
The build
Your site, rebuilt from the one you already have.
Wes does not drop you into a template and ask you to fill it. He rebuilds the site you already have: your texts, your dishes, your photos, even the typeface the original was set in.
From there you can move. Two designs to sit it in, one modern and one closer to fine dining, and colours and a logo that are yours. Missing pieces get filled in from what we know about your restaurant, and only the pieces that are actually empty. Whatever you already wrote is left alone.
The site did not go stale because it was bad. It went stale because changing it meant asking someone.
Changing it
You say it, and that is the whole procedure.
No dashboard to learn, no page builder, no web person to chase. You write what you want changed the way you would say it out loud, and Wes changes it.
And here is the part that quietly saves the most: if your site speaks more than one language, your change is carried into all of them. You write it once in Dutch, and the English and German versions move with it. Unless you say you only want that one language, which he also understands.
Nothing goes live until you say so.
A website only rots because changing it is a favour you have to ask someone for. Take the asking away and the site simply stays true: the price is right, the terrace is mentioned in April, and the Monday closure is on there before a guest drives over for nothing.
The menu
The page everybody actually opens.
Guests click through to your menu before they decide anything. It is the most visited page you have, and the one most likely to be out of date.
Change a price, rename a dish, rewrite a description, all in one line. The same change flows into the other languages of your site. And because it is your menu rather than a PDF from two years ago, a guest reads it on their phone instead of pinching and dragging a scan of an A4.
Sea bass to 26,50 and take the mussels off, they are done for the season.
Sea bass is now 26,50 and the mussels are off the menu. Your English and German menus are updated too. Publish?
One line in, two languages out.
Reservations
Guests book the way they already booked.
You do not have to move systems. If you take reservations through Zenchef, Formitable or TheFork, that widget sits on your site and works there.
Or you keep it simple: a phone number to call, or your own reservation link. Say which one you want and Wes sets it. Your Instagram feed can sit on the page too, and a map, without you touching an embed code.
Your booking system stays yours. The site simply carries it.
Safety
Look at it first. And walk it back if you want.
Before anything goes live you can ask to see it. Wes puts the change up as a preview, you look at it on your phone, and only then does it go out.
Changed your mind after publishing? Say so and he puts the previous version back. There is no version you can lose and no state you cannot get out of, which is the only reason it is safe to hand your public face to something that moves this fast.
Being found
Your own name above the door.
Your site can live on your own domain, the one you already own. Wes walks you through connecting it, and only calls it live on your own name once it truly is.
Underneath, the ordinary things that decide whether anyone arrives are handled: a title and description per page, a focus word, an image that looks right when your link is shared, and a contact form whose messages actually reach you. Your Google reviews from four stars up appear on the site by themselves, so the page a guest lands on says the same thing your profile does.
Your website is where your Google profile sends people. It is the second thing a guest looks at, straight after your rating, and the one that has to survive being read one handed on a phone at a tram stop. Google also states that businesses with complete and accurate information are more likely to show up in local search results, and your website address is part of that information.
Google Business Profile Help, on local ranking"I used to email someone for every price change and wait a week. Now I send a message between two services and it is done."
He does not take over your reservations
Your booking system stays your booking system. Wes puts its widget on your site and sends guests into it. He does not manage tables, take bookings himself, or move you onto something new.
He does not call it live before it is
A site is only described as live on your own name once the domain is truly connected and working. Until then you get the plain address, and the truth about which step is still open.
He does not lock you into a look
Two designs, your own colours, your own logo, your own photos, and everything changeable by message. If you want something back the way it was, say so and it goes back.
Wes builds and keeps your website. Gigi keeps the Google profile that sends people to it, and Marco answers the reviews they leave afterwards.
I already have a website. Do I lose it?
No, it is the starting point. Wes rebuilds your site from the one you have, carrying over your texts, dishes and photos. You keep what you wrote and gain the ability to change it yourself.
Do I need to know anything technical?
No. You write what you want changed the way you would say it, and he changes it. If you would rather look before it goes out, ask to see it first, and if you want it back the way it was, say that.
Does it work in more than one language?
Yes, and this is where most of the work disappears. Change something once and it is carried into the other languages of your site. If you only want one language changed, say so explicitly and only that one moves.
Can guests still book through my own system?
Yes. Zenchef, Formitable and TheFork widgets work on your site, or you can point reservations at your own link, or simply have guests call you. Your system stays yours.
Can I use my own domain name?
Yes, the one you already own. Wes walks you through connecting it, and he only says your site is live on your own name once that is actually true.
What if I break something?
You cannot, really. Ask to see a change before it goes out, and if something is already live that you would rather undo, one message puts the previous version back.
Send him your first change.
Free for 3 days. No login, nothing to install. Start with Wes alone or take the whole team.