A website for your restaurant
Almost everyone arriving at a restaurant website wants one of two things: the menu, or whether you're open. A site that makes either of those hard is failing at the only job it has.
What a restaurant site needs
The menu is the website
It is one of the most-visited pages on any restaurant site, and it needs to be real text on the page — current, and readable on a phone without pinching. A menu that's a PDF is the most common mistake in this category and the most costly one.
Hours have to be right, holidays included
Nothing burns goodwill faster than someone driving over and finding a locked door. Your hours will change — for holidays, for staffing, for the season — so what matters is that you can correct them yourself in under a minute, from a phone, on the day.
Most people are already nearby
A great deal of restaurant traffic is someone standing a few streets away deciding where to eat in the next ten minutes. Address, a map, parking, and how to find the door should never be more than one tap from wherever they land.
Reservations, waitlist or walk-in — say which
If you don't take bookings, saying so plainly prevents a bad first interaction. If you do, having it on your own page rather than only on someone else's platform keeps the relationship, the data and the fees.
Photographs of your actual food
Every restaurant site on earth uses beautiful food photography, so stock imagery is spotted instantly — and it quietly suggests the real food wasn't worth showing. A phone photograph of your actual plate beats a perfect photograph of someone else's.
Your team builds it with you
WrenTalks your business through with you and sets its look.
ScoutPlans every page and feature it needs.
ForgeBuilds it, and keeps building as you grow.
BelleWrites your emails and messages to customers.
HawkFinds what moves your numbers and says what to do.
What it costs
One plan, per site
Free
Your design and your plan for your first business, on a private preview.
$28 a month
Live: your first pass built on it, your site hosted at its own address and your own domain, payments into your own Stripe, your backend run for you, your data backed up every day, your code yours to download, and your edits.
Credits
After you see your first pass, $1 a credit, in packs of 25, 50, 100 or 200. They build each step of your plan, such as booking or a shop, taken only when you approve it.
0%
Steed takes nothing from your sales.
Cancel any time.
Questions
How do I change the menu when the specials change?
Edit it yourself. Once your site is Live, turn on Edit above your site in Steed and click the words you want to change; they go live when you save. Anything bigger, ask in chat and it waits for your yes.
Can people book a table through the site?
Yes. Tell Wren how you take tables (the times you seat, how many at once) and table booking goes on your plan, a step built with credits, taken only when you approve it. If you already use a reservations service, your site can link to it instead.
Do I need a separate site if I have more than one location?
Usually not. Tell Wren about every location and the plan accounts for each, because hours, menus and directions differ, and that's what people look for.