How to hire a restaurant web designer, written by one.

Walk into any restaurant’s Friday-morning inbox and you will find three pitches sitting on top of the booking confirmations: a Wix reseller offering a $99-a-month “done-for-you” site, a freelance graphic designer who builds websites on the side, and an agency promising AI-powered restaurant marketing for $24,000. The hard part of hiring a restaurant web designer is not finding one. The hard part is telling them apart. What follows is the honest version — the three kinds of builder, what each one is actually selling, what the work is worth, the ten questions that separate the real from the resold, and the red flags that keep coming back. The piece reads as buyer-protection because that is what it is, and because the only operators who ever do well hiring a builder are the ones who learned to vet first.

The three kinds of “web designer” (and what each really sells)

Three kinds of builder pitch restaurants, and the labels they use rarely match the work. The template reseller sells a platform subscription dressed as a build. The freelance generalist sells time and craft. The specialist sells an operator-owned system.

The template reseller’s margin is the platform’s monthly bill, marked up. The work is usually a Wix, Squarespace, or BentoBox template, lightly customized, billed at a low one-time fee plus an ongoing “maintenance” subscription that conveniently covers the platform’s own rent. The freelance generalist builds in WordPress, Webflow, or a custom stack — usually fine craftsmanship, usually no restaurant-specific reflexes. The restaurant specialist’s portfolio is restaurants only, the writing on the site reads like a menu, and the integrations (Google Business Profile, schema, ordering, reservations) are familiar territory rather than research. The price bands sort accordingly, and so does ownership: the reseller’s default is the platform owns the keys, the generalist’s default is negotiable, the specialist’s default is the operator owns everything. Knowing which one you are talking to in the first ten minutes is the difference between a build and a rental dressed up as a build. The companion piece on the best restaurant website platform covers the platform half of the same decision.

What a restaurant website actually has to do

Before vetting builders, name what the site is for. A restaurant website is an owned channel that has to do six jobs cleanly: answer the search query, hold the menu, hand off the booking, take the direct order, route the call, and feed the schema.

Search-query handling means the page reads cleanly when Google quotes it, which is mostly a writing job. Menu means the live menu in real HTML — not a PDF, not a photographed laminated card, not a Canva image — because Google’s extractor and an AI assistant both have to read it as text (the full case is in how to put your restaurant menu online). Booking is the click that hands the guest to OpenTable, Resy, or whichever reservation system you run, in one tap from the home page. Direct ordering is the click that keeps the transaction off a 15-to-30-percent commission platform. Routing the call is the phone-number link that opens the dialer on mobile. Feeding the schema is the structured-data block that names the cuisine, hours, address, and menu so the result reads correctly in search and Maps. A restaurant specialist builds for these six jobs by default. A generalist asks what they are. A template reseller hands you a template that does two of them.

The implication for hiring: if the builder you are talking to cannot itemize these six jobs without prompting, you are not talking to a restaurant specialist. That is fine in some cases — a known freelance generalist working under a tight brief can build all six on instruction. It is not fine in others. A reseller will quote the same monthly bill regardless, because the bill is the product.

What it’s fair to pay

The fair-pay question splits along the same three kinds of builder. DIY-assisted runs roughly $0 to $500 plus a monthly platform bill. Freelance runs $2,500 to $8,000 one-time. Restaurant specialist runs $8,000 to $25,000 or more. The wide bands track scope, not skill alone.

DIY-assisted means the operator builds on Squarespace, Wix, or a similar platform — the cash cost is the template fee, the platform’s monthly rent ($16 to $40 typically), and a domain registration of about $15 a year. Add an optional one-time consultation with a freelancer to clean up the menu page and you are still well under $500 cash. Freelance one-time fees cover a five-to-seven-page brochure build on WordPress or Webflow with a known menu, basic Google Business Profile alignment, and one or two feedback rounds. The $8,000 ceiling reflects what custom-restaurant pricing actually quotes for a clean independent build, as of May 2026; varies by scope. Specialist pricing covers everything the freelance band covers plus integrated ordering, menu schema, reservation handoff, photography direction, page-speed budgets, and a content workshop on the menu copy itself. The $25,000-and-up ceiling is the high end of independent specialist work and reflects what published agency-directory benchmarks (Clutch, GoodFirms) report for the same scope.

Where the money goes inside each band matters as much as the headline number. A reseller’s monthly bill funds the platform’s rent first and the builder’s margin second; a freelancer’s one-time fee funds the build and nothing else; a specialist’s fee funds the build, the integration work, and a finished asset the operator keeps. The chart below walks each kind’s monthly-vs-one-time split so the “cheap” option does not stay cheap on the second look.

The 10 questions to ask before you hire

Ten questions, asked in order, sort the builder inside thirty minutes. The first three name the builder kind. The next four sort scope and writing. The last three sort ownership — the bucket most operators forget until handoff.

Ask them on the discovery call, not by email; the speed and texture of the answer is half the signal. Builders who have done this for restaurants answer in concrete examples. Builders who have not answer in adjectives.

1. Show me three live restaurants you built — not designed — in the last twelve months. “Designed” can mean a moodboard; “built” means the live URL is the one they shipped. Three live URLs that 200 today is the floor.
2. Which platform or stack do you use, and why? A clean answer names one or two and the reason for each. A reseller answers with the platform’s marketing language. A specialist answers with the menu-page tradeoff that pushed them there.
3. What does your process look like, week by week? Two weeks for a freelance brochure; four to twelve for a specialist build. Vague timelines mean the builder is winging it.
4. How do you handle the menu — PDF, image, or live HTML? Only live HTML is a real answer. The PDF and the image both fail the schema, the AI extractor, and the screen reader at the same time.
5. How will the site rank for “[my cuisine] near [my city]” in six months, and how will I measure that? The honest answer names Search Console, the Map Pack, and the slow signals — not a guarantee.
6. Who writes the copy — you, me, or someone you bring in? A specialist either writes it themselves or runs a workshop with the operator. A reseller hands you a template with “Welcome to our restaurant” placeholder text.
7. What happens if I want to change the menu next Tuesday? A real answer names a dashboard or a one-line edit. A bad answer is “send me an email and I’ll get to it.”
8. Who owns the domain name at the registrar, and is the registrar account in my name? The answer must be “you, in your name, at a registrar you control.” Anything else is a lock-in.
9. Who owns the source code and the content at handoff? “You” is the only correct answer. If the builder keeps it “for support reasons,” you are renting.
10. What does it take to leave you? A real builder names a clean export, a registrar transfer code, and a working handoff checklist. A reseller cannot answer this question.

The pattern across all ten is the same. The builder either gives a one-sentence answer with a concrete artifact attached, or hedges with platform marketing language. The first kind builds. The second kind resells.

Red flags

Some warning signs repeat across enough hiring cycles that they are worth keeping as a checklist. None of them are deal-breakers on their own. Three of them together is the signal to walk.

The vetting failure is rarely a single red moment; it is a pattern of small ones that the operator notices in retrospect.

• No portfolio. The “NDA” explanation is almost always cover for “no live work to show.” A real builder has at least three live URLs and is happy to send them.
• The monthly “maintenance” tied to platform lock-in. “$99 a month and we handle everything” is the reseller’s default pitch. The everything is mostly paying the platform’s rent and keeping you from leaving.
• No written contract. A handshake build sounds friendly; it ends in a dispute about scope, ownership, or timing within the first six weeks. A two-page contract with deliverables and ownership terms is the floor.
• “We’ll handle the SEO.” Spoken alone, with nothing measurable behind it, this means “we will charge you for it.” A real answer names the metrics (Map Pack, Search Console, organic clicks) and the cadence of the report.
• The portfolio is all moodboards. Pretty mockups of restaurants that never launched is a designer, not a builder. Restaurants need a live site, not a Figma deck.
• The platform is the answer to every question. “Our platform handles that” is fine once. Said five times in a discovery call, it means the builder cannot work outside the platform’s defaults.
• The price reads as too low. A $500 custom build means corners cut on the menu, the schema, the photos, or the ownership terms. The math has to work for the builder too, or the build will not get finished.
• The price reads as too high without scope to match. $35,000 for a five-page brochure site means the agency is selling brand, not build. Ask what is in the price, line by line.
• No reference call. “I can give you names but they prefer not to be contacted” means no calls have ever happened.
• The contract names hosting and licensing terms that survive cancellation. If a clause says the platform keeps the content or the code after you leave, you do not own the site you paid for.

DIY vs hire: a quick honest test

The honest test of whether to hire at all is three questions: Is the site the front door of a business that runs on bookings or orders? Does the menu change weekly? Does the operator have ten free evenings? The answers route the decision cleanly.

If the site is genuinely the front door — the booking or order flow that funds rent — hire someone whose portfolio shows the integration working. The risk of a sloppy front door compounds: every leaked booking is gone, every search result that names the wrong hours costs a cover. If the menu changes weekly and the operator is comfortable in a CMS, a DIY-assisted launch followed by a freelance audit at month three reads as fair work; the editorial control is worth more than the polish a specialist would add. If the operator does not have ten free evenings, do not pretend they do; the half-built DIY site that sits in draft for nine months is the most common outcome of trying to save the freelance fee.

The case for hiring is strongest where the work is restaurant-specific and the cost of getting it wrong is recurring. Menu schema, Google Business Profile alignment, page-speed budgets, accessibility on the menu page, and the reservation handoff all have correct answers that a generalist will improvise. The case for DIY is strongest where the site is genuinely a brochure, the menu is stable, and the operator wants editorial control. Neither path is wrong; pretending the wrong one fits your case is.

Frequently asked questions

How much does it cost to hire someone to build a restaurant website? As of May 2026, DIY-assisted runs $0–$500 plus monthly platform rent; freelance $2,500–$8,000; specialist $8,000–$25,000+. Varies by scope — see the pricing guide.

Should I hire a freelancer or an agency? A freelance generalist fits a simple brochure build with a known menu and no ordering or reservation stack. A specialist or small agency fits when the site has to carry ordering, schema, reservations, and ongoing edits. The decision is scope, not status.

Will I own the website and domain? Only when the contract names ownership explicitly. The default with many builders and platforms is that they keep the domain, the code, or the content. Verify domain registrar, source code, and content rights before signing.

How long does a restaurant website take to build? DIY off a template runs about a week of focused evenings; freelance two to six weeks; specialist four to twelve weeks because the integrations and schema work inside the same project.

Do I need a specialist or will any web designer do? A generalist can ship a brochure site. The restaurant-specific work — Google Business Profile alignment, menu schema, ordering flow, page-speed budgets, photo specs — usually needs a specialist to ship correctly.

What good looks like

What good looks like is the same shape regardless of who builds it. The operator owns the domain, the source code, and the content. The site reads as the restaurant, not as a template. The price was a number, not a monthly rent.

Good builders ship sites that load in under two seconds on the cellular connection a guest actually uses, render the menu as live HTML the AI extractor and the screen reader can both read, hand off the booking in one tap, route the direct order off a 30-percent commission marketplace, name the cuisine and the hours in schema, and answer the question the search query was actually asking. Good builders also disappear cleanly when the operator wants to leave — a clean export, a registrar transfer code, no recurring lock-in. The work is not romantic. It is craft applied to a specific business problem, billed honestly, and handed off to the operator at the end.

The way Muntin works is the same shape: every build ships under the operator’s name at a registrar the operator controls, the code lives in a repository the operator owns, the writing reads like the restaurant, and the price is a number on a page. If that shape fits the project — a real restaurant site with the integrations done correctly the first time — the studio is one of the options. If a freelance generalist fits the scope better, the pricing guide and this hiring guide are written to help the operator find one. Either path is fine; the operator-owns-the-result rule does not bend. Compare the Muntin options at studio compare when the scoping conversation is ready.