Guides
The numbers a meal-plan business should actually track
Most 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.
The ones that predict something
Active subscriptions and meals per week
The two together describe committed demand. Headcount alone hides a base drifting to smaller plans.
Recurring revenue
Computed from live plan records rather than from last month’s invoices, so a pause shows up immediately rather than in arrears.
Expiring within 14 days
The single most actionable list available, and the one most often not built.
Long-paused customers
Paused for months is functionally churn. Counting them as active flatters everything downstream.
Failed delivery rate
An operational churn signal that appears well before the customer says anything.
Food cost as a share of plan price
Derived from the same bill of materials as purchasing, so it cannot drift from what you actually buy.
Why derived beats reported
A number typed into a monthly report is a snapshot of someone’s understanding at the time. A number derived from the operational records is a view of what is true now, and it cannot quietly disagree with the kitchen.
This matters most for revenue. If MRR is calculated from plans and terms rather than from historic invoices, a wave of pauses is visible the week it happens rather than a month later.
What we will not give you
Benchmarks. We have no defensible industry figures for churn, margin or food cost percentage in this sector, and inventing them would be worse than useless — you would make decisions against a number somebody made up.
Your own trend over the last six months is far more informative than a number from a blog anyway, because it reflects your market, your prices and your customers.
Common questions
- What is a good churn rate for a meal subscription business?
- We will not quote one, because we have no defensible industry data and an invented benchmark is worse than none. Track your own trend over six months; that comparison is genuinely informative.
- Should long-paused customers count as active?
- Functionally no. Someone paused for months generates no revenue and no operational load, and counting them as active inflates every other figure that depends on the active base.
- Why derive MRR rather than report it from invoices?
- Because invoices are historic. Derived from live plans and terms, a wave of pauses appears the week it happens instead of surfacing a month later in the billing run.
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
- 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.
- SolutionsThe customer record in a meal-plan business is an operational documentIn most industries a CRM is a sales tool. In a meal-plan kitchen the customer record drives what gets cooked and where it goes, which makes it the most operationally dangerous data in the business.
- 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.
- GuidesBilling a meal plan that keeps changingBilling here is harder than a flat subscription because the thing being billed for is physical and intermittent. The invoice has to agree with a stack of boxes that may or may not have arrived.
- 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.
- SolutionsMeal delivery software for business ownersThe 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.