# Heavywharf

*/Startups/Heavywharf*

## Startup Overview

This platform schedules terminal vehicles and resolves container routing bottlenecks for maritime port operations. It processes live terminal telemetry to dispatch straddle carriers, automated guided vehicles, and yard trucks to specific stack locations. Operators eliminate vehicle deadheading and container dwell times by dynamically assigning the closest available asset to the next priority move.

Terminal operators and stevedores struggle against rigid yard plans that fail when ships arrive off-schedule or dockside equipment breaks down. Traditional terminal operating systems rely on batch-processed assignments, forcing dispatchers to manage cascading delays through manual spreadsheet adjustments. The resulting friction creates heavy traffic queues at the gate and delays ship turnaround times.

Unlike Navis N4 or Tideworks TOS, this routing architecture is entirely event-driven. Instead of locking in a static shift plan, the system recalculates dispatch instructions instantly when a container clears the quay crane or an external truck enters the terminal gate. The commercial model aligns directly with physical execution, charging operators strictly on an outcome-priced basis per container moved.

## Startup Founding Hypothesis

**Approach**: that schedules terminal vehicles and resolves container routing bottlenecks
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Tideworks TOS](/Competitors/Tideworks_TOS)
- [Manual Dispatch Spreadsheets](/Competitors/Manual_Dispatch_Spreadsheets)
**Differentiator2x2**: event-driven rather than batch-processed and outcome-priced per container moved

## Startup Solution Coordinate

**Solution**: [Terminal Dispatch Service](/Services/Terminal_Dispatch_Service)

## Startup Position2x2

```mermaid
quadrantChart
title Terminal Operating System Positioning
x-axis Batch Processed --> Event-Driven
y-axis Fixed License Pricing --> Outcome-Priced per Container
quadrant-1 Next-Gen TOS
quadrant-2 Niche Automation
quadrant-3 Legacy Port Software
quadrant-4 Custom Point Solutions
Navis N4: [0.2, 0.3]
Tideworks TOS: [0.3, 0.2]
Manual Dispatch Spreadsheets: [0.1, 0.1]
Heavywharf: [0.85, 0.85]
```

## Startup Offer

**Proof**:
- Targeting regional marine terminals aiming to reduce outside truck turn times by 10+ minutes.
- Aiming to deploy at inland intermodal yards processing over 250,000 TEUs annually.
- Designed for container facilities seeking to replace manual spreadsheet dispatch with live, event-driven sequencing.
**Tiers**:
- Name: Pilot Terminal · Price: ~$0.15–$0.25 per container moved · Inclusions: Real-time routing for up to 50 terminal tractors, designed to integrate with one primary Terminal Operating System (TOS), capped at 50,000 moves per month.
- Name: Full Facility · Price: ~$0.08–$0.15 per container moved · Inclusions: Unlimited terminal vehicles, multi-zone cross-yard scheduling, intended integration with gate operating systems, covering full-volume facilities moving over 100,000 TEUs monthly.
**Guarantee**: Guarantees a measurable reduction in average terminal tractor idle time during the first 90 days, or Heavywharf waives all per-container routing usage fees for that quarter.
**Business Function**: ProvideService
**Objection Handlers**:
- Concern: We already rely on Navis N4 or Tideworks and cannot replace our core TOS. Rebuttal: Heavywharf is designed to sit alongside your existing TOS via API, pulling manifest data to handle only the dynamic vehicle dispatching layer.
- Concern: Our yard suffers from WiFi dead zones that drop live instructions. Rebuttal: The application is designed to cache the next 3-5 optimal moves locally on the vehicle mounted terminal, tolerating intermittent connection drops.
- Concern: Operators might reject the routing if they spot a hazard the system cannot see. Rebuttal: Drivers maintain a one-tap override function to skip an unworkable container, immediately triggering a system re-route for the fleet.
**Pricing Architecture**: UsageMeter

## Startup Brand

**Voice**: Authoritative and operational, prioritizing physical throughput and terminal efficiency.
**Tagline**: Move more containers and eliminate port vehicle routing bottlenecks.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: High-visibility safety yellow and heavy tarmac grays anchor a rugged interface featuring stenciled typography reminiscent of shipping container weight markings.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Heavywharf → Terminal Operations Director → Yard Dispatcher → Shipping Line
**Gtm Motion**: Secures initial terminal access through low-risk, single-berth pilot deployments to demonstrate immediate routing efficiency. Expands across the broader port facility by scaling to all yard blocks, utilizing an outcome-based pricing model tied directly to the volume of containers moved.
**Agent Channel**: Would target listings in supply chain automation directories and autonomous equipment API registries, designed to allow global logistics AI agents to programmatically discover and invoke port-level vehicle routing endpoints.
**Primary Channel**: Direct outbound sales and structured RFP participation targeting Port Authority CIOs and Terminal Directors, alongside technical exhibits at specialized maritime logistics conferences like TOC Europe.

## Startup Customer Journey

```mermaid
flowchart LR; A[TOC Europe Exhibit]-->B[Pilot Proposal]; B-->C[Single-Berth Pilot]; C-->D[Navis N4 Integration]; D-->E[Vehicle Mounted Terminal]; E-->F[Full Port Facility]; F-->G[Autonomous Equipment Registry];
```

## Startup Proof Points

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

**Pilot Goals**:
- 90-day deployment on up to 50 terminal tractors to validate a measurable reduction in average tractor idle time against the historical baseline.
- 30-day API integration test with a primary TOS to successfully ingest manifest data and dynamically sequence up to 50,000 container moves.
**Target Metrics**:
- target: 10-minute reduction in average outside truck turn time
- target: 20 percent decrease in average terminal tractor idle time per shift
- target: 100 percent retention of dispatch instructions through yard WiFi dead zones via local caching
**Target Case Studies**:
- Regional marine terminal operations director shifting from manual spreadsheet dispatch to live, event-driven sequencing to reduce outside truck turn times.
- Inland intermodal yard processing over 250,000 TEUs annually implementing dynamic vehicle dispatching to lower tractor idle time during peak operations.
**Testimonial Targets**:
- Terminal Operations Director expressing relief that the dispatching layer sits alongside their existing TOS via API without requiring a core system replacement.
- Fleet Dispatcher highlighting how the one-tap override function empowers drivers to bypass unseen hazards without breaking the yard-wide sequencing flow.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Incumbent Terminal Operating Systems restrict API access to real-time container data, rendering the event-driven scheduler blind. · Mitigation Status: unmitigated
- Severity: high · Description: Longshoreman unions block the deployment of algorithmic dispatch tools by citing violations of collective bargaining agreements regarding work allocation. · Mitigation Status: in-progress
- Severity: high · Description: The per-container pricing model drops revenue to zero during port strikes or severe weather closures, starving the company of operating cash. · Mitigation Status: unmitigated
- Severity: moderate · Description: Intermittent wireless connectivity in legacy port yards drops real-time vehicle telemetry, degrading the event-driven scheduler to batch performance. · Mitigation Status: in-progress

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Legacy Incumbent
- [Tideworks TOS](/Competitors/Tideworks_TOS) — Incumbent TOS
- [Manual Dispatch Spreadsheets](/Competitors/Manual_Dispatch_Spreadsheets) — Status Quo
- [CyberLogitec OPUS Terminal](/Competitors/CyberLogitec_OPUS_Terminal) — Enterprise Platform
- [Inform SyncroTESS](/Competitors/Inform_SyncroTESS) — Point Solution

## Startup Solution Stack

- [Terminal Dispatch Service](/Services/Terminal_Dispatch_Service) — Service-as-Software
- [Vehicle Scheduling Agent](/Agents/Vehicle_Scheduling_Agent) — Agent
- [Bottleneck Resolution Worker](/Agents/Bottleneck_Resolution_Worker) — Agent
- [Event Routing Engine](/Software/Event_Routing_Engine) — Software
- [Container State API](/Software/Container_State_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the logistics leader who masters yard flow, not the one firefighting gridlock
- **Want**: to increase hourly container throughput without adding more terminal tractors
- **Identity**: a terminal operations manager at a high-volume marine port
**Plan**:
- Step: Review · Detail: Upload your current yard manifest and gate schedule to identify your primary routing bottlenecks.
- Step: Confirm · Detail: Verify the live vehicle-mounted terminal sync to ensure drivers receive optimized move sequences instantly.
- Step: Deploy · Detail: Execute event-driven scheduling to reduce tractor idle time and accelerate container cycles.
**Guide**:
- **Empathy**: Fuel margins and vessel windows are won in minutes — but yard flow is often lost to the lag of manual spreadsheet dispatch.
**Problem**:
- **Villain**: Batch-Processed Dispatch
- **External**: Navis N4 and Tideworks TOS leave terminal tractors idling while manual dispatch spreadsheets fail to account for live gate surges
- **Internal**: You feel the mounting pressure of vessel delays while seeing your fleet sit stationary
- **Philosophical**: Terminal intelligence belongs in real-time movement, not in stagnant batch reports.
**Success**: The terminal moves more containers per hour with a fleet that stays in constant, productive motion.
**One Liner**: Every shift, terminal managers battle tractor idling and gate gridlock. Heavywharf provides event-driven vehicle scheduling so ports move more containers with the same fleet.
**Positioning**:
- **So That**: eliminate terminal tractor idle time and increase hourly throughput
- **Unlike**: Manual Dispatch Spreadsheets
- **For Whom**: Terminal operations managers at marine ports
- **Category**: Event-driven terminal vehicle scheduling
**Call To Action**:
- **Direct**: Route a container
- **Transitional**: Terminal ROI Calculator
**Failure Stakes**:
- Increased truck turn times
- Excessive fuel waste
- Vessel loading delays
**Transformation**:
- **To**: the terminal's logistics architect
- **From**: a spreadsheet-bound dispatcher chasing yard delays
**Controlling Idea**: Yard efficiency should be measured by movement, not by the age of the data.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every shift, terminal managers battle tractor idling and gate gridlock. Heavywharf provides event-driven vehicle scheduling so ports move more containers with the same fleet.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 8587e7beff0d5b60

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Event-driven terminal vehicle scheduling for Terminal operations managers at marine ports. Unlike Manual Dispatch Spreadsheets — eliminate terminal tractor idle time and increase hourly throughput.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: bd824b53f25a4559

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Navis N4 and Tideworks TOS leave terminal tractors idling while manual dispatch spreadsheets fail to account for live gate surges
Solution: Every shift, terminal managers battle tractor idling and gate gridlock. Heavywharf provides event-driven vehicle scheduling so ports move more containers with the same fleet.
Customer: Terminal operations managers at marine ports
Unlike: Manual Dispatch Spreadsheets
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: a2f5034583543be7

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

**Pain**: Navis N4 and Tideworks TOS leave terminal tractors idling while manual dispatch spreadsheets fail to account for live gate surges
**Metrics**: Target: The terminal moves more containers per hour with a fleet that stays in constant, productive motion.
**Rendered**: Pain: Navis N4 and Tideworks TOS leave terminal tractors idling while manual dispatch spreadsheets fail to account for live gate surges
Economic buyer: Terminal Operations Director
Metrics: Target: The terminal moves more containers per hour with a fleet that stays in constant, productive motion.
Competition: Manual Dispatch Spreadsheets
**Mechanism**: spine-derived-v1
**Competition**: Manual Dispatch Spreadsheets
**Economic Buyer**: Terminal Operations Director
**Vocab Fingerprint**: 730d71dad6e096b4

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Event-driven terminal vehicle scheduling for Terminal operations managers at marine ports

Terminal operations managers at marine ports — Navis N4 and Tideworks TOS leave terminal tractors idling while manual dispatch spreadsheets fail to account for live gate surges Every shift, terminal managers battle tractor idling and gate gridlock. Heavywharf provides event-driven vehicle scheduling so ports move more containers with the same fleet.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 36ce0464db183de6

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Event-driven terminal vehicle scheduling. Every shift, terminal managers battle tractor idling and gate gridlock. Heavywharf provides event-driven vehicle scheduling so ports move more containers with the same fleet. Serves Terminal operations managers at marine ports.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: d7e244850998a3cf

## Neighborhood

### Candidate solutions

- [Source Heavy Plate Welders](/Problems/Source_Heavy_Plate_Welders) — candidate solution for · Problems

### Composed of

- [Terminal Dispatch Service](/Services/Terminal_Dispatch_Service) — composes · Services
- [Vehicle Scheduling Agent](/Agents/Vehicle_Scheduling_Agent) — composes · Agents
- [Bottleneck Resolution Worker](/Agents/Bottleneck_Resolution_Worker) — composes · Agents
- [Event Routing Engine](/Software/Event_Routing_Engine) — composes · Software
- [Container State API](/Software/Container_State_API) — composes · Software

### Embodies

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

### Competitors

- [Inform SyncroTESS](/Competitors/Inform_SyncroTESS) — competes with · Competitors
- [Tideworks TOS](/Competitors/Tideworks_TOS) — competes with · Competitors
- [Manual Dispatch Spreadsheets](/Competitors/Manual_Dispatch_Spreadsheets) — competes with · Competitors
- [CyberLogitec OPUS Terminal](/Competitors/CyberLogitec_OPUS_Terminal) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors

### Similar Startups

- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Portepoch](/Startups/Portepoch) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Autonomywharf](/Startups/Autonomywharf) — similar · Startups
- [Spotterquay](/Startups/Spotterquay) — similar · Startups
- [Managerquay](/Startups/Managerquay) — similar · Startups
- [Baywharf](/Startups/Baywharf) — similar · Startups
- [Jointoptimaquay](/Startups/Jointoptimaquay) — similar · Startups
- [Basisyard](/Startups/Basisyard) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Depotport](/Startups/Depotport) — similar · Startups
- [Choreographytower](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Choreographytower) — similar · Startups
- [Logisticsyard](/Startups/Logisticsyard) — similar · Startups
- [Assetdock](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Assetdock) — similar · Startups
- [Zonecongestion](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Zonecongestion) — similar · Startups
- [Crossyard](/Startups/Crossyard) — similar · Startups
- [Cadencehue](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Cadencehue) — similar · Startups
- [Floorsensepost](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Floorsensepost) — similar · Startups
- [Congestionyard](/Startups/Congestionyard) — similar · Startups