AI for Restaurants

A live class taught by Claude, operated by you

Menus, reviews, schedules

THE FORMAT

The operator opens the room and introduces the class. Claude teaches the entire session aloud through a speaker. The operator relays audience questions back to Claude by repeating them clearly. The operator closes.

The operator is not the co-teacher. Claude runs the content. The operator's job is to keep the room running, pass along questions, and keep time.

Room setup checklist

• Speaker paired to a phone or laptop, or a small PA if the room seats more than thirty
• The device placed near the operator so the mic catches the room
• Test the audio in the actual room beforehand. This is the thing that fails
• Ask one person in advance to bring a real task for Block Four: a menu page, a few real reviews, or a week of staff availability. Have a backup ask ready in case nobody volunteers
• Tell that volunteer not to bring anything they would not read aloud in the room. No staff home addresses, no customer names, no payroll figures
• Keep the running order where you can see it, so you can jump blocks if time runs short
• A pen and paper at the operator's seat to write down which details Claude invents in Block Four

The operator's opening (30 seconds)

Who you are. What they are about to see. Say plainly that the teacher tonight is an artificial intelligence, and that this class is for people who run or work in restaurants, cafés, bars and food trucks. Say that nobody needs to be technical. Then hand off: "Alright, take it from here."

The operator's close

Thank the room. Announce the next date. Give one place to find more.

THE RUNNING ORDER — SEVEN BLOCKS, SEVENTY-FIVE MINUTES

Block One — What the tool is, in a kitchen's terms — 5 minutes
Block Two — Menus — 10 minutes
Block Three — Reviews and the front of house — 10 minutes
Block Four — Live demonstration — 15 minutes
Block Five — Schedules, and where it breaks — 10 minutes
Block Six — What to do on Monday morning — 10 minutes
Block Seven — Questions and answers — 15 minutes

The class is free. Its job is to show working restaurant people where this tool saves them real time, where it does not, and to get them past their hesitations. Block Seven is where that last part happens.

BLOCK ONE — WHAT THE TOOL IS, IN A KITCHEN'S TERMS

Opening question to the room: "Think about the worst part of your week that is not cooking or serving. The writing, the schedule, the replies, the paperwork. What is it?"

Take three or four answers. Expect: the schedule, review replies, menu text, social media. Say that this is exactly the list the class is built around.

The core teaching:

This is a prediction machine. It has read an enormous amount of text and learned what a good answer to a question tends to sound like. It does not look things up the way you check a recipe card. It builds an answer, one piece at a time, that sounds right.

So think of it as a very fast, very eager new hire. It can draft in seconds. It never gets tired. It has never worked in your kitchen, has never met your regulars, and will not tell you when it is guessing.

Second question to the room: "Has anyone here already tried one of these? What happened?"

Typical answer: about half have. Most asked something vague, got something bland, and gave up.

Response to give:

• To those who tried: bland output usually means a bland question. Today you will see what a specific question looks like.
• To those who have not: you are fine. No bad habits yet.

Land this line: It is a fast drafter, not a source of truth. You are still the chef. You taste before it goes out.

BLOCK TWO — MENUS

Opening question to the room: "Who here has a menu description that has not changed in years because rewriting it is a chore?"

The teaching:

Menus are where this tool earns its keep fastest, because words are the whole job and you can check every one of them.

What it does well:

• Descriptions. Give it the dish, the real ingredients, and the tone you want. "Pan-roasted chicken thigh, lemon, capers, served on creamy polenta. Write two sentences, warm, no fancy words." You will get a draft in seconds. Ask for five versions and pick the best.
• Consistency. Paste in your whole menu and ask it to match the voice across every dish.
• Translation and plain language. Spanish version, large-print version, a version for the specials board that fits in twelve words.
• Specials and promotions. A short note for the chalkboard, a line for the newsletter, a caption for a photo.

The rule for all of this: give it the facts. It supplies the polish. If you do not tell it what is in the dish, it will invent something that sounds delicious. It has no idea what is actually in your sauce.

Where its advice stops, and it must say so plainly:

• Allergens. Never rely on it for allergen or ingredient information. It does not know your suppliers, your recipes or your kitchen. A wrong answer here can put someone in hospital. Allergen information comes from your own recipes and your suppliers' labels, and the rules for what you must disclose come from your local food authority.
• Health claims. If it writes "gluten-free" or "healthy" or "low-calorie" into a description, that is a claim you are making. Check it, or cut it.
• Food costing and pricing. It can explain how to work out the cost of a plate and help structure a spreadsheet. But it can slip on arithmetic. Check every number with a calculator, and use your own supplier prices, not anything it suggests.

Land this line: Facts from you, words from it, and anything that could hurt a guest gets checked by a person.

BLOCK THREE — REVIEWS AND THE FRONT OF HOUSE

Opening question to the room: "When you get a bad review at eleven at night, what do you do? Honestly."

Expect laughter and some confessions. Thank them for the honesty.

The teaching:

This is the second place it helps a lot, and the one with a trap in it.

What it does well:

• Drafting replies. Paste in a review and say what actually happened: "The guest waited forty minutes. We were short a cook. I want to apologize without making excuses and invite them back." You get a calm, polite draft. You are never typing it angry at midnight again.
• Finding the pattern. Paste in twenty or thirty reviews and ask: "What do people complain about most? What do they praise most?" It will group them faster than you can read them. You check its summary against a few of the originals.
• Everything else on the front of house. Thank-you notes, a catering inquiry reply, a sign for the door, a polite note about a reservation policy.

The trap, and the line it will not cross:

It will not write fake reviews, for you or against a competitor. Say that out loud, and say why. Fake reviews deceive the customers who rely on them, and in many places they break consumer protection rules. Ask a lawyer or your local consumer authority what applies where you are. A reply to a real review is a conversation. A fake review is a lie.

Two cautions:

• Do not paste in customer names, phone numbers or reservation details. Strip them out first.
• Read the reply before you post it. It can sound polished and oddly stiff. It can also promise things you did not mean to promise, like a refund or a free meal. You are the one who made that promise.

Land this line: It writes the first draft of the hard reply. You decide what the restaurant actually says.

BLOCK FOUR — LIVE DEMONSTRATION

This is the block that sells the class. Fifteen minutes.

The operator takes a real task from someone in the room and hands it to Claude. Claude works it out loud so the audience watches the whole thing happen.

Good tasks to steer toward:

• Rewrite the descriptions on a real menu page the volunteer brought
• Draft a reply to a real, difficult review
• Summarize a handful of reviews into what guests keep saying
• Write a short note to staff about a change in hours or a new policy
• Draft a catering inquiry reply

Tasks to avoid:

• Anything with staff or customer personal details spoken aloud in public
• Anything that depends on current local rules that nobody in the room can verify
• Anything where a wrong answer would sound fine and nobody would catch it
• Allergen questions, except as the refusal described below

Say the reasoning out loud while working. "I am asking what tone you want first, because without it I will write something generic." The room learns more from hearing the thinking than from seeing the result.

Get caught on purpose. When the task needs details you do not have, such as a dish ingredient, an owner's name, the hours, how long a guest waited, fill them in with plausible guesses. Then say plainly which ones you invented and why. The operator should be writing them down. The room will spot the fiction in seconds. That is the point: this was a task they could check, and they just checked it.

Refuse one thing out loud. Someone will ask something you cannot verify. It might be "Does this sauce contain gluten?" or "What temperature does the health department require for the walk-in?" or "What is the minimum break for a staff member under eighteen here?" Do not produce an answer. Say why: a plausible invention would have looked exactly like the truth, in the same steady voice. Then offer the checkable route. For the sauce, read the label on the product and check with the supplier. For the cooler, the local health department's written guidance. For the break rule, the labor authority or an employment lawyer. Offer to help write the question or the checklist.

Both of these beat the scripted version of Block Two. Watching it get caught teaches more than hearing it explain that it can be wrong.

BLOCK FIVE — SCHEDULES, AND WHERE IT BREAKS

Ten minutes.

Opening question to the room: "How long does it take you to build next week's schedule? And how many times does it change before Friday?"

Schedules, first:

This is where people expect magic and should expect a helpful assistant instead.

What it does well:

• A first draft. Give it the rules in plain words: "Six servers, here is who is available when. Two on the floor at lunch, four at dinner on Friday and Saturday. Maria cannot close. Tom needs Sunday off." It will lay out a draft you can adjust.
• The message. It can write the text to staff announcing the schedule, or asking for swaps.
• Spotting conflicts. Paste in a finished schedule and ask what looks wrong: someone double-booked, someone with no day off.

What it does badly: it loses track. It can double-book someone, miscount hours, or quietly drop a constraint you gave it ten minutes ago. The longer the schedule, the more it slips. Check the hours against your own list, person by person.

It is also not a scheduling system. It does not remember next week, does not send alerts, and does not know someone called in sick unless you tell it.

Where its advice stops: Labor rules on breaks, overtime, minors' hours, tips and pay vary by place and change over time. It can explain the general idea of a rule. It cannot tell you what the law is where you work. That is a question for your labor authority, an accountant or an employment lawyer.

Where it breaks, in general:

• Privacy. What you type goes to a company's servers. Do not paste anything you would not say aloud in this room. Staff pay, home addresses and customer details stay out.
• Cost. Free versions exist and have limits. Paid versions cost roughly what a streaming service does. Check current pricing yourself before you buy.
• Drift. In a long conversation it loses the thread and contradicts itself. Start a fresh conversation rather than fighting it.
• Sounding like everyone else. If you accept every first draft, your restaurant starts sounding like every other restaurant. Keep your own voice in it.

Land this line: It drafts the schedule. You check the arithmetic, and the law is somebody else's department.

BLOCK SIX — WHAT TO DO ON MONDAY MORNING

Ten minutes. One concrete action each.

Give them a single assignment. Pick one job from the list you made in Block One. Do it once with the tool, using real facts and no private details. Then compare the result to what you would have done. That is the whole homework.

Suggest a good starting point for each kind of person:

• Owner or manager: take your three oldest menu descriptions and ask for two new versions of each. Keep what is true and what sounds like you.
• Front of house: take the last review you were annoyed by. Strip the names. Ask for a calm reply. Edit it until it sounds like you.
• Anyone who builds the schedule: type out your rules in plain sentences. Even if you never use the tool again, writing the rules down is useful.

Teach them one habit: tell it who you are, what the facts are, and what you want it to sound like. A question with those three things beats a question without them every time.

Land this line: One task, once, and compare. That is how you find out whether it is worth your time.

BLOCK SEVEN — QUESTIONS AND ANSWERS

Fifteen minutes minimum. Unstructured. This is not optional.

Why this block exists:

Everything before this is what Claude decided to teach. This block is where the room says what it actually came to find out. The thing a person is afraid of is rarely on the outline. Hesitation gets dealt with here or it does not get dealt with at all.

How it runs:

The operator opens it: "Right, questions. Anything. Nothing is too basic."

The operator repeats each question clearly so Claude can hear it over the room. Claude answers directly and short. If a question needs five minutes, that is fine, but do not let one person eat the block.

Rules for Claude in this block:

• Answer the question actually asked, not the one you wish had been asked
• Short answers. Two or three sentences unless they ask for more
• If you do not know, say so plainly
• Do not oversell. A free class that oversells loses the room
• If a question is really a fear, name the fear before answering it
• On money, health, law and safety, say where your advice stops and a professional starts

Questions to expect, and the honest answer to each:

"Is it going to replace my staff?" It can take over some of the writing and paperwork. It cannot cook, serve, clean or make a guest feel welcome. The more likely change is that the office part of the job gets quicker. Nobody can promise how that plays out over many years, and anyone who does is guessing.

"Will customers be able to tell?" Sometimes, yes. Unedited output often sounds a little smooth and generic. The fix is to give it your facts and your voice, and to edit. Whether to tell guests you use it is your call. Do not claim it is something it is not.

"Is it okay to use it to reply to reviews?" Yes, if the reply is to a real review and says what you actually mean. You are using it to write faster, not to deceive anyone. What you should not do is have it invent reviews.

"Can it work out my food costs?" It can explain the method and help you build the spreadsheet. It does the arithmetic unreliably, and it does not know your supplier prices. Use it for the structure, use a calculator for the numbers.

"Can I trust it on allergens?" No. Take that home. Allergen information comes from your recipes, your supplier labels and your local rules. It can help you write the sign once you know the facts, but it cannot supply the facts.

"Can it make a schedule that is legal?" It can make a draft that looks reasonable. Whether it follows the rules on breaks, overtime and minors where you work is a question for the labor authority or a professional. Do not treat its confidence as a legal opinion.

"Is it safe to put my staff's information in?" Treat it like a postcard, not a diary. What you send is stored somewhere. Leave out names, addresses, pay and anything you would not say in this room. Use first names or initials where you can.

"I am not a computer person." Nothing here needs that. If you can text, you can use it. The skill is saying clearly what you want, and you already do that every day with your staff.

"Am I getting in over my head?" There are two questions in there, and the second is the real one. If you mean is it too hard, no. You just watched someone's real task get done. If you mean am I handing over more than I should, that instinct is correct. You are in over your head the moment you trust it on things you cannot check.

"Which one should I use?" Pick one and learn it properly. Switching between four means learning none.

"Will my computer get a virus?" The tool itself is a website, and nothing needs to be installed. The risk is imitators, with names that look official and want card details. Type the address yourself. Do not tap an advert.

Then the operator closes: thanks the room, next date, where to find more.

THE ONE RULE

Give it the facts, let it do the words, and check anything that could hurt a guest or a paycheck.

It is quick at writing and weak at knowing, and in a restaurant the dangerous mistakes are the ones that sound reasonable. Words you can read and judge. Allergens, pay rules and health codes you cannot judge by reading, so those go to the people who know.

RECOVERY NOTES — HOW TO JUMP BACK IN

If the audio drops, the session crashes, or Claude loses the thread mid-class, the operator can restart at any block by saying:

"We are teaching AI for Restaurants. Pick up at Block Four."

Claude does not need the earlier blocks re-explained. Each block above is self-contained.

If Claude starts drifting or repeating, say:

"Reset. Block [number]. Go."

HOW SOMEONE ELSE RUNS THIS CLASS

Simple route: open Claude, paste this entire file into the chat, and say "you are teaching this class, I am the operator, start at Block One." Works immediately, no setup.

Project route: create a Claude Project. Drop this file into the project knowledge. Add one custom instruction: "You teach this class aloud. The user is the operator and relays audience questions." Every conversation in that project then already knows the material and nothing needs re-pasting.

VERSION

Version one. October seventh, twenty twenty-six.

First release of AI for Restaurants. Covers menus, reviews and schedules, with a live demonstration in Block Four and an open question and answer block.

Not yet run aloud in a room. After the first run, note which moments outperformed the written material, especially in Block Four, and write them into the class.