Services

Restaurant websites that start with the menu.

Almost everything a restaurant website gets judged on is one thing: whether somebody standing on a sidewalk can read today's menu on a phone without pinching to zoom.

The most common restaurant website problem is not the design. It is a menu that lives in a PDF, uploaded whenever somebody remembers, opening in a document viewer that does not reflow text and cannot be read at arm's length.

A PDF also cannot be updated by the person who knows what changed. It goes back to whoever made it, which means it lags reality by however long that takes — and a menu that lags reality is worse than no menu, because the price on screen is the price the customer expects.

The menu is structured data, not a document

Every item is a record: name, description, price, section, and whatever flags matter to your kitchen — vegetarian, gluten-free, spicy, contains nuts. Not a line of text inside a layout, a field you can change on its own.

That structure buys three things a document cannot:

  • You change a price without calling anybody. Edit the field, save, it is live.
  • Eighty-sixing an item is a toggle. It greys out or disappears immediately and comes back the same way, without re-exporting anything.
  • Seasonal sections switch cleanly. A winter menu can be built ahead, held back, and turned on the day it starts.

Because the same records drive the page, the ordering flow, and the structured markup search engines read, the menu is described once and stays consistent everywhere it appears. A PDF is legible to a person and close to opaque to everything else.

Ordering direct, on the processor you choose

Ordering runs through whichever payment system you already use or want to use. Stripe if you want a straightforward processor and nothing else attached. Square if you are already taking card payments in the room and want one account behind both. Toast or Clover if you run one of those as your point of sale, in which case ordering should tie into the system your kitchen already prints from rather than becoming a second menu somebody has to keep in sync.

The structural argument for taking orders on your own site is simple and worth stating plainly. A third-party delivery marketplace charges a commission on every order it hands you. The rate depends on the platform and on your agreement, so read your own contract rather than a number off a blog — but an order placed directly on your site does not carry that commission at all.

That does not mean dropping the marketplaces. They bring discovery you would not otherwise get. It means the regulars who already know your name have somewhere to order that does not take a cut, and over a year that difference is the whole argument.

More than one room

Multiple locations are where most restaurant templates fall apart. Each location gets its own page, its own address and phone number, and its own hours — because the second location almost never keeps the same ones.

Menus work the same way. Where locations share a menu, it is defined once. Where one has items the other does not, that location overrides just those items instead of maintaining a whole second copy. Each address also wants its own Google Business Profile, since a customer searching from two towns over is being shown the nearest one.

The things that quietly go stale

Hours are the other field that costs real money when wrong. Regular hours, holiday closures, and the fact that the kitchen often stops before the room does. All of it stated on the page, and matching what the profile says, because a customer who drives over on a Monday you are closed does not come back on Tuesday.

What you control afterward

Menu items, descriptions, prices, availability, hours, and closures. All of it yours to change, with no ticket and no wait. The site itself is static files that load fast on a phone with one bar, which is the condition most people are actually in when they look you up.

Somebody deciding where to eat is holding a phone and has about eight seconds of patience. The build is shaped around that person and nobody else.

No restaurant site is live yet, so there is nothing to show you here. A free audit of the site you already have is the honest way to find out whether I would be any use, and the other services carry work you can look at.

Twenty free minutes. Bring your worst website.

Or no website at all. A free 20-minute consult, a straight answer, and zero pressure either way.