Better conversations about seasonal dining menus start earlier
With seasonal dining menus, one link replaced a drifting set of emails. First discussions begin prepared, and the boundary around sensitive documents is explicit.
- Client
- Lebanese mezze restaurant
- Region
- Chandler, Arizona
- Size
- 15 staff, one locally managed operation
- Timeline
- 10 working days
How it went, course by course
Four stages, in the order they happened, in the words the project was recorded in.
01 · Where they started
Preparation advice for seasonal dining menus went out by hand from the Lebanese mezze restaurant, one rewritten email at a time. The wording drifted a little further with each sender.
02 · What was going wrong
When it comes to seasonal dining menus, the notes drifted out of sync, and people arrived at the first conversation with very different ideas of what was needed.
03 · What we built
One maintained page covers visit date, party size and menu interest and gives an overview of the current menu and staff-reviewed dietary guidance. Online forms stay limited to initial inquiry details, with sensitive records handled through the approved internal process afterwards.
04 · What changed
With seasonal dining menus, one link replaced a drifting set of emails. First discussions begin prepared, and the boundary around sensitive documents is explicit.
What went into it
- Preparation page
- Minimal initial fields
- Staff-approved instructions
- Secure-process signposting
10working days
The time it took
After content approval, including staff review and handover. A new site goes live in 7 days on The Folio; work like this runs through your monthly revisions or alongside the build.
Book a demoI point people to the seasonal dining menus guide and the explaining is done. No more hurried rewrites of the same email at four o'clock.
Questions about this project
How long did this project take?
10 working days after content approval, including staff review and handover. The clock starts once the restaurant has approved the content, so the time is spent building and checking rather than waiting on copy.
Which parts of the offer did it use?
Preparation page, Minimal initial fields, Staff-approved instructions, Secure-process signposting. On this site that work sits under menu pages set like a printed menu and reservations and enquiries land where you already work, which are included on every plan from The Folio up.
Why is the restaurant not named?
We describe each client by the kind of restaurant it is and where it is: here, a lebanese mezze restaurant in Chandler, Arizona, 15 staff; one locally managed operation. The quote is credited to Matilda Netherton, weekend supervisor. We never publish a trading name, address, logo or photograph.
Could the same work fit our restaurant?
If guests read your pages or send you inquiries before they visit, most likely. Nothing here was a custom add-on: plans start at $117 a month, the $647 build fee is invoiced only after launch, and a walk-through on your own menu shows what the equivalent would look like for you.
See what this would look like on your menu
A live walk-through of the site you would get, in about 30 minutes. Plans from $117 a month, the $647 build fee invoiced only after launch, domain and hosting included.
Or compare the plans and pricing first.