Guides

Do you actually need meal delivery software?

We sell this software, so treat what follows accordingly — but the honest answer for a meaningful number of kitchens is not yet, and buying early tends to end with the spreadsheet running alongside the system.

The threshold is not the meal count

Operators usually ask "how many meals a week before I need software", and the number they are given is roughly two to four hundred. That is a symptom rather than the cause.

The real driver is coordination load: customers multiplied by how often they change something. A hundred customers who pause monthly generate more propagation work than three hundred who never change anything. Two kitchens at identical volume can sit on opposite sides of this line.

Signals in both directions

Not yetProbably now
One person can hold the whole week in their head.Nobody is confident the production sheet matches what customers ordered.
Plan structure and menu format still change monthly.The model has settled; the admin has not.
Customers rarely pause or swap.Amendments are the majority of customer contact.
Errors are rare and easily traced.Individual boxes go wrong and nobody can reconstruct why.
Purchasing is accurate by inspection.You are buying to a sheet you no longer fully trust.

What buying too early costs

A business still discovering its model needs to reshape things weekly, and a spreadsheet is unbeatable at that. Rigid software imposed on an unsettled model produces the worst outcome available: the system for the parts it handles, and a spreadsheet alongside it for everything else — two sources of truth instead of one.

If you recognise yourself in the left column, the better investment is writing down your process clearly. That costs nothing and makes the eventual migration far easier.

Common questions

Is there a meal count that means it is time?
Not reliably. Somewhere between two and four hundred meals a week is common, but it is really customers multiplied by change frequency — a smaller base that pauses constantly hits the wall sooner.
What is the cost of buying too early?
Usually running the software and the spreadsheet in parallel, which is strictly worse than either alone because you now maintain two sources of truth for the same facts.
What should I do if it is too early?
Write your process down properly — cut-off, pause rules, how a change reaches production. That costs nothing, improves things immediately, and makes the eventual migration much simpler.

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.