# Fleet Allocation Engine

*/Opportunities/Fleet_Allocation_Engine*

## Opportunity Overview

**Wedge**: The beachhead is automated backhaul matching for refrigerated carriers operating in regional loops. Refrigerated carriers face strict time constraints and high operating costs per mile, making empty miles exceptionally costly and proving ROI instantly. The system expands to dry van freight and then into predictive maintenance scheduling based on route proximity to preferred repair shops.
**Timing**: Widespread adoption of ELD mandates provides standardized, real-time telemetry on truck location and driver hours. Concurrent advances in constrained optimization logic combined with LLMs allow systems to parse unstructured broker emails and instantly run allocation algorithms without manual data entry.
**Why This I C P**: Mid-sized carriers operating 50 to 250 trucks feel the acute pain of deadhead margins but lack the IT budgets of mega-carriers to build proprietary routing software. They operate on tight margins where a minor reduction in empty miles determines operational survival.
**Size Of Prize**: There are roughly 40,000 mid-sized trucking carriers in the US spending an average of $50,000 annually on dispatchers and load-planning overhead. Multiplying 40,000 entities by $50,000 per year yields a $2B addressable market for automated fleet allocation.
**Gap Narrative**: Mid-sized fleet dispatchers manually match trucks to available loads using fragmented load boards, static spreadsheets, and tribal knowledge of driver preferences. They leave revenue on the table through excessive deadhead miles and idle time because human operators cannot compute the optimal combinations across thousands of permutations in real-time. A systemic allocation engine actively pairs assets with profitable freight while factoring in hours-of-service and maintenance schedules.
**Defensibility**: The system builds workflow lock-in as it becomes the sole interface drivers use to receive loads and report status. It compounds proprietary data by learning specific facility wait times and driver route preferences, creating a localized routing advantage that generic map APIs cannot replicate. Switching costs scale directly with usage, as abandoning the software requires hiring human dispatchers to replace the automated volume.
**Why This Thesis**: A Service-as-Software approach acts as a digital dispatcher, bridging the gap between raw telemetry and action. By delivering pre-computed, compliant dispatch instructions directly to the driver, the system replaces the human-in-the-loop coordination rather than providing another analytical dashboard.

## Opportunity Linked Thesis

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

## Opportunity Linked I C P

**Icp**: [Logistics Provider](/CompanyTypes/Logistics_Provider)

## Opportunity Market Sizing

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

**S A M**: ~$1B-1.5B US mid-market 3PL and freight providers
**S O M**: ~$30M-80M
**T A M**: ~50k global mid-to-large logistics and freight firms x ~$60k-80k/yr allocation software and dispatch spend = ~$3B-4B
**Growth Rate**: ~12-18%/yr, driven by rising fuel costs and tightening delivery SLA requirements
**Paid Comparable Spend**: ~$40k-100k/yr per firm on legacy TMS routing modules and manual dispatcher labor

## Opportunity Incumbents

- [Samsara Fleet](/Products/Samsara_Fleet) — Tool
- [Verizon Connect](/Products/Verizon_Connect) — Tool
- [Omnitracs Fleet Routing](/Products/Omnitracs_Fleet_Routing) — Tool
- [Google OR-Tools](/Products/Google_OR-Tools) — Open-Source
- [VROOM Routing Engine](/Products/VROOM_Routing_Engine) — Open-Source
- [Custom Excel Sheets](/Products/Custom_Excel_Sheets) — Spreadsheet
- [Daily Dispatch Spreadsheets](/Products/Daily_Dispatch_Spreadsheets) — Spreadsheet

## Opportunity Win Conditions

**Kill Thresholds**:
- Average pilot integration time > 14 days
- Dispatcher override rate > 20 percent after 14 days
- Zero closed-won contracts > 40k dollars per year within 90 days
- Day-30 dispatcher seat retention < 80 percent
**Leading Metrics**:
- Time-to-first-automated-route
- Dispatcher manual override percentage
- Daily active usage per dispatcher seat
- Deadhead miles reduction percentage
- TMS integration setup hours
**What Proves Right**: Customers fully automate daily dispatch schedules for at least 60 percent of their routes within the first 14 days of deployment. Mid-market logistics providers sign annual contracts at a 50k dollar price point after a two-week pilot demonstrating reduced deadhead miles. Dispatchers log into the engine daily and manually override fewer than 10 percent of the algorithmic assignments.
**What Proves Wrong**: Pilots stall because legacy TMS integrations require custom engineering work that exceeds two weeks per client. Dispatchers abandon the system because the routing engine fails to account for undocumented driver preferences, leading to manual schedule reconstruction. The system achieves parity with Excel workflows but fails to deliver a measurable reduction in daily route planning time.

## Opportunity Build Profile

**Hardest Part**: Solving the combinatorial explosion of vehicle assignments under conflicting real-world constraints such as driver shift limits, varying vehicle maintenance states, and strict facility appointment windows.
**Min Viable Scope**: Build an overnight daily static allocation generator for a single uniform vehicle class moving on dedicated point-to-point lanes. Deliberately exclude dynamic intra-day rerouting, multi-stop routing, and mixed-fleet balancing from the initial release.
**Cold Start Problem**: The optimization engine lacks baseline facility dwell times and lane-specific transit speeds without active operational data. Overcome this by integrating directly with a launch partner's existing telematics API to ingest 90 days of historical breadcrumb data before generating the first live schedule.
**Time To First Value**: 2 to 3 weeks of onboarding, gated by the ingestion of historical telematics and manual mapping of the fleet's unique business constraints.
**Data Moat Available**: true
**Technical Difficulty**: High

## Neighborhood

### Where the gap lives

- [Co-op General Manager](/JobTypes/Co-op_General_Manager) — latent gap · JobTypes
- [Management of Material Resources](/Skills/Management_of_Material_Resources) — latent gap · Skills

### Incumbent in

- [Verizon Connect](/Products/Verizon_Connect) — incumbent in · Products
- [Samsara Fleet](/Products/Samsara_Fleet) — incumbent in · Products
- [VROOM Routing Engine](/Products/VROOM_Routing_Engine) — incumbent in · Products
- [Custom Excel Sheets](/Products/Custom_Excel_Sheets) — incumbent in · Products
- [Daily Dispatch Spreadsheets](/Products/Daily_Dispatch_Spreadsheets) — incumbent in · Products
- [Google OR-Tools](/Products/Google_OR-Tools) — incumbent in · Products
- [Omnitracs Fleet Routing](/Products/Omnitracs_Fleet_Routing) — incumbent in · Products

### Applies thesis

- [Logistics Provider](/CompanyTypes/Logistics_Provider) — applies thesis · CompanyTypes

### Embodies

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

### Similar Opportunities

- [Backhaul Dispatch Service](/Opportunities/Backhaul_Dispatch_Service) — similar · Opportunities
- [Fleet Utilization Engine](/Opportunities/Fleet_Utilization_Engine) — similar · Opportunities
- [Dynamic Fuel Routing](/Opportunities/Dynamic_Fuel_Routing) — similar · Opportunities
- [Autonomous Dispatch Agent](/Industries/Transportation_and_Warehousing/Opportunities/Autonomous_Dispatch_Agent) — similar · Opportunities
- [Route Preference Matching for Logistics Fleets](/Opportunities/Route_Preference_Matching_for_Logistics_Fleets) — similar · Opportunities
- [Driver Dispatch Concierge](/Opportunities/Driver_Dispatch_Concierge) — similar · Opportunities
- [Capacity Yield Optimizer](/Opportunities/Capacity_Yield_Optimizer) — similar · Opportunities
- [Wholesale Route Intelligence](/Opportunities/Wholesale_Route_Intelligence) — similar · Opportunities
- [Algorithmic Freight Routing](/Opportunities/Algorithmic_Freight_Routing) — similar · Opportunities
- [Autonomous Fleet Dispatcher](/Occupations/Transportation_and_Material_Moving_Occupations/Opportunities/Autonomous_Fleet_Dispatcher) — similar · Opportunities
- [Freight Exception Management](/Opportunities/Freight_Exception_Management) — similar · Opportunities
- [Fleet Dispatch API](/Opportunities/Fleet_Dispatch_API) — similar · Opportunities
- [Dynamic Route Optimization](/Opportunities/Dynamic_Route_Optimization) — similar · Opportunities
- [Leverage Route](/Opportunities/Leverage_Route) — similar · Opportunities
- [AI Equipment Dispatcher](/Opportunities/AI_Equipment_Dispatcher) — similar · Opportunities
- [Dynamic Routing for Pallet Networks](/Opportunities/Dynamic_Routing_for_Pallet_Networks) — similar · Opportunities
- [Autonomous Matching Engine](/Opportunities/Autonomous_Matching_Engine) — similar · Opportunities
- [Autonomous Routing Pipeline](/Opportunities/Autonomous_Routing_Pipeline) — similar · Opportunities
- [Emergency Routing Agent](/Opportunities/Emergency_Routing_Agent) — similar · Opportunities
- [Fuel Deployment Dispatcher](/Opportunities/Fuel_Deployment_Dispatcher) — similar · Opportunities