How it works

From first idea to final plate cost, held to one standard


ChefPro.ai carries a menu through its whole life as one guided sequence, applies fixed rules that never change, and runs a final check that stops anything it cannot support.

The guided sequence

One workflow, four stages, costed as it goes

Each stage carries the discipline with it, so the standard is not something added at the end. It is applied the whole way through.

  1. 01Start from your way of cooking

    Concept

    You set the brief: the house standard, the constraints, the way this kitchen cooks. ChefPro.ai works from that, grounded in your own curated evidence base rather than whatever it found on the open web.

  2. 02Develop to the standard

    Development

    It develops dishes that fit the brief, inside fixed rules that never change. Stock bases, allergens, and pairing logic are applied the same way every time, so the standard holds from the first dish to the last.

  3. 03Build the menu, not just the dish

    Composition

    Dishes are composed into a menu with balance and sequence considered. Where a traditional technique is drawn on, its source is credited rather than quietly absorbed.

  4. 04Cost as you create

    Costing

    Plate cost, yields, and margins are part of the same workflow, not a separate spreadsheet afterwards. The number is there while the menu is still being shaped, when it can still change the decision.

The verification gate

The work does not pass until it holds

Before anything reaches the pass, it goes through a final check. Where the system cannot support a claim, it does not invent one. It holds the item for review and says why.

Held to the line
A guided path, bounded by a standard. The work moves forward only when the check is satisfied.

This is the honest part of the design. No system that generates is provably free of error. ChefPro.ai does not claim to be. What it does is lower the rate, and make the residue catchable: an unverified allergen is flagged and held, not waved through.

That single behaviour, refusing to pass what it cannot support, is what makes the output safe to put in front of a brigade, a guest, or a class.

Technical note

For readers who want the engine names: the guided concept-to-cost workflow is called PARA, and the rules-and-verification layer that prevents invention is called CADI. You will not need either name to use ChefPro.ai. They are how the two halves, the path and the gate, are referred to in technical and credibility contexts.


Book a demo

Book a demo to walk a real menu through the workflow, from concept to costed pass.