Pricing
No per-driver seats, no per-stop metering, no add-on maze. Every engagement begins with a route audit on your real data — platform access follows when the fit is proven.
Where every engagement starts: your data, our pipeline, an evidence packet.
For a single plant proving weekly route value with founder-led onboarding.
For plants that keep CoeRoute after the pilot proves value.
Controlled rollout. Start with the free Route Reality Audit. Buyer-1's already-committed design-partner rate is honored separately; all new public pricing is USD, flat per plant.
What a serious evaluation includes
The question is not whether a demo route looks tidy. The question is whether the plan explains mileage, workload, constraints, dispatch friction, and the service-time assumptions that make routes succeed or fail.
Optimized output is compared against your existing assignments, so the benefit is grounded in your real operation — not a synthetic benchmark.
Capacity, depot, truck count, demand, per-stop service times, locked stops, and service windows become explicit solver inputs instead of dispatcher tribal knowledge.
Driver taps, post-mortems, and service-time drift show how the plan improves after routes actually run — the part one-time optimization projects never deliver.
No. The platform is live, but access is intentionally controlled while the product matures. Every customer comes in through a founder-led audit, by invitation.
A conversation. No platform access, card, or contract is required to run one — the audit exists to prove, on your data, whether the routes are better enough to act on.
Tenant isolation is enforced at the database level, and there is no lock-in by design: CSV in, CSV out. Route data is exchanged directly during the engagement, never through this website.
Intake on your real stop export, pin verification, constraint capture, a solve on road-network distances, and a before/after against your current assignments — ending in a route packet you keep.
Route data is messy, workflows vary by operator, and early deployments live or die on operational details. A controlled evaluation keeps the product focused on the right early users instead of broad self-serve signups.
Yes. Drivers open secure route links at drive.coeroute.com on any phone — no install. A native shell for persistent background capture is in progress.
CSV import/export covers the pilot path today. Enterprise conversations can include custom import/export or integration work once the route value is proven.
Next step
A short note about your operation — fleet size, region, weekly stop count, how routes are planned today — is enough.