# Planequay

*/Startups/Planequay*

## Startup Overview

This engine continuously correlates incoming flight manifests with terminal berthing schedules to synchronize multimodal freight handoffs. It operates as a headless data orchestration layer, ingesting air cargo arrival data and mapping it directly to port availability windows. By bridging the gap between aviation schedules and maritime logistics, the system ensures that ground transport units dispatch precisely when cargo touches down and clears customs.

Port operators and freight forwarders currently manage intermodal transfers through fragmented channels, relying on manual email-based dispatch workflows or standalone dashboards that fail to communicate. Legacy Terminal Operating Systems handle maritime vessels but remain completely blind to inbound air freight, forcing dispatchers to manually cross-reference arrival times. This data disconnect creates chronic delays at the terminal gate and misaligned drayage scheduling.

Instead of forcing operators to adopt another visual interface, the architecture deploys entirely without UI dependencies, feeding its synchronization logic directly into existing enterprise logistics databases. It generates predictive timing across both air and sea transport modes, updating dispatch protocols based on real-time transit deviations rather than static schedules. This continuous, cross-modal correlation eliminates the traditional blind spots between the runway and the dock.

## Startup Founding Hypothesis

**Approach**: that correlates incoming flight manifests with terminal berthing schedules
**Competitors**:
- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems)
- [Email-based dispatch](/Competitors/Email-based_dispatch)
- [Standalone freight forwarding dashboards](/Competitors/Standalone_freight_forwarding_dashboards)
**Differentiator2x2**: predictive across transport modes and deployable without UI dependencies

## Startup Solution Coordinate

**Solution**: [Terminal Sync Engine](/Software/Terminal_Sync_Engine)

## Startup Position2x2

```mermaid
quadrantChart
title Market Positioning: Planequay
x-axis Reactive / Siloed --> Predictive across Modes
y-axis UI-Dependent Monolith --> Headless / API-Deployable
quadrant-1 API-First / Multi-Modal
quadrant-2 API-First / Siloed
quadrant-3 Legacy / Manual
quadrant-4 UI-Heavy / Multi-Modal
ALegacy Terminal Operating Systems: [0.15, 0.15]
Email-based dispatch: [0.10, 0.70]
Standalone freight forwarding dashboards: [0.40, 0.20]
Planequay: [0.85, 0.85]
```

## Startup Offer

**Proof**:
- Target: 30% reduction in truck idling times at terminal gates for integrated freight forwarders.
- Target: Eliminate manual email-based dispatch coordination between air cargo arrival and ground transit.
- Target: Headless API integration with legacy Terminal Operating Systems completed in under 14 days.
**Tiers**:
- Name: On-Demand Correlation · Price: ~$0.15–$0.35 per manifest processed · Inclusions: Headless API access for correlating incoming flight manifests with ground terminal berthing schedules, standard data mapping, and standard latency.
- Name: Terminal Volume · Price: ~$2,500–$6,000/mo · Inclusions: Up to 50,000 manifest correlations per month, predictive transport delay modeling, and dedicated webhook infrastructure designed to feed existing Terminal Operating Systems.
**Guarantee**: If the API fails to return a correlated berthing schedule within 3 seconds of receiving a valid flight manifest payload, the metered charge for that transaction is automatically waived.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Our dispatchers require a visual dashboard to manage shipments. Rebuttal: Planequay is designed to operate completely headless, pushing predictive berthing updates directly into your existing dispatch UIs or enterprise email workflows.
- Objection: We already use a heavy Terminal Operating System (TOS) that we cannot replace. Rebuttal: Planequay is designed to complement, not replace, your TOS by feeding it enriched predictive air-manifest data via standard APIs.
- Objection: Flight delays make early berthing schedules obsolete. Rebuttal: The platform continuously polls aviation data to dynamically adjust terminal berthing recommendations in real time as flight statuses change.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative dispatch register defined by precise intermodal logistics terminology.
**Tagline**: Synchronize air freight arrivals with seaport berthing schedules.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: The brand pairs high-visibility hazard yellow with corrugated steel gray, utilizing stark typography reminiscent of shipping manifests.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: Planequay → Terminal Operating System (TOS) Provider → Freight Forwarder
**Gtm Motion**: Acquires legacy terminal operators via targeted developer outreach for a single-port flight manifest API pilot, expanding into enterprise contracts by upselling automated multi-modal dispatch webhooks across their global terminal networks.
**Agent Channel**: Would expose its headless correlation endpoints as an OpenAPI specification intended for the LangChain tool registry and OpenAI schema directories, allowing autonomous supply chain agents to discover and query berthing schedules directly.
**Primary Channel**: Technical documentation and API marketplace listings capturing queries from logistics engineers searching for 'flight manifest to terminal berthing API' or 'headless cargo scheduling'.

## Startup Customer Journey

```mermaid
flowchart LR
  A[API Marketplace Listing] --> B[OpenAPI Specification]
  B --> C[Single-Port Pilot]
  C --> D[TOS Webhook Pipeline]
  D --> E[Enterprise Terminal Contract]
  E --> F[Supply Chain Agent Directory]
```

## Startup Proof Points

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

**Pilot Goals**:
- Aim for a 30-day sandbox API evaluation to demonstrate sub-3-second manifest correlation and successful webhook payload delivery into the client's legacy Terminal Operating System.
- Target a 60-day parallel run at a single cargo terminal to compare the efficiency of automated berthing adjustments against manual dispatch coordination.
**Target Metrics**:
- Target: 30% reduction in truck idling times at terminal gates
- Target: 100% elimination of manual email-based dispatch coordination between air and ground transit
- Aim: Under 14 days to complete headless API integration with a legacy Terminal Operating System
- Target: Sub-3-second latency for returning correlated berthing schedules from valid manifest payloads
**Target Case Studies**:
- Target: Mid-sized freight forwarder transitions from manual email-based dispatch coordination to automated manifest-to-berthing correlation, routing predictive schedules directly into their existing dispatch UI.
- Target: Regional cargo terminal operator integrates the headless API into their legacy Terminal Operating System, automatically adjusting berthing allocations based on continuous aviation data polling.
- Target: Large third-party logistics provider utilizes predictive transport delay modeling to align truck arrivals with actual air cargo availability, aiming to reduce gate idling times.
**Testimonial Targets**:
- Target role: Dispatch Manager. Sentiment: Relief that dispatchers no longer manually cross-reference flight delays, as predictive updates now push seamlessly into their existing enterprise workflow.
- Target role: Terminal Operations Director. Sentiment: Appreciation that the integration enriched their heavy legacy TOS with dynamic berthing schedules without requiring a costly system replacement.
- Target role: VP of Logistics Engineering. Sentiment: Satisfaction with the sub-3-second API response time and the automated billing waiver guarantee, proving the reliability of the infrastructure.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Major airlines or port authorities revoke access to live flight manifests and terminal berthing API feeds. · Mitigation Status: unmitigated
- Severity: high · Description: Incumbent Terminal Operating Systems refuse integration or block incoming data feeds from third-party predictive engines. · Mitigation Status: in-progress
- Severity: moderate · Description: Freight forwarders reject the headless deployment model and require full graphical interfaces to adopt the system. · Mitigation Status: unmitigated
- Severity: low · Description: Micro-local physical delays like crane maintenance or weather patterns skew the cross-mode prediction accuracy. · Mitigation Status: in-progress

## Startup Competitors

- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems) — Incumbent
- [Email-Based Dispatch](/Competitors/Email-Based_Dispatch) — Status Quo
- [Standalone Freight Forwarding Dashboards](/Competitors/Standalone_Freight_Forwarding_Dashboards) — Point Solution
- [Navis N4 TOS](/Competitors/Navis_N4_TOS) — Incumbent
- [Manual Spreadsheet Tracking](/Competitors/Manual_Spreadsheet_Tracking) — Status Quo

## Startup Solution Stack

- [Manifest Correlation Service](/Services/Manifest_Correlation_Service) — Service-as-Software
- [Berth Allocation Agent](/Agents/Berth_Allocation_Agent) — Agent
- [Schedule Sync Worker](/Agents/Schedule_Sync_Worker) — Agent
- [Flight Ingestion API](/Software/Flight_Ingestion_API) — Software
- [Terminal Sync Engine](/Software/Terminal_Sync_Engine) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the strategic architect of terminal throughput rather than a frantic email intermediary
- **Want**: to synchronize incoming flight manifests with ground terminal berthing schedules automatically
- **Identity**: the dispatch supervisor at a high-volume intermodal air-cargo terminal
**Plan**:
- Step: Submit manifest · Detail: Push your incoming flight manifest data directly into our API endpoint.
- Step: Validate schedule · Detail: Our engine matches the payload against real-time terminal berthing availability and aviation data.
- Step: Direct dispatch · Detail: Receive predictive updates directly in your existing UI to trigger immediate truck mobilization.
**Guide**:
- **Empathy**: Does your dispatch process still suffer from truck idling due to misaligned flight arrival data?
**Problem**:
- **Villain**: Email-based dispatch
- **External**: Coordinating ground transit involves manual copy-pasting from flight dashboards into terminal emails and legacy Terminal Operating Systems.
- **Internal**: You feel the constant pressure of gate congestion while waiting for manual status updates.
- **Philosophical**: Logistics expertise belongs in flow optimization, not in transcribing manifest data between siloed screens.
**Success**: Air freight arrivals and ground berthing align perfectly, reducing gate congestion and eliminating manual dispatch emails entirely.
**One Liner**: Manual manifest coordination costs dispatchers hours in truck idling. Planequay correlates flight arrivals with berthing schedules so terminals maintain fluid intermodal throughput.
**Positioning**:
- **So That**: reduce truck idling through predictive air-manifest correlation
- **Unlike**: legacy Terminal Operating Systems
- **For Whom**: dispatch supervisors at air-cargo terminals
- **Category**: Intermodal dispatch automation
**Call To Action**:
- **Direct**: Process a manifest
- **Transitional**: Review API documentation
**Failure Stakes**:
- Extended truck idling times at terminal gates
- Manual data entry errors in the TOS
- Missed ground transit windows
**Transformation**:
- **To**: the lead who manages intermodal flow via headless automation
- **From**: the dispatcher buried in email-based coordination
**Controlling Idea**: Intermodal synchronization must be automated to eliminate terminal gate congestion.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Manual manifest coordination costs dispatchers hours in truck idling. Planequay correlates flight arrivals with berthing schedules so terminals maintain fluid intermodal throughput.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 4bf5b9e42673083e

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Intermodal dispatch automation for dispatch supervisors at air-cargo terminals. Unlike legacy Terminal Operating Systems — reduce truck idling through predictive air-manifest correlation.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 7a0287cbbd007322

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Coordinating ground transit involves manual copy-pasting from flight dashboards into terminal emails and legacy Terminal Operating Systems.
Solution: Manual manifest coordination costs dispatchers hours in truck idling. Planequay correlates flight arrivals with berthing schedules so terminals maintain fluid intermodal throughput.
Customer: dispatch supervisors at air-cargo terminals
Unlike: legacy Terminal Operating Systems
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 03ae284694d263ce

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

**Pain**: Coordinating ground transit involves manual copy-pasting from flight dashboards into terminal emails and legacy Terminal Operating Systems.
**Metrics**: Target: Air freight arrivals and ground berthing align perfectly, reducing gate congestion and eliminating manual dispatch emails entirely.
**Rendered**: Pain: Coordinating ground transit involves manual copy-pasting from flight dashboards into terminal emails and legacy Terminal Operating Systems.
Economic buyer: Terminal Operating System Provider
Metrics: Target: Air freight arrivals and ground berthing align perfectly, reducing gate congestion and eliminating manual dispatch emails entirely.
Competition: legacy Terminal Operating Systems
**Mechanism**: spine-derived-v1
**Competition**: legacy Terminal Operating Systems
**Economic Buyer**: Terminal Operating System Provider
**Vocab Fingerprint**: f63a3027e75c8967

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Intermodal dispatch automation for dispatch supervisors at air-cargo terminals

dispatch supervisors at air-cargo terminals — Coordinating ground transit involves manual copy-pasting from flight dashboards into terminal emails and legacy Terminal Operating Systems. Manual manifest coordination costs dispatchers hours in truck idling. Planequay correlates flight arrivals with berthing schedules so terminals maintain fluid intermodal throughput.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: f34cb72a539bf237

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Intermodal dispatch automation. Manual manifest coordination costs dispatchers hours in truck idling. Planequay correlates flight arrivals with berthing schedules so terminals maintain fluid intermodal throughput. Serves dispatch supervisors at air-cargo terminals.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: ad82a7baa0ebfe39

## Neighborhood

### Candidate solutions

- [Standardize Bespoke Quoting Margins](/Problems/Standardize_Bespoke_Quoting_Margins) — candidate solution for · Problems
- [Unbillable Tax Data Extraction](/Problems/Unbillable_Tax_Data_Extraction) — candidate solution for · Problems

### Composed of

- [Terminal Sync Engine](/Software/Terminal_Sync_Engine) — composes · Software
- [Manifest Correlation Service](/Services/Manifest_Correlation_Service) — composes · Services
- [Berth Allocation Agent](/Agents/Berth_Allocation_Agent) — composes · Agents
- [Schedule Sync Worker](/Agents/Schedule_Sync_Worker) — composes · Agents
- [Flight Ingestion API](/Software/Flight_Ingestion_API) — composes · Software

### Embodies

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

### Competitors

- [Manual Spreadsheet Tracking](/Competitors/Manual_Spreadsheet_Tracking) — competes with · Competitors
- [Standalone Freight Forwarding Dashboards](/Competitors/Standalone_Freight_Forwarding_Dashboards) — competes with · Competitors
- [Email-Based Dispatch](/Competitors/Email-Based_Dispatch) — competes with · Competitors
- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems) — competes with · Competitors
- [Navis N4 TOS](/Competitors/Navis_N4_TOS) — competes with · Competitors

### Similar Startups

- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Jointoptimaquay](/Startups/Jointoptimaquay) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Adjectival](/CompanyTypes/Terminal_Handling_Contractor/Startups/Adjectival) — similar · Startups
- [Warehouseloom](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Warehouseloom) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Agriculturalharbor](/Startups/Agriculturalharbor) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Cadencehue](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Cadencehue) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Sweeperdock](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Sweeperdock) — similar · Startups
- [Zonecongestion](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Zonecongestion) — similar · Startups
- [Floorfuel](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Floorfuel) — similar · Startups
- [Congestionbeam](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Congestionbeam) — similar · Startups
- [Axiomquay](/Startups/Axiomquay) — similar · Startups
- [Delaysforge](/Startups/Delaysforge) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Anchorcongestion](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Anchorcongestion) — similar · Startups
- [Valleyrail](/Startups/Valleyrail) — similar · Startups