Guides
A month-end checklist for a meal-plan business
Daily operations catch what is urgent. A monthly pass catches what is merely expensive — the slow leaks that never trigger an alarm.
The hour that pays for itself
Reconcile invoices against deliveries
Spot-check a sample. Any systematic mismatch is a process problem worth fixing now rather than after twenty more invoices.
Review long-paused customers
Anyone paused beyond sixty days is functionally churn. Decide whether to contact them or reclassify them, but stop counting them as active.
Check terms that expired quietly
Confirm nobody is still receiving food on a finished term. This is the purest form of loss in the business.
Compare food cost to plan price
Ingredient prices move continuously and plan prices do not. A monthly look catches erosion before it becomes a year.
Review failed deliveries
Repeat failures at the same address are an addressing problem, not bad luck.
Look at the expiring list for next month
So renewal conversations happen before the last delivery rather than after.
Why monthly is the right cadence
Weekly is too often for these to have moved meaningfully, and quarterly lets a cost drift run for three months before anyone looks. Monthly is short enough to correct and long enough to show a trend.
The exception is the expiring list, which should be a standing daily view rather than a monthly review — by month end, some of those customers have already gone.
Write the answers down
The value of this review is the trend, not the snapshot. A food cost figure on its own tells you nothing; the same figure next to the last five months tells you whether something is drifting and roughly when it started.
Keeping a short running note — six numbers and a sentence about anything unusual — turns an hour of checking into a record you can actually reason from, and it takes about two minutes more than not doing it.
Common questions
- What does a month-end review catch that daily operations miss?
- Slow leaks: cost drift, long-paused customers still counted as active, terms that expired without anyone noticing. None of them trigger an alarm on any given day.
- How long should this take?
- About an hour if the data is derived rather than assembled. If it takes a day, the problem is not the review — it is that the underlying numbers have to be reconstructed each time.
- Should the expiring list wait for month end?
- No. That one should be a standing daily view. By the time a monthly review runs, some of those customers have already finished and moved on.
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.
Related reading
- 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.
- GuidesRenewal best practices for meal subscriptionsThe renewal conversation that works happens while the customer is still receiving deliveries. After expiry you are asking someone to restart a habit they have already stopped.
- SolutionsRecipe costing for meal-plan businessesMost meal-plan operators can tell you their revenue precisely and their food cost approximately. The gap between those two levels of confidence is where the margin quietly goes.
- 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.
- SolutionsSoftware for recurring cateringCaterers moving from event work to recurring contracts discover that their existing systems model the wrong thing — and that meal-plan systems assume a fixed menu they do not have.
- GuidesHiring the first operations person in a meal businessThe first operations hire is where most meal-plan founders discover how much of the business was never written down — usually in the third week, when something goes wrong in a way it never did before.