Fixed quote after a free call

A restaurant website with online ordering that guests can use on their phone

We design and build a restaurant website, or rebuild an old one, that loads fast on a phone, shows menus as real text rather than PDFs, puts reservations, private dining enquiries and online ordering one tap away, and carries the local SEO basics. Ordering connects to your POS through its official route, such as Toast or Square online ordering, so you avoid paying a commission on every direct order. Projects typically cost $5,000 to $15,000 and take six to ten weeks.

The problem

Why restaurant websites lose bookings and orders

Guests check the website on their phone before they book or order, usually from a map listing. A slow page, a PDF menu that needs zooming or a missing reservation link sends them back to the map or to a delivery app that charges the venue a commission.

Many restaurant sites were built once and left. Menus are out of date, opening hours disagree with Google, allergen notes are missing and nobody knows how to change anything without the original designer.

What we build

What our restaurant website design includes

Menus as real text

Menus as web pages the team can edit, with prices, dietary icons and an allergen note pointing guests to staff.

Reservations and events

Your reservation widget and a private dining form that feeds the events workflow.

Direct online ordering

Ordering through your POS's online ordering, such as Toast or Square, or a custom flow built on the POS API where the vendor allows.

Local SEO basics

Restaurant schema, consistent name, address and phone, location pages for groups and a technical audit before launch.

Accessible and fast

Readable contrast, keyboard navigation, alt text and compressed images, checked with PageSpeed Insights.

Easy updates

Hours, menus, specials and events editable by the team without a developer.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Guest finds you

    A guest arrives from Google Maps, search or social.

  2. 02 Automated

    Menu and details

    Menus, hours and policies answer their questions on the page.

  3. 03 Automated

    Book or order

    They reserve, enquire about an event or order online.

  4. 04 Team review

    Team keeps it current

    The manager updates menus, specials and hours in simple screens.

  5. 05 Manager or chef decides

    Menu and allergen content

    Dish descriptions and allergen notes are approved by the chef before publishing.

How it behaves

How the website and ordering behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • A fast page with today's menu as real text
  • Reservations and ordering one tap away
  • Clear hours, location and allergen notes

What the team sees

  • Orders landing in the POS like any other ticket
  • Event enquiries in the events workflow
  • Simple screens to change menus and hours

What the automation does

  • Routes forms and orders to the right system
  • Keeps schema and the sitemap current for search engines

Edge cases and fallbacks

Online ordering is paused at a busy time
The site shows a clear message and the phone number.
Old URLs from the previous site
Redirected to the matching new pages so links and rankings carry over.
Reservation widget is down
The page shows a request form and phone number instead.

Architecture

A restaurant website with ordering at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Google and social Maps, search, links Website Fast, accessible Reservations Platform widget Online ordering POS-linked Event form Private dining POS and tools Toast, Square, n8n Manager Menus and hours
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 Guests arrive from Google Maps, search or social links.
  2. 2 Menus, hours and policies load fast on a phone as real text.
  3. 3 Reservations, event enquiries and orders flow to the platform, POS and workflows.
  4. 4 The manager keeps menus and hours current; the chef approves allergen notes.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Restaurant website with online ordering project plan

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    About 1 week

    Current site, map listing, POS ordering options, reservation platform and competitors nearby.

  2. 02

    Content and design

    About 2 weeks

    Page plan, menus, photography plan and design on your brand.

  3. 03

    Build

    2 to 4 weeks

    Pages, menu editor, reservation and ordering links, event form and schema.

  4. 04

    Test

    About 1 week

    Speed, accessibility, ordering tests, redirects and a technical SEO audit.

  5. 05

    Launch

    2 to 3 days

    Go live, update Google Business Profile links and submit the sitemap.

  6. 06

    Support

    Ongoing

    Optional monthly care for menus, events and security updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Laravel or WordPress Tailwind CSS Toast Online Ordering or Square Online (or the POS API) Your reservation widget Schema.org Restaurant markup PageSpeed Insights and Search Console

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and audit

    Current site, map listing, POS ordering options and competitors.

    $500 – $1,200

  • Content and design

    Page plan, menus and design on your brand.

    $1,200 – $3,500

  • Build

    Pages, menu editor, ordering, reservations, event form and schema.

    $2,300 – $7,300

  • Integrations

    POS ordering, reservation widget, workflows and Search Console.

    $500 – $1,800

  • Testing and launch

    Speed, accessibility, ordering tests, redirects and launch.

    $500 – $1,200

  • Total project estimate

    $5,000 – $15,000

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A custom ordering flow on a POS API sits at the upper end. Hosting, domain, POS online ordering and payment fees are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Hosting and domain: Billed by your hosting provider and registrar.
  • POS online ordering: Your POS vendor's own plan and card processing fees.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Google booking and order links

Google Business Profile lets you add booking links to your listing and mark a preferred one.

Source: support.google.com

EU and UK: allergen information online

Allergen information rules for non-prepacked food also cover distance selling, so online menus carry clear allergen information or a route to staff.

Source: www.legislation.gov.uk

EU: AI disclosure if you add chat

An AI chat on the site must tell people they are interacting with an AI system under Article 50 of the EU AI Act, from 2 August 2026.

Source: artificialintelligenceact.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Restaurant online ordering website questions questions, answered.

Many venues use both: delivery apps for reach, and direct ordering on their own site for regulars, without the per-order commission. We set up direct ordering through your POS and link to the apps where it makes sense.

Usually the one your POS offers, such as Toast Online Ordering or Square Online, so orders land in the kitchen with no re-keying. A custom ordering flow on the POS API is possible where the vendor allows partner or custom access.

PDF menus are slow on phones, hard to read for screen readers and harder for search engines to understand. Text menus fix all three and are easier to update.

Our fixed quotes range from $5,000 to $15,000 depending on pages, locations and ordering. Hosting, domain and POS ordering fees are billed to you directly.

Yes. Menus, specials, hours and events are editable without a developer, and we hand over notes and logins.

Track online orders and reservations from the site, event enquiries, calls from the map listing and Search Console impressions for menu and location pages.

Free 20-minute call

Want this for your restaurants & café?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call