# Spotterquay

*/Startups/Spotterquay*

## Startup Overview

Port operators lose critical turnaround time relying on static schedules to manage incoming maritime traffic. This platform dynamically maps incoming vessels to available quay slots by matching live vessel telemetry with physical terminal capacity. It automatically assigns and reserves docking locations to keep maritime freight moving.

Terminal dispatchers typically depend on manual spreadsheets or legacy systems like Navis N4 and Portchain to handle berthing schedules. When weather delays occur or loading times shift, these tools require immediate manual intervention to prevent port congestion. This system removes that bottleneck by functioning as a continuous-updating and self-correcting scheduling engine.

As conditions at sea or on the docks change, the software instantly recalculates the port schedule to accommodate new variables. Port authorities secure maximum utilization of their quay infrastructure while eliminating the constant manual reshuffling of berth assignments.

## Startup Founding Hypothesis

**Approach**: that dynamically maps incoming vessels to available quay slots
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Portchain](/Competitors/Portchain)
- [Manual Spreadsheets](/Competitors/Manual_Spreadsheets)
**Differentiator2x2**: continuous-updating and self-correcting rather than requiring manual dispatcher intervention

## Startup Solution Coordinate

**Solution**: [Quay Slot Engine](/Software/Quay_Slot_Engine)

## Startup Position2x2

```mermaid
quadrantChart
 x-axis Manual Updates --> Continuous Updating
 y-axis Dispatcher Dependent --> Self-Correcting
 Manual Spreadsheets: [0.1, 0.1]
 Navis N4: [0.3, 0.3]
 Portchain: [0.7, 0.6]
 Spotterquay: [0.9, 0.9]
```

## Startup Brand

**Voice**: Authoritative and precise, speaking directly to maritime dispatch operations.
**Tagline**: Self-correcting quay assignment for incoming vessels.
**Icon Concept**: bollard
**Palette Intent**: industrial-safety
**Visual Identity**: High-visibility yellow and heavy slate grey dominate the palette, paired with industrial sans-serif typography and stark maritime terminal imagery.
**Archetype Reference**: the-ruler

## Startup Customer Journey

```mermaid
flowchart LR; A[Maritime Software Directory] --> B[Terminal Operations Manager]; B --> C[Shadow Pilot Environment]; C --> D[Slot Reallocation Engine]; D --> E[Terminal Operating System]; E --> F[Port Network]; F --> G[Shipping Line API];
```

## Startup Proof Points

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

**Pilot Goals**:
- 30-day single-terminal read-only synchronization pilot: Aiming to prove complete mapping of up to 400 vessel calls while continuously ingesting real-time ETA data without disrupting existing legacy TOS workflows.
- 60-day bidirectional regional deployment: Targeting the successful automated execution of self-correcting berth reallocations across multiple terminals based on AIS-validated ETA shifts.
**Target Metrics**:
- Target: 20% reduction in average vessel anchorage wait times.
- Aim: Zero manual dispatcher interventions for standard ETA drift adjustments and weather delays.
- Target: 3-minute maximum system latency for executing automated quay slot reallocations.
- Aim: 15% increase in total quay utilization rates by automatically mapping gap-slots.
**Target Case Studies**:
- Mid-sized container terminal operations director: Transforming from manual spreadsheet berth planning to automated bidirectional synchronization that dynamically corrects quay slots based on real-time maritime ETAs.
- Regional multi-terminal port authority: Consolidating vessel call tracking across up to three distinct terminals to automatically capture and reallocate berth gaps previously missed by human dispatchers.
- Bulk cargo terminal planning manager: Validating carrier APIs against AIS satellite data to autonomously correct scheduling deviations without requiring core legacy TOS upgrades.
**Testimonial Targets**:
- Terminal Operations Director: Expressing relief that the platform acts as a reliable co-pilot, auto-routing standard scheduling deviations while explicitly flagging extreme physical anomalies for human oversight.
- Lead Dispatcher: Validating that the software polls data non-invasively from older systems like Navis N4 via standard EDIFACT messaging without forcing a core software upgrade.
- Port Network IT Manager: Praising the data reliability achieved by cross-referencing AIS satellite tracking with carrier APIs before executing self-correcting slot adjustments.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Major port authorities refuse to integrate their legacy terminal operating systems with a third-party mapping tool. · Mitigation Status: in-progress
- Severity: high · Description: Real-time vessel tracking data experiences high latency during adverse weather, causing the self-correcting algorithm to misallocate quay slots. · Mitigation Status: unmitigated
- Severity: moderate · Description: Veteran dispatchers frequently override the automated slot assignments due to lack of trust, reducing the software to a read-only dashboard. · Mitigation Status: in-progress
- Severity: low · Description: Established competitors like Portchain release a fast-follow auto-correction module to existing clients before Spotterquay secures its first port. · Mitigation Status: unmitigated

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Incumbent TOS
- [Portchain](/Competitors/Portchain) — Startup Competitor
- [Manual Spreadsheets](/Competitors/Manual_Spreadsheets) — Status Quo
- [Tideworks Mainsail](/Competitors/Tideworks_Mainsail) — Legacy TOS
- [CyberLogitec OPUS](/Competitors/CyberLogitec_OPUS) — Terminal Operating System

## Startup Story Brand

**Hero**:
- **Need**: to be the strategic architect of terminal flow, not a spreadsheet firefighter
- **Want**: to maximize quay utilization without manual scheduling conflicts
- **Identity**: the berth dispatcher at a regional container terminal
**Plan**:
- Step: Submit constraints · Detail: Input your terminal's physical crane reaches and draft depths into the digital quay map.
- Step: Confirm reallocations · Detail: Review self-correcting slot adjustments that Spotterquay suggests as vessel ETAs shift.
- Step: Sync terminal · Detail: Push the optimized schedule back to your TOS to coordinate crane crews and tugs.
**Guide**:
- **Empathy**: Quay-hour margins are won in the minutes following a delay — but manual dispatchers cannot recalculate the whole terminal in real-time.
**Problem**:
- **Villain**: ETA drift
- **External**: Vessel schedules in Navis N4 fall apart as weather and speed shifts force hours of manual re-planning in spreadsheets.
- **Internal**: You feel like you are chasing shadows while vessels wait at expensive anchorage.
- **Philosophical**: Why should terminal efficiency accept data-lag when satellite AIS can update a berth schedule in seconds?
**Success**: The quay schedule stays perfectly synchronized with actual vessel arrivals, eliminating anchorage bottlenecks and maximizing crane throughput.
**One Liner**: Every vessel delay, dispatchers struggle with manual berth re-planning. Spotterquay provides self-correcting quay assignment so terminals maximize utilization and eliminate anchorage wait times.
**Positioning**:
- **So That**: quay slots update automatically based on real-time AIS vessel drift
- **Unlike**: manual spreadsheets and static TOS scheduling
- **For Whom**: berth dispatchers at container terminals
- **Category**: Self-correcting berth planning software
**Call To Action**:
- **Direct**: Map your terminal
- **Transitional**: View sample quay-slot schema
**Failure Stakes**:
- Increased vessel anchorage wait times
- Underutilized quay crane capacity
- Costly manual dispatcher intervention errors
**Transformation**:
- **To**: the dispatcher who orchestrates autonomous terminal flow
- **From**: a dispatcher trapped in spreadsheet re-planning
**Controlling Idea**: Maritime quay assignment should be as dynamic as the vessels themselves.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every vessel delay, dispatchers struggle with manual berth re-planning. Spotterquay provides self-correcting quay assignment so terminals maximize utilization and eliminate anchorage wait times.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 870ebeeac1cd1939

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Self-correcting berth planning software for berth dispatchers at container terminals. Unlike manual spreadsheets and static TOS scheduling — quay slots update automatically based on real-time AIS vessel drift.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: bda8d637b33956ee

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Vessel schedules in Navis N4 fall apart as weather and speed shifts force hours of manual re-planning in spreadsheets.
Solution: Every vessel delay, dispatchers struggle with manual berth re-planning. Spotterquay provides self-correcting quay assignment so terminals maximize utilization and eliminate anchorage wait times.
Customer: berth dispatchers at container terminals
Unlike: manual spreadsheets and static TOS scheduling
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 19bd6ddd2fc367e2

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

**Pain**: Vessel schedules in Navis N4 fall apart as weather and speed shifts force hours of manual re-planning in spreadsheets.
**Metrics**: Target: The quay schedule stays perfectly synchronized with actual vessel arrivals, eliminating anchorage bottlenecks and maximizing crane throughput.
**Rendered**: Pain: Vessel schedules in Navis N4 fall apart as weather and speed shifts force hours of manual re-planning in spreadsheets.
Economic buyer: Terminal Operator
Metrics: Target: The quay schedule stays perfectly synchronized with actual vessel arrivals, eliminating anchorage bottlenecks and maximizing crane throughput.
Competition: manual spreadsheets and static TOS scheduling
**Mechanism**: spine-derived-v1
**Competition**: manual spreadsheets and static TOS scheduling
**Economic Buyer**: Terminal Operator
**Vocab Fingerprint**: c0a27040b206e79b

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Self-correcting berth planning software for berth dispatchers at container terminals

berth dispatchers at container terminals — Vessel schedules in Navis N4 fall apart as weather and speed shifts force hours of manual re-planning in spreadsheets. Every vessel delay, dispatchers struggle with manual berth re-planning. Spotterquay provides self-correcting quay assignment so terminals maximize utilization and eliminate anchorage wait times.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: d6227c23fc223040

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Self-correcting berth planning software. Every vessel delay, dispatchers struggle with manual berth re-planning. Spotterquay provides self-correcting quay assignment so terminals maximize utilization and eliminate anchorage wait times. Serves berth dispatchers at container terminals.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: ad42003d0b0814d8

## Neighborhood

### Candidate solutions

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

### What it offers

- [Quay Slot Engine](/Software/Quay_Slot_Engine) — offers · Software
- [Spatial Dispatch Agent](/Agents/Spatial_Dispatch_Agent) — offers · Agents
- [Cadence Dispatch](/Agents/Cadence_Dispatch) — offers · Agents

### Competitors

- [CyberLogitec OPUS](/Competitors/CyberLogitec_OPUS) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors
- [Tideworks Mainsail](/Competitors/Tideworks_Mainsail) — competes with · Competitors
- [Portchain](/Competitors/Portchain) — competes with · Competitors
- [Manual Spreadsheets](/Competitors/Manual_Spreadsheets) — competes with · Competitors
- [Manhattan Active WMS](/Competitors/Manhattan_Active_WMS) — competes with · Competitors
- [Manual Radio Dispatching](/Competitors/Manual_Radio_Dispatching) — competes with · Competitors
- [FourKites Yard Management](/Competitors/FourKites_Yard_Management) — competes with · Competitors
- [Blue Yonder WMS](/Competitors/Blue_Yonder_WMS) — competes with · Competitors
- [Motorola Two-Way Radios](/Competitors/Motorola_Two-Way_Radios) — competes with · Competitors
- [SAP EWM](/Competitors/SAP_EWM) — competes with · Competitors
- [FourKites](/Competitors/FourKites) — competes with · Competitors
- [Manual Radio Dispatch](/Competitors/Manual_Radio_Dispatch) — competes with · Competitors
- [Blue Yonder](/Competitors/Blue_Yonder) — competes with · Competitors

### Embodies

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

### Composed of

- [Forklift Routing Agent](/Agents/Forklift_Routing_Agent) — composes · Agents
- [Live Manifest API](/Agents/Live_Manifest_API) — composes · Agents
- [Spatial Routing Engine](/Agents/Spatial_Routing_Engine) — composes · Agents
- [Yard Telemetry Worker](/Agents/Yard_Telemetry_Worker) — composes · Agents
- [Throughput Dispatch Service](/Services/Throughput_Dispatch_Service) — composes · Services
- [Forklift Dispatch Agent](/Agents/Forklift_Dispatch_Agent) — composes · Agents
- [Floor Cadence Service](/Services/Floor_Cadence_Service) — composes · Services
- [Manifest Triage Agent](/Agents/Manifest_Triage_Agent) — composes · Agents
- [Yard Telemetry API](/Agents/Yard_Telemetry_API) — composes · Agents
- [Spatial Grid Engine](/Agents/Spatial_Grid_Engine) — composes · Agents

### Who it serves

- [Large-Scale 3PL & Cross-Docking Hub](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub) — serves · CompanyTypes

### Similar Startups

- [Managerquay](/Startups/Managerquay) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Baywharf](/Startups/Baywharf) — similar · Startups
- [Jointoptimaquay](/Startups/Jointoptimaquay) — similar · Startups
- [Portepoch](/Startups/Portepoch) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Acceleratedock](/Startups/Acceleratedock) — similar · Startups
- [Cornerstonedock](/Startups/Cornerstonedock) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Congestionyard](/Startups/Congestionyard) — similar · Startups
- [Autopilotdock](/Startups/Autopilotdock) — similar · Startups
- [Chronofxyard](/Startups/Chronofxyard) — similar · Startups
- [Crossyard](/Startups/Crossyard) — similar · Startups
- [Autonomywharf](/Startups/Autonomywharf) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Turnexpert](/Startups/Turnexpert) — similar · Startups
- [Logisticsyard](/Startups/Logisticsyard) — similar · Startups