# Daleharbor

*/Startups/Daleharbor*

## Startup Overview

Freight brokers and logistics operators manage a continuous influx of unstructured shipping manifests that bottleneck terminal routing. The system ingests these raw freight documents and extracts bill-of-lading data directly into normalized EDI payloads. This direct translation from unstructured text to rigid electronic data interchange standards allows operators to route shipments without any manual transcription.

Generalized document processing tools like Rossum or Scale AI deliver probabilistic outputs that still demand human-in-the-loop review, while manual broker entry introduces fatal latency. In contrast, this pipeline is fully deterministic in its extraction accuracy, guaranteeing that every output perfectly maps to routing requirements. Customers pay strictly per successful parse, ensuring capital is only deployed when a document is flawlessly converted and ready for the logistics network.

## Startup Founding Hypothesis

**Approach**: that extracts bill-of-lading data into normalized EDI payloads
**Competitors**:
- [Rossum](/Competitors/Rossum)
- [Scale AI](/Competitors/Scale_AI)
- [manual broker entry](/Competitors/manual_broker_entry)
**Differentiator2x2**: billed strictly per successful parse and fully deterministic in extraction accuracy

## Startup Solution Coordinate

**Solution**: [Lading Extraction Engine](/Software/Lading_Extraction_Engine)

## Startup Position2x2

```mermaid
quadrantChart
    title Bill-of-Lading Extraction Positioning
    x-axis Fixed Cost / Subscription --> Pay-Per-Success Pricing
    y-axis Probabilistic / Variable --> Deterministic Accuracy
    quadrant-1 High-Value Automation
    quadrant-2 Predictable Overhead
    quadrant-3 Legacy Manual
    quadrant-4 Variable Efficacy
    manual broker entry: [0.15, 0.15]
    Rossum: [0.30, 0.65]
    Scale AI: [0.85, 0.45]
    Daleharbor: [0.90, 0.90]
```

## Startup Offer

**Proof**:
- Targeting a 98% reduction in manual data entry time for mid-sized freight brokers.
- Aiming to return validated EDI payloads in under 3 seconds per document.
- Designed to achieve deterministic accuracy on over 100 regional bill of lading variations without custom templates.
**Tiers**:
- Name: Standard Parser · Price: ~$0.50–$0.80 per successful parse · Inclusions: On-demand bill of lading extraction to EDI 310 payloads, up to 5,000 documents per month, with standard API and webhook endpoints.
- Name: Volume Brokerage · Price: ~$0.15–$0.35 per successful parse · Inclusions: High-volume batch processing for over 5,000 documents per month, priority queueing, and intended direct integration with primary transportation management systems.
**Guarantee**: If a bill of lading fails to map to a valid, fully structured EDI payload, or if data requires post-extraction manual correction, the parse is entirely unbilled.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: LLMs hallucinate critical weights and container numbers. Rebuttal: The engine relies on deterministic validation against strict EDI schemas, instantly rejecting and flagging ambiguous values rather than guessing.
- Objection: Our drivers submit crumpled, low-light photos of documents. Rebuttal: Unreadable documents fail the confidence threshold and route to your manual queue; you are billed strictly for automated successes.
- Objection: We already pay for a generic OCR platform. Rebuttal: Generic OCR requires continuous maintenance of bounding boxes and rules; Daleharbor is purpose-built to output standardized freight EDI directly.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Direct and operational, grounded strictly in freight logistics terminology.
**Tagline**: Extract bills of lading into perfectly structured EDI payloads.
**Icon Concept**: pallet
**Palette Intent**: industrial-safety
**Visual Identity**: Steel grays and high-visibility dockyard orange contrast against dense, monospaced typography evocative of terminal shipping manifests.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: Daleharbor → Freight Broker / 3PL → Logistics Carrier
**Gtm Motion**: Acquires mid-market freight brokers through direct outbound targeting EDI specialists with a zero-risk per-parse billing model. Expands account value organically as brokers route additional shipping lanes, ports, and inbound email queues through the extraction API.
**Agent Channel**: Designed to list in the LangChain tool registry and the OpenAI API catalog as an EDI payload generator, allowing autonomous supply chain and freight-routing agents to discover and call the endpoint when encountering raw PDF bills of lading.
**Primary Channel**: Direct outbound to logistics operations managers, supported by intended partner listings in major TMS integration directories like MercuryGate and McLeod Software where brokers search for automation plugins.

## Startup Customer Journey

```mermaid
flowchart LR; A[TMS Directory]-->B[API Sandbox]; B-->C[EDI Payload]; C-->D[Routing Engine]; D-->E[Volume Tier]; E-->F[Partner Referral];
```

## Startup Proof Points

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

**Pilot Goals**:
- 14-day parallel run alongside an existing manual entry team to prove the API returns compliant EDI 310 payloads for diverse regional BOLs with zero manual correction required.
- 30-day peak volume stress test processing over 5,000 driver-submitted BOL photos to validate the under-3-second payload return time and the reliable routing of low-light images to the manual queue.
**Target Metrics**:
- Target: 98% reduction in manual data entry time per bill of lading processed.
- Target: Under 3 seconds average return time for validated EDI 310 payloads.
- Aim: 100% rejection rate for illegible or ambiguous BOL fields to prevent downstream data corruption.
- Aim: Zero hours spent per month on OCR bounding-box maintenance.
**Target Case Studies**:
- Mid-sized freight broker shifting from manual BOL-to-TMS data entry to automated EDI 310 ingestion, eliminating document processing backlogs during peak shipping seasons.
- Regional 3PL provider standardizing document intake across dozens of regional carrier BOL formats without requiring IT to build or maintain custom extraction templates.
- High-volume transportation management firm migrating from flat-fee legacy OCR software to a usage-based parser, achieving zero payment for failed or inaccurate parses.
**Testimonial Targets**:
- VP of Freight Operations stating that automated EDI mapping entirely eliminated their weekend paperwork backlogs and reduced overtime costs.
- Lead Logistics IT Manager expressing confidence that strict EDI schema validation prevents the ingestion of hallucinated weights and container numbers.
- Brokerage Owner praising the usage-based pricing model that ensures they only pay for perfectly mapped outputs rather than failed extraction attempts.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Model accuracy fails to handle heavily degraded bills of lading from long-tail shippers, bankrupting the strictly per-successful-parse revenue model. · Mitigation Status: unmitigated
- Severity: high · Description: Horizontal competitors like Rossum release zero-shot logistics extraction models that match deterministic accuracy without requiring custom setup. · Mitigation Status: unmitigated
- Severity: high · Description: Legacy freight forwarders resist integrating the normalized EDI payloads due to hardcoded constraints in their on-premise ERP systems. · Mitigation Status: in-progress
- Severity: moderate · Description: Cloud inference and OCR compute costs scale faster than the per-parse fee, deteriorating gross margins on highly complex or multi-page documents. · Mitigation Status: in-progress

## Startup Competitors

- [Rossum](/Competitors/Rossum) — IDP Platform
- [Scale AI](/Competitors/Scale_AI) — Human in the Loop
- [Manual Broker Entry](/Competitors/Manual_Broker_Entry) — Status Quo
- [ABBYY FlexiCapture](/Competitors/ABBYY_FlexiCapture) — Legacy OCR
- [Google Document AI](/Competitors/Google_Document_AI) — General API
- [KlearNow](/Competitors/KlearNow) — Logistics AI Incumbent

## Startup Solution Stack

- [EDI Normalization Service](/Services/EDI_Normalization_Service) — Service-as-Software
- [Lading Extraction Agent](/Agents/Lading_Extraction_Agent) — Agent
- [Payload Verification Worker](/Agents/Payload_Verification_Worker) — Agent
- [Lading Extraction Engine](/Software/Lading_Extraction_Engine) — Software
- [Deterministic Parsing API](/Software/Deterministic_Parsing_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the strategic architect of a touchless dock-to-billing operation
- **Want**: to convert bill of lading documents into EDI payloads without manual data entry
- **Identity**: the logistics operations manager at a mid-sized freight brokerage
**Plan**:
- Step: Upload documents · Detail: Send your bill of lading PDFs or driver photos through the API or webhook endpoint.
- Step: Validate payloads · Detail: Review the automatically generated EDI 310 data for your specific transportation management system.
- Step: Approve extraction · Detail: Confirm the parsed data and pay only for documents that achieve 100% successful extraction.
**Guide**:
- **Empathy**: Does your document intake still stall because of unreadable driver photos and EDI mapping errors?
**Problem**:
- **Villain**: manual broker entry
- **External**: Processing bills of lading into EDI 310 payloads in the TMS requires hours of copying container numbers and weights from crumpled driver photos.
- **Internal**: You feel like a glorified typist rather than a logistics expert overseeing freight movement.
- **Philosophical**: Logistics expertise belongs in moving freight, not in transcribing documents.
**Success**: Bills of lading transform into structured EDI payloads in under three seconds, allowing your team to focus strictly on exceptions.
**One Liner**: Manual broker entry costs logistics teams thousands in lost hours. Daleharbor extracts bills of lading into perfectly structured EDI payloads so you can scale freight volume without adding headcount.
**Positioning**:
- **So That**: convert bills of lading to EDI payloads in three seconds
- **Unlike**: generic OCR platforms like Rossum
- **For Whom**: logistics operations managers at freight brokerages
- **Category**: EDI data extraction for freight brokers
**Call To Action**:
- **Direct**: Parse a document
- **Transitional**: Download sample EDI 310 payload
**Failure Stakes**:
- Billing delays from transcription errors
- Increased overhead from manual data entry
- Missed container weight discrepancies
**Transformation**:
- **To**: one of the few logistics managers who operate at scale
- **From**: a broker trapped in manual Rossum bounding boxes
**Controlling Idea**: Freight data extraction must be deterministic and billed only on success.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Manual broker entry costs logistics teams thousands in lost hours. Daleharbor extracts bills of lading into perfectly structured EDI payloads so you can scale freight volume without adding headcount.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 78f2b5282343e271

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: EDI data extraction for freight brokers for logistics operations managers at freight brokerages. Unlike generic OCR platforms like Rossum — convert bills of lading to EDI payloads in three seconds.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 0283868f629995e6

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Processing bills of lading into EDI 310 payloads in the TMS requires hours of copying container numbers and weights from crumpled driver photos.
Solution: Manual broker entry costs logistics teams thousands in lost hours. Daleharbor extracts bills of lading into perfectly structured EDI payloads so you can scale freight volume without adding headcount.
Customer: logistics operations managers at freight brokerages
Unlike: generic OCR platforms like Rossum
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 96f61470694d46ec

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

**Pain**: Processing bills of lading into EDI 310 payloads in the TMS requires hours of copying container numbers and weights from crumpled driver photos.
**Metrics**: Target: Bills of lading transform into structured EDI payloads in under three seconds, allowing your team to focus strictly on exceptions.
**Rendered**: Pain: Processing bills of lading into EDI 310 payloads in the TMS requires hours of copying container numbers and weights from crumpled driver photos.
Economic buyer: Freight Broker / 3PL
Metrics: Target: Bills of lading transform into structured EDI payloads in under three seconds, allowing your team to focus strictly on exceptions.
Competition: generic OCR platforms like Rossum
**Mechanism**: spine-derived-v1
**Competition**: generic OCR platforms like Rossum
**Economic Buyer**: Freight Broker / 3PL
**Vocab Fingerprint**: 041b763030fef402

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: EDI data extraction for freight brokers for logistics operations managers at freight brokerages

logistics operations managers at freight brokerages — Processing bills of lading into EDI 310 payloads in the TMS requires hours of copying container numbers and weights from crumpled driver photos. Manual broker entry costs logistics teams thousands in lost hours. Daleharbor extracts bills of lading into perfectly structured EDI payloads so you can scale freight volume without adding headcount.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 5e83029c785e8d8b

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: EDI data extraction for freight brokers. Manual broker entry costs logistics teams thousands in lost hours. Daleharbor extracts bills of lading into perfectly structured EDI payloads so you can scale freight volume without adding headcount. Serves logistics operations managers at freight brokerages.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 2d4ba6036ae63a27

## Neighborhood

### Candidate solutions

- [Micro-Trend Demand Forecasting](/Problems/Micro-Trend_Demand_Forecasting) — candidate solution for · Problems

### Composed of

- [EDI Normalization Service](/Services/EDI_Normalization_Service) — composes · Services
- [Lading Extraction Agent](/Agents/Lading_Extraction_Agent) — composes · Agents
- [Payload Verification Worker](/Agents/Payload_Verification_Worker) — composes · Agents
- [Lading Extraction Engine](/Software/Lading_Extraction_Engine) — composes · Software
- [Deterministic Parsing API](/Software/Deterministic_Parsing_API) — composes · Software

### Embodies

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

### Competitors

- [Google Document AI](/Competitors/Google_Document_AI) — competes with · Competitors
- [KlearNow](/Competitors/KlearNow) — competes with · Competitors
- [Rossum](/Competitors/Rossum) — competes with · Competitors
- [Scale AI](/Competitors/Scale_AI) — competes with · Competitors
- [Manual Broker Entry](/Competitors/Manual_Broker_Entry) — competes with · Competitors
- [ABBYY FlexiCapture](/Competitors/ABBYY_FlexiCapture) — competes with · Competitors

### Similar Startups

- [Foliumquay](/Startups/Foliumquay) — similar · Startups
- [Dalyard](/Startups/Dalyard) — similar · Startups
- [Cratefield](/Startups/Cratefield) — similar · Startups
- [Carvauge](/Startups/Carvauge) — similar · Startups
- [Valleymanifest](/Startups/Valleymanifest) — similar · Startups
- [Voyagefield](/Startups/Voyagefield) — similar · Startups
- [Pinnacleship](/Startups/Pinnacleship) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Dematter](/Startups/Dematter) — similar · Startups
- [Conduitharbor](/Startups/Conduitharbor) — similar · Startups
- [Challengequay](/Startups/Challengequay) — similar · Startups
- [Heavyport](/Startups/Heavyport) — similar · Startups
- [Brokeragedome](/Startups/Brokeragedome) — similar · Startups
- [Kerforder](/Startups/Kerforder) — similar · Startups
- [Bridgack](/Startups/Bridgack) — similar · Startups
- [Crossoyage](/Startups/Crossoyage) — similar · Startups
- [Napot](/Startups/Napot) — similar · Startups
- [Anchorloft](/Startups/Anchorloft) — similar · Startups
- [Abearing](/Startups/Abearing) — similar · Startups
- [Paperinsight](/Startups/Paperinsight) — similar · Startups