# Cargowharf

*/Startups/Cargowharf*

## Startup Overview

This platform parses customs declarations to automate drayage dispatch. It extracts container availability, hold status, and release numbers instantly from clearing documents, connecting directly to terminal operating systems to schedule truck movements the moment cargo clears customs.

Importers and logistics providers frequently incur demurrage fees and container pileups due to delays between clearance and gate appointments. Instead of relying on manual data entry or fragmented email updates to monitor freight, dispatch teams use this system to trigger routing workflows automatically the second an entry summary is validated.

Unlike legacy software from Descartes Systems, traditional freight forwarders, or rigid in-house EDI portals, this routing infrastructure is fully programmable. Supply chain teams integrate custom dispatch logic directly into their own stacks and pay exclusively per successful terminal gate entry, tying infrastructure costs directly to completed freight movements.

## Startup Founding Hypothesis

**Approach**: that parses customs declarations to automate drayage dispatch
**Competitors**:
- [Descartes Systems](/Competitors/Descartes_Systems)
- [traditional freight forwarders](/Competitors/traditional_freight_forwarders)
- [in-house EDI portals](/Competitors/in-house_EDI_portals)
**Differentiator2x2**: fully programmable and charged only per successful terminal gate entry

## Startup Solution Coordinate

**Solution**: [Drayage Dispatch Engine](/Software/Drayage_Dispatch_Engine)

## Startup Position2x2

```mermaid
quadrantChart
    title Drayage Dispatch Automation
    x-axis "Rigid / Monolithic" --> "Fully Programmable"
    y-axis "Fixed / Subscription Costs" --> "Pay-per-Successful Gate Entry"
    quadrant-1 "Agile & Outcomes-Aligned"
    quadrant-2 "Rigid but Outcomes-Aligned"
    quadrant-3 "Legacy & Sunk Costs"
    quadrant-4 "Programmable but Fixed Costs"
    Cargowharf: [0.88, 0.85]
    Descartes Systems: [0.35, 0.40]
    Traditional Freight Forwarders: [0.15, 0.20]
    In-house EDI Portals: [0.45, 0.15]
```

## Startup Offer

**Proof**:
- Targeting a 99.5% first-time terminal gate acceptance rate for automated dispatches.
- Aiming to process and route standard customs clearances in under 60 seconds.
- Designed to eliminate manual document transcription for mid-sized freight forwarders.
**Tiers**:
- Name: Standard Dispatch · Price: ~$12–$20 per successful gate entry · Inclusions: Automated customs declaration parsing, drayage dispatch routing, and standard SMS/email carrier notifications with no monthly minimums.
- Name: High-Volume Integrator · Price: ~$6–$10 per successful gate entry · Inclusions: Custom EDI/API endpoints for Transport Management System (TMS) sync, dedicated webhook callbacks, and automated exception flagging for volumes exceeding 2,000 entries per month.
**Guarantee**: If a dispatched truck is denied terminal entry due to a parsing or routing error generated by our system, we waive the dispatch fee and reimburse the resulting dry run penalty.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Our TMS already has a dispatch module. Rebuttal: Cargowharf is designed to feed extracted customs data directly into your existing TMS via API, triggering the dispatch without replacing your core system.
- Objection: Terminal APIs are notoriously unreliable or non-existent. Rebuttal: The system is designed to fall back on automated EDI parsing and direct port portal scraping if a primary terminal API goes down.
- Objection: What if the parser extracts the wrong container or booking number? Rebuttal: Every data extraction is assigned a confidence score; parses falling below the threshold are instantly routed to your internal team for one-click manual validation.
- Objection: Drivers won't install a new app to receive dispatches. Rebuttal: No new app is required; gate passes and routing instructions are delivered directly to carriers via standard SMS and email.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative logistics register emphasizing operational certainty
**Tagline**: Turn customs declarations into automated pay-per-entry drayage dispatch
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: Utilitarian typography pairs with high-visibility safety orange and concrete gray, using stark photography of terminal gates to emphasize ground-truth logistics.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Cargowharf → Customs Broker / Freight Forwarder → Drayage Carrier
**Gtm Motion**: Acquires initial users through targeted outbound to logistics operations teams by offering immediate declaration parsing on pilot container volumes. Expands account value automatically through an outcome-based API model that scales as the customer routes more TEUs through the system, charging solely per successful terminal gate entry.
**Agent Channel**: Designed to list in developer tool registries like the LangChain integration catalog and OpenAI schema directory, formatted as a callable drayage dispatch and terminal status API for autonomous supply chain agents.
**Primary Channel**: Targeted outbound to customs compliance managers and intended integration directory listings on freight management systems like CargoWise, capturing demand when operations teams search for automated drayage dispatch connectors.

## Startup Customer Journey

```mermaid
flowchart LR; A[CargoWise Directory] --> B[Developer Sandbox]; B --> C[Pilot Declaration Batch]; C --> D[Dispatch SMS]; D --> E[TMS API Endpoint]; E --> F[Agent Schema Registry]
```

## Startup Proof Points

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

**Pilot Goals**:
- A 30-day proof-of-concept with a mid-sized freight forwarder processing 500 gate entries, aiming to validate the under-60-second processing time for standard customs clearances.
- A two-week technical validation with a regional 3PL to test the API fallback mechanisms, targeting zero failed dispatches during simulated terminal API outages.
**Target Metrics**:
- Target: 99.5% first-time terminal gate acceptance rate for automated dispatches
- Target: Under 60 seconds processing time from customs clearance receipt to dispatch generation
- Aim: Zero dry run penalties incurred due to system parsing or routing errors
- Aim: Less than 5% of document extractions requiring manual one-click validation due to low confidence scores
**Target Case Studies**:
- Mid-sized Freight Forwarder (Operations Manager): Demonstrating the elimination of manual document transcription by feeding extracted customs data directly into an existing TMS via API to trigger immediate dispatch.
- Regional Drayage Operator (Dispatch Supervisor): Validating the delivery of automated gate passes and routing instructions via standard SMS, resulting in high terminal gate acceptance rates without driver app installations.
- High-volume 3PL (Director of IT): Proving the reliability of automated EDI parsing and direct port portal scraping fallbacks when primary terminal APIs experience downtime during high-volume periods.
**Testimonial Targets**:
- Operations Director expressing relief that the API feeds extracted customs data into their existing TMS automatically, eliminating data entry without requiring a core system replacement.
- Dispatch Manager highlighting confidence in the system's fallback port portal scraping, ensuring drivers receive accurate gate passes even when terminal APIs go offline.
- Carrier Owner-Operator validating the low-friction driver experience of receiving gate passes and routing instructions via standard SMS instead of requiring a new mobile app.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Customs authorities or port terminal operators block third-party data scraping or deprecate public APIs, instantly blinding the parsing engine. · Mitigation Status: unmitigated
- Severity: high · Description: The performance-based pricing model ruins unit economics if port congestion causes high dispatch compute costs without yielding billable gate entries. · Mitigation Status: in-progress
- Severity: moderate · Description: Entrenched legacy freight forwarders refuse to adopt a new programmable API over their existing long-term Descartes EDI contracts. · Mitigation Status: in-progress
- Severity: low · Description: Localized drayage driver shortages lead to rejected automated dispatches, requiring manual carrier sourcing and breaking the automation loop. · Mitigation Status: unmitigated

## Startup Competitors

- [Descartes Systems](/Competitors/Descartes_Systems) — Incumbent
- [Traditional Freight Forwarders](/Competitors/Traditional_Freight_Forwarders) — Status Quo
- [In-House EDI Portals](/Competitors/In-House_EDI_Portals) — DIY Tool
- [WiseTech Global](/Competitors/WiseTech_Global) — Enterprise Platform
- [Expeditors International](/Competitors/Expeditors_International) — Legacy Forwarder

## Startup Solution Stack

- [Drayage Dispatch Service](/Services/Drayage_Dispatch_Service) — Service-as-Software
- [Customs Parsing Agent](/Agents/Customs_Parsing_Agent) — Agent
- [Gate Scheduling Worker](/Agents/Gate_Scheduling_Worker) — Agent
- [Terminal Entry API](/Software/Terminal_Entry_API) — Software
- [Drayage Routing SDK](/Software/Drayage_Routing_SDK) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the logistics architect driving volume, not the clerk typing container numbers
- **Want**: to convert customs clearances into terminal gate dispatches instantly
- **Identity**: the dispatch lead at a mid-sized freight forwarding firm
**Plan**:
- Step: Upload declaration · Detail: Drop your PDF customs clearance or EDI file into the portal to extract all line-item container data.
- Step: Inspect routing · Detail: Verify the auto-populated carrier and terminal gate instructions before the dispatch triggers via SMS.
- Step: Monitor gates · Detail: Track the carrier's arrival and only pay the usage fee once the truck successfully clears the terminal gate.
**Guide**:
- **Empathy**: When a customs entry clears, the delay spent re-typing container and booking details into a dispatch module risks missing a terminal window.
**Problem**:
- **Villain**: manual transcription
- **External**: Transcribing customs declarations into a TMS like Descartes for every drayage move creates six-minute delays and frequent typos per load.
- **Internal**: You feel like a bottleneck between the broker and the carrier while the demurrage clock ticks.
- **Philosophical**: Logistics expertise belongs in solving capacity constraints, not in rekeying data from a PDF.
**Success**: Cargowharf automates your drayage dispatch at the speed of a customs clearance, charging only for successful terminal entries.
**One Liner**: Manual document transcription costs freight forwarders precious terminal windows. Cargowharf parses customs declarations to automate drayage dispatch so trucks move the moment they clear.
**Positioning**:
- **So That**: trigger dispatches instantly with pay-per-successful-gate pricing
- **Unlike**: manual TMS data entry
- **For Whom**: dispatch leads at mid-sized freight forwarders
- **Category**: Automated drayage dispatch software
**Call To Action**:
- **Direct**: Dispatch first load
- **Transitional**: View sample parse
**Failure Stakes**:
- Costly dry run penalties
- Missed terminal appointments
- Data-entry burnout
**Transformation**:
- **To**: managing automated port-flow instead of re-typing documents
- **From**: a data-entry clerk transcribing PDF clearances
**Controlling Idea**: Drayage dispatch should trigger automatically the moment a customs entry clears.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Manual document transcription costs freight forwarders precious terminal windows. Cargowharf parses customs declarations to automate drayage dispatch so trucks move the moment they clear.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: d203f66ef64656f6

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Automated drayage dispatch software for dispatch leads at mid-sized freight forwarders. Unlike manual TMS data entry — trigger dispatches instantly with pay-per-successful-gate pricing.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 160cb288841902c6

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Transcribing customs declarations into a TMS like Descartes for every drayage move creates six-minute delays and frequent typos per load.
Solution: Manual document transcription costs freight forwarders precious terminal windows. Cargowharf parses customs declarations to automate drayage dispatch so trucks move the moment they clear.
Customer: dispatch leads at mid-sized freight forwarders
Unlike: manual TMS data entry
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 085f5cd3093bda99

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

**Pain**: Transcribing customs declarations into a TMS like Descartes for every drayage move creates six-minute delays and frequent typos per load.
**Metrics**: Target: Cargowharf automates your drayage dispatch at the speed of a customs clearance, charging only for successful terminal entries.
**Rendered**: Pain: Transcribing customs declarations into a TMS like Descartes for every drayage move creates six-minute delays and frequent typos per load.
Economic buyer: Customs Broker / Freight Forwarder
Metrics: Target: Cargowharf automates your drayage dispatch at the speed of a customs clearance, charging only for successful terminal entries.
Competition: manual TMS data entry
**Mechanism**: spine-derived-v1
**Competition**: manual TMS data entry
**Economic Buyer**: Customs Broker / Freight Forwarder
**Vocab Fingerprint**: d2fbba9d74fe1a55

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Automated drayage dispatch software for dispatch leads at mid-sized freight forwarders

dispatch leads at mid-sized freight forwarders — Transcribing customs declarations into a TMS like Descartes for every drayage move creates six-minute delays and frequent typos per load. Manual document transcription costs freight forwarders precious terminal windows. Cargowharf parses customs declarations to automate drayage dispatch so trucks move the moment they clear.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 52fc06a903bb2bf7

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Automated drayage dispatch software. Manual document transcription costs freight forwarders precious terminal windows. Cargowharf parses customs declarations to automate drayage dispatch so trucks move the moment they clear. Serves dispatch leads at mid-sized freight forwarders.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 4efe8059a3d0838b

## Neighborhood

### Candidate solutions

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

### Composed of

- [Drayage Routing SDK](/Software/Drayage_Routing_SDK) — composes · Software
- [Terminal Entry API](/Software/Terminal_Entry_API) — composes · Software
- [Gate Scheduling Worker](/Agents/Gate_Scheduling_Worker) — composes · Agents
- [Customs Parsing Agent](/Agents/Customs_Parsing_Agent) — composes · Agents
- [Drayage Dispatch Service](/Services/Drayage_Dispatch_Service) — composes · Services

### Competitors

- [Descartes Systems](/Competitors/Descartes_Systems) — competes with · Competitors
- [Traditional Freight Forwarders](/Competitors/Traditional_Freight_Forwarders) — competes with · Competitors
- [In-House EDI Portals](/Competitors/In-House_EDI_Portals) — competes with · Competitors
- [WiseTech Global](/Competitors/WiseTech_Global) — competes with · Competitors
- [Expeditors International](/Competitors/Expeditors_International) — competes with · Competitors

### Embodies

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

### What it offers

- [Drayage Dispatch Engine](/Software/Drayage_Dispatch_Engine) — offers · Software

### Similar Startups

- [Clearquay](/Startups/Clearquay) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Heavyport](/Startups/Heavyport) — similar · Startups
- [Brokeragemill](/Startups/Brokeragemill) — similar · Startups
- [Trade Flow Agent](/Startups/Trade_Flow_Agent) — similar · Startups
- [Abearing](/Startups/Abearing) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [M](/Startups/M) — similar · Startups
- [Apoyage](/Startups/Apoyage) — similar · Startups
- [Arrivalquay](/Startups/Arrivalquay) — similar · Startups
- [Cargoharbor](/Startups/Cargoharbor) — similar · Startups
- [Beaconharbor](/Startups/Beaconharbor) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Cargofield](/Startups/Cargofield) — similar · Startups
- [Kerforder](/Startups/Kerforder) — similar · Startups
- [Crossoyage](/Startups/Crossoyage) — similar · Startups
- [Pinnacleship](/Startups/Pinnacleship) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Burdendock](/Startups/Burdendock) — similar · Startups