# Voyagepoint

*/Startups/Voyagepoint*

## Startup Overview

This deterministic data layer provides global supply chain visibility by converting fragmented carrier EDI feeds into standardized routing events. Rather than relying on fuzzy logic to interpret shipment statuses, the system ingests raw terminal messages and maps them strictly to structured schemas.

Logistics operators and third-party logistics providers routinely manage blind spots in their networks caused by legacy carrier systems. To reconcile conflicting EDI signals and locate missing freight, operations teams typically resort to manually scraping individual ocean and motor carrier portals.

While incumbent visibility networks like Project44 and FourKites bundle opaque subscriptions with varying data fidelity, this architecture executes fully deterministic mapping. Downstream systems trigger accurately without probabilistic guessing, and the commercial model aligns directly with value delivery by pricing solely per successful event.

## Startup Founding Hypothesis

**Approach**: that normalizes carrier EDI feeds into standardized routing events
**Competitors**:
- [Project44](/Competitors/Project44)
- [FourKites](/Competitors/FourKites)
- [manual portal scraping](/Competitors/manual_portal_scraping)
**Differentiator2x2**: fully deterministic in its mapping and priced per successful event

## Startup Solution Coordinate

**Solution**: [Carrier Event Router](/Software/Carrier_Event_Router)

## Startup Position2x2

```mermaid
quadrantChart
    title Market Positioning: Routing Event Normalization
    x-axis Probabilistic Mapping --> Fully Deterministic Mapping
    y-axis Fixed Subscription / Labor Cost --> Priced Per Successful Event
    quadrant-1 High-Value Utility
    quadrant-2 Experimental Pay-for-Performance
    quadrant-3 Legacy Operations
    quadrant-4 Enterprise SaaS Giants
    Project44: [0.45, 0.25]
    FourKites: [0.35, 0.30]
    Manual Portal Scraping: [0.80, 0.15]
    Voyagepoint: [0.90, 0.85]
```

## Startup Offer

**Proof**:
- Targeting 99.9% deterministic mapping accuracy across the top 50 global ocean and motor carriers
- Aim to eliminate up to 80% of manual portal scraping labor for mid-market freight forwarders
- Designed to process peak-season EDI feed volumes with sub-200ms API response times
**Tiers**:
- Name: On-Demand · Price: ~$0.15–$0.25 per successful event · Inclusions: Pay-as-you-go API access designed for low-volume or testing environments, including standard REST endpoints and baseline rate limits with no monthly minimum.
- Name: Committed Volume · Price: ~$0.08–$0.12 per successful event · Inclusions: Intended for logistics teams processing 10k–100k events per month, including webhook notifications, batch processing, and priority updates for new carrier codes.
- Name: High-Throughput · Price: ~$0.02–$0.05 per successful event · Inclusions: Designed for enterprise freight forwarders processing >100k events per month, featuring dedicated support channels, custom carrier onboarding, and SLA-backed uptime.
**Guarantee**: If a valid carrier EDI payload fails to map to our standardized routing schema due to parser error, that event is not billed and is automatically queued for our internal resolution team.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Carrier data is notoriously dirty; strict deterministic mapping will just throw errors. Rebuttal: We only charge for successful events—if the EDI is truly unparseable garbage, you pay nothing while the anomaly is logged.
- Objection: Project44 and FourKites provide a full visibility dashboard, not just an API. Rebuttal: Voyagepoint is a headless engine built specifically for teams who want to embed tracking data into their own custom TMS without paying a premium for a redundant UI.
- Objection: What happens when a carrier updates their AS2/EDI specifications unannounced? Rebuttal: The engine is designed to instantly detect schema drift, quarantine the unmapped fields, and alert our maintenance team to update the parser.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative and technical, prioritizing deterministic exactness over narrative.
**Tagline**: Deterministic routing events from chaotic carrier data feeds.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: High-contrast layouts pair high-visibility safety yellow and stark black with monospaced typography reminiscent of shipping manifest readouts.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: Voyagepoint -> Supply Chain Data Engineer -> Freight Forwarder Operations -> End Shipper
**Gtm Motion**: Acquisition targets supply chain data teams with a self-serve API sandbox to test deterministic carrier mapping on their own broken EDI feeds. Expansion scales organically as these teams route additional carriers and shipping lanes through the normalized API, shifting from a per-event trial to high-volume API contracts.
**Agent Channel**: Designed to list as a structured supply chain oracle in the LangChain tool registry and the OpenAI plugin directory, allowing autonomous procurement and routing agents to query standardized transit events via predictable API schemas.
**Primary Channel**: Technical SEO and GitHub repositories targeting developer searches for carrier EDI 214 parser, logistics event webhook, or automated freight tracking API, capturing engineers actively trying to fix broken logistics data integrations.

## Startup Customer Journey

```mermaid
flowchart LR; A[Search Engine Result] --> B[GitHub Repository]; B --> C[API Sandbox]; C --> D[Parsed EDI Payload]; D --> E[Custom TMS]; E --> F[High-Volume Contract]; F --> G[LangChain Tool 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 API integration pilot routing 10,000 live events from three historically problematic ocean carriers, aiming to prove >98% automated mapping accuracy before the client commits to a volume tier
- A two-week side-by-side benchmark against a legacy visibility platform, targeting proof that the headless engine delivers equivalent event latency into a custom TMS at a fraction of the per-event cost
**Target Metrics**:
- Target: 99.9% deterministic mapping accuracy across the top 50 global ocean and motor carriers
- Aim: 80% reduction in manual portal scraping labor hours for logistics operations teams
- Target: Sub-200ms API response times during peak-season EDI feed volumes
- Target: Zero dollars charged for unparseable anomalies or failed carrier payloads
**Target Case Studies**:
- Targeting mid-market freight forwarders to validate the transition from manual carrier portal scraping by 3+ FTEs to automated headless API ingestion directly into a proprietary TMS
- Targeting enterprise 3PL logistics teams to prove the ability to route high-throughput ocean carrier EDI feeds through a single engine, standardizing status updates across 20+ disparate carrier formats without building custom parsers
- Targeting supply chain software vendors to demonstrate how embedding the tracking API expands their supported carrier networks without requiring additional internal integration engineering headcount
**Testimonial Targets**:
- VP of Engineering at a freight forwarder expressing relief at retiring 30+ fragile, internally maintained AS2 and EDI carrier parsers
- Director of Logistics Operations highlighting the value of receiving standardized tracking data directly inside their native TMS without paying a premium for redundant third-party visibility dashboards
- Lead Integration Developer praising the schema drift detection, noting that unannounced carrier specification updates are quarantined and resolved without breaking internal pipelines

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Carriers revoke access to EDI feeds or transition to closed APIs that break the core data ingestion pipeline. · Mitigation Status: unmitigated
- Severity: high · Description: The pay-per-successful-event pricing model severely limits revenue when carrier systems output poor quality or incomplete data. · Mitigation Status: unmitigated
- Severity: high · Description: Incumbents like Project44 bundle deterministic mapping updates into their existing enterprise contracts to block new vendor approvals. · Mitigation Status: in-progress
- Severity: moderate · Description: Engineering resources are drained by the continuous maintenance required to support undocumented changes in legacy carrier EDI formats. · Mitigation Status: in-progress

## Startup Competitors

- [Project44](/Competitors/Project44) — Visibility Platform
- [FourKites](/Competitors/FourKites) — Visibility Platform
- [Manual Portal Scraping](/Competitors/Manual_Portal_Scraping) — Status Quo
- [Descartes MacroPoint](/Competitors/Descartes_MacroPoint) — Incumbent
- [Shippeo](/Competitors/Shippeo) — Visibility Platform

## Startup Solution Stack

- [Routing Event Service](/Services/Routing_Event_Service) — Service-as-Software
- [EDI Translation Agent](/Agents/EDI_Translation_Agent) — Agent
- [Deterministic Mapping Worker](/Agents/Deterministic_Mapping_Worker) — Agent
- [Carrier Ingestion API](/Software/Carrier_Ingestion_API) — Software
- [Standardized Event Webhook](/Software/Standardized_Event_Webhook) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the technical architect of a high-performance logistics engine
- **Want**: to feed clean, standardized routing data into their custom TMS
- **Identity**: the logistics engineer at a mid-market freight forwarder
**Plan**:
- Step: Submit payloads · Detail: Post your raw carrier EDI feeds to our REST endpoints for instant processing.
- Step: Check results · Detail: Verify successful events via webhooks while unmapped anomalies are automatically queued for resolution.
- Step: Update TMS · Detail: Ingest the clean, standardized JSON into your existing logistics systems without manual intervention.
**Guide**:
- **Empathy**: When a carrier updates their AS2 specification without notice, your visibility dashboards break and your customers lose trust.
**Problem**:
- **Villain**: schema drift
- **External**: tracking freight requires manual portal scraping and cleaning messy EDI feeds across fifty different carrier formats
- **Internal**: you feel like a glorified data janitor instead of a systems engineer
- **Philosophical**: Engineering talent belongs in building proprietary value, not in maintaining brittle carrier parsers.
**Success**: Your TMS receives a steady stream of validated, high-fidelity tracking events while you only pay for what actually maps.
**One Liner**: Chaotic carrier EDI feeds cost freight forwarders hours of manual data cleaning. Voyagepoint normalizes these feeds into deterministic routing events so logistics teams scale without manual scraping.
**Positioning**:
- **So That**: embed clean tracking data without paying for redundant dashboards
- **Unlike**: Project44 and FourKites
- **For Whom**: logistics engineers at mid-market freight forwarders
- **Category**: Headless Carrier Data API
**Call To Action**:
- **Direct**: Fetch API Key
- **Transitional**: View Schema Documentation
**Failure Stakes**:
- manual labor costs rise
- stale shipment data
- brittle custom integrations break
**Transformation**:
- **To**: architecting headless logistics infrastructure instead of chasing carrier updates
- **From**: a scraper technician managing broken Excel workarounds
**Controlling Idea**: Logistics data should be deterministic, pay-per-event, and headless.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Chaotic carrier EDI feeds cost freight forwarders hours of manual data cleaning. Voyagepoint normalizes these feeds into deterministic routing events so logistics teams scale without manual scraping.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: d712c9ed73e1ccc2

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Headless Carrier Data API for logistics engineers at mid-market freight forwarders. Unlike Project44 and FourKites — embed clean tracking data without paying for redundant dashboards.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 9436892a80ea350c

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: tracking freight requires manual portal scraping and cleaning messy EDI feeds across fifty different carrier formats
Solution: Chaotic carrier EDI feeds cost freight forwarders hours of manual data cleaning. Voyagepoint normalizes these feeds into deterministic routing events so logistics teams scale without manual scraping.
Customer: logistics engineers at mid-market freight forwarders
Unlike: Project44 and FourKites
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 9e34dda7a7233a37

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

**Pain**: tracking freight requires manual portal scraping and cleaning messy EDI feeds across fifty different carrier formats
**Metrics**: Target: Your TMS receives a steady stream of validated, high-fidelity tracking events while you only pay for what actually maps.
**Rendered**: Pain: tracking freight requires manual portal scraping and cleaning messy EDI feeds across fifty different carrier formats
Economic buyer: Supply Chain Data Engineer
Metrics: Target: Your TMS receives a steady stream of validated, high-fidelity tracking events while you only pay for what actually maps.
Competition: Project44 and FourKites
**Mechanism**: spine-derived-v1
**Competition**: Project44 and FourKites
**Economic Buyer**: Supply Chain Data Engineer
**Vocab Fingerprint**: 86ed27266e922872

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Headless Carrier Data API for logistics engineers at mid-market freight forwarders

logistics engineers at mid-market freight forwarders — tracking freight requires manual portal scraping and cleaning messy EDI feeds across fifty different carrier formats Chaotic carrier EDI feeds cost freight forwarders hours of manual data cleaning. Voyagepoint normalizes these feeds into deterministic routing events so logistics teams scale without manual scraping.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: d3f9c17b8642fc3a

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Headless Carrier Data API. Chaotic carrier EDI feeds cost freight forwarders hours of manual data cleaning. Voyagepoint normalizes these feeds into deterministic routing events so logistics teams scale without manual scraping. Serves logistics engineers at mid-market freight forwarders.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 849c6a3f8111721f

## Neighborhood

### Candidate solutions

- [Calculate Grower Liquidations](/Problems/Calculate_Grower_Liquidations) — candidate solution for · Problems

### What it offers

- [Carrier Event Router](/Software/Carrier_Event_Router) — offers · Software

### Composed of

- [Routing Event Service](/Services/Routing_Event_Service) — composes · Services
- [EDI Translation Agent](/Agents/EDI_Translation_Agent) — composes · Agents
- [Deterministic Mapping Worker](/Agents/Deterministic_Mapping_Worker) — composes · Agents
- [Carrier Ingestion API](/Software/Carrier_Ingestion_API) — composes · Software
- [Standardized Event Webhook](/Software/Standardized_Event_Webhook) — composes · Software

### Competitors

- [Shippeo](/Competitors/Shippeo) — competes with · Competitors
- [FourKites](/Competitors/FourKites) — competes with · Competitors
- [Project44](/Competitors/Project44) — competes with · Competitors
- [Manual Portal Scraping](/Competitors/Manual_Portal_Scraping) — competes with · Competitors
- [Descartes MacroPoint](/Competitors/Descartes_MacroPoint) — competes with · Competitors

### Embodies

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

### Similar Startups

- [Cargovista](/Startups/Cargovista) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Coordinatortower](/Startups/Coordinatortower) — similar · Startups
- [Crossoyage](/Startups/Crossoyage) — similar · Startups
- [Freighter](/Startups/Freighter) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Beamlane](/Startups/Beamlane) — similar · Startups
- [Daleharbor](/Startups/Daleharbor) — similar · Startups
- [Axiomquay](/Startups/Axiomquay) — similar · Startups
- [Valleyrail](/Startups/Valleyrail) — similar · Startups
- [Conveyorbond](/Startups/Conveyorbond) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Conduitharbor](/Startups/Conduitharbor) — similar · Startups
- [Cratefield](/Startups/Cratefield) — similar · Startups
- [Cadencewharf](/Startups/Cadencewharf) — similar · Startups
- [Wholesalerange](/Startups/Wholesalerange) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Delaygraph](/Startups/Delaygraph) — similar · Startups
- [Quadova](/Startups/Quadova) — similar · Startups