Better routes, proven on your own data.
Route optimization and execution for delivery, distribution, and service fleets.
See it on a week you already ran, before you commit.
Daily routing · Network realignment · Scenario analysis · Feedback loop · Order scheduling · Fleet sizing
The Missing Checkbox
Earlier this year, at an industry event, vendors surveyed the room on what matters when choosing a routing technology partner. Features. Integrations. Support. Security.
Route quality wasn't on the list.
Ask every routing vendor to prove route quality on your own data. Including us.
We don't ask you to trust a demo. We prove it on your data.
Send us one to two weeks of route history from a single market: orders, vehicles, drivers, and the routes you actually ran.
We re-plan those same days offline, with the same rules and your real costs. Then you see your plans next to ours.
You send history
One to two weeks, one market. No integration required.
We learn your business rules
Your constraints, documented and confirmed with your team before anything is measured.
We re-plan the same days
Same orders, same fleet, same constraints, your real costs — run on the same system we run live operations on. Fully offline, no access to your live systems.
You compare
Every route inspectable on the map.
What gets compared
- Total miles
- Total drive time
- Routes and vehicles required
- Route duration and workload balance
- Time-window and rule compliance
- Feasibility violations — reported on both sides
Any plan can win on miles, drive time or vehicle count by breaking a rule. Run a vehicle over capacity, miss a delivery window, and the totals improve.
So feasibility is measured on both sides. Your routes and ours are checked against the same constraints, and violations are reported for each. If we win by breaking a rule, we haven't won. The rules we model are confirmed with your team before the comparison is finalized.
Both plans are then scored the same way: one distance and time matrix, one set of service times, one set of costs, applied to your routes and ours alike. Measure each side with different travel and service times and you don't have a comparison.
If the numbers aren't meaningful, that's a fast, free answer.
Real constraints, no simplification.
BOSOPT solves routing, scheduling, and driver and vehicle assignment together, in one optimization run — against the constraints your operation actually has, instead of the simplified version most tools can model.
Some of the constraints we handle
- High stop counts
- Tight and multiple time windows
- Vehicle capacities and vehicle-type restrictions
- Zones and subzones
- Liftgates, equipment, and skill matching
- Order-ready times and wave-based production
- Driver work-time rules
- Multi-terminal operations
If you've been told "our routing handles that" but your dispatchers still fix routes every morning — the tool is simplifying your problem. We don't.
A simplified version of the problem looks optimized on screen and falls apart on the road.
Already have an execution platform? Keep it.
Plenty of operations already run a delivery platform they're committed to, or execute on a platform their customer chose for them. That doesn't have to be the end of the conversation.
BOSOPT is built API-first. Your system sends orders in, gets optimized routes back. No workflow replacement, no rip-and-replace, no retraining your dispatchers and/or drivers on a new tool.
The API is REST. We don't ship pre-built connectors for specific TMS platforms — the data flow gets connected by your team or ours, and for anyone who works with REST APIs it's straightforward.
Two ways to run it
The full platform
Optimization, Driver App and Control Tower together — plan, assign, execute and monitor in one system.
The optimization layer only
BOSOPT sits underneath what you already have. Better routes flow into your existing execution stack.
Your operation teaches the plan.
After the day runs, a specialized AI agent compares what was planned with what actually happened — which stops were resequenced, where driver decisions departed from the plan, where the timing differed. Those differences come back as calibration input.
There is an engineer in that loop on purpose. We review what changed and why, and adjust deliberately — because not every deviation should teach the system. The result is a configuration that gets closer to your operation's reality over time, instead of one that was set once and left to age.
Most routing tools never listen.
The feedback loop
One cycle, running every day you operate.
Check the box nobody asks about.
Send us a week of routes you already ran. We'll re-plan those same days under your constraints and show you your routes next to ours.
Free, offline, and no integration.