A productized offer · one page

The $1,500 Menu Drop-In.

Most restaurant websites have one page that’s costing them dinners: the menu. One hand-coded HTML page — mobile-fast, schema-marked, EN/ES — plugged into your existing Wix, Squarespace, or Shopify site without the rebuild. Seven business days, flat fee.

“The bones of your site work. The menu is the leak. Replace one page, not the whole house.”

$1,500flat · 7 business days · two free updates in 90 days

Active build slots

One drop-in a week, one operator · waitlist if booked

14

Years on restaurant floors — FOH, BOH, GM

<1.5s

Mobile first-paint target, every Drop-In, every time

EN/ES

Both indexed, hreflang-stamped, reviewed by a native speaker

1

Drop-In a week, one operator, no template

What lands on your customer’s phone.

Hand-coded, mobile-first, sticky call/directions/reserve, AVIF photos, schema-marked. The render below is the actual HTML pattern I ship — not a screenshot.

9:41
Casa Tita Call

Starters

Pulpo a la Planchasmoked paprika, fingerlings
18
Bone Marrow Toastsourdough, gremolata, sea salt
14
Beets & Chèvreheirloom, candied walnuts
13

Mains

Branzino al Limonewhole roasted, salsa verde
38
Cochinita Pibilslow-roasted pork, banana leaf
26

What this page does that yours doesn’t

Sticky call, sticky directions, sticky reserve — one tap, no menu hunt.

The category nav stays in reach as the guest scrolls. The call/directions/reserve bar lives at the thumb. AVIF photos load below the fold, never blocking first paint. The text is real type, not images of type.

First paint, 4G, real device

Wix template 14.2s
Drop-In 1.3s

From an actual side-by-side, August 2025: same restaurant, same connection, same Pixel 7. The Wix page made 47 requests; the Drop-In made 4.

What Google + Apple Maps see.

Every Drop-In ships with Restaurant + Menu + MenuItem JSON-LD, validated against Google’s Rich Results test before delivery. Your dishes, your prices, and your dietary tags show up in search the way they’re supposed to.

{ "@type": "Restaurant", "name": "Casa Tita", "servesCuisine": ["Mexican", "Spanish"], "hasMenu": { "@type": "Menu", "hasMenuSection": [{ "name": "Starters", "hasMenuItem": [{ "name": "Pulpo a la Plancha", "offers": { "price": "18.00", "priceCurrency": "USD" } }] }] } }

What lands in your inbox on day seven.

A full bundle, in writing, with the Loom that shows whoever maintains your existing site exactly where to paste the embed.

One hand-coded HTML page

Built on your brand. No template fight, no app dependency. Loads under 1.5 seconds on a phone on 4G.

Bilingual EN + ES

Both indexed, hreflang-stamped. ES is reviewed by a fluent Spanish-speaking writer, not Google Translate.

Restaurant + Menu schema

JSON-LD so Google and Apple Maps see your dishes and prices. Validated with the Rich Results test before delivery.

Mobile-first layout

Sticky category nav. One-tap call/directions/reservation. Photos AVIF + WebP. Tested iPhone SE to iPad.

Drop-in Loom + embed snippet

A short walkthrough for whoever maintains your existing site, showing exactly where to paste the embed. Wix, Squarespace, Shopify, or self-hosted.

Two free updates in 90 days

Menu changes, price corrections, holiday-hours swaps. Anything bigger gets quoted, small touch-ups are part of the deal.

What every Drop-In ships with by default.

AVIF + WebP fallback Hand-coded HTML, no JS framework JSON-LD Restaurant + Menu schema hreflang EN + ES Core Web Vitals green WCAG AA accessibility

Who it’s for.

You like the rest of your site. The homepage works, the photos are fine — the menu is the drag.
You can’t justify $5k+ for a full rebuild this quarter, but you see the menu is the leak.
You serve a bilingual community and your current site only ships English.
You’ve been using a menu PDF that nobody on a phone can read — or a Wix-template menu that takes 14 seconds to load.

Seven business days, start to embed.

00 Day zero

Send the menu.

PDF, doc, photos, whatever you have, plus the URL of your existing site. Stripe invoice goes out same day; payment in full before work starts.

01 Days 1–3

The draft.

I build the page on your brand. You see a staging URL on day 3.

02 Days 4–5

One round of edits.

Two if the second round is small. Honest about what’s in scope vs. what gets quoted.

03 Days 6–7

Polish + validate.

Schema validated, photos optimized, ES reviewed by a native speaker, embed snippet packaged.

04 Day 7

Loom + embed.

The walkthrough lands in your inbox with the embed snippet. Your site builder pastes it in, or I do, depending on platform.

Two things in writing before you click buy.

One Drop-In a week. Capacity capped.

I don’t schedule two Drop-Ins in the same week. If the week is full, the next open slot is named on this page and you can join the waitlist for no charge.

Two free updates in the first 90 days.

Menu changes, price corrections, holiday-hour swap-ins — small touch-ups are part of the deal. Bigger asks get quoted, in writing, before any work starts.

If the Drop-In goes well — the $1,500 credits toward a full build.

Within 90 days, if you decide you want me to rebuild the rest of the site against the new menu page, the $1,500 carries forward against an Essentials build ($2,500–$4,000). You pay the difference; I rebuild the rest of the site against the page you already love. No re-quote, no re-discovery.

$1,500 paid + $1,000–$2,500 due = Essentials build

Start a Drop-In → Or audit my site first ($499)

Where the Drop-In sits on the ladder

Sister surfaces