# Freight Co-Routing Engine

*/Opportunities/Freight_Co-Routing_Engine*

## Opportunity Overview

**Wedge**: The beachhead is specialized flatbed and oversized partial freight, where dimensional constraints make human co-routing exceptionally difficult and error-prone. By solving multi-stop routing for flatbed partials first, the engine proves immediate high-margin value to specialized brokers. From there, the system expands into standard dry van partials and eventually fully autonomous full-truckload matching across all equipment types.
**Timing**: Recent advancements in fast inference and LLM-based parsing allow systems to ingest messy, unstructured load data from email feeds and fragmented load boards in milliseconds. Previously, calculating multi-stop co-load permutations required fragile, hard-coded data pipelines that broke whenever a carrier updated their formatting.
**Why This I C P**: Mid-market freight brokerages operate on razor-thin margins and lack the engineering budgets of tier-one logistics giants to build proprietary routing engines. They feel the pain of underutilized partial capacity most acutely, making them eager adopters of tools that immediately increase the margin-per-load without requiring new carrier acquisition.
**Size Of Prize**: There are roughly 17,000 registered freight brokerages in the US, with about 4,000 mid-market players spending an average of $50,000 annually on dispatcher headcount and load board fees dedicated to routing partials. Multiplying these 4,000 mid-market brokerages by $50,000 yields a $200M immediate addressable prize, expanding to an $850M market if adopted by the entire brokerage ecosystem.
**Gap Narrative**: Freight brokers rely on static routing tables and manual load board matching, leaving partial loads underutilized. Existing transportation management systems lack the real-time spatial awareness to stitch disparate partial loads into continuous, profitable multi-stop routes. This engine continuously calculates permutations of partial loads, identifying profitable co-routing opportunities that human dispatchers miss due to cognitive load limits.
**Defensibility**: The system compounds value through proprietary lane pricing data and carrier preference profiles built over time. As the engine executes more routes, it maps which specific carriers reliably accept complex co-load configurations and records their true clearing prices. A new entrant cannot easily replicate this historical carrier behavior data, locking brokers into the engine that yields the highest automated acceptance rates.
**Why This Thesis**: An Agent-driven Service-as-Software thesis fits perfectly because routing is a discrete, logic-heavy task currently performed by human dispatchers cross-referencing multiple browser tabs. An autonomous agent directly replaces the labor cost of monitoring load boards, ingesting load requirements and executing the matching logic to deliver a completed, bookable route.

## Opportunity Linked Thesis

**Thesis**: [Software](/Theses/Software)

## Opportunity Linked I C P

**Icp**: [Freight Carrier](/CompanyTypes/Freight_Carrier)

## Opportunity Market Sizing

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**S A M**: ~$800M-1.2B North American mid-market and enterprise freight carriers
**S O M**: ~$30M-60M
**T A M**: ~150k mid-to-large global freight fleets × ~$20k-30k/yr routing and optimization spend ≈ $3B-4.5B
**Growth Rate**: ~10-14%/yr, driven by volatile fuel costs, driver shortages, and margin pressure to eliminate non-revenue empty miles
**Paid Comparable Spend**: ~$15k-40k/yr per fleet on legacy TMS routing modules, standalone mileage engines, and manual dispatcher labor for load consolidation

## Opportunity Incumbents

- [Descartes Route Planner](/Products/Descartes_Route_Planner) — Tool
- [Oracle Transportation Management](/Products/Oracle_Transportation_Management) — Tool
- [Coyote Logistics](/Products/Coyote_Logistics) — Service
- [Manual Dispatch Spreadsheets](/Products/Manual_Dispatch_Spreadsheets) — Spreadsheet
- [McLeod Software](/Products/McLeod_Software) — Tool
- [Uber Freight](/Products/Uber_Freight) — Service
- [Trimble Transportation](/Products/Trimble_Transportation) — Tool

## Opportunity Win Conditions

**Kill Thresholds**:
- Dispatcher override rate exceeds 60 percent after 14 days of active use
- Demonstrated empty mile reduction falls below 5 percent compared to historical baseline
- TMS API integration demands more than 40 hours of custom engineering per fleet deployment
- Pilot-to-paid conversion rate rests below 40 percent at the 90-day mark
**Leading Metrics**:
- Engine-suggested route acceptance rate
- Average reduction in empty miles per co-routed load
- Time spent per dispatcher per shift on load matching
- Days to complete legacy TMS data integration
- Ratio of multi-stop routes to single-stop routes generated
**What Proves Right**: Dispatchers accept and execute at least 40 percent of multi-stop load suggestions without manual overrides within the first 30 days of deployment. Participating fleets record a 10 to 15 percent drop in non-revenue empty miles across co-routed vehicles. Customers sign $25k annual contracts after a 60-day pilot because documented fuel and labor savings strictly outpace the software licensing cost.
**What Proves Wrong**: Dispatchers override more than half of the suggested co-routes because the engine misses strict facility appointment windows or driver hours-of-service constraints. Integration cycles with legacy TMS platforms like McLeod or Trimble stretch beyond 90 days and consume outsized engineering resources. Fleets churn after initial pilots because the routing logic fails to adjust for live weather or traffic delays.

## Opportunity Build Profile

**Hardest Part**: Calculating dynamically viable multi-stop routes across independent shippers that satisfy strict appointment windows, physical trailer dimension constraints, and driver Hours of Service rules without triggering manual dispatch overrides.
**Min Viable Scope**: Focus exclusively on outbound dry-van LTL freight leaving a single major geographic hub. Deliberately exclude refrigerated freight, hazardous materials, inbound backhauls, and dynamic carrier procurement from v1.
**Cold Start Problem**: The engine requires high lane density across multiple shippers on day one to find viable co-routing matches. Break this by onboarding a single anchor 3PL or broker with existing captive volume in a specific geographic corridor to seed the network.
**Time To First Value**: 2-4 weeks of shadow simulation on historical load data to prove cost savings before a dispatcher trusts the engine with live freight
**Data Moat Available**: true
**Technical Difficulty**: High

## Neighborhood

### Where the gap lives

- [Network Planning Engineers](/Occupations/Network_Planning_Engineers) — latent gap · Occupations

### Incumbent in

- [Descartes RoutePlanner](/Products/Descartes_RoutePlanner) — incumbent in · Products
- [Coyote Logistics](/Products/Coyote_Logistics) — incumbent in · Products
- [Uber Freight](/Products/Uber_Freight) — incumbent in · Products
- [Oracle Transportation Management](/Products/Oracle_Transportation_Management) — incumbent in · Products
- [Trimble Transportation](/Products/Trimble_Transportation) — incumbent in · Products
- [Manual Dispatch Spreadsheets](/Products/Manual_Dispatch_Spreadsheets) — incumbent in · Products
- [McLeod Software](/Products/McLeod_Software) — incumbent in · Products

### Applies thesis

- [Freight Carrier](/CompanyTypes/Freight_Carrier) — applies thesis · CompanyTypes

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Similar Opportunities

- [Algorithmic Freight Routing](/Opportunities/Algorithmic_Freight_Routing) — similar · Opportunities
- [Modal Routing Agent](/Opportunities/Modal_Routing_Agent) — similar · Opportunities
- [Autonomous LTL Freight Routing](/Opportunities/Autonomous_LTL_Freight_Routing) — similar · Opportunities
- [Autonomous Matching Engine](/Opportunities/Autonomous_Matching_Engine) — similar · Opportunities
- [Vector Freight Engine](/Opportunities/Vector_Freight_Engine) — similar · Opportunities
- [Parade Bid Automation](/Opportunities/Parade_Bid_Automation) — similar · Opportunities
- [Autonomous Routing Pipeline](/Opportunities/Autonomous_Routing_Pipeline) — similar · Opportunities
- [Autonomous Dispatch Agent](/Industries/Transportation_and_Warehousing/Opportunities/Autonomous_Dispatch_Agent) — similar · Opportunities
- [Leverage Route](/Opportunities/Leverage_Route) — similar · Opportunities
- [Load Ratio Automation](/Opportunities/Load_Ratio_Automation) — similar · Opportunities
- [Freight Exception Management](/Opportunities/Freight_Exception_Management) — similar · Opportunities
- [Fleet Utilization Engine](/Opportunities/Fleet_Utilization_Engine) — similar · Opportunities
- [Spot Freight Pricing Agent](/Opportunities/Spot_Freight_Pricing_Agent) — similar · Opportunities
- [Modal Routing Agent](/Knowledge/Transportation/Opportunities/Modal_Routing_Agent) — similar · Opportunities
- [Freight Procurement Agent](/Opportunities/Freight_Procurement_Agent) — similar · Opportunities
- [LoadMatch Copilot](/Opportunities/LoadMatch_Copilot) — similar · Opportunities
- [Route Preference Matching for Logistics Fleets](/Opportunities/Route_Preference_Matching_for_Logistics_Fleets) — similar · Opportunities
- [Capacity Yield Optimizer](/Opportunities/Capacity_Yield_Optimizer) — similar · Opportunities
- [Autonomous Fleet Dispatcher](/Occupations/Transportation_and_Material_Moving_Occupations/Opportunities/Autonomous_Fleet_Dispatcher) — similar · Opportunities
- [Dynamic Routing for Pallet Networks](/Opportunities/Dynamic_Routing_for_Pallet_Networks) — similar · Opportunities