Guides
Hiring the first operations person in a meal business
The 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.
You are not hiring hands
Founders reach this point feeling overloaded and hire for capacity. But the work they are handing over is rarely mechanical: it is deciding whether to honour a late pause, whether a substitution is acceptable, whether a distant customer is worth serving.
Those are judgements, currently held in one head, and applied consistently only because one person makes all of them. Handing them to a second person without writing them down produces inconsistency that customers notice before anybody internally does.
The practical implication is that documenting the rules is a precondition of the hire rather than something to do afterwards when there is time.
Write these down before they start
The cut-off and what happens after it
Including whether exceptions are ever made and who may authorise one.
The pause and skip rules
Extend or forfeit, and how much notice is required.
Failed delivery handling
Redeliver, credit or neither, applied identically.
Substitution rules
Especially the allergen constraint, which is the one place inconsistency is dangerous rather than merely annoying.
The service boundary
Which areas, on which days, and who decides on an exception.
What to hand over first
Give away the repetitive, rule-bound work before the judgement-heavy work: applying pauses and skips, chasing selections before the cut-off, closing out failed deliveries. These have clear right answers and produce quick confidence for both sides.
Hold customer-facing exceptions and supplier decisions longer. Those depend on relationships and commercial judgement that genuinely takes months to transfer, and handing them over early is how a good hire ends up looking like a bad one.
Consider whether the answer is a hire at all
Some of what feels like an overload is work that should not exist. If a large share of the day is applying customer changes that customers could apply themselves, or rebuilding a production sheet that could be derived, hiring distributes that work rather than removing it — and permanently raises cost per customer.
The honest test is to log a fortnight and mark each task as judgement or mechanical. If the mechanical share dominates, fix that first; the hire will be more valuable and less urgent afterwards.
That said, there is a real floor. One person cannot be on the road, at the bench and answering messages simultaneously, and no amount of automation changes that. The point is to hire against the genuine constraint rather than against the accumulated inefficiency.
Common questions
- What goes wrong with the first operations hire?
- The founder hires for capacity but hands over judgement — late pauses, substitutions, service-area exceptions — that was never written down. The result is inconsistency customers notice before anyone internally does.
- What should be documented before they start?
- The cut-off and its exceptions, pause and skip rules, failed delivery handling, substitution rules including the allergen constraint, and the service boundary with who may vary it.
- What should be handed over first?
- Rule-bound repetitive work — applying pauses, chasing selections, closing out failed deliveries. Customer-facing exceptions and supplier decisions depend on judgement that takes months to transfer.
- Is hiring always the right answer to feeling overloaded?
- Not always. Log a fortnight and mark each task as judgement or mechanical. If mechanical work dominates, hiring distributes it rather than removing it and permanently raises cost per customer.
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
- GuidesWhy meal-prep operations break at a predictable sizeMeal-plan businesses rarely stall because demand ran out. They stall because the coordination cost of each additional customer stops being close to zero, and nobody notices until the week it does.
- GuidesA daily operations checklist for a meal-plan kitchenMost operational checklists are organised by department, which is convenient and wrong. Ordering them by when a problem is still cheap to fix is what makes a checklist worth running.
- SolutionsCustomer self-service for meal plansEvery routine change a customer cannot make themselves becomes a message someone has to read, interpret and apply correctly before a cut-off. That workload grows with your customer count, not with your feature list.
- GuidesDeciding which areas you actually serveAlmost no meal-plan business decides its service area. It accumulates, one reasonable exception at a time, until a driver is spending ninety minutes reaching three customers.
- SolutionsRoles and permissions in meal-plan softwareA meal-plan system holds names, phone numbers, home addresses and health information. Who can see which parts of that is a privacy decision before it is a convenience one.
- GuidesA launch checklist for a meal delivery serviceThe items below are ordered by how expensive they become once customers exist. Everything near the top is nearly free to decide now and requires a conversation with every customer to change later.