The starting point
An earlier project had delivered a site and then vanished. Every question about updating bistro private dining content depended on reaching someone who no longer worked on it.
Case study, market town bistro
A bistro private dining site the team can run themselves
For bistro private dining, the site now comes with its own instructions for keeping it. Cover arrangements are a matter of reading a document, not interviewing former staff.
Where the room started
The situation before the work, in the team's own terms.
What was in the way
Day to day with bistro private dining, approval routes, update procedures and test steps existed in no written form. When the usual contact was away, the site simply froze.
What we built
The handover includes a page inventory, update instructions, a contact list and a brief check of the route to a private dining discussion with the restaurant. It names an owner and a backup reviewer for set-menu choices and room arrangements.
The plan features behind it
- Monthly revisions and a client portal5 revisions a month of any size, each done within 2 to 5 working days, requested from your client portal.
- Your domain, your content, and a clean move from the old siteDomain registered in your name, redirects from your old pages, and a content export if you ever leave.
Delivered for this client
- 1Page inventory
- 2Maintenance notes
- 3Backup reviewer
- 4Form check instructions
- 5Support contacts
25working days
How long it took
25 working days after content approval, including staff review and handover.
- Content approved
- Build and staff review
- Handover
What changed
For bistro private dining, the site now comes with its own instructions for keeping it. Cover arrangements are a matter of reading a document, not interviewing former staff.
Rooms this work fits
Launch-day me was grateful for the bistro private dining pages. Holiday-returning me was grateful for the documentation. The second gratitude lasts longer.
Have the same problem in your room?
A 30-minute walk-through of the site you would get, with your menu and your inquiries. Plans from $117 a month; The Table is live in 7 days and the $647 build fee is invoiced only after you approve the launch.
Questions about this project
Who was the client?
A market town bistro in Tulsa, Oklahoma, with 6 staff, one locally managed operation. We publish the kind of room and the region rather than the business name.
How long did the project take?
25 working days after content approval, including staff review and handover.
What exactly was delivered?
Page inventory, Maintenance notes, Backup reviewer, Form check instructions, Support contacts. The handover includes a page inventory, update instructions, a contact list and a brief check of the route to a private dining discussion with the restaurant. It names an owner and a backup reviewer for set-menu choices and room arrangements.
Could the same work be done for my restaurant?
Yes. This was built on our normal plans, from $117 a month with a $647 build fee invoiced only after launch. Tell us which step is slowing your team down and we will show you what we would change first.
Services behind this project
Each one has its own page with what is included and how it runs.
- Restaurant web design companyA restaurant web design company that designs, builds, hosts and updates the site every month, instead of handing over a page-builder account.
- Restaurant website templatesRestaurant website templates designed for bistros, wine bars and group dining spots, customized to your room instead of left generic.
Related case studies
Other projects that worked on a similar step or a similar room.
Tell us which step is slowing your team down
We will say plainly what we would change first, and what it would cost.