Case study No. 20
Instructions included: restaurant reservations after launch
Day to day with restaurant reservations, maintenance no longer depends on memory or on any single individual. Whoever picks up the task finds instructions, contacts and ownership written down.
Case docket
- Restaurant Tapas and wine restaurant, Savannah, Georgia
- The team 9 staff; one locally managed operation
- Built with Page inventory, Maintenance notes, Backup reviewer, Form check instructions, Support contacts 5 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
The business had previously been handed a website with no practical handover. Questions about maintaining restaurant reservations information meant tracking down the original designer.
What it cost the team
For restaurant reservations, simple updates became small crises of uncertainty. Without documented steps, the safest option was always to do nothing.
What we built
The fix, in plain terms
Documentation delivered with the site covers pages, procedures and contacts, and walks the team through the path to a booking response from the restaurant team. Reservation guidance and the current food menu have an assigned owner and a deputy.
The parts that went in
- Page inventory
- Maintenance notes
- Backup reviewer
- Form check instructions
- Support contacts
Timeline
25 working days, from sign-off to handover
Content approved
The working-day count starts once the restaurant has signed off the content that goes on the page.
Built
Documentation delivered with the site covers pages, procedures and contacts, and walks the team through the path to a booking response from the restaurant team.
Staff review
The restaurant's own team checked the work against how they actually take inquiries before anything went live.
Handed over
Live and handed over 25 working days after content approval.
After
What changed
Day to day with restaurant reservations, maintenance no longer depends on memory or on any single individual.
Whoever picks up the task finds instructions, contacts and ownership written down.
The restaurant reservations notes were tested by my absence, which is the only test that matters. My cover ran the site without calling me once.
Is your inquiry form costing you mornings too?
Show us your current site on a live walk-through and we will point at the first thing we would fix, and say so if it is not the website at all.
Questions about this project
How long did this project take?
25 working days after content approval, including staff review and handover. On our plans a new site goes live in 7 days on The Daily Menu, 10 on The Full Menu and 15 on The Tasting Menu, counted from the onboarding call.
What exactly did the tapas and wine restaurant get?
Documentation delivered with the site covers pages, procedures and contacts, and walks the team through the path to a booking response from the restaurant team. Reservation guidance and the current food menu have an assigned owner and a deputy. The pieces, in the restaurant's own list: page inventory, maintenance notes, backup reviewer, form check instructions, support contacts.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: The business had previously been handed a website with no practical handover. The quickest way to tell is a demo call, where we look at your current site and say plainly whether this is the fix it needs or whether something else matters more.
Is this part of a plan, or an extra?
It is part of building and running the site. The site features this project used: weekly updates so specials and hours never go stale (on every plan); hosting, security and uptime, handled (on every plan). Plans start at $117 a month, the $647 build fee is invoiced only after launch, and 5 revisions a month are included.
More case files
Related case studies
More projects for bars and gastropubs and restaurants that had the same problem.
- Gastropub with dining room, Chandler, ArizonaEvery restaurant reservations request has an ownerWith restaurant reservations, every inquiry has a name and a state attached to it.Read the case study
- Farm-to-table country restaurant, Harrisburg, PennsylvaniaA common reference for restaurant reservations questionsWith restaurant reservations, the same question now gets the same answer everywhere.Read the case study
- Thai family restaurant, Santa Rosa, CaliforniaEnding the restaurant reservations version confusionWhen it comes to restaurant reservations, the business maintains key information in one place and has a practical method for checking related pages.Read the case study
Related services
- Restaurant website redesignRestaurant website redesign that keeps your search rankings through redirects, replaces the old menu PDF and hands you a managed, custom-coded site.
- Restaurant website designRestaurant website design built around the menu page, mobile legibility and your own photography, on three managed plans from $117 a month.
- Websites for bars and gastropubsA website for a bar or gastropub where the drink menu gets equal billing with the kitchen
See the site you would get
About 30 minutes, on your screen, built around your menu and how your team takes bookings. Plans from $117 a month, with the $647 build fee invoiced only after launch.