AI for Restaurant Owners — Menu and Ops Memory

Updated January 2026 | 8 min read

You're planning the spring menu but can't remember which appetizer sold well last April and which one died after two weeks. Your vendor changed pricing three times this quarter, and you're not sure if the ribeye is still margin-positive at the current menu price. The health inspector flagged something six months ago—you think you fixed it, but the documentation is in a binder somewhere.

Standard AI can't help. It doesn't know your cost structure, your seasonal sales patterns, or that your Saturday prep cook calls out twice a month.

Claude Code with Obsidian gives your AI a permanent file of menu performance, vendor pricing, staff schedules, compliance checklists, and operational patterns. Every dish's food cost, every vendor's lead time, every recurring issue—written once, available forever. No subscription. No cloud dependency. Just a markdown file that remembers how your restaurant actually runs.

What Restaurant Owners Need AI to Remember

Menu performance varies by season, day of week, and customer demographics. The butternut squash soup sells in November, not July. The patio cocktails move on Friday nights, not Tuesday afternoons. The lunch special attracts a different crowd than dinner service. Without data, you're guessing which items to promote.

Recipe costing requires current vendor pricing. The beef tenderloin was $18/lb last month, now it's $22. The tomatoes are cheap in August, expensive in February. Your margin on each dish shifts with input costs. Tracking this manually means outdated menu pricing.

Vendor relationships have details that matter. Sysco delivers Tuesday and Friday. The produce guy gives you first pick if you order before 2pm Monday. The seafood vendor has a $200 minimum. The craft beer distributor runs promotions quarterly. Lose these notes and you're relearning the system every order.

Staff availability patterns affect scheduling. Your best line cook takes the first two weeks of July off. The dishwasher is unreliable on Mondays. The weekend bartender can't work Sunday mornings. Building schedules without this context means last-minute scrambles.

The Menu Engineering Problem

High-margin items subsidize low-margin ones. The burger barely breaks even, but it drives traffic. The wine program carries the profit. The desserts are pure margin but require pastry staff. Your file tracks the real numbers so you know which items work as loss leaders and which must perform.

Dish popularity shifts over time. The Korean BBQ tacos were the hit of last summer. This year, they're middle of the pack. The Caesar salad sells consistently year-round. The daily special depends on who's cooking. Pattern recognition requires memory of past performance.

Portion control affects food cost. The pasta dish is supposed to be 8oz, but the new cook serves 10oz. The side of fries varies between 5oz and 7oz depending on who's working. Your target food cost is 28%, but actual comes in at 32% because portions creep. Tracking this prevents margin erosion.

How the Memory System Works for Restaurants

You create a markdown file in Obsidian. Inside: menu items with recipes and costing, vendor contacts with pricing and terms, staff schedules and availability, compliance checklists, reservation notes, and seasonal sales patterns. Plain text, readable by you and by Claude.

Claude Code reads this file every time you start a conversation. You ask about the ribeye, and Claude already knows the current food cost, the portion size, the menu price, the margin, and whether it's selling at target mix.

When costs change or performance shifts, you update the file—new vendor pricing, revised recipes, seasonal menu swaps, staff availability. Next time you're planning orders or building schedules, the current information's ready. No spreadsheet hunting, no memory testing, no guessing based on last quarter's numbers.

The structure scales. Single-location owner-operator? One file tracks everything. Multi-location or franchise? Separate files for each location's menu, vendors, and staff. Claude reads all of it because it's organized folders and markdown.

Recipe and Costing Template

Each menu item gets a section with ingredients, quantities, preparation steps, plating instructions, and current cost per portion. Include yield percentage—the 10lb beef tenderloin trims to 7.5lb usable. Track waste factors for produce and proteins.

Calculate margin by comparing food cost to menu price. The salmon dish costs $8.50 in ingredients, sells for $28, yielding a 70% margin. The burger costs $6.20, sells for $14, yielding a 56% margin. Your file holds these numbers so you spot margin compression before it kills profitability.

Note substitutions and modifications. The pasta can use gluten-free noodles for $2 upcharge. The salad loses margin if customers remove protein. The side of vegetables costs more when asparagus replaces green beans. Track these to ensure modifiers reflect actual cost.

Vendor Management and Ordering

Your file holds vendor contacts, delivery schedules, minimum orders, payment terms, and pricing by product. Sysco delivers Tuesday/Friday, net 30 terms, $500 minimum. The seafood vendor delivers daily if ordered by 3pm, cash on delivery. The bakery delivers Monday/Wednesday/Friday, net 15 terms.

Price tracking matters for budgeting. The ribeye was $16/lb in January, $19 in March, $22 in May. The avocados swing from $1.20 to $2.80 depending on season. Your file logs these trends so you adjust menu pricing or run specials when costs spike.

Lead times prevent stock-outs. The craft beer takes two weeks to order if it's not in the distributor's warehouse. The specialty cheese needs five business days. The oysters arrive daily but must be ordered 24 hours ahead. Claude cross-checks your notes before confirming you can run a special.

Staff Scheduling and Availability

Your file tracks preferred shifts, time-off requests, certifications, and reliability patterns. The lead line cook has ServSafe certification and prefers closing shifts. The weekend bartender is TIPs certified but can't open. The dishwasher is 70% reliable on Mondays, 95% the rest of the week.

Labor cost targets require hours management. Your target is 30% of revenue. Weekend dinner service runs six FOH staff and four BOH. Weekday lunch is three FOH and two BOH. Your file holds these configurations so you build schedules that hit targets without short-staffing.

Cross-training notes matter when someone calls out. The sous chef can work the line if a cook is out. The bartender can run food in a pinch. The host knows the POS system and can help with takeout orders. Documenting who can do what prevents service failures.

Health Code Compliance and Inspections

Your file holds inspection history, corrective actions, recurring issues, and follow-up dates. The inspector flagged the walk-in temperature in March—you recalibrated and documented. The handwashing station needed upgrading in January—completed with invoice filed. The grease trap cleaning is quarterly—last done December 15, next due March 15.

Daily checklists prevent violations. Temperature logs for coolers and hot hold. Cleaning schedules for equipment and surfaces. Date labels for prep items. Your file holds the checklists so you don't rely on staff memory or hope the notebook doesn't walk off.

Allergen tracking matters for liability. The bread contains wheat and soy. The fried items share oil with shellfish. The house salad dressing has eggs. Your file documents every allergen by menu item so staff can answer customer questions accurately.

Reservation and Customer Notes

Regulars have preferences. Table 12 by the window for the couple who comes every Friday. No cilantro for the guy with the sensitivity. Extra napkins for the family with young kids. Complimentary dessert for the couple celebrating their anniversary. Your file holds these notes so service feels personal, not generic.

Dietary restrictions repeat for regular customers. The gluten-free, dairy-free regular who orders the salmon with modifications. The vegan who wants the pasta with substitutions. The keto customer who orders protein and vegetables only. Documenting this prevents re-asking every visit.

Seasonal Menu Planning

Your file tracks which dishes succeed by season. The autumn menu featured braised short ribs—sold well in October, tapered off in November. The summer menu had watermelon salad—strong June through August, dead in September. Historical data informs next year's planning.

Ingredient availability drives seasonal changes. Tomatoes are cheap and good July-September. Squash and root vegetables peak October-March. Asparagus has a short spring window. Your notes track vendor availability so you plan menus around what's actually in season and affordable.

What This Costs vs. What It Saves

Setup is $997 one-time. You get Claude Code configured, Obsidian installed, and a starter file template for restaurant operations. No monthly fees. No per-location charges. Your menu data, vendor contacts, and staff notes stay on your device, accessible offline.

Compare that to one week of incorrect food costing that kills your margin. Or one scheduling failure that forces you to close early or comp meals due to slow service. Or one health inspection failure because you couldn't prove corrective action.

The system pays for itself when you stop rebuilding seasonal menus from scratch every quarter. It pays again when vendor orders pull from actual usage patterns instead of guesswork. It keeps paying every time you adjust menu prices based on current food costs instead of outdated numbers.