← All use cases

Use case B30 · Business

Barbecue owner builds a kitchen operations app with Claude Code

Joe Zavala, owner, Zavala's Barbecue (via evolv Consulting) · Publication date not stated; date field records access on 2026-10-20. The source describes a March-April 2026 implementation.

The short version

What they did

Zavala used Claude Code to replace spreadsheets for inventory, food cost, prep, scheduling, catering and invoicing with a shared app. The source says it reached production after a late-March 2026 start. Zavala also works at the publishing consultancy, and its CTO supported the project; this is not independent reporting.

Result (as claimed)

“The old way ate up about 30 hours a week in spreadsheets. Now it is 2” is Zavala’s reported weekly admin-time comparison. The source supplies no underlying time logs. Its separate 26% food-cost figure is a best week, not a sustained average.

Prompt

I run a barbecue kitchen and use spreadsheets for inventory, recipe costs and prep. I’m using Claude Code to build a small operations app. My current sheets are [attach files], and our units and daily routine are [describe].

1. Explain how the sheets work now. Identify formulas, units and missing inputs before building anything.
2. Propose a simple inventory, recipe-cost and daily-prep layout. Show sample calculations using the supplied numbers, then ask me to confirm it.
3. After I confirm, build a prototype I can review. Explain how to compare it with our sheets.

Keep the explanation to one page in plain words. Don’t guess ingredient prices or convert units silently. Leave scheduling, catering and invoicing for later.

Do it yourself

These steps are my suggested way in, not Joe Zavala’s setup.

Level: Advanced for a shared app your team logs into. Cleaning up one spreadsheet with a chat assistant is Beginner.

What you need

  • The spreadsheets you use now for inventory, recipes and prep.
  • A chat assistant that can read files, such as Claude or ChatGPT.
  • For the full version: an AI coding agent such as Claude Code, and someone who can help you host the app.

Start simple

  1. Pick one sheet that eats the most time, such as recipe costs.
  2. Remove anything private, then upload it to a chat and use the Prompt’s first step to review the sheet.
  3. Ask it to explain how your sheet works today and list any broken or missing formulas.
  4. Ask for a cleaner version with one tab for ingredients and prices and one for recipes.
  5. Use the new sheet for a week next to the old one.

Take it further

  • Add a daily prep list that pulls from recipes and expected covers.
  • Once the sheets work, have a coding agent turn them into a small app with logins for your team.
  • Add scheduling, catering or invoices one at a time, never all at once.

Check your work

  • Cost three dishes by hand and compare them with the tool. Units are the usual mistake.
  • Run old and new side by side for at least two weeks before you drop the spreadsheets.
  • Keep staff pay and customer payment details out of anything you haven’t secured.

Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: 12 team members using the system. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.

More in Operations

New cases go out every Saturday in Inside AI.