Solutions
The customer record in a meal-plan business is an operational document
In 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.
A stale field here spoils food
If a contact record in a normal sales system is out of date, someone sends an email to the wrong address. If a meal-plan customer record is out of date, a kitchen cooks a dish containing an allergen, or a driver spends twenty minutes at a building the customer moved out of last month.
That difference should change how the record is treated: fewer free-text notes, more structured fields that other parts of the system actually read.
The fields that do operational work
Allergens and dietary needs
Structured rather than written in a notes box, because a notes box cannot raise a conflict warning against tomorrow’s production.
A precise delivery location
A pin plus access notes, not only a typed address, because that is what a driver can actually navigate to.
Current plan state
Active, paused, expiring — the field that determines whether this person generates work next week at all.
Delivery history
What actually arrived and what failed, which is the evidence behind any billing conversation.
The renewal window is where CRM value is concentrated
Meal plans end. The most valuable list a kitchen has is the customers whose term is about to run out, and the second most valuable is those whose term just did. Both are trivial to compute from data the business already holds, and both are commonly missed because nobody built the view.
This is the one genuinely commercial use of the customer record, and it is worth more than most outbound activity, because these are people who already know whether they liked the food.
Common questions
- Can a general-purpose CRM do this job?
- It can hold the contact details, but it cannot flag an allergen conflict against tomorrow’s production or remove a paused customer from a manifest. The operational half is the half that matters here, and it lives with the subscription data.
- Should allergies be free text?
- No. Structured allergen fields can be checked automatically against assigned meals; free text can only be read by a human who happens to look. On a busy morning, nobody looks.
- How should customer history inform renewals?
- By making expiring and recently expired subscriptions a standing view rather than a report someone requests. These are the highest-intent conversations available, and they are time-limited.
See it running against a real kitchen
The product pages show the actual admin, loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- SolutionsManaging mid-cycle subscription changes without re-typing themSelling the subscription is the easy part. The work is everything that happens after, when a customer changes something and five downstream systems need to hear about it before Tuesday.
- SolutionsOrder management when the orders repeat themselvesOrder management systems assume an order is created, fulfilled and closed. A meal-plan order is created once and fulfils itself over and over, which breaks most of the assumptions underneath the category.
- SolutionsMeal subscription software and the lifecycle it has to modelSubscription software for digital products only has to keep charging a card. A meal subscription also has to keep a kitchen, a packing bench and a van in step with whatever state it is in today.
- SolutionsInvoicing for meal-plan businessesAn invoice from a meal-plan kitchen has to agree with something physical — a set of boxes that did or did not arrive — which makes it harder to get right than a simple recurring charge.
- SolutionsMeal delivery software for finance and adminFinance in a meal-plan business spends most of its time on one question: does the amount we billed match what the customer actually received? Everything else follows from getting that right.
- GuidesWhy a general-purpose CRM struggles hereKitchens often start on a CRM because they already have one, and it holds contact details perfectly well. It fails for a reason that is about data model rather than features.