Private beta · By invitation

Route operations intelligence

Route planning that gets smarter after the truck leaves.

CoeRoute is a private-beta platform for operators who need more than a route sequence: cleaner customer data, real road-network solves, driver-ready dispatch, and a feedback loop from the routes your team actually runs.

Import messy stops Optimize on road distances Dispatch driver links Learn from route execution

Private beta by invitation. Prospects evaluate CoeRoute through Luke-led conversations before platform access is granted.

ROUTE BOARD LANCASTER · WED
47Stops
4Trucks
162.4Miles
HighConfidence
R-0112 stops41.8 mi
R-0211 stops38.6 mi
R-0313 stops44.9 mi
R-0411 stops37.1 mi
Alert Mercy Hospital averages 14 min service time, not the planned 10 min. Apply learned value before next solve.
Real road networkOSRM / Mapbox-ready matrices
Solver coreGoogle OR-Tools CVRP
Driver loopTap capture; GPS dwell next
Operations surfaceImport · Solve · Dispatch · Learn
New wedge · Private beta

Most route tools optimize once. CoeRoute becomes the operating memory around the route.

The wedge is not another map with colored lines. CoeRoute connects planning, dispatch, field execution, and post-route learning so each completed route improves the next planning cycle.

1

Messy data intake

Customer addresses, demand, service-time assumptions, current assignments, truck limits, and depot rules are normalized before they reach the solver.

2

Explainable solve

Routes are built on real road distances with visible workload, capacity, mileage, and assignment tradeoffs — not black-box territory drawings.

3

Operational dispatch

Locked plans turn into driver-specific route links, exports, and dispatcher review surfaces so the plan can actually move into the day.

4

Learning loop

Driver events, dwell signals, post-mortems, and service-time drift become better assumptions for the next solve.

Where CoeRoute differs from generic routing software

  • Built for ongoing route maintenance, not one-off route drawing
  • Surfaces data quality problems before they create bad routes
  • Shows before/after comparisons against the operation you run today
  • Keeps dispatcher review, driver execution, and post-route learning in one loop

What the platform makes visible

BaselineCurrent assignments vs. optimized alternatives
BalanceStops, demand, capacity, and workload across trucks
RealityRoad-network distance, service-time drift, and field variance
ExecutionFrom locked plan to driver link to completed-route feedback

Access is intentionally controlled while the product matures: prospects go through Luke before entering the platform.

What CoeRoute does today

One workflow from raw stops to a route your team can run.

Most routing tools stop at the optimized sequence. CoeRoute keeps going: it helps you clean up customer data, compare the plan against your current routes, dispatch to drivers, and use the actual day to improve tomorrow's assumptions.

01

Import customer stops without babysitting the data.

Upload CSVs with addresses, coordinates, demand, service time, and truck preferences. The app validates columns, geocodes missing coordinates, caches results, and lets operators correct bad addresses before they poison a route.

02

Solve using real driving distances.

CoeRoute builds road-network distance and duration matrices, then uses OR-Tools to assign stops across the fleet under capacity, depot, and service assumptions. That means routes reflect roads, not straight-line guesses.

03

Inspect, stage, and lock route changes.

Dispatchers can review maps, truck loads, stop order, and projected mileage impacts before locking a route. Manual moves are staged first so the operator sees consequences before committing.

04

Compare against the route you run now.

Upload current route assignments and see before/after miles, time, and workload balance. CoeRoute is built to answer the practical buyer question: “Is this route better enough to change how we work?”

05

Dispatch driver-specific route links.

Locked routes become driver views reachable at drive.coeroute.com, with SMS/email dispatch hooks where configured and copy/paste links when messaging is not connected yet.

06

Manage the operating system around the route.

Customers, fleet, drivers, route history, usage, and tenant boundaries live in the product. CoeRoute is more than a solver script; it is an operations console for maintaining routes over time.

The operator workflow

From spreadsheet to dispatched route, then back into better data.

1

Load

Bring in customer addresses, coordinates, demand, service-time assumptions, current assignments, and fleet limits.

2

Clean

Resolve geocoding misses, review address-confidence flags, and cache known-good locations for future solves.

3

Solve

Generate routes with real road distances, configurable vehicles, depot assumptions, capacity limits, and cost-function choices.

4

Review

Explore the map, route tree, mileage totals, workload balance, and insertion/move costs before committing the plan.

5

Dispatch

Send drivers secure route links. Drivers tap arrived/complete today; passive GPS dwell and day-bracket capture are next on the roadmap.

6

Learn

Post-mortems reveal variance, reordered stops, service-time drift, and concrete updates to apply before the next route cycle.

The moat

Every completed route becomes training data for the next plan.

Generic solvers know the map. CoeRoute learns the operation: which customer docks take longer, where drivers reverse the order, which stops need a practical time window, and where OSRM's estimate misses the real world.

Tap dataArrived + Service Complete events capture precise service time when drivers participate.
Passive dwellRoadmap: GPS waypoints will infer arrival and departure when the driver page or native shell is open.
Day bracketRoadmap: a Start day / Done fallback will allocate elapsed work across stops when no per-stop capture exists.
Dispatcher actionApply learned service times, inspect route post-mortems, and spot reorder patterns before they compound.

Why it matters

Efficient routes are not a one-time optimization problem.

Less manual planning time

Repeatable CSV import, cached distance matrices, and route history reduce the spreadsheet grind.

Fewer hidden route costs

Road-network distances, workload balance, and before/after comparison make the tradeoffs visible.

Routes drivers can actually run

Driver capture turns field reality into service-time updates, post-mortems, and better next-week assumptions.

A system that compounds

Each route adds operational evidence instead of disappearing into memory and dispatch folklore.

Private beta access

CoeRoute is shown through founder-led prospect conversations.

This site is meant to help prospects understand the platform before Luke grants access. The current focus is qualified, relationship-led evaluation — not inbound requests or self-serve signup.

Marketing site for prospects Invitation-only platform access No public trial or open signup