Guides

Why meal-prep operations break at a predictable size

Meal-plan businesses rarely stall because demand ran out. They stall because the coordination cost of each additional customer stops being close to zero, and nobody notices until the week it does.

The coordination cost is what scales badly

Cooking scales reasonably well — more portions of the same recipe is mostly a labour and equipment question. What scales badly is the number of facts that must be kept consistent across several documents, because that grows with customers multiplied by how often they change something.

That is why the wall arrives suddenly. For a long time one person can hold the week in their head; then one week they cannot, and everything that depended on that quietly stops being true.

What fails first, roughly in order

  • Propagation of changes

    A pause or swap applied to some documents and not others. The first errors are individual, which makes them easy to dismiss as one-offs.

  • Purchasing accuracy

    Buying to a sheet that no longer matches the cook list, producing waste in one direction and shortages in the other.

  • Delivery accuracy

    Stale addresses and stops for customers who paused, both of which cost road time.

  • Renewals

    Terms ending unnoticed, which looks like a marketing problem and is actually an operational blind spot.

Which fixes buy real capacity

Hiring another coordinator postpones the problem and raises the cost per customer. The fixes that genuinely buy capacity are the ones that remove work rather than distribute it: deriving production and purchasing from a single set of selections, letting customers make their own routine changes, and enforcing the cut-off in software.

Each of those removes an entire category of daily task rather than making it faster, which is what changes the slope rather than the intercept.

Common questions

At what size do meal-prep operations usually struggle?
It varies with how often customers change their plans rather than with volume alone. A base that rarely changes can be coordinated by hand for far longer than one that pauses and swaps constantly at the same meal count.
Is hiring more coordinators a reasonable answer?
It buys time and raises cost per customer, and it does not address the underlying duplication. More people maintaining more copies of the same facts increases the number of places those facts can disagree.
What is the highest-leverage change to make first?
Deriving production and purchasing from one set of customer selections, so they cannot disagree. Almost every other operational failure at this scale is downstream of those two numbers drifting apart.

See how this works in practice

The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.