Plan a produce-box pilot before adding routes

A produce-box pilot should answer a concrete question: can this team assemble and hand over this offer, in this area, on the promised schedule, at a cost the business can support? A broad launch can obscure the answer. Different routes, changing quantities, and improvised collection points make it hard to see which part of the operation needs work. Start with one zone and a written plan that someone else could follow.

The worksheet below is a planning approach, not an industry benchmark. Use quotes, observed times, and your own trial records. Where a number is unknown, leave it visibly unknown and assign someone to find it. A spreadsheet filled with plausible guesses looks reassuring while leaving the real questions untouched. The pilot exists to replace the most consequential guesses with evidence.

Define the box before the budget

Write the contents rule, packing unit, frequency, and handoff method. Decide if the customer is buying a fixed assortment or a selection that varies with confirmed supply. State how quantities will be described and how substitutions will be communicated. Take a representative box through the entire packing process before promising it publicly. An assortment can look appealing on a table and fit poorly in its intended carton.

Choose a maximum order count based on the actual packing and handoff capacity you can test. Capacity includes suitable receiving and holding arrangements, available people, and the time window for the work. Confirm food handling requirements for the proposed operation with appropriate local authorities and qualified support. Keep those arrangements in the plan rather than assuming that a short route makes every handling method suitable.

Draw one practical zone

Mark the packing location, customer cluster, possible collection point, and return journey on a map. Check the streets and building access at the time you expect to operate. A small distance can still involve slow parking, stairs, reception desks, or restricted access. Record these details beside each planned stop. Travel time alone will understate the work if every handoff requires several minutes inside a building.

Compare home delivery with a collection point using the same order assumptions. Collection might reduce driving while introducing venue coordination and uncollected orders. Home delivery may be more convenient for customers but harder to schedule. Neither format wins by definition. Write down who does each task, where the goods wait, and what happens when the customer is absent. Ask prospective customers about the actual options you can provide.

The USDA’s aggregation and distribution resources can orient you to local food distribution models. Use those materials to develop questions for nearby operators. They do not supply the cost of your route, and an older example should not become a current financial assumption without verification.

Separate costs that behave differently

Create one group for costs tied closely to each order: produce, carton, inserts, and any payment charge that applies to that purchase. Create another for costs incurred for the delivery day or packing session: hired hours, vehicle use, venue charges, and preparation work. Keep initial purchases, such as reusable equipment, in a separate startup section. This makes it easier to see what changes when orders rise or fall.

Use a consistent basis for produce costs. If you buy by weight and pack by bunch, record how the purchased quantity becomes the packed unit. Track unusable or unallocated product separately rather than hiding it inside a rounded cost per box. The point is not to assign blame for every leaf. It is to understand the quantity the business must buy to fulfill the quantity it sells.

Labor deserves a line even when founders perform it. Record receiving, packing, loading, delivery, customer messages, and cleanup as separate activities. Use an explicit planning rate when valuing unpaid labor, and label it as an assumption. Later you can compare the estimate with the cost of hiring for that work. Leaving labor at zero prevents the worksheet from describing a repeatable business.

Work one illustrative calculation

Suppose a trial has 24 orders. For illustration only, imagine each order generates 30 units of revenue and 19 units of direct order cost. That leaves 11 units per order, or 264 across the trial, before shared operating costs. If the day’s labor, route, and venue costs total 240 units, 24 remain before overhead, tax, startup recovery, and other omitted expenses. These figures are invented teaching numbers, not recommended prices or expected margins.

Now imagine the same shared operating costs with only 18 orders. The 198 units remaining after direct order costs no longer cover the 240 units of shared costs. That change tells you why order density and minimum operating volume matter in this particular model. It does not tell you to pressure customers into larger commitments. You might revise the schedule, choose collection, reduce the service area, or change the offer after studying the actual constraints.

Keep the formulas visible: order contribution equals revenue minus direct order costs; pilot result equals total order contribution minus shared pilot costs. Document which expenses are still excluded. The SBA startup cost guide is useful for checking that initial and recurring expense categories have not been forgotten. Have an appropriate adviser review consequential financial decisions for the actual business.

Set deadlines around real supply

Work backward from handoff. Set a supplier confirmation time, customer order cutoff, final packing count, and deadline for communicating substitutions. Agree with growers about how changes will be reported. Record the person authorized to revise the box when expected produce is unavailable. A backup ingredient is only a backup if it is obtainable, suitable for the offer, and accurately reflected in customer information.

Make the customer exception process short and specific. Decide how to handle a missing item, a damaged box, a missed delivery, or a customer who changes plans after cutoff. Write the process in language a team member can use during a busy afternoon. Record exceptions during the pilot, including the minutes and direct expense they create. Routine service recovery belongs in the economics.

Review before widening the map

After each trial, compare planned and actual purchase quantities, packing time, route duration, exceptions, and repeat orders. Ask customers what they used and what made the handoff awkward. Separate an offer problem from an operational problem. If customers like the box but cannot meet the collection window, changing the vegetables will not fix the issue.

Finish with a written decision: repeat unchanged, revise a named part, or pause. Define the evidence you want from the next cycle before running it. Add another route only when the first one has a process another person can follow and costs you can explain. The immediate next step is a map of one zone, a trial packing session, and a worksheet with every unknown clearly marked.