Food & drink
A website for a restaurant
The brief for a restaurant, bistro or café: a menu people can read on a phone, the hours, the way to book, and what makes the place worth the trip.
In short
For a restaurant whose guests read the menu on their phone. Gets your assistant to build the menu as a real page with prices and allergens, the hours and the book button first, groups and events with a form, and to update the menu the day the kitchen changes it. Published with SayLive.
What this prompt asks your assistant to build
Written as you would say it. Paste it as is, then answer what your assistant asks.
I want a website for my restaurant, built in this conversation and published with SayLive. We serve lunch and dinner, the menu changes with the season, and most guests look at the menu on their phone before they come. The site has one job: make someone decide to come tonight, and let them book without calling. Before writing. Look us up (Google Maps, the reviews, the booking platforms, our social accounts), tell me what you found, and ask me one question at a time for the rest: the current menu with prices and allergens, how people book, the group policy, the photographs I have, what regulars come back for. Never invent a dish, a price or a review. Then propose the site plan, page by page, with what each page says and where it links. I validate, then you write. The pages. Home: what kind of place this is in one sentence, tonight's hours, the book button, three dishes with photographs. The menu as a real page, not a PDF: by service and by course, with prices and allergens, readable on a phone with one thumb. The kitchen and the people: who cooks, where the produce comes from, since when. Groups and private events: capacity, set menus, how to ask, with a form. Find us: address, map, parking or transport, full hours by day with the closing day, a tappable phone number, children and dogs welcome or not. And an FAQ with the eight questions we get on the phone. The tone. The way we talk to a guest at the door: warm, short, concrete. No "culinary journey". Dish names as they are on the menu. So people find us. Write what people type: restaurant and the neighbourhood, the kind of cuisine, open on Sunday, lunch menu, private dining. One title and description per page, one H1, the hours and the address in the footer of every page, and the menu page updated the day the kitchen changes it. Technically. A static site, fast on a phone: photographs in WebP and resized, the map loaded on tap, no third-party script and no cookie banner since we track nobody. The book button links to the tool we already use; the form is for groups and events. With SayLive. I drop the photographs in the media library, you place them. When I say publish, publish and give me the address. The day the menu changes I tell you the new dishes, you edit the page and republish; if a version is worse, we go back to the previous one. When I am happy, I connect our domain.
What to have at hand before you paste it
- Your business name, address, opening hours, phone and email.
- Five to ten photographs you own the rights to.
- Three concrete proofs: years in business, a certification, a number that means something.
- The current menu with prices and allergens, as a text or a photo.
With SayLive, even better
What you get with SayLive on top
This prompt is enough: pasted into any assistant, it gets you a good site. Connected to SayLive, the same assistant works with what is held back here, with nothing to install:
- The SayLive skills, loaded by themselves: the research on your business before a line is written, the floor a page has to reach, the SEO plan with its queries and internal links, the structured data, and the critical review the assistant gives its own work before publishing. Included with every site.
- The Blueprint "Restaurant": what a specialist of your trade knows and this prompt does not say. The questions to ask before the first line, the pages a site of this kind needs, what goes wrong in this trade, and the claims never to make unchecked. Bought once, for the site, 29.
- Alma, our designer agent: an art direction that holds from one conversation to the next, rather than your assistant's default style. Recruited once, 99.
- A human, if you want one: the Boost, 499 per expert day, when you would rather have a person take the site in hand.
And with every published site: 150 publications, 50 MB of media, 50 form messages, 50 review tickets, your own domain connected, and the previous version back in one sentence.
Frequently asked questions
Why a menu page instead of a PDF?
A PDF is unreadable on a phone and invisible to search engines. A menu page is both, and your assistant updates it in one sentence when the season changes.
Can the site take bookings?
It links to the booking tool you already use, or shows the phone and the hours. The form that comes with the site is for groups and events.
How often should the menu change online?
Every time it changes in the kitchen. Tell your assistant the new dishes, it edits the page and republishes; the previous version stays available for a rollback.