Restaurants are the best retainer client in local business, for one structural reason. Here’s what to charge, how to get in, and how it recurs.
Here’s the problem with most local web clients.
They don’t actually need you after launch.
A solicitor’s website is substantially the same three years later. So is a plumber’s, an accountant’s, a driving instructor’s. You build it, you hand it over, and then you go and find another one. Forever. That isn’t a business, it’s a treadmill with invoices attached.
Restaurants are the exception, and understanding why is worth more than any sales technique.
Why Restaurants Are Structurally Different
Their content changes constantly. Menus, prices, specials, seasons, opening hours, a new chef, a Christmas menu, a summer terrace, the bank holiday nobody updated.
Something changes most months. And they are not going to do it themselves, because they are running a restaurant — a business with brutal hours and thin margins where the owner is frequently also working the floor.
So the retainer is not something you have to talk them into. It is something they need.
That single fact is why how to sell websites to restaurants is a different problem from selling websites to anyone else, and a considerably better one.
The second advantage: you can walk in
Most local niches are hard to reach. The owner is on a job, behind a desk, or screened by a receptionist.
Restaurants have a quiet hour — roughly 2:30 to 4:30 — when the owner is often on site and not busy. Buying a coffee gives you a completely legitimate reason to be standing there. No other local niche offers that.
What To Charge
This is where most people wreck the opportunity before they start.
You know the site took you four hours, because you have a system that builds it. The owner does not know that. They see a finished, branded site with a searchable menu, a gallery, a booking form and mobile layouts that work — and the quotes they have had elsewhere tell them that is several weeks of agency work.
Price from your effort and you charge $400. Price from their alternative and you charge $1,800. Same website.
A three-tier structure
Three tiers, always. Three converts a yes/no decision into a which-one decision, and most people take the middle.
| Essentials | Complete | Managed | |
|---|---|---|---|
| Build | $895 | $1,795 | $2,995 |
| Monthly | $59 | $149 | $299 |
| Online booking | — | Yes | Yes |
| Menu updates | Text changes | Monthly, done for you | Unlimited |
| Google Business | — | Setup | Full management |
Adjust by venue. A café sits at $695–$995 with a $49–$79 monthly. An independent restaurant sits at $1,495–$2,195 with $129–$179. A steakhouse or fine dining venue supports $2,495–$3,995 and $199–$349.
The reframe that makes the monthly easy
Your monthly should cost the restaurant less than one average cover per week.
At $149 a month against a $45 average spend, that is under one extra table a week to break even. Say that out loud in the pitch. It does more work than any feature list, because it converts an abstract cost into something the owner can picture on a Tuesday night.
Three pricing mistakes to avoid: quoting per page, which invites the owner to strip the quote down; one-off pricing with no monthly, which means finding a brand new client forever; and being the cheapest, which signals to a restaurant owner — all of whom have been burned by cheap web work — that you will vanish in five weeks.
Getting In Front Of Owners
The whole approach rests on one thing: build the demo before you make contact.
You cannot describe a restaurant website persuasively. You can only show one. And a demo built for a generic “Example Bistro” convinces nobody — it has to have their name, their menu, their photos.
The walk-in
Timing is the whole thing. Mid-afternoon. Never lunch, never a Friday or Saturday evening, never during service. Many independents close Mondays, so check.
Buy something. It costs three pounds and turns you from a salesperson into a customer.
Then: “Hi — is the owner about? I’m not selling anything today, I’ve actually just built something I thought you’d want to see. Can I show you on my phone?”
Open the demo of their restaurant. Hand them the phone. Say nothing while they scroll — people engage far more with something they are holding than something being shown to them.
The email
Short, no attachment, no deck. Its only job is to get a reply, and it hangs on one specific observation about their current site.
Observations that work: the menu is a PDF that won’t zoom on a phone; the site says closed Mondays but Google says open; there’s no online booking, just a phone number; the photos are visibly from 2016; there’s no site at all, just a Facebook page.
Each of those is an opening sentence that could not have been copy-pasted to anyone else, and that is precisely why it gets a reply.
The objection worth learning properly
“We get all our bookings through [delivery or reservation platform].”
The answer: “Good, keep it. I’m not trying to replace that. But you’re paying commission on every cover that comes through it, and the ones who book direct from your own site cost you nothing. Even shifting one in five across is worth more than what I charge.”
That is the strongest card you hold with any restaurant on a commission-based platform, and it reframes your fee as a cost saving rather than an expense.
Making It Recur
The build fee pays this month. The care plan pays next year.
What goes in it
The plan has to contain things the owner can see. Hosting, backups and security updates are necessary and completely unpersuasive on their own.
The visible half is what they are paying for: menu updates done for them, seasonal pages, hours kept accurate everywhere including Google, photo refreshes, Google Business posts, and a monthly one-page report.
The menu clause is the retainer. “You send me a photo of the new menu and it’s live the same day” is the single sentence that sells a care plan to a restaurant. Everything else is supporting detail.
Sell it as one sentence
“The site’s $1,795 to build and then $149 a month to keep running” is one decision.
“It’s $1,795, and there’s an optional maintenance plan if you want it” is two decisions, and the second one gets declined. Never present the monthly as optional.
Why clients cancel, and the cheap fix
Churn happens in months three to six, and almost always for the same reason: the client forgot you exist. If nothing visibly changed in ninety days and they heard nothing from you, the charge on the statement looks like a subscription they meant to cancel.
The fix is a one-page monthly report on the same date every month. Three numbers, a line on what you did, and a suggestion for next month. Four lines of work. It proves the money is doing something, reminds them you exist, and contains next month’s upsell.
The twelve-month picture
| Month | Clients | Monthly recurring |
|---|---|---|
| 1–2 | 3 | ~$350 |
| 3–4 | 6 | ~$750 |
| 5–6 | 10 | ~$1,300 |
| 7–9 | 15 | ~$2,000 |
| 10–12 | 20 | ~$2,800 |
Plus build fees along the way — twenty builds averaging $1,400 is $28,000 across the year. Ordinary numbers for someone working at it steadily, not exceptional ones.
One caution: restaurants close, change hands, and have bad years, and when they do the web retainer is an early casualty. Twenty small retainers across different venue types is considerably more stable than five large ones.
The Production Side
Everything above assumes you can turn out a professional restaurant website quickly. Build each one from scratch and the economics collapse — you cannot afford to make free demos for twenty prospects if each one costs a day.
Restaurant Agency Studio is a WordPress system built for exactly this: five restaurant design styles, ten niche content packs (Italian, pizza, steakhouse, seafood, sushi, catering and others), a searchable menu builder, galleries, table booking with capacity limits, plus an agency site and instant quote tool for your own business. Native block editing, no page builder required, and commercial rights for unlimited client sites. It’s $27 at launch against $97 regular.
The honest verdict
What it does well: the personalised demo workflow is the standout, because it makes the give-first approach economically viable. Building a free demo used to cost a day, so nobody did it. At an hour or two you can afford to do it for twenty prospects, and that changes how you win clients entirely.
What it does not do: it won’t tell you what to charge, get you in front of an owner, or structure your recurring revenue. It also assumes you’re comfortable with WordPress basics — this is a system for someone who can host and manage sites, not a no-code builder.
Who should skip it: anyone with no interest in local client work. This is a production tool for a service business, and without the service business it’s just five themes.
Because the money side is the gap, I wrote three reports to go alongside it — the full pricing playbook, a fourteen-day plan to five clients, and the recurring revenue report. Free if you pick it up through my link.
See Restaurant Agency Studio and the bonus package ?
Frequently Asked Questions
How much should I charge a restaurant for a website?
Between $895 and $2,995 to build, depending on the venue, plus $59–$299 a month for care. A café sits at the lower end; an independent restaurant around $1,495–$2,195; fine dining and small groups considerably higher. Price against what a website is worth to them, not the hours it took you.
Do restaurants pay for website maintenance?
More readily than almost any other local business, because their content genuinely changes every month. The retainer sells itself on one clause: you update the menu for them whenever it changes.
How do I get restaurant clients with no portfolio?
Build demo sites for three real, named local restaurants before contacting anyone. Then walk in during the quiet afternoon hour and show the owner their own restaurant on your phone. A demo is a portfolio and a pitch in one.
What’s the best time to approach a restaurant owner?
Mid-afternoon, roughly 2:30 to 4:30, between lunch and dinner service. Never during service, never a Friday or Saturday evening, and check whether they close Mondays. Turning up at the wrong hour is the fastest way to be remembered badly.
Should I use WordPress for restaurant websites?
It’s a reasonable default for client work — you can hand over ownership, the client can find someone else to maintain it if you part ways, and hosting is cheap. What matters more than the platform is whether the menu is searchable text rather than a PDF, and whether it loads quickly on a phone.
The Short Version
Pick restaurants because their content changes constantly, which means the retainer is something they need rather than something you sell.
Build three demos for three real local restaurants. Walk in at the quiet hour, buy a coffee, and hand the owner a phone with their own name on the screen.
Quote three tiers, quote the build and the monthly as one sentence, and frame the monthly against covers rather than against other agencies. Then send a one-page report on the same date every month so they never forget you exist.
Disclosure: this post contains affiliate links. If you buy through one of them I earn a commission at no extra cost to you.
