Customer stop CSV
Street, city, state, ZIP, latitude/longitude if available, demand/load, and any known service-time assumptions.
Pilot request
Bring the route file your team actually uses.
CoeRoute is not trying to impress you with a toy demo. Send a real customer list, current route assignment, or messy spreadsheet and we will evaluate the route workflow against your operation.
Email directly
Start the conversation with Luke.
Include what kind of operation you run, how many stops and trucks are involved, and whether you have current route assignments for comparison. Do not send secrets or private credentials.
luke.coe@coeroute.comHelpful context
What makes a pilot useful.
The more closely the pilot mirrors your real planning cycle, the more clearly CoeRoute can show where route maintenance improves: data cleanup, assignment quality, dispatch flow, and feedback from the field.
Current route assignment
If you have today's routes, include truck/driver assignment and stop order so CoeRoute can produce a before/after comparison.
Fleet constraints
Truck count, capacity limits, depot assumptions, driver territories, preferred trucks, and hard operational rules.
Operational pain
Where planning breaks down: bad addresses, too much manual routing, imbalanced trucks, late stops, driver deviations, or stale service-time estimates.
What we will look for
A pilot should produce operational evidence.
QualityDo routes reduce unnecessary mileage without creating impossible workloads?
ExplainabilityCan the dispatcher see why each assignment was made and what changes cost?
DispatchCan the route move cleanly from locked plan to driver-facing execution?
FeedbackCan the completed day reveal service-time drift, route deviations, and better next-route inputs?