No. 001 · chef-led restaurants
A restaurant website set with the same care as your menu
A managed, custom-coded website for chef-led restaurants: live in 7 days, 90+ PageSpeed, weekly updates, researched articles and hosting included, from one monthly fee.
The offer, plainly
- Plans from$117 a month
- Build fee$647, invoiced after launch
- Live in7 days
- Revisions5 a month, no size limit
- Speed90+ PageSpeed
- Domain and hostingIncluded
7 days
To launch on The Folio
5 a month
Revisions included, no size limit
90+
Google PageSpeed guaranteed
2/week
Researched articles, minimum
No. 002 · The problem
Most restaurant sites treat the menu as an afterthought
A menu built by a kitchen that cares about every word deserves a page built with the same care. Instead it usually gets flattened into a PDF, a page-builder block, or a template designed for an average restaurant rather than yours.
- The menuBefore:A PDF nobody can read on a phone without pinching to zoom.After:Typeset, structured content that reads correctly at any size.
- A seasonal changeBefore:Someone re-exports and re-uploads a file whenever they find an afternoon.After:You send the update; it is set and live within 2 to 5 working days.
- Search visibilityBefore:Search engines cannot read text trapped inside an image or a PDF.After:Every dish and description is real, indexable text.
- The wine listBefore:One long bulleted list with no grouping by region or glass.After:Grouped the way your staff actually talk about it at the table.
No. 003 · How it runs
The build, read like a course order
Three courses, served in order: what you send us, what we build, and what keeps the site current after launch.
Appetiser
Onboarding, in about 15 minutes
You send your current menu, hours, brand and where reservations should land. Anything missing can follow later; it never holds up the build.
Main
Built and typeset, live in 7 days
Your menu is set as structured content, the site is custom coded for speed, and one onboarding call fills any remaining gaps.
Dessert
Revisions and articles, every month after
Five revisions a month keep the menu current as the season changes, and researched articles publish weekly through your client portal.
No. 004 · What is included
Every page reads like it was set on purpose
- 01 Menu pages set like a printed menuThe tasting menu, wine list or small-plates list, structured and typeset, never a PDF.
- 02 Pages that open instantlyCustom-coded pages served from the edge, 90+ PageSpeed guaranteed.
- 03 Revisions built for a menu that changes5 revisions a month included, no size limit, turned around in 2 to 5 working days.
- 04 Reservations and enquiries land where you already workEnquiries route into any CRM, booking tool or inbox by API, Zapier or Make.
- 05 Researched articles published every week2 or 3 articles a week, 2,500 to 3,200 words, written for your kitchen and its area.
- 06 The AI EngineAI-assisted menu Q&A and guest support, trained on your actual menu and hours.
No. 005 · Who it is for
Six kinds of chef-led kitchen, six different sites
A tasting menu room and a neighborhood trattoria are not the same business, and their websites should not read like the same template with different colors.
See every sub-niche- 01Tasting menu restaurantsA site that sets a tasting menu the way the kitchen means it read
- 02Seasonal and farm-led kitchensA website built around a menu that moves with the season, not a static PDF
- 03Wine bars and small-plates roomsA site built around a list, not a set menu, for wine bars and small-plates rooms
- 04Neighborhood bistros and chef-owned trattoriasA website for the neighborhood bistro that runs on regulars and a menu people trust
- 05Supper clubs and pop-up chefsA website that can sell a one-night seating the way an ordinary restaurant sells a table
- 06Hotel and boutique-property restaurantsA restaurant site that stands on its own inside a hotel or boutique property
No. 006 · A specimen
This is the level of type your menu gets
Not a mockup: an actual proof of the type scale, spacing and rule weight every page on your site is built from. Fictional example menu, shown for illustration only.
Tasting menu · Five courses
Charred grape, burrata, sourdough crumb
01Aged sherry vinegar, torn basil, first-press olive oil.
Heirloom carrot, brown butter, hazelnut
02Whipped goat curd, carrot-top oil, toasted grain.
Line-caught fish, fennel, citrus
03Blood orange, fennel pollen, a thread of chili oil.
Set in Fraunces / Work Sans, the pairing every page on this site uses.
No. 007 · Pricing
Three plans, one build fee charged after you approve the site
Every plan includes the menu build, managed hosting, a free domain and weekly articles. Higher tiers add the AI Engine and the Content Engine.
The Folio
The website, fully managed
$117/ month
plus $647 build fee, invoiced after launch
- Live in 7 days
- 2 researched articles a week
Most chosen
The Broadside
Everything, plus the AI Engine
$247/ month + usage
plus $647 build fee, invoiced after launch
- Live in 10 days
- 2 researched articles a week
- The AI Engine
The Standing Order
Everything, plus the Content Engine
$597/ month
plus $647 build fee, invoiced after launch
- Live in 15 days
- 3 researched articles a week
- The AI Engine
- The Content Engine
No. 008 · What is in every plan
The full ledger, side by side
| Included | The Folio | The Broadside | The Standing Order |
|---|---|---|---|
| Typeset menu pages | Included | Included | Included |
| Managed hosting and SSL | Included | Included | Included |
| Free domain | Included | Included | Included |
| Revisions a month | 5 | 5 | 5 |
| Researched articles a week | 2 | 2 | 3 |
| The AI Engine | Not on this plan | Included | Included |
| The Content Engine | Not on this plan | Not on this plan | Included |
| Launch window | 7 days | 10 days | 15 days |
No. 009 · One revision, in detail
What actually happens when you send a menu change
Not a support ticket that sits in a queue. Here is the exact path a revision takes from your inbox to your live site.
- 01
You send the change
Through your client portal: a new course, a price, a whole seasonal menu. One request, whatever the size.
- 02
We set it in the structure
A person, not a script, types it into the existing menu structure and checks the line breaks and spacing.
- 03
We check it on a phone
The most common way your menu is actually read, before anything publishes.
- 04
It goes live
Within 2 to 5 working days, and the previous version is archived rather than lost.
No. 010 · What clients tell us
Our tasting menu finally reads on the site the way it reads on the pass. We send the new courses through the portal and it is set the same week, not whenever someone finds time in a page builder.
The wine list used to be one long bulleted mess. Now it is grouped by region the way we actually talk about it at the table, and updating a vintage is a two-line email, not an afternoon.
Guests stopped asking us the same three questions about dietary options once the AI Engine could answer them directly from our actual menu. Front of house noticed within the first week.
We announce a supper club date and the old ones do not vanish, they sit in an archive that makes us look like we have been doing this for years, because by now we have.
01 / 04
Illustrative examples of the outcomes clients report. Verified reviews are added after launch.
No. 011 · From the notebook
Notes on running a chef-led site
No. 012 · Questions
Answers on the offer
What exactly do we get for the monthly fee?
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.
How long until my restaurant's site is live?
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.
Do you write our menu descriptions for us?
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.
What happens straight after I buy?
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.
What is the client portal?
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.
What if our menu is not finalized yet when we sign up?
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.
No. 013 · Ready when you are
See your menu set the way it deserves
Plans from $117 a month, a $647 build fee invoiced only after launch, live in 7 days.