# Depotquay

*/Startups/Depotquay*

## Startup Overview

This system processes unstructured gate emails to track container state transitions. Inland terminals and container depots receive thousands of dispatch messages daily coordinating gate-in and gate-out events. Instead of deploying staff for manual yard checks to verify physical inventory, the software reads inbound communications, extracts container IDs, and logs the exact operational state of each unit.

Legacy terminal operating systems like Navis N4 and Tideworks demand heavy IT integration and rigid data feeds to track equipment. This architecture bypasses complex software deployments entirely through a zero-integration model. It connects directly to existing dispatch inboxes and operates on a consumption basis, priced strictly per successful container handoff to align expenses with actual terminal throughput.

## Startup Founding Hypothesis

**Approach**: that extracts container state transitions from unstructured gate emails
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Tideworks](/Competitors/Tideworks)
- [manual yard checks](/Competitors/manual_yard_checks)
**Differentiator2x2**: zero-integration and priced per successful container handoff

## Startup Solution Coordinate

**Solution**: [Container Handoff Service](/Services/Container_Handoff_Service)

## Startup Position2x2

```mermaid
quadrantChart
title Market Positioning: Depotquay
x-axis Heavy IT Integration --> Zero Integration
y-axis Fixed/License Pricing --> Priced per Handoff
quadrant-1 Usage-Based Automation
quadrant-2 Niche
quadrant-3 Heavy Enterprise TOS
quadrant-4 Manual Operations
Navis N4: [0.15, 0.20]
Tideworks: [0.25, 0.25]
Manual Yard Checks: [0.90, 0.15]
Depotquay: [0.85, 0.85]
```

## Startup Offer

**Proof**:
- Targeting regional intermodal yards to process 10,000 gate emails weekly with zero manual data entry.
- Aiming for independent depots to eliminate manual terminal operating system (TOS) update delays.
- Designed to allow terminal operators to automate data ingestion from smaller trucking fleets without requiring EDI compliance.
**Tiers**:
- Name: Starter Volume · Price: ~$0.30–$0.50 per successful handoff · Inclusions: Extraction of up to 5,000 container state transitions (in-gate, out-gate, release) per month from unstructured emails.
- Name: Terminal Volume · Price: ~$0.15–$0.25 per successful handoff · Inclusions: Volume between 5,001 and 50,000 container handoffs per month, including support for multi-carrier non-standard email templates.
- Name: Enterprise Network · Price: ~$0.08–$0.12 per successful handoff · Inclusions: Over 50,000 container handoffs per month, including dedicated webhook endpoints designed for direct Terminal Operating System (TOS) routing.
**Guarantee**: Depotquay guarantees 99.5% accuracy on container state extraction from supported carrier emails; if accuracy falls below this threshold in a billing period, the extraction fees for that period are credited back to the account.
**Business Function**: ProvideService
**Objection Handlers**:
- Trucking companies send unstructured text emails instead of structured forms. -> Depotquay uses LLM-based parsing specifically built to extract container IDs, seal numbers, and transition states from plain text.
- Our TOS (like Navis N4) requires rigid data formats. -> The service is designed to map extracted unstructured data into clean, compliant JSON payloads formatted for standard TOS ingestion layers.
- Small carriers often omit crucial details like seal numbers in their emails. -> Incomplete emails are automatically flagged in an exception queue for quick human review rather than silently dropping the record.
- EDI integration is the industry standard, why rely on email parsing? -> Many small carriers cannot afford EDI; Depotquay allows you to automate their handoffs based on the emails they already send.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Direct and industrial, prioritizing operational accuracy over tech jargon.
**Tagline**: Instant container visibility extracted directly from gate emails.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: High-visibility safety yellow and concrete grey dominate the palette, paired with heavy block typography that echoes shipping container markings.
**Archetype Reference**: the-everyman

## Startup Buyer Chain

**Chain**: Depotquay → Independent Container Depot Operator → Drayage Dispatcher
**Gtm Motion**: Acquires independent container depots through direct outbound offering a zero-integration pilot where yard managers simply auto-forward their gate email aliases. Expansion occurs by moving from processing a single shipping line's handoffs to processing the entire yard's volume, multiplying the per-container transaction fees.
**Agent Channel**: Intends to list as a verified container status tool in supply chain orchestration registries and LLM capability feeds, allowing autonomous freight-forwarding agents to query real-time gate transitions without parsing unstructured text.
**Primary Channel**: Direct outbound email and cold calling targeting operations managers sourced from the Intermodal Association of North America (IANA) directory and regional port authority tenant lists.

## Startup Customer Journey

```mermaid
flowchart LR; A[IANA Directory Campaign] --> B[Zero-Integration Pilot]; B --> C[Gate Email Alias]; C --> D[LLM Extraction Engine]; D --> E[Exception Queue Dashboard]; E --> F[Multi-Carrier Rollout]; F --> G[Agentic Orchestration Registry];
```

## Startup Proof Points

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

**Pilot Goals**:
- 30-day parallel processing pilot with a regional yard to prove the extraction engine matches human accuracy on 5,000 historical gate-in emails.
- 14-day live integration pilot routing email-derived JSON payloads to a staging TOS environment to validate webhook compatibility and formatting.
**Target Metrics**:
- Target: 99.5 percent accuracy rate on container state and seal number extraction from unstructured plain text.
- Aim: Zero manual data entry hours required for processing standard non-EDI carrier handoff emails.
- Target: Under 5 seconds of latency between receipt of carrier email and TOS webhook payload delivery.
**Target Case Studies**:
- A regional intermodal yard that replaces the manual transcription of 10,000 weekly carrier emails into automated Terminal Operating System webhook routing.
- An independent container depot that expands its trucking network by accepting freight from non-EDI compliant fleets without increasing back-office headcount.
- A mid-sized terminal operator that reduces gate-in and gate-out recording delays from hours to seconds by automating email-to-TOS ingestion.
**Testimonial Targets**:
- Terminal Operations Manager expresses relief that messy carrier emails translate directly into the terminal operating system without manual transcription.
- Intermodal Depot Owner praises the ability to onboard smaller trucking fleets without forcing them to adopt expensive EDI integrations.
- Back-Office Data Clerk appreciates transitioning from copying and pasting container IDs all day to simply managing a small exception queue.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: The email parsing model hallucinates or drops container state transitions, leading to lost containers in the yard and immediate customer churn. · Mitigation Status: in-progress
- Severity: high · Description: Port authorities or shipping lines block terminal operators from auto-forwarding gate emails due to strict data privacy policies. · Mitigation Status: unmitigated
- Severity: moderate · Description: Entrenched competitors like Navis or Tideworks launch basic email-parsing features to their existing user base, neutralizing the zero-integration advantage. · Mitigation Status: unmitigated
- Severity: moderate · Description: The per-handoff pricing model causes severe revenue drops during macro shipping downturns or seasonal port volume lulls. · Mitigation Status: in-progress

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Incumbent TOS
- [Tideworks](/Competitors/Tideworks) — Incumbent TOS
- [Manual Yard Checks](/Competitors/Manual_Yard_Checks) — Status Quo
- [Octopi TOS](/Competitors/Octopi_TOS) — Cloud TOS
- [Data Entry Clerks](/Competitors/Data_Entry_Clerks) — Status Quo

## Startup Solution Stack

- [Container Handoff Service](/Services/Container_Handoff_Service) — Service-as-Software
- [Gate Email Agent](/Agents/Gate_Email_Agent) — Agent
- [State Transition Worker](/Agents/State_Transition_Worker) — Agent
- [Handoff Verification API](/Software/Handoff_Verification_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the high-velocity hub of the supply chain, not a data-entry bottleneck
- **Want**: to update container status without manual entry from carrier emails
- **Identity**: the terminal manager at a regional intermodal yard
**Plan**:
- Step: Upload emails · Detail: Forward your unstructured gate and release emails from small carriers to your secure Depotquay endpoint.
- Step: Approve extractions · Detail: Verify the container IDs and seal numbers extracted from plain text before they hit your yard records.
- Step: Sync terminal · Detail: Route the validated data directly into your TOS to reflect real-time gate transitions across the yard.
**Guide**:
- **Empathy**: You shouldn't still be re-typing gate logs into a terminal operating system. Navis N4 wasn't built to parse the messy, unstructured text emails that small carriers send every day.
**Problem**:
- **Villain**: unstructured gate emails
- **External**: Updating Navis N4 requires staff to manually copy container IDs and seal numbers from thousands of plain-text emails sent by small trucking fleets.
- **Internal**: You feel like your yard's throughput is limited by how fast your team can type, not how fast your cranes move.
- **Philosophical**: Every terminal manager deserves a yard that moves at the speed of steel — not the speed of an inbox.
**Success**: Your yard stays fluid with every gate transition reflected in your TOS the moment the email arrives, regardless of carrier EDI capability.
**One Liner**: Every shift, terminal managers struggle with manual data entry from carrier gate emails. Depotquay extracts container states from unstructured text so your yard updates in real-time.
**Positioning**:
- **So That**: automate handoffs from small carriers without requiring EDI compliance
- **Unlike**: Manual TOS data entry
- **For Whom**: Regional intermodal terminal managers
- **Category**: Automated container data extraction
**Call To Action**:
- **Direct**: Automate first handoff
- **Transitional**: View sample JSON payload
**Failure Stakes**:
- Yard congestion from data delays
- Incorrect container seal records
- Missed demurrage billing cycles
**Transformation**:
- **To**: free to optimize yard flow and crane cycles, no longer stuck re-keying carrier emails
- **From**: a gate clerk buried in a Tideworks data-entry backlog
**Controlling Idea**: Container visibility should come from the emails you already receive, not manual entry.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every shift, terminal managers struggle with manual data entry from carrier gate emails. Depotquay extracts container states from unstructured text so your yard updates in real-time.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: d25fd595b1dc58d5

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Automated container data extraction for Regional intermodal terminal managers. Unlike Manual TOS data entry — automate handoffs from small carriers without requiring EDI compliance.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 3c4bbd95627141a2

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Updating Navis N4 requires staff to manually copy container IDs and seal numbers from thousands of plain-text emails sent by small trucking fleets.
Solution: Every shift, terminal managers struggle with manual data entry from carrier gate emails. Depotquay extracts container states from unstructured text so your yard updates in real-time.
Customer: Regional intermodal terminal managers
Unlike: Manual TOS data entry
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: c8f177a6cd89f2da

## Startup Token M E D D P I C C

**Pain**: Updating Navis N4 requires staff to manually copy container IDs and seal numbers from thousands of plain-text emails sent by small trucking fleets.
**Metrics**: Target: Your yard stays fluid with every gate transition reflected in your TOS the moment the email arrives, regardless of carrier EDI capability.
**Rendered**: Pain: Updating Navis N4 requires staff to manually copy container IDs and seal numbers from thousands of plain-text emails sent by small trucking fleets.
Economic buyer: Independent Container Depot Operator
Metrics: Target: Your yard stays fluid with every gate transition reflected in your TOS the moment the email arrives, regardless of carrier EDI capability.
Competition: Manual TOS data entry
**Mechanism**: spine-derived-v1
**Competition**: Manual TOS data entry
**Economic Buyer**: Independent Container Depot Operator
**Vocab Fingerprint**: 5abfa9b561c87dea

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Automated container data extraction for Regional intermodal terminal managers

Regional intermodal terminal managers — Updating Navis N4 requires staff to manually copy container IDs and seal numbers from thousands of plain-text emails sent by small trucking fleets. Every shift, terminal managers struggle with manual data entry from carrier gate emails. Depotquay extracts container states from unstructured text so your yard updates in real-time.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: c5531b05106f7b7b

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Automated container data extraction. Every shift, terminal managers struggle with manual data entry from carrier gate emails. Depotquay extracts container states from unstructured text so your yard updates in real-time. Serves Regional intermodal terminal managers.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 64350da465666b24

## Neighborhood

### Candidate solutions

- [Cross-Dock Throughput Bottlenecks](/Problems/Cross-Dock_Throughput_Bottlenecks) — candidate solution for · Problems

### Competitors

- [Manual Yard Checks](/Competitors/Manual_Yard_Checks) — competes with · Competitors
- [Octopi TOS](/Competitors/Octopi_TOS) — competes with · Competitors
- [Data Entry Clerks](/Competitors/Data_Entry_Clerks) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors
- [Tideworks](/Competitors/Tideworks) — competes with · Competitors

### Composed of

- [Handoff Verification API](/Software/Handoff_Verification_API) — composes · Software
- [Container Handoff Service](/Services/Container_Handoff_Service) — composes · Services
- [Gate Email Agent](/Agents/Gate_Email_Agent) — composes · Agents
- [State Transition Worker](/Agents/State_Transition_Worker) — composes · Agents

### Embodies

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

### Similar Startups

- [Depotport](/Startups/Depotport) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Cargofield](/Startups/Cargofield) — similar · Startups
- [Wholesalequay](/Startups/Wholesalequay) — similar · Startups
- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Valleyrail](/Startups/Valleyrail) — similar · Startups
- [Digitalyard](/Startups/Digitalyard) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Directoryard](/Startups/Directoryard) — similar · Startups
- [Coordinatyard](/Startups/Coordinatyard) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Bloomdock](/Startups/Bloomdock) — similar · Startups
- [Yardlane](/Startups/Yardlane) — similar · Startups
- [Autonomywharf](/Startups/Autonomywharf) — similar · Startups
- [Bookdock](/Startups/Bookdock) — similar · Startups
- [Clearquay](/Startups/Clearquay) — similar · Startups