Jimenez Julien, the person behind FreezerFive

Why I built this for meal prep kitchens

FreezerFive started in a rented commissary kitchen in the Midwest, standing next to an owner named Dana at eleven at night while she reconciled sixty three orders against a recipe binder written for six portions. She was not confused and she was not slow. She was doing arithmetic that no cook should have to do twice a week, in a room where the freezer was already humming and the produce was already bought. What struck me was that every single number she needed already existed somewhere in her order inbox. Nothing was missing. It was just scattered.

I have built software for small operators for over a decade, mostly in trades where the business runs on a weekly rhythm and the owner is also the person doing the work. Meal prep kitchens have a rhythm tighter than most: menu out, cutoff, purchase, thaw, prep, pack, drive. Miss one beat and the whole week limps. When I looked at what was on offer, it was either restaurant point of sale software built for tickets rather than weeks, or generic subscription tools that had no idea what a yield or a case pack is. Neither of them knew that a recipe scales with rounding rules, that allergens must inherit from ingredient to dish, or that a delivery route is really a question about which stops share a zip code and a time window.

So I wrote the thing that was missing, starting with the scaling engine because that is where the trust lives. If the pounds are wrong, nothing else matters. I spent the first six months doing nothing but sitting with owners on their cutoff nights, comparing what the system produced against what they would have written by hand, and correcting the model until the two matched every time. Only after that did I build the pick lists, the labels and the route groups on top.

What I learned about this trade

The first lesson was that the owners already have a system. It is on paper, in a spreadsheet, or in their head, and it works. My job was never to replace their judgment, only to remove the repetitive counting that stands between their judgment and the pan. The second lesson was about allergens. Every owner I met carried the restrictions of their families in memory, and every one of them described the same quiet fear about the morning they would be tired and forget. Making the flag travel from ingredient to dish to printed label was the single change that got the strongest reaction.

The third lesson was about volume. Growth in this trade is not a curve, it is a step. A kitchen goes from forty portions to a hundred and forty because one school parent group signed up, and the admin work that was tolerable on Sunday becomes impossible on Wednesday. Software should absorb that step without asking the owner to change how she cooks.

Experience and expertise

• Twelve years building and running production software for independent operators, working directly with owners rather than through account managers.
• Four years specifically inside meal prep and freezer meal operations, from home cottage licenses to licensed commissary kitchens running several delivery days.
• Hands on work on recipe yield modeling, unit conversion, allergen data structures, purveyor ordering formats and route clustering.
• Publication director of MLJ, SASU, the company that publishes FreezerFive and stands behind it commercially.

How this product is built and maintained

Every feature in FreezerFive traces back to a named kitchen that asked for it during a real production week. Nothing ships because it looks good in a screenshot. Changes go out on a weekly cycle, always after the cutoff windows most of our kitchens use, and never on a Thursday. Recipe and order data is backed up daily and restorable to any point in the previous thirty days.

The writing on this site follows the same rule as the software. Every number published here comes from anonymized aggregate usage across active accounts or from a customer who agreed to be quoted by name, and I update figures when they move rather than leaving a flattering one in place. If you find a claim on this site you think is wrong, write to me and I will either show you the underlying measurement or change the page.

I am accountable for three things: that the ingredient math is correct, that your data stays yours, and that a support email gets a real answer from a person within one business day. Those are the promises I will not delegate.

Contact the author

The fastest way to reach me is email at jimenezjulien42@gmail.com. If you would rather show than tell, send a week of your orders and your current menu and I will load them into a sample account before we talk. You can also request a walkthrough from the contact form on the home page.

Profiles

• jimenezjulien.com
• X, @mljjulien
• LinkedIn
• Facebook
• Instagram