# Headless Yard Routing

*/Opportunities/Headless_Yard_Routing*

## Opportunity Overview

**Wedge**: Begin with drop-hook trailer spotting at heavy manufacturing facilities, where yard layouts are fixed and internal jockey routes remain highly predictable. This proves the automated dispatch capability on private property without complex over-the-road carrier variables. Expansion moves outward to multi-tenant cross-docking yards, integrating inbound gate arrivals with outbound loading schedules to coordinate live unloads.
**Timing**: Computer vision at the gate and IoT telematics on yard trucks provide the necessary live state data continuously. Concurrently, multimodal AI models with low-latency audio capabilities allow systems to communicate directly with drivers over existing radio channels without requiring custom tablet installations.
**Why This I C P**: Third-party logistics providers and enterprise retailers operate high-throughput yards where dock delays cascade into missed outbound schedules. Strict margin pressures force them to automate middle-management orchestration rather than hiring additional human dispatchers.
**Size Of Prize**: Approximately 15,000 high-volume distribution centers and manufacturing yards in North America spend around $80,000 per year on dedicated yard dispatch labor or software. This yields a total addressable market of roughly $1.2B annually.
**Gap Narrative**: Yard jockeys and gate guards rely on radio chatter and static yard management systems that require manual data entry to move trailers between gates and docks. This manual orchestration causes dock starvation and gate bottlenecks. Headless yard routing ingests live telemetry from camera feeds, telematics, and warehouse schedules to issue direct audio or digital dispatch commands to yard trucks, eliminating the human dispatcher bottleneck.
**Defensibility**: The product establishes deep workflow lock-in by completely replacing the physical dispatch desk and radio protocols of the yard. The system accrues proprietary datasets of facility-specific turn times, localized congestion patterns, and individual driver speeds, which compound into superior routing execution. Displacing the agent requires a facility to re-hire manual dispatchers and rip out established operating procedures.
**Why This Thesis**: Agentic orchestration fits the yard dispatch problem because the activity is entirely rule-bound, high-frequency, and requires constant state-tracking. By executing the routing logic headlessly, the system bypasses the need to train drivers on complex user interfaces and acts directly as the facility's dispatch authority.

## Opportunity Linked Thesis

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

## Opportunity Linked I C P

**Icp**: [Distribution Center](/CompanyTypes/Distribution_Center)

## Opportunity Market Sizing

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

**S A M**: ~$500M-$800M for high-volume North American and European retail and 3PL distribution centers with modern API-driven tech stacks
**S O M**: ~$15M-$30M
**T A M**: ~40,000-50,000 enterprise distribution centers globally × ~$40,000-60,000/yr per facility software allocation ≈ ~$1.6B-$3.0B
**Growth Rate**: ~12-18%/yr, driven by increasing trailer turn velocity requirements and the adoption of automated gate sensors
**Paid Comparable Spend**: ~$80,000-$150,000/yr per facility spent on legacy monolithic Yard Management Systems, physical spotter coordinators, and two-way radio dispatch labor

## Opportunity Incumbents

- [Manhattan Active Yard](/Products/Manhattan_Active_Yard) — Tool
- [SAP Yard Logistics](/Products/SAP_Yard_Logistics) — Tool
- [FourKites YMS](/Products/FourKites_YMS) — Tool
- [Excel Yard Trackers](/Products/Excel_Yard_Trackers) — Spreadsheet
- [Custom In-House Routing](/Products/Custom_In-House_Routing) — DIY
- [Outsourced Gate Management](/Products/Outsourced_Gate_Management) — Service

## Opportunity Win Conditions

**Kill Thresholds**:
- Time-to-first-value exceeds 45 days during pilot phase
- Manual override rate of API-generated moves remains above 20 percent after 30 days
- Less than 40 percent of pilot facilities convert to paid annual contracts
- Pilot CAC exceeds $25k per facility
**Leading Metrics**:
- Days to first production API call
- Percentage of spotter tasks completed without manual dispatch override
- API response latency under peak load
- Trailer dwell time reduction in minutes
- Number of concurrent spotter connections per yard
**What Proves Right**: Facilities integrate the headless routing API within 14 days and route 90 percent of yard movements without human intervention. Spotters complete tasks directly from the API output without two-way radio dispatch. Cohorts that deploy the system in one distribution center expand to three or more facilities within the first contract year.
**What Proves Wrong**: Implementation stalls because target distribution centers lack the necessary WMS endpoints to feed the headless engine. Spotters repeatedly override API-directed moves due to physical yard constraints missing from the data model. Dispatchers abandon the software and revert to Excel and radios during peak volume surges due to system latency.

## Opportunity Build Profile

**Hardest Part**: Maintaining a precise, real-time state of physical trailer locations and dock availability relying solely on delayed or incomplete API payloads from legacy Warehouse Management Systems.
**Min Viable Scope**: An API-only routing engine that ingests trailer states to sequence optimal shunter moves for a single, uniform yard. Deliberately exclude gate computer vision, driver mobile applications, and multi-site inventory balancing.
**Cold Start Problem**: The routing engine requires realistic, constrained yard operations data to tune turn-times and sequence logic. Break this by running a shadow mode on 30 days of historical logs from a single logistics partner to prove offline efficiency gains.
**Time To First Value**: 2-4 weeks of integration to map yard topology and validate real-time state synchronization.
**Data Moat Available**: false
**Technical Difficulty**: High

## Neighborhood

### Where the gap lives

- [Support Activities for Transportation](/Industries/Support_Activities_for_Transportation) — latent gap · Industries

### Incumbent in

- [SAP Yard Logistics](/Products/SAP_Yard_Logistics) — incumbent in · Products
- [Manhattan Active Yard](/Products/Manhattan_Active_Yard) — incumbent in · Products
- [Outsourced Gate Management](/Products/Outsourced_Gate_Management) — incumbent in · Products
- [Custom In-House Routing](/Products/Custom_In-House_Routing) — incumbent in · Products
- [Excel Yard Trackers](/Products/Excel_Yard_Trackers) — incumbent in · Products
- [FourKites YMS](/Products/FourKites_YMS) — incumbent in · Products

### Applies thesis

- [Distribution Center](/CompanyTypes/Distribution_Center) — applies thesis · CompanyTypes

### Embodies

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

### Similar Opportunities

- [AI Freight Yard Dispatch](/Opportunities/AI_Freight_Yard_Dispatch) — similar · Opportunities
- [Yard Dispatch Automation](/Opportunities/Yard_Dispatch_Automation) — similar · Opportunities
- [Staging Routing Engine](/Opportunities/Staging_Routing_Engine) — similar · Opportunities
- [Autonomous SCADA Gate Routing](/Opportunities/Autonomous_SCADA_Gate_Routing) — similar · Opportunities
- [Autonomous Fleet Dispatcher](/Occupations/Transportation_and_Material_Moving_Occupations/Opportunities/Autonomous_Fleet_Dispatcher) — similar · Opportunities
- [Autonomous Yard Shunting](/Opportunities/Autonomous_Yard_Shunting) — similar · Opportunities
- [Autonomous Dispatch Agent](/Industries/Transportation_and_Warehousing/Opportunities/Autonomous_Dispatch_Agent) — similar · Opportunities
- [Algorithmic Freight Routing](/Opportunities/Algorithmic_Freight_Routing) — similar · Opportunities
- [Yard Dispatch Automation](/CompanyTypes/Trade_Show_&_Exhibit_Furnishings_Provider/Opportunities/Yard_Dispatch_Automation) — similar · Opportunities
- [Tactical Fleet Orchestrator](/Opportunities/Tactical_Fleet_Orchestrator) — similar · Opportunities
- [Driver Dispatch Concierge](/Opportunities/Driver_Dispatch_Concierge) — similar · Opportunities
- [AI Intermodal Dispatch for Freight Forwarders](/Opportunities/AI_Intermodal_Dispatch_for_Freight_Forwarders) — similar · Opportunities
- [Fleet Dispatch API](/Opportunities/Fleet_Dispatch_API) — similar · Opportunities
- [Autonomous Matching Engine](/Opportunities/Autonomous_Matching_Engine) — similar · Opportunities
- [Predictive Yard Scheduling](/Opportunities/Predictive_Yard_Scheduling) — similar · Opportunities
- [AI Fleet Dispatch](/Opportunities/AI_Fleet_Dispatch) — similar · Opportunities
- [Dynamic Train Dispatching](/CompanyTypes/Belt_Line_Railroads/Opportunities/Dynamic_Train_Dispatching) — similar · Opportunities
- [AI Equipment Dispatcher](/Opportunities/AI_Equipment_Dispatcher) — similar · Opportunities
- [Fleet Utilization Engine](/Opportunities/Fleet_Utilization_Engine) — similar · Opportunities