Get your kitchen on the grid.

The Grid Cook is a kitchen operations system for people who feed a household week after week: a method, and the software I built to run it. One planned cooking session a week, a fridge that reads like an inventory, and weeknight dinners that are assembly rather than cooking.

I'm Dima, and I'm The Grid Cook: I turn kitchen chaos into a system — first in my own kitchen, now in other people's.

COMPONENTS PROTEIN GRAIN VEGETABLE FLAVOR DISHES

The system

Recipes tell you what to cook tonight. An operations system decides what your kitchen produces this week, and in what order. It has five parts.

  1. 01

    Products

    The raw materials, chosen by how they store and how they cook — not by what a recipe happens to call for. A short list, bought the same way every week.

  2. 02

    Components

    What a cooking session actually makes: a protein, a base, a vegetable, a sauce — cooked in batches, portioned, labelled. A handful of components combine into more dinners than the same number of recipes.

  3. 03

    Assembly

    A weeknight dinner is a plate put together from components already in the fridge or freezer. Heat, combine, plate.

  4. 04

    The weekly plan

    Dishes go on days; the plan works backwards from there — which components, which products, what to buy, what is already on the shelf — and ends in a production plan for the session: one page, in order, by workstation.

  5. 05

    The cycle

    Storage decides how far a week stretches: the first days eat from the fridge, the later ones from the freezer, and every session puts a few portions into a reserve. The plan gets modified when the week goes sideways. The system does not get abandoned.

What it asks of you: one cooking session a week that is planned, not improvised; a fridge and freezer you keep labelled; and a plan you follow before you start changing it.

What I offer

I built the first version of this system for a food operation I was running — on software made for companies: heavy, complicated, built for a production line rather than a kitchen. So I wrote my own. Same discipline, adapted to home cooking and household volumes. That software is the core of the system; the course is how you learn to run it.

The course

The course comes first: eight modules, from a kitchen audit to your second full weekly cycle. It changes how you think about the kitchen — recipes and willpower out, a system and a process in — and then teaches you to run the app the way it was built to be run. Each module ends with something done in your kitchen, not something watched.

Coming soon

The app

The app is what the system runs on. It puts the dishes on the days and does the arithmetic: the components those dishes need, the products behind them, the shopping list by store section, and the production sessions that cook it all — in order, with timings. A pantry that keeps its own stock, so the list stops asking for what is already on the shelf. And a kitchen sheet to run the session from, at the stove.

Coming soon

In-kitchen sessions

The course and the app are how you run the system yourself. This is how you hand it over: I come to your kitchen and cook a week of food for your family in one visit. The Garraf comarca, province of Barcelona.

The service, prices and conditions

* Available only together with the course.

Who is behind it

Dima Sharonov

Dmitrii on the paperwork. Software developer by trade; the operator of this system.

The food operation that started all this is gone; the system it forced into existence stayed. It has run my own kitchen every week since, and now it runs in other people's.