Chef-led restaurant websites from $117 a month, live in 7 days

A fully managed, custom-coded website for your restaurant: menu pages set as structured content rather than a PDF, a reservation and enquiry flow that connects to whatever you already use, 90+ PageSpeed, managed hosting, a free domain, and 2 researched articles a week on The Folio and The Broadside, 3 on The Standing Order. Nobody on your team edits the website directly; you send us changes and we make them.

7 days on The Folio, 10 on The Broadside while the AI Engine is trained on your menu and policies, and 15 on The Standing Order while the Content Engine's editorial calendar is built. The clock starts at the onboarding call, not at purchase, so the sooner the onboarding form is in, the sooner you are live.

No. The words on your menu are yours, since nobody outside your kitchen can describe a dish the way it was actually built. We handle the structure, the typesetting and the speed of the page the menu sits on, and researched blog articles are written separately from the menu itself.

You fill in the onboarding form and submit it. It asks for your current menu, your hours, your brand, your domain and where reservations and enquiries should land, and it takes about 15 minutes. If something is missing, submit anyway: you can send the rest by email or raise it as a ticket in your client portal, and it will not hold up the build. We then run one onboarding call to fill any gaps and agree the launch date.

It is your account with us, and you get it the day your site goes live. From the portal you request revisions such as a menu swap, raise a support ticket for anything that needs attention, send us files you still owe us, and message our team directly. Everything to do with your site runs through it, so a seasonal menu change never gets lost in an inbox. You never log in to the website itself; we handle that side.

Submit the onboarding form with your best current draft. Menus for chef-led restaurants change often by nature, so the launch menu does not need to be final; it needs to be typeset and live, and the first real update after that is simply your first revision.

A revision is any change request you send, and there is no limit on how much goes into one. Swapping the entire seasonal menu, adding a new wine list, or updating hours for a holiday closure: each is one revision, not one per item changed. 5 are included every month. After the fifth, each additional revision is a flat $20, with no cap on how many you can buy and no hourly billing anywhere. Every revision is completed within 2 to 5 working days, whatever the size.

Raise it in your client portal. You describe the change, attach the new menu or prices, and it lands with the team as a tracked request so you can see where it is. You can also email us or reply to any thread with our team, and we log it for you. Unused revisions do not roll over to the next month.

Yes, as long as it is submitted as one request. "Replace the current tasting menu with these six new courses and this new wine pairing list" is one revision regardless of how many individual dishes and prices it touches, which is exactly how a real seasonal changeover works for a chef-led kitchen.

Topics your future guests are searching for: dining guides for your area, context on your seasonal menu, and questions specific to your cuisine and neighborhood, each 2,500 to 3,200 words. They are researched and written around your actual restaurant rather than a generic template reused across clients.

2 a week on The Folio and The Broadside, and 3 a week on The Standing Order, at roughly four weeks a month, published to your site's blog automatically.

It answers common guest questions, such as dietary accommodations, dress code or private dining capacity, using information trained on your real menu, hours and policies, so a guest gets an answer without waiting for a phone call to be returned. It is included from The Broadside up.