Solutions
Meal delivery software for business owners
The owner’s problem is not a lack of numbers. It is that the numbers live in different files, disagree with each other, and take a person half a day to assemble — by which point they describe last week.
Why the weekly figures never quite agree
In a spreadsheet-run kitchen, revenue comes from one file, meal counts from another, and customer status from a third. Each is maintained by a different person on a different day, and each is a copy of a decision recorded somewhere else.
They disagree because copies always do. A customer who upgraded on Tuesday is on the new plan in the order master and the old one in the revenue sheet, and the difference is invisible until somebody notices the total is wrong.
The fix is not a better dashboard on top of the same files. It is having the figures derive from the operational records themselves, so there is no second copy to fall out of step.
The four questions worth answering weekly
Not a comprehensive metrics programme — the small set that actually changes decisions.
What is committed revenue this month?
Recurring revenue from live subscriptions, not last month’s invoices. It tells you what you have before you spend it.
How many meals a week are we committed to producing?
The number the kitchen must hit. Compared against capacity it tells you whether the next ten customers are growth or a crisis.
Who is drifting?
Paused subscriptions that have not resumed, and plans approaching renewal. Churn is usually visible for weeks before it happens.
What is a portion actually costing?
Derived from recipe costs and current ingredient prices, not from a figure someone worked out at launch and never revisited.
Capacity is the constraint nobody tracks
Most meal businesses that get into trouble do not do so because demand dried up. They do so because demand grew past what the kitchen and the delivery day could absorb, and nothing in the system said so until quality slipped.
Meals per week against your realistic production ceiling is the single most useful number an owner can hold, and it is one almost nobody computes, because it requires production and subscription data in the same place.
The same is true of the delivery day. Stops per route and the geographic spread of your customers set a hard limit on how many households you can serve well, and it is usually reached before the kitchen’s limit is.
What an owner should not have to do
Ask someone to assemble a report. If a figure requires a person to compile it, you will look at it monthly at best, and you will be making decisions on a picture that is several weeks old.
Nor should the numbers require trust in whoever assembled them. Every figure ought to be traceable to the records that produced it — this subscription, this production run, this delivery — so a surprising number can be investigated rather than argued about.
That traceability is the point of holding the operation in one system rather than five files. The dashboard is a consequence, not the product.
Common questions
- Where do the revenue figures come from?
- From live subscription records — the same ones production and delivery run on. There is no separate revenue file to reconcile, which is what stops the figures disagreeing with each other.
- Can I see whether we are near capacity?
- Committed meals per week is shown against the production and delivery day, so growth that is about to outrun the kitchen is visible before quality slips rather than after.
- Does it forecast revenue?
- No. It reports committed recurring revenue from current subscriptions and what has actually been invoiced. Projection based on assumed growth is not something we generate, because it would be a guess presented as data.
- How current are the figures?
- They are computed from the operational records as they stand, so a change made this morning is reflected without anyone rebuilding a report.
The numbers, without the assembly
See the dashboard computed from a demonstration kitchen’s live records — subscriptions, production and delivery in one place.
Related reading
- SolutionsMeal delivery management software for the daily operating rhythmEvery meal-plan business runs the same loop every single day — cook, pack, drive, confirm. Management software earns its place by making the current position of that loop visible without anyone compiling it.
- GuidesThe numbers a meal-plan business should actually trackMost meal-plan operators track revenue and headcount because those are easy. The numbers that predict next quarter are operational, and nearly all of them are already sitting in records you keep anyway.
- GuidesWhat a meal delivery dashboard should actually showThe test of a dashboard is whether anyone opens it before noon. Reports get opened monthly; operating tools get opened daily, and the difference is entirely in what they show.
- GuidesWorking out how many customers you can actually serveMost operators estimate capacity from their kitchen equipment and then discover the real ceiling somewhere else entirely — usually in the delivery window or in the coordination workload.
- GuidesRenewals and churn in a meal-plan businessMost meal-plan customers do not leave in a dramatic moment. Their term quietly ends, nobody notices, and a month later they are simply gone — which makes renewal an operational problem before it is a marketing one.