Our process - From a live restaurant URL to a site guests can use.
Audit the current site, build the pages around the venue, then stay on for menu and hours changes. For a new brief, start with the free website audit.
The live URL
Send the current restaurant website. We look at the homepage, menus, mobile layout, and whether a guest can book or order without leaving for a marketplace.
That is the free restaurant audit. You get a short written note on what to fix first — then a recommendation and a price if you want us to do the work.
We do not start from a generic agency workshop. The brief is the venue: name, rooms, hours, and the path from a Google search to a table or a takeaway.
What we look at
- Live homepage
- Menus on a phone
- Address and hours
- Booking path
- Ordering path
- How findable the name is
The site, then the diary or the order
We design the restaurant website around the room — not a stock hospitality template. Menus, hours, and the next step have to work with a thumb.
If the brief needs reservations, TableGo can sit on the page. If it needs collection or delivery, dishGO sits on a branded ordering address. We only mark the work we actually did.
You see the live pages before launch. Menu copy and photos come from the restaurant; we do not invent a guest story for the site.
Launch and the week after
We check the site on a phone before it goes live: menu, number, address, and the booking or order control.
After launch the restaurant should not need a developer to change tomorrow's special. We stay on for menu and hours updates, and the odd landing page.
After launch
- Phone check. The guest path — search, site, book or order — on a small screen.
- Findable basics. A unique title, the correct address, and a sitemap Google can read.
- Menu changes. Hours, dishes, and the occasional event page without a rebuild.
How we work - What we will and will not do.
No invented review scores. No marketplace sold as “your own ordering”. TableGo and dishGO are named only when they are on the project.
- Only mark what we built. Website, Table bookings, or Online ordering — and only if that work is actually on the live site.
- Your domain. Guests book or order on the restaurant’s address, not a third-party brand’s homepage.
- Location sites for groups. Each dining room gets its own URL when the group has more than one site.
- Menus that can change. Tomorrow’s special should not wait on a developer sprint.
- A written next step. The audit is a note, then a price if you want the work — not a long workshop.
- UK company. Compera Ltd, 2019. The registered office is a Companies House address, not a showroom.