Built by a working chef,
for independent restaurants.

Lewis built Good Provisions after years in professional kitchens, where food cost, vendor pricing, recipe costing, prep planning, and sales data often lived in separate places. Invoices were in one pile. Recipes were in another. POS sales were somewhere else. Menu prices were usually updated only after a problem had already shown up.

That is the reality for a lot of independent restaurants. The operator is busy running service, managing people, ordering product, handling events, fixing problems, and trying to protect margins at the same time. The numbers matter, but most tools make them harder to use than they should be.

The available options usually fall into two camps: expensive restaurant platforms built for larger groups, or spreadsheets that still require hours of manual updates. Neither one fits the pace of a real independent kitchen where decisions need to happen quickly.

Good Provisions was built to answer the questions operators ask every week:

• What does this dish actually cost me?
• Is this menu price still profitable?
• Which items are helping my margin?
• Which items are quietly hurting me?
• What changed in my vendor pricing?
• What should the kitchen prep based on what actually sells?

The goal is not to replace the operator’s judgment. The goal is to give that judgment better information. Good Provisions connects ingredients, invoices, recipes, menu pricing, sales imports, prep sheets, events, and weekly reporting into one practical workflow.

It has been tested with real restaurant data in a working kitchen environment, shaped around the needs of chefs and operators who do not have time to babysit complicated software.

Good Provisions exists for independent restaurants that want to stop guessing, tighten their numbers, and make better decisions before profit slips away.