WHO WE BUILD FOR / RESTAURANTS & CAFÉS
Websites and automation for restaurants
Your best table shouldn't depend on whether someone heard the phone over service. We build the site people book through — and the workflows that handle enquiries while the kitchen is slammed.
WEBSITE ONLY · AUTOMATION ONLY · OR JOINED — EVERY SPEC SOLD SEPARATELY
Sound familiar?
What's still done by hand
Every one of these is a workflow waiting to exist. None of them needs new software your team has to learn.
THE REAL COST
A missed reservation call during Friday service is a table you never knew you lost. The maths is brutal: if the phone rings ten times over a dinner rush and three go unanswered, you're quietly running at a discount on your busiest night.
- Reservations arrive by phone during the exact hours nobody can answer it
- The menu PDF on the site is two prices out of date
- Party and catering enquiries sit in an inbox until the day after
- Feedback is a card on the table that nobody reads or files
What we'd build
Two pieces — take one, or join them
Each side is a separate engagement with its own scope and price. Plenty of clients start with one and add the other only when it earns its place.
PIECE A — THE WEBSITE
- A site with menus your manager edits — prices and specials, same afternoon
- Reservation requests that land in one place, with party size and time
- Event and catering enquiry forms that capture the details up front
- Photos and pages that load fast on the phones people browse on
PIECE B — THE OPERATIONS
- Reservation confirmations and day-of reminders, sent automatically
- Party enquiries routed to the manager with a drafted reply ready to send
- A feedback message after the visit — complaints routed to you, not to Google
- A chatbot answering hours, parking, and veg/allergen questions from your menu
Example workflows
Three we'd start with
Written the way we'd actually spec them — trigger, steps, outcome. Yours would be drafted from your operation, on the call.
WORKFLOW 01
The reservation catcher
TRIGGER: BOOKING REQUEST FROM THE SITE
- 01Guest gets an instant confirmation with the details
- 02The booking lands in your reservation sheet or system
- 03Day-of reminder goes out; cancellations free the table
The phone stops deciding who gets a table.
WORKFLOW 02
The party enquiry
TRIGGER: EVENT FORM SUBMITTED
- 01Details captured: date, headcount, budget, occasion
- 02A reply is drafted from your packages for the manager to approve
- 03No decision in 2 days → polite follow-up goes out automatically
Big-ticket enquiries answered the same day, every time.
WORKFLOW 03
The quiet feedback loop
TRIGGER: RESERVATION MARKED SEATED, NEXT MORNING
- 01Guest gets a one-question message: how was it?
- 02Unhappy answers route straight to the owner's phone
- 03Happy guests get the review link
Problems reach you before they reach the reviews.
Heard all day
The questions your customers repeat
A chatbot grounded in your own pages answers these in seconds, cites the source, and hands anything unusual to your team.
- “Do you have a table for four tonight?”
- “Are you open now? How late do you serve?”
- “Do you have vegetarian / Jain / gluten-free options?”
- “Is there parking nearby?”
- “Do you take large group bookings or host birthdays?”
Drawn in ink
What stays human
Automation earns its keep on the repetitive work. These lines don't move — they're where your judgment and your relationships live.
01
The food and the room — no workflow touches what made people come
02
Complaints — a bad night gets the manager's personal reply, not an autoresponse
03
Regulars — the system can flag that it's their tenth visit; the warm welcome is yours
Fair questions
Asked by restaurants & cafés
We take bookings on the phone too. Does that break this?
No — phone bookings can be typed into the same sheet or system the site writes to, and the reminder workflows treat them identically.
Can our manager really update the menu without calling anyone?
Yes. That's the CMS piece: menu items, prices, and specials become fields your manager edits, with a preview before publishing.
What about delivery platforms?
We don't replace them — but the site gives you a direct channel that doesn't take a commission, and workflows can log enquiries from anywhere into one place.
Can this handle no-shows on reservations?
Day-of reminders with a one-tap cancel cut most of them, and freed tables can go to a waitlist automatically.
We change the menu often. Is that a problem?
It's the point — the menu is editable by your manager, and the chatbot answers from whatever is currently published, so it's never quoting last season's prices.
Do we have to take both the website and the automation?
No. Every service is scoped and sold separately — website only, automation only, or a single workflow to start. The two compound when joined, which is why the page shows both, but nothing requires buying both.
Tell us what your team still does by hand.
Thirty minutes. You'll leave knowing what we'd build, what it would cost, and whether it's worth doing at all.
Prefer to write first? Use the full form.