Side-by-side, in writing
Four ways to put a restaurant on the web.
Each option below works for someone. The honest version of which one fits depends on budget, calendar, and what you want to do for yourself. Pricing is current as of May 2026. Where a vendor publishes a number, we cite it; where they don’t, we list the typical contract range from operators we’ve talked to.
| DIY template Wix · Squarespace · Shopify |
Restaurant vendor BentoBox · Toast Sites · Popmenu |
Local web agency DMV generalist shops |
Muntin Digital One operator-built studio |
|
|---|---|---|---|---|
| Money | ||||
| Up-front cost | $0–$300 self-build, then your hours | Often $0 setup, locked behind a contract | $8,000–$25,000 typical first build | $2,500 Essentials · $5–9k Full Service · $8–15k+ Group |
| Monthly | $17–$49 platform, plus apps | $165–$295/mo typical, climbs with add-ons | $0 if hosted yourself, $80–$300 if managed | $0 to leave it alone · $99/mo Care Plan Light · $225/mo full Care Plan |
| Year-two cost | $200–$600 platform + apps + your hours | $2,000–$3,500 in subscriptions, no equity built | $2,000–$6,000 retainer or change-orders | $1,200/yr if you hold a Care Plan Light · $0 if you don’t |
| Transaction take | Stripe/PayPal fees only | Often a 2–5% take on online orders, on top of the subscription | None — you keep the processor relationship | None. You own the Stripe account and the data behind it. |
| Ownership | ||||
| Domain & DNS | Yours, if you bought it separately | Often delegated to the vendor; recoverable but painful | Yours | Yours, in your registrar account, day one |
| Codebase | Locked into the platform | Locked into the platform; export is read-only HTML | Yours, usually delivered as a Git repo | Yours, in a Git repo, with the build instructions in the README |
| Customer data | Shared with the platform; export available | Co-controlled with the vendor; portability varies | Yours | Yours. The studio holds only what the engagement letter names. /never/ #2. |
| Who actually builds it | ||||
| The person at the keyboard | You, on Saturday nights | A salesperson, then a templating tool, then support tickets | Whoever’s available — designer, intern, subcontractor | Don. The same person who quoted, designs, codes, and ships. Two builds at a time, no exceptions. |
| Restaurant operating experience | Yours | Generic restaurant sales playbook | Variable; usually none | 14 years on the floor. Currently running front-of-house at a DMV restaurant. ServSafe certified. |
| First reply turnaround | n/a | Sales rep within an hour, support ticket within 24–72 | 1–3 business days | Mondays through Fridays, within 4 hours |
| Restaurant-specific things that often go wrong | ||||
| Hours visible on phone, above the fold | Theme-dependent; often buried under hero photo | Yes, but inside their template | Depends on the designer | Required. Verified on the audit before launch. |
| Schema for menu, hours, reservations | App-dependent, usually partial | Yes, mapped to their CMS | Variable | Restaurant + LocalBusiness + Menu + OpeningHoursSpecification, validated with Google’s Rich Results Test before publish |
| EN/ES menu page | Manually duplicated; usually drifts | Add-on, paid | Quoted as extra scope | Native bilingual mirror, hreflang stamped, in the base build |
| Mobile LCP under 2.0s on 4G | Rare on default themes | Mixed; depends on the template chosen | Depends on the developer | Block-merge gate. If a page misses 2.0s, it doesn’t deploy. |
| When things change | ||||
| Updating Thanksgiving hours | You log in, find the right widget, and hope | You email support | You email an account manager and wait | You email Don — or it’s already done if you’re on a Care Plan |
| If you outgrow this option | Migration is a manual rebuild | Export is partial; rebuild required | Hand-off depends on the agency | You already own the codebase. The studio writes you a hand-off doc on the way out. |
| If the vendor changes the rules | You change with them | You change with them, or pay to leave | Doesn’t apply — but the agency can fold | Doesn’t apply. Stack is open-source: HTML, CSS, vanilla JS, Cloudflare. No proprietary CMS to lose. |
| Honest fit | ||||
| Best for | Coffee shops, single-location concepts under $200k revenue, owners who enjoy this | Multi-unit ops who already use Toast or BentoBox for POS, want sales-led onboarding | Any operator with a generalist agency relationship that’s working today | Independents from $200k–$5M revenue who want a custom site, posted pricing, and to talk to the person who builds it |
| Worst for | Anyone whose hours and menu change weekly | Anyone who’d rather not pay a transaction take in perpetuity | Operators who want the person quoting to be the person building | Anyone who needs five active builds running this quarter — the studio runs two at a time |
Pricing dated May 2026. Where a vendor publishes a number, we cite it. Vendor-side claims (“often $0 setup,” “2–5% take”) reflect contract terms reported by DMV operators we’ve interviewed in 2025–2026. Spot a number that’s wrong? don@muntin.digital — corrections land in /changelog/ within two business days.
The honest version in three lines.
If your hours and menu rarely change and you enjoy fiddling with software, a Wix template is the cheapest answer. Don’t hire anyone.
If you already run Toast or BentoBox for POS and the website is a row in that bill, the path of least resistance is staying inside that vendor’s ecosystem. Negotiate the take-rate.
If you want a site that loads fast, reads bilingual, owns its own data, and gets fixed by the same person every time — that’s where the studio fits. See the three tiers, or send a one-line note and a written quote will arrive within two business days.
Sister surfaces