Claude Code for Restaurant Owners: Less Admin, More Covers

Claude Code for restaurant owners takes on the work that happens after close: writing the specials, replying to reviews, answering catering enquiries, updating checklists, emailing suppliers and working out where the food cost went. The kitchen and the floor are yours. The paperwork can be drafted for you.

Claude Code for restaurant owners means keeping your menu, policies and sales exports in a folder an AI agent reads before every job. It drafts menu copy, specials posts, review replies, catering quotes, staff checklists and supplier emails, and explains your sales numbers. You check and send everything.

Here is the setup, the jobs, and the rules that keep you out of trouble.

Set up your restaurant folder

• menu.md: every dish with real ingredients, allergens, prices and the story behind the signature plates.
• voice.md: a few posts and replies that sound like your place.
• policies.md: reservations, large parties, deposits, cancellations, corkage, dietary requests.
• checklists/: opening, closing, line check and cleaning lists.
• exports/: sales and inventory exports from your point-of-sale system.

The jobs

Menu copy and specials

Give it the dish, the ingredients and why you love it, and ask for a menu description, a short version for the board and an Instagram caption. For the weekly specials, ask for all three at once plus a short email to your list. Every ingredient and allergen comes from menu.md, and you check it before printing.

Review replies

Paste each review and ask for a reply in your voice: thank them by name, address any complaint without making excuses, and invite them back or offer to make it right offline. A thoughtful reply to a bad review is read by every future guest who looks you up.

Catering and event enquiries

Large orders and private events often go to whoever answers first with a clear quote. Ask for a reply from policies.md and your catering menu: the options that fit their headcount and budget, the deposit and timeline, and one question to firm up the details. Prices only from your files.

Staff checklists and training

Turn the way your best manager runs a close into a checklist, and ask for a short training guide for new hires: station setup, line check, how to handle an allergy order, how to close out. Consistency is what makes a guest's second visit as good as the first.

Translate the key checklists if your team speaks more than one language. Claude Code can produce side-by-side versions, and a closing checklist everyone can read is one everyone can follow. Have a bilingual team member check the translation before it goes on the wall.

Supplier emails

Ask for supplier emails that state exactly what you need: the order, a delivery issue with photos, or a question about a price increase. Clear, polite, specific emails get faster answers than a rushed phone call during service.

When a supplier raises prices, ask Claude Code to compare the new prices with your last few invoices and show which dishes are affected most. That turns a vague worry into a clear decision: absorb it, adjust the menu price or switch the ingredient.

Food cost check

Drop in your sales export and your invoice totals, and ask for a weekly summary: sales by category, best and worst sellers, and dishes that sell well but may be priced too low for their ingredients. Many owners use a rough rule of thumb of about a third each for food, labour and everything else; ask Claude Code where you sit against your own targets and show you the numbers behind each answer.

A weekly rhythm for owners

• Monday: sales and food cost summary from last week's exports, and one menu decision.
• Tuesday: supplier emails and any price or delivery issues.
• Wednesday: review replies caught up, good and bad.
• Thursday: weekend specials copy, posts and the email to your list.
• Friday: checklists updated with anything that went wrong this week.

Twenty minutes a day on this rhythm keeps marketing consistent and catches problems while they are small, without stealing time from service.

A worked example: Thursday specials

Here is a weekly run for a made-up restaurant.

Specials this weekend, Corner Table Bistro (fictional)
- Braised short rib, celeriac purée, charred broccolini, red wine jus
- Halibut, brown butter, capers, crushed new potatoes
- Dessert: burnt honey panna cotta
- Allergens noted in menu.md; short rib contains celery

Read menu.md and voice.md. Write the specials board copy (one line each),
an Instagram caption with all three, a short email to our list, and a
reply template for "is the halibut gluten free?". Use only ingredients
and allergens from menu.md.

The board lines are short and appetising, the caption leads with the short rib, and the email gives the weekend's three dishes with a booking link. The gluten-free reply answers from menu.md and suggests the guest tells their server, because cross-contact rules are for your kitchen to confirm. Ten minutes on a Thursday and the weekend's marketing is done.

Rules that keep you out of trouble

• Allergens from your files only. Never let a draft guess an ingredient or an allergen. Check every menu change with the kitchen.
• No fake reviews or incentives. Ask happy guests to leave a review; never write reviews or pay for them.
• Prices and deposits from your policies. Quotes must match what you charge.
• Health and labour rules are yours. Claude Code can draft checklists; local food safety and employment rules decide what goes in them.
• Drafts only. You or your managers send every message and post.

Mistakes to avoid

• Generic menu copy. "Delicious and fresh" sells nothing; specific ingredients and a short story do.
• Arguing in review replies. Thank, acknowledge and take it offline.
• Slow catering replies. Answer large enquiries the same day with a clear quote.
• Ignoring your sales data. Your POS export tells you which dishes earn their place.
• Unwritten procedures. If only one manager knows how to close properly, write it down.

Claude Code for restaurant owners: FAQ

Which AI is best for restaurants?

The best setup pairs your point-of-sale and reservation systems, which hold the records, with an AI that drafts menu copy, review replies, catering quotes, checklists and reports from your files. Claude Code fits that drafting and analysis role.

What is the 30/30/30 rule for restaurants?

The 30/30/30 rule is a rough guide that splits revenue into about a third for food cost, a third for labour and a third for everything else including profit. Real targets vary by concept, so compare against your own numbers.

Can I use Claude Code for my restaurant business?

You can use Claude Code for your restaurant on a paid Claude plan, subject to Anthropic's terms. It is well suited to the writing and analysis around running a restaurant: menus, marketing, replies, checklists and numbers.

How much does Claude Code cost for a business?

Claude Code is included with paid Claude plans or can run on API credits, and prices vary by plan. Check Anthropic's current pricing page for the plan that fits your usage.

Can AI help with restaurant reviews?

AI can draft replies to every review in your voice, so no guest is ignored, and summarise what reviews say about your food, service and atmosphere each month. You approve each reply and decide what to change in the restaurant.

Get the operator workspace

The AI Operator Kit includes content repurposing for specials and posts, review replies through its local search play, fast replies to enquiries, SOPs from recordings and one-page weekly reports.