Mizu Temakase
A handroll omakase counter in Richmond Hill, where AI-staged photography turned a small takeout-format sushi bar into a room people want a reservation at.
See the case studyfor restaurants and cafes
A restaurant website that keeps up with the kitchen
We rebuild restaurant sites that look like the room, load on a phone at the bar, and get named when somebody asks ChatGPT for a vegetarian dinner in your neighbourhood. Your menu goes up as real pages rather than a PDF, your dishes get written up properly, and the booking handoff actually confirms. The audit is free.
Sites we built for restaurants and cafes
Shizuku
A ten-seat omakase counter on Kennedy Road, where the website has to filter as much as it sells. Every rule, price and course count stated plainly, and readable by the assistant a $295 dinner now gets researched in.
See the case studyWhat restaurants and cafes tell us
The five lines we hear from restaurants and cafes on every audit call.
They told us
“The menu on the site is six months out of date and I keep meaning to fix it.”
What that means
The CMS makes a menu update feel like a project, so nobody touches it, and the site drifts away from the kitchen by the week.
1 day/wk lost
They told us
“People keep calling to ask if we're open and what the hours are.”
What that means
Your hours and holiday closures are not written anywhere a machine can read them, so Google and ChatGPT answer from stale information found elsewhere, and the phone rings instead.
~$8k/yr in covers
They told us
“We pay an agency a few hundred a month and I can't tell you what they actually do.”
What that means
The retainer buys a generic blog post and an Instagram repost. The menu pages, the allergen answers and the dish write-ups that would actually lift dinner-time search never get made.
~$3.6k/yr wasted
They told us
“OpenTable books the table but the confirmation flow is somebody else's brand.”
What that means
Reservation handoffs leak the guest off-site before they've finished imagining the meal, and the post-confirmation email is the booking platform's brand, not yours.
~12% repeat lift gone
They told us
“We're paying for delivery apps and the website does nothing for our own orders.”
What that means
DoorDash and Uber Eats take a cut on every cover that could have come through a direct order on the site, and the site doesn't even rank for the dish names that drive the queries.
20-30% per cover
Four things this buys you
Get found, get asked, get read
Almost every restaurant site we replace does one job: it proves you exist. These are the four jobs it should be doing instead, and you can watch every one of them working right here.
01
Turn up higher when somebody searches for dinner
Most restaurant sites give Google one page and a PDF menu, so there is almost nothing to rank. The top of the page ends up being a review site selling ads against your name. We give Google a real page for every part of your offer, with your hours, your neighbourhood and your dishes written where they can be read. That is the unglamorous half of this, and it is the half that fills tables on a Tuesday.
Illustration. The businesses are invented and the wording is ours, so nothing here claims a result we have not measured.
02
Get named when somebody asks an AI where to eat
A growing share of your bookings start with a question typed into ChatGPT rather than a search box. The answer names two or three restaurants and explains why. Getting into that answer takes the same thing: your dishes, your style of service and your neighbourhood written down plainly enough to be quoted back.
Illustration. The business is invented and the wording is ours, so nothing here claims a result we have not measured.
03
Open with the food, moving
People choose where to eat with their eyes, and a menu PDF has never made anyone hungry. Your photography is the strongest thing you own and it belongs at the top of the page rather than three clicks in. The front page we built for Mizu Temakase in Richmond Hill is at the top of this page.
04
Answer the phone questions before the phone rings
Corkage, bookings, what is actually on the set menu, whether you can do shellfish-free. Your team answers these all night. An assistant on your own site answers them at the moment somebody is deciding. Then it hands them to the booking page, or takes their details for the floor manager. That is where a hungry visitor turns into a covered table.
🍣
Aoi Temaki Bar
Open until 10pm
Hi — I can help with bookings, the menu, or anything about your visit.
What's your corkage fee?What's on the menu?How do I book?
Ask about your visit…
Powered by ✦ Cite-Met Pulse
Mock-up. A real one is briefed on your own prices, hours and policies, and sends the enquiry wherever you want it.
What we ship
The restaurant stack, end to end
01
A page for every dish worth talking about
Not pages for the sake of pages: a page for the dishes people come for, with what is in them, what they cost, and what they can be made without. Another reason to stay on your site, and the thing Google and ChatGPT quote when somebody asks about a specific dish.
02
A page for each way people eat with you
Brunch, dinner, vegetarian, kids, set menu, catering, late-night and seasonal each get their own page and their own answers, because somebody searching for a vegetarian set menu is not the same customer as somebody searching for brunch.
03
OpenTable, Resy, and Tock integration with confirmation flows
Reservation handoffs that match your brand on both sides of the booking, with confirmation pages and post-visit emails that read like the room, not like a booking platform stock template.
04
Updates that take two minutes, not an agency ticket
The chef talks into their phone for two minutes about the new tasting menu and it comes back as a written piece for the site. A photo of a new dish updates its page without anyone logging into anything.
05
Allergens and dietary needs, answered up front
Gluten-free, halal, kosher, vegan, nut-free, and seed-oil-free are explicit, searchable, and surfaced to ChatGPT and Perplexity, instead of buried in a PDF menu nobody can crawl.
06
A page for each occasion people book for
Date night, business dinner, group dining, private events, anniversary, and walk-in late dinner each get a dedicated page with a real FAQ, real photos of the room set for the occasion, and the booking flow that fits the use case.
Pricing
What each tier looks like for a restaurant
The build is one-time, the retainer is monthly, and the audit at the top is free. Most independent restaurants land at Story plus Local. The full pricing across every tier sits inside our solutions overview if you want the long version.
Site
$2,500$2,500. Up to eight pages, your menu as real pages rather than a PDF, hours and contact written where machines can read them, and one booking provider wired in. The starter for a single-location spot that needs the menu to be current and the phone to stop ringing about opening times.
Story
$5,000$5,000. Up to fifteen pages plus the setup that turns a chef's two-minute voice note into a written piece and a phone photo into an updated dish page. Per-menu-variant pages (brunch, dinner, vegetarian, prix-fixe, catering) and per-occasion pages (date night, private events) come standard. The right fit for the place that wants the website to keep up with the kitchen without anyone editing a CMS.
Engine
$9,000$9,000. Up to 200+ pages generated from one list. Useful when you have a group of locations, a rotating seasonal calendar, or a catering arm that needs a page per event type, and you want every menu, neighbourhood and occasion combination findable.
Studio
$15,000+$15,000+. Custom builds for multi-domain restaurant groups, embedded ordering apps, or a conversational layer that handles reservations and dietary questions inline. Rare for a single restaurant, the right shape for a hospitality group that's running five rooms under one operating system.
Monthly plan (search and AI work included at every tier)
- Local$300/moHosting, upkeep, 1 post a month
- Growth$700/mo+ 4 posts a month, rival tracking
- Authority$2,000+/mo+ press, reviews, research
Prices shown exclude applicable taxes.
See the full pricing and tier breakdownProof in the wildSee the Mizu Temakase case
Mizu Temakase: premium handroll omakase, Richmond Hill
Mizu Temakase is an intimate handroll omakase counter in Richmond Hill, Ontario, and the closest fit to what we ship for restaurants today. Hokkaido uni, otoro, engawa, hamachi, ikura, salmon, shiitake, kanpyo, avocado, each roll built one at a time in front of the guest. The brief was the one we hear most often from restaurants: how do we get AI engines to send us the table, and how do we look like the room we are without performing.
We rebuilt the site on a fast, modern build as an intimate single-page experience with the temaki lineup as the spine. Every handroll is written up as its own dish, the dinner-only hours are stated plainly, and the Richmond Hill location is unmistakable, so ChatGPT and Perplexity answer is Mizu Temakase open tonight correctly rather than guessing. The whole site loads in under a second.
The reservation block sits below the menu lineup rather than gating the experience, which is the inverse of how most restaurant sites are built. Buyers see the food, the room, and the story before they hit the booking link, which is the order they actually want. The reservation volume has shifted from Google Maps as the primary entry point to an increasing share of AI engines naming the restaurant by name on neighborhood omakase queries, which is the citation pattern we built the site to compound.
The same same menu and dish groundwork ranks twelve dish-detail pages, twelve menu-variant pages, or twelve neighborhood-and-occasion combinations on a larger restaurant. The reason restaurants don't show up in AI Overviews today is that the average restaurant website is still a Squarespace template, a menu PDF, and an OpenTable widget. That groundwork isn't there, the dish names cannot be read, the dietary data lives inside a photo. The Mizu build is the proof of what changes when that stack gets rebuilt for 2026.
Why us
Why a restaurant should work with the studio
01
Getting you found in AI answers is included in every monthly plan, so the menu and dish work is in the build rather than in a six-month upsell.
02
Mahmoud's PickEasy background and the studio's boutique retail work share the same eye for menus and inventory, so a restaurant build here feels closer to home than a generic agency project.
03
Cite-met monitoring across six AI engines is real-time and runs at every retainer tier, so when ChatGPT starts citing your vegetarian menu page you find out in days, not quarters.
04
A chef can update the site by talking into their phone for two minutes or taking a photo, instead of waiting for an agency ticket to clear.
05
The studio's own site gets roughly a third of its traffic from AI engines, which is the receipt that the model we'd run for you is the one we run on ourselves.
06
The audit is free and the comparison happens on paper before anyone signs anything.
Free audit
24-page AI search audit, no commitment.
You hand us your web address and we send back a scored report: how fast the site loads on a phone, whether Google and ChatGPT can actually read it, how often they mention you today, and the gap between what you have and what restaurants and cafes need to show up in 2026. A web address is all we need.
Go deeper
Restaurants and cafes guides & pricing.
What does a restaurant website actually cost?
Honest pricing for a restaurant website with real menu pages, dish pages, and booking wired in. Build tiers from $2,500, monthly plans from $300.
Read the guideHow diners find you when they ask an AI where to eat
How your restaurant gets named when somebody asks ChatGPT or Google where to eat: real menu pages, a page per dish, and answers to what people actually ask.
Read the guideQuick answers
Frequently asked.
Where we work
Restaurants and cafes across Canada.
We build and rank restaurants and cafes sites across Canada and the UK. Our Toronto page goes deep on the local market; for any other city, tell us on the audit and we tailor the build to it.
TorontoVancouverMontrealCalgaryOttawaEdmontonMississaugaBramptonHamiltonQuebec CityWinnipegLondon ONKitchener-WaterlooHalifaxVictoriaMarkhamVaughanBurlingtonOakvilleSurrey
Start with the audit
We'd rather show you the gap than describe it
Send us your current web address and we will come back with a written read on your menu pages, your dish pages, the booking flow, and how often the AI tools mention you today. The audit is free and there's no pitch attached.