Guides
Onboarding a new meal-plan customer
Signup is the only moment a customer will patiently answer questions. What you fail to capture there, you will spend the next six months chasing — or worse, guessing at.
Capture at signup, not later
Structured allergens
Not a notes box. Retrofitting structure means re-contacting your entire base, and until you do the automatic checks cannot run.
A precise delivery location
A map pin or Makani number plus access notes. Asking later, once deliveries are already failing, is a worse conversation.
Delivery days and start date
Which weekdays they receive on, and when the term begins, so the first week generates correctly without intervention.
Who to contact and how
Especially where the payer and the eater differ, as in corporate and family accounts.
The first delivery is the risky one
It is the delivery where the address has never been tested, the allergen record has never been exercised, and the customer has no basis yet for assuming a problem is unusual. A failure here is disproportionately likely to end the relationship.
Treating the first delivery as a checked event rather than a routine one — confirming the location resolves, confirming the allergen record produced a sensible label — costs very little and protects the relationship at its most fragile point.
Set expectations while they are listening
Signup is also when to explain the cut-off, how pausing works, and what happens if a delivery fails. A customer who learns the cut-off exists only when their late request is refused experiences it as a rule invented to inconvenience them.
The same sentence delivered at signup is simply how the service works, and it prevents most of the awkward conversations that follow.
Common questions
- What is the most commonly missed field at signup?
- A precise delivery location. A typed address feels sufficient until the first driver cannot find the door, and by then you are asking a customer to fix a problem you created.
- Why is the first delivery higher risk?
- Because the address, the allergen record and the whole chain are untested, and the customer has no history with you to judge whether a problem is unusual. Failures there disproportionately end the relationship.
- When should the cut-off be explained?
- At signup, while the customer is paying attention. Explained only when a late request is refused, it reads as an arbitrary rule rather than as how the service works.
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
- 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.
- GuidesPreventing meal delivery address errorsAddress problems look like small individual incidents and are actually one of the largest recurring costs in a delivery operation, because each one consumes two people at once.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- GuidesImplementing meal delivery software without a bad weekThe risk in this migration is not data loss. It is the week where half the operation is in one system and half in another, and nobody is certain which is authoritative.
- GuidesWhat to collect when a meal plan customer signs upEvery field you skip at signup becomes either a chase later or a guess. Two of them, added late, mean re-contacting your entire customer base.
- SolutionsSoftware for corporate meal providersCorporate meal programmes look like a bigger version of consumer meal plans and behave nothing like them. Three structural differences change almost every part of the operation.