EXAMPLEIllustrative example · fictional restaurant «Sazón de Origen». Not your data: your result is built with YOUR restaurant's.See the assistant →
Sazón de OrigenFictional contemporary Colombian restaurant in Medellín, 2 locations, 6 years in business. Every sample result in the library comes from this same case.
Automations

Sample result

Recurring Cycle Builder for Restaurants

The owner asked this:«Every month I review the numbers with my accountant and we always end up arguing about the same thing: why food cost went up. We do it differently every time, sometimes with the POS report and sometimes with the purchasing sheet, and a written plan never comes out of it. I want to turn that into a routine that always runs the same way, is handled by my manager, and does not eat half my morning.»

① The cycle card

Name: Monthly Profit Close.

Which decision it helps make: what gets fixed next month and who fixes it — not «how did we do».

If nobody runs it: food cost gets argued from memory, the same conversation repeats in March as in February, and no owner with a date is left.

VERDICT: it is a cycle. It returns 12 times a year, its steps chain, and there is a decision behind it. Note: if you only wanted the report and not the plan, it would be a standalone prompt and it would tell you so.

② Trigger and cadence

Trigger: the POS closes the month (it happens on its own, it does not depend on you remembering).

Cadence: the 3rd of each month, 9:00. Not «early in the month»: the 3rd.

Why the 3rd and not the 1st: on the 1st the POS has not consolidated credit notes yet, and a cycle fed by a figure still moving is a cycle that lies.

The full example has 3 more part(s): you see them inside the library, with your account.