The first pilot
What we’re building first.
A first pilot needs to tell us what to change—not simply give us a launch to announce.
2 minute read
Define the useful journey.
Loope is developing a low-speed ride service delivered through small electric pods. The proposed first pilot would bring together the rider app, pods, and an operating team within a defined service area. Rides are not currently available.
The starting conversation with a property partner should identify a specific movement problem. Which destinations are difficult to connect today? Who makes those trips, and when? What transportation already serves them? A pilot needs a useful role alongside those existing options.
From there, we would agree a manageable set of destinations, designated stops, service hours, and operating responsibilities. The property contributes knowledge of the place; the pilot scope must also reflect the capability we can demonstrate.
Observe where the journey breaks down.
For riders, useful observations would include whether people find the pickup without assistance, understand their request status, and know how to change a plan or get help. Repeated confusion at one stop would be a reason to examine its location or guidance, even if the app screen itself worked as designed.
For operations, we would examine whether requests can be matched to available pods, how exceptions are handled, and what charging, cleaning, maintenance, and support require across a service day. A recurring gap in pod availability could point to the operating plan, the route scope, or the resources needed to run it.
Pod development also needs to establish boarding, passenger fit, comfort, and readiness for passenger service. Artwork communicates a design direction; it is not evidence that those questions have been resolved.
Agree what the evidence will mean.
Before testing, we should agree with the partner which observations matter, how to collect them, and what would prompt a change or pause. We have not set public performance targets. The measures need to fit the actual pilot rather than give a proposal an appearance of precision.
A useful result might lead to fewer stops, clearer pickup guidance, different hours, or a revised operating responsibility. Expansion should depend on a service that people find useful and a team that can support it consistently, including when plans go wrong.
Autonomy and broader integrations remain longer-term ambitions. The first decision is more immediate: can this focused service support these journeys in this place, and what must change before it grows?
Let’s talk about useful journeys and a focused first pilot.
Bring Loope to your district