Most delivery plans look sound on paper. The collection time suits the kitchen or the warehouse, the route fits neatly on a map and the cost per drop works in the spreadsheet.
Then the first real week arrives. The goods are ready twenty minutes after the courier. One recipient only accepts deliveries at a side entrance. A van is booked where a car would have done, or the other way round. Nobody has decided who calls the customer when a delivery cannot be completed.
None of this means the model is wrong. It means it has not been tested yet.
For a founder launching a delivery promise, or an established business adding a new product line, site or customer service, a pilot is the cheapest point at which to find out. This article explains what a useful delivery pilot should test, how to run one and how to tell when it is ready to scale.
Part 1 of 4 in our series on building a delivery operation: test the delivery model (this article), design the operation, turn it into a repeatable process and automate the process.
Key Takeaways
- A pilot tests an operating model, not only a price.
- Test the whole job: timing, access, handover, information, exceptions and capacity.
- Record what was planned against what happened, including the jobs that went well.
- Judge the pilot on repeatability, not on one good day.
- Scale only what the evidence supports.
A pilot is not a cheaper trial delivery
It is tempting to treat a first run as a trial of the courier: book a few jobs, see whether they arrive, compare the price.
That tells you very little. A delivery that arrives on a quiet Tuesday with a flexible recipient proves that the courier can drive. It does not prove that the model works when volumes rise, when the collection is late or when the person who usually signs is away.
A useful pilot tests the operating model: the promise you are making to your own customers, the process behind it and the assumptions in your costs. The courier is part of that test, and so are your collection times, your recipient information and the way exceptions are handled. If you are also comparing providers, our guide to choosing a courier partner sets out the questions worth asking.
The difference matters because a pilot is where you can still change the model cheaply. Once software has been built around it, staff have been hired for it or customers have been promised it, every correction costs more.
What a useful delivery pilot should test
Most delivery models rest on the same handful of assumptions. A pilot should test each one deliberately rather than hoping it holds.
Timing
- Collection windows. Is the item ready when the courier arrives, every time?
- Actual route timings. How long does the route take at the hour it will run, including parking and access?
- Recipient windows. When can each recipient take delivery, and what happens outside that window?
The physical job
- Volume. How much moves on a normal day, a light day and a busy one?
- Vehicle requirements. Does the load, its size and its handling fit the vehicle booked?
- Loading and access. Entrances, keys, goods lifts, loading bays and security desks.
- Handover. Who can receive, what they need to check and how the item should be presented.
Information and communication
- Recipient information. Are names, numbers and instructions complete before the job starts?
- Communication. Who is told what, when, and through which channel?
- Proof of delivery. What evidence closes the job, and does it answer the questions your customers will ask?
Exceptions, capacity and cost
- Exceptions. What happens when a recipient is absent, an address is wrong or an item is not ready?
- Courier capacity. Is there cover if a courier is unavailable or the volume doubles?
- Cost assumptions. Does the real cost per drop match the plan once waiting and failed attempts are counted?
- Repeatability. Could the same result be produced next week by a different courier?
The last question matters most. A pilot that only works because one experienced person is holding it together has not yet produced a model.
How to run a pilot that tells you something
A pilot does not need to be large. It needs to be designed so that its result means something.
- Start with one question. For example: can we offer next-morning delivery to our central London customers at this cost?
- Keep the scope small but real. One route, one site, one customer group or one collection pattern, run under normal trading conditions.
- Agree the brief before the first job. Addresses, windows, contacts, handling notes and the evidence that closes a delivery.
- Record planned against actual. The planned collection time, the time the goods were ready, arrival, handover and the cause of any delay.
- Keep the exceptions. A missed recipient or a late collection is the most useful data a pilot produces.
- Review together. Both sides should look at the record before anyone decides to extend, change or stop.
Run it long enough to meet the variation your business will face: a quiet day, a busy day and at least one change of plan. A single perfect week is encouraging, but it is not evidence.
Inside Selena
When a business asks us to support a new delivery model, we usually suggest starting with one agreed pattern rather than a full rollout. For an early-stage founder, that might be one or two fixed collection times each day with ad-hoc support around them. Once the real volume and geography are clear, it becomes possible to judge whether a planned route or a dedicated courier day would serve the business better.
We take the same approach when we join an existing operation. When a London florist asked us for cover alongside its existing courier, we agreed to begin with a single paid trial. The arrangement is still at that stage: the service will be extended only after the first completed job has been reviewed with the client.
What a pilot often reveals
The findings are rarely dramatic. They are usually small and specific, which is exactly why they are worth finding early.
Time is lost at the door rather than on the road. On new routes, delays tend to come from access: keys, loading bays, goods lifts and reception desks that were never part of the plan.
Collection readiness is the real schedule. If goods are regularly ready later than planned, the route is built around the wrong time. Recording the actual ready time, not only the booked time, shows this within days.
Recipient information decides the handover. A missing phone number, a general inbox instead of a named contact or an instruction that lives only in someone’s memory will cause more failed handovers than traffic.
Success can hide a capacity problem. A week in which every job was completed may still have depended on one courier working longer than planned, or on the only spare vehicle. That is a warning, even though the deliveries arrived.
Elena's Perspective
Founders often ask me for a price per drop in our first conversation. I understand why, but at that stage the price is the least reliable number in the plan. The founder does not yet know the real volume, the geography or what their customers will expect at the door.
What they need first is help to design a delivery journey they can keep promising. A small pilot gives us both the facts. The rate follows from those facts, not the other way round.
How to tell when a delivery model is ready to scale
Before extending a pilot, check:
- Do collections happen at the planned time on most days, and is the cause of each late one understood?
- Are route timings based on the hour the route will run, not an estimate?
- Is recipient information complete before the courier sets off?
- Does every exception have an owner and a known response?
- Is proof of delivery consistent enough to answer a customer query?
- Is there cover if a courier or vehicle is unavailable?
- Does the real cost per drop match the plan once waiting and failed attempts are counted?
- Could a different, briefed courier run the same route to the same standard?
If several answers are still uncertain, extend the pilot or change the model before you scale it. Scaling multiplies what already exists, including the gaps.
From a successful pilot to a delivery process
A pilot that works is the start of the next stage, not the end. What was learned has to be written down and turned into a process that runs the same way next month, whoever is on the route. We cover that step in how to turn a pilot into a repeatable process.
That is where a delivery partner becomes more useful than a list of bookings. Through our Embedded Delivery Solutions, Selena helps London businesses test a delivery model, turn it into a planned, recurring route and keep it under review as volumes and sites change. One-off and urgent work can still run alongside it through our same-day courier service.
If you are planning a new delivery model, tell us what needs to move, where and how often. We will suggest a pilot that tests the parts of the plan that matter most.
