An AI consultant for your restaurant, not a chatbot
Stu is Sturgeon's AI operations consultant. It answers questions about your restaurant from your live POS, labor, purchasing, and guest data. Then it does the work, drafting the purchase order or the schedule fix and waiting for your approval.
How it works
Ask it what you'd ask your best manager
Who should close Friday? What should we 86 tonight? Which vendor is creeping on price? What's driving the food-cost creep since June? Stu answers from your own invoices, sales mix, recipes, and schedules, not from a generic idea of a restaurant, and shows which systems it looked in.
It looks things up before it answers
Stu runs 30+ tools over your live data: sales forecasts from the POS, stock on hand, this week's invoice prices, schedules, reservations, and reviews. Ask it to reorder salmon for the weekend, and it checks the covers forecast, what's in the walk-in, and what the vendor charged this week before it says a word.
Then it acts, with your sign-off
Answers end in work: a drafted purchase order with the quantity and price filled in, a schedule change, a win-back campaign, a review reply. Nothing reaches a guest or a vendor until you approve it, and approved orders go out by email, text, or call.
Private by design
Stu runs on your restaurant's own dedicated, isolated Sturgeon instance. Your data is never pooled with other businesses or used to train shared models, and the plan is flat, so there's no per-question or per-token fee for asking.
Questions
What can I ask Stu?
Anything you'd ask a very good operations analyst who never sleeps: what's driving food cost up, who is heading into overtime, which dishes to push or pull, what to order for the weekend, which vendor raised prices. Stu answers from your invoices, sales mix, recipes, schedules, and reviews.
Does Stu send orders or messages on its own?
Only if you want it to. Purchase orders, review replies, and campaigns are drafted for you and wait for one-tap approval, so you stay in control of everything that reaches a guest or a vendor.
How long before Stu knows my restaurant?
About three days. You connect your systems on day one. History backfills and the models calibrate on day two. By day three, Stu already knows your covers, costs, and guests.
Guides on the numbers behind this
- Food cost percentageHow to calculate restaurant food cost percentageThe formula, a worked example, actual versus theoretical, and how to track it daily.
- Prime costWhat is prime cost in a restaurant, and how do you calculate it?Cost of goods sold plus labor, why operators watch it weekly, and how to read it.
- Labor costRestaurant labor cost percentage: formula, benchmarks, and how to lower itThe formula, what to include, sales per labor hour, and where labor leaks.
- Recipe costingRestaurant recipe costing: how to calculate plate cost and menu priceYield, trim, the plate cost formula, and how to turn a cost into a menu price.
- Reducing food wasteHow to reduce restaurant food waste, and measure what it costsWhere waste comes from, how to log and price it, and the fixes that tend to work.
See your own numbers in Sturgeon in under a week, with your POS connected, your forecasts calibrated, and Stu answering. White-glove onboarding is included.
No credit card. No six-month contract. Your data stays yours.