# Managerquay

*/Startups/Managerquay*

## Startup Overview

This platform dynamically allocates port berth schedules by processing live vessel telemetry. Instead of relying on static estimated times of arrival, it adjusts mooring assignments in real time based on actual ship speed, heading, and localized maritime conditions.

Port operators handling bulk cargo face constant scheduling collisions due to unpredictable arrival windows and shifting logistics. The system eliminates the idle waiting times and demurrage fees caused by ships queuing for unavailable docks. By continuously recalculating arrival timelines, terminal managers slot incoming vessels into the exact right berth sequence without manual intervention.

Unlike legacy terminal operating systems such as Navis N4 and Tideworks, or rigid spreadsheet schedules, this architecture is structurally adapted for the extreme volatility of bulk shipping. It operates on an outcome-priced model, aligning platform costs directly with the reduction of vessel turnaround times rather than charging flat software licenses.

## Startup Founding Hypothesis

**Approach**: that dynamically allocates berth schedules using live vessel telemetry
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Tideworks](/Competitors/Tideworks)
- [static spreadsheet schedules](/Competitors/static_spreadsheet_schedules)
**Differentiator2x2**: outcome-priced and structurally adapted for unpredictable bulk cargo arrivals

## Startup Solution Coordinate

**Solution**: [Dynamic Berth Allocator](/Services/Dynamic_Berth_Allocator)

## Startup Position2x2

```mermaid
quadrantChart
title Berth Allocation Positioning
x-axis "Fixed License Cost" --> "Outcome-Priced"
y-axis "Static Container Focus" --> "Dynamic Bulk Adaptation"
quadrant-1 "Dynamic Value"
quadrant-2 "Premium Adaptable"
quadrant-3 "Legacy Static"
quadrant-4 "Commodity Static"
"Navis N4": [0.15, 0.25]
"Tideworks": [0.20, 0.35]
"Spreadsheet Schedules": [0.10, 0.10]
"Managerquay": [0.85, 0.90]
```

## Startup Offer

**Proof**:
- Aim to reduce anchorage idle time by 15% for incoming bulk carriers
- Target zero manual spreadsheet updates during sudden weather delays
- Target a 20% reduction in total demurrage penalties across volatile cargo arrivals
**Tiers**:
- Name: Regional Port · Price: ~$150–$300 per vessel arrival · Inclusions: Dynamic berth scheduling for up to 2 active bulk terminals, live AIS telemetry ingestion, and daily turnaround reporting.
- Name: Major Terminal · Price: ~$400–$800 per vessel arrival · Inclusions: Scheduling for up to 6 berths, continuous automated queue readjustment, intended integration with existing Terminal Operating Systems (e.g., Navis N4), and demurrage risk alerting.
- Name: Authority Network · Price: Custom quote: ~$10k–$25k/mo baseline + usage · Inclusions: Multi-terminal scheduling oversight, custom telemetry pipelines, fleet-wide delay modeling, and dedicated engineering support for complex bulk cargo variations.
**Guarantee**: If Managerquay fails to reduce a scheduled vessel's anchorage wait time below your historical 90-day baseline for that cargo type, the scheduling fee for that specific vessel call is waived.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: 'We already use Navis N4 for our terminal operations.' Rebuttal: Managerquay is designed to handle the volatile front-end of bulk berth scheduling via API, feeding a finalized, stable queue directly into your existing TOS.
- Objection: 'Live AIS telemetry is too noisy to drive an automated schedule.' Rebuttal: The platform filters raw AIS signals through predictive transit models to remove false coordinates and normalize arrival windows before updating the queue.
- Objection: 'Bulk loading times fluctuate too much to predict departures.' Rebuttal: When a current vessel exceeds its estimated completion block, the system automatically runs reallocation scenarios for incoming ships and proposes the least disruptive alternative berth.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol
- stored-credential

## Startup Brand

**Voice**: Authoritative maritime register grounded in immediate logistical facts.
**Tagline**: Dynamic berth allocation driven by live vessel telemetry.
**Icon Concept**: bollard
**Palette Intent**: industrial-safety
**Visual Identity**: High-visibility safety yellow and tarmac black anchor heavy, stenciled typography to reflect the physical reality of bulk cargo terminals.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Managerquay → Bulk Terminal Operator → Shipping Line
**Gtm Motion**: Acquires initial bulk cargo terminals through pilot agreements structured around demurrage reduction, expanding port-wide as telemetry-driven scheduling proves out higher berth utilization.
**Agent Channel**: Intended to list its scheduling webhook in Port Community System (PCS) integration directories and maritime AI capability registries so autonomous supply chain agents can directly query berth availability.
**Primary Channel**: Direct outbound targeting Port Operations Directors and Harbormasters via industry-specific networks and maritime logistics conferences like TOC Worldwide.

## Startup Customer Journey

```mermaid
flowchart LR; A[TOC Worldwide Conference] --> B[Demurrage Reduction Pilot]; B --> C[Live AIS Telemetry]; C --> D[Dynamic Berth Schedule]; D --> E[Navis N4 API]; E --> F[Authority Network Platform]; F --> G[Port Community System];
```

## 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 shadow pilot at a regional bulk terminal running Managerquay alongside legacy spreadsheets to prove a 15% reduction in projected anchorage idle time.
- 60-day integration pilot at a major terminal to validate clean API handoffs of finalized queues into their existing Terminal Operating System without manual data entry.
**Target Metrics**:
- Target: 15% reduction in anchorage idle time for incoming bulk carriers
- Target: 20% reduction in total demurrage penalties across volatile cargo arrivals
- Aim: Zero manual spreadsheet updates required during sudden weather delays
- Target: 100% automated generation of reallocation scenarios when a vessel exceeds its loading block
**Target Case Studies**:
- Target: A regional bulk terminal transitioning from static spreadsheet scheduling to dynamic AIS-driven queues, aiming to eliminate manual schedule rebuilds during sudden weather delays.
- Target: A major multi-berth port authority integrating front-end scheduling volatility with their existing Terminal Operating System to reduce fleet-wide demurrage risks.
- Target: A private bulk export facility utilizing continuous automated queue readjustment to minimize anchorage wait times when cargo loading durations fluctuate.
**Testimonial Targets**:
- Port Operations Manager expressing relief that sudden weather delays trigger automatic reallocation scenarios instead of requiring hours of manual spreadsheet updates.
- Terminal Director validating that the predictive transit models successfully filter noisy AIS signals into stable, trustworthy arrival windows.
- Commercial Director highlighting the financial impact of feeding a stable, finalized queue directly into their existing TOS, lowering overall demurrage payouts.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Legacy Terminal Operating Systems like Navis N4 block API access, preventing the platform from executing live berth schedule updates. · Mitigation Status: in-progress
- Severity: high · Description: Customers dispute outcome-based pricing fees by blaming pilot shortages or labor strikes for delays instead of scheduling inefficiencies. · Mitigation Status: unmitigated
- Severity: high · Description: State-owned port authorities enforce multi-year procurement cycles that drain capital runway before the first commercial deployment goes live. · Mitigation Status: unmitigated
- Severity: moderate · Description: Live vessel AIS telemetry experiences latency near crowded anchorages, causing the allocation algorithm to incorrectly sequence inbound bulk carriers. · Mitigation Status: in-progress

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Incumbent
- [Tideworks](/Competitors/Tideworks) — Legacy Platform
- [Static Spreadsheet Schedules](/Competitors/Static_Spreadsheet_Schedules) — Status Quo
- [Portchain](/Competitors/Portchain) — Berth Optimization
- [Awake AI](/Competitors/Awake_AI) — Smart Port Platform

## Startup Solution Stack

- [Berth Allocation Service](/Services/Berth_Allocation_Service) — Service-as-Software
- [Vessel Telemetry Agent](/Agents/Vessel_Telemetry_Agent) — Agent
- [Schedule Optimization Worker](/Agents/Schedule_Optimization_Worker) — Agent
- [Bulk Cargo Arrival Engine](/Software/Bulk_Cargo_Arrival_Engine) — Software
- [Berth Matrix API](/Software/Berth_Matrix_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the logistics lead who masters unpredictable arrivals rather than reacting to them
- **Want**: to minimize vessel anchorage wait times and maximize berth utilization
- **Identity**: the terminal manager at a bulk cargo port
**Plan**:
- Step: Input parameters · Detail: Define your berth constraints and typical loading rates for specific bulk cargo types.
- Step: Approve sequence · Detail: Review the telemetry-driven queue and accept the optimized arrival order for incoming vessels.
- Step: Sync terminal · Detail: Push the finalized schedule to your existing TOS to coordinate stevedores and shore cranes.
**Guide**:
- **Empathy**: You shouldn't still be manually re-calculating queues when weather shifts. Navis N4 wasn't built to dynamically re-allocate berths based on live AIS telemetry.
**Problem**:
- **Villain**: static spreadsheet schedules
- **External**: Managing arrivals in Navis N4 requires constant manual overrides as bulk carriers drift from their estimated arrival times on Excel trackers.
- **Internal**: You feel like a dispatcher in a crisis, constantly apologizing to agents for anchorage delays you couldn't predict.
- **Philosophical**: Marine expertise belongs in moving cargo, not in endlessly re-keying vessel ETA data.
**Success**: Vessels move directly from sea to berth with zero manual spreadsheet updates, even during weather delays.
**One Liner**: What if your berth schedule updated itself as ships moved? Managerquay uses live vessel telemetry to automate berth allocation, reducing anchorage idle time and demurrage costs.
**Positioning**:
- **So That**: reduce vessel anchorage wait times through live telemetry
- **Unlike**: static spreadsheet schedules
- **For Whom**: terminal managers at bulk cargo ports
- **Category**: Dynamic berth allocation software
**Call To Action**:
- **Direct**: Schedule a vessel
- **Transitional**: View arrival telemetry dashboard
**Failure Stakes**:
- Rising demurrage penalties
- Underutilized crane teams
- Congested anchorage zones
**Transformation**:
- **To**: the port lead who orchestrates a high-velocity bulk terminal
- **From**: a dispatcher buried in vessel arrival spreadsheets
**Controlling Idea**: Live vessel telemetry should dictate the berth schedule, not manual data entry.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if your berth schedule updated itself as ships moved? Managerquay uses live vessel telemetry to automate berth allocation, reducing anchorage idle time and demurrage costs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 5d2d50959a0bcdde

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Dynamic berth allocation software for terminal managers at bulk cargo ports. Unlike static spreadsheet schedules — reduce vessel anchorage wait times through live telemetry.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 0e51d394469cfb94

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Managing arrivals in Navis N4 requires constant manual overrides as bulk carriers drift from their estimated arrival times on Excel trackers.
Solution: What if your berth schedule updated itself as ships moved? Managerquay uses live vessel telemetry to automate berth allocation, reducing anchorage idle time and demurrage costs.
Customer: terminal managers at bulk cargo ports
Unlike: static spreadsheet schedules
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 3b55169d39440361

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

**Pain**: Managing arrivals in Navis N4 requires constant manual overrides as bulk carriers drift from their estimated arrival times on Excel trackers.
**Metrics**: Target: Vessels move directly from sea to berth with zero manual spreadsheet updates, even during weather delays.
**Rendered**: Pain: Managing arrivals in Navis N4 requires constant manual overrides as bulk carriers drift from their estimated arrival times on Excel trackers.
Economic buyer: Bulk Terminal Operator
Metrics: Target: Vessels move directly from sea to berth with zero manual spreadsheet updates, even during weather delays.
Competition: static spreadsheet schedules
**Mechanism**: spine-derived-v1
**Competition**: static spreadsheet schedules
**Economic Buyer**: Bulk Terminal Operator
**Vocab Fingerprint**: 1bd798f5289d707e

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Dynamic berth allocation software for terminal managers at bulk cargo ports

terminal managers at bulk cargo ports — Managing arrivals in Navis N4 requires constant manual overrides as bulk carriers drift from their estimated arrival times on Excel trackers. What if your berth schedule updated itself as ships moved? Managerquay uses live vessel telemetry to automate berth allocation, reducing anchorage idle time and demurrage costs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 5f1a700ea681f17e

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Dynamic berth allocation software. What if your berth schedule updated itself as ships moved? Managerquay uses live vessel telemetry to automate berth allocation, reducing anchorage idle time and demurrage costs. Serves terminal managers at bulk cargo ports.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 862084b5a8c9cb8b

## Neighborhood

### Candidate solutions

- [LARC Inventory Spoilage](/Problems/LARC_Inventory_Spoilage) — candidate solution for · Problems
- [Showroom Sample Loss](/Problems/Showroom_Sample_Loss) — candidate solution for · Problems
- [Cross-Dock Throughput Bottlenecks](/Problems/Cross-Dock_Throughput_Bottlenecks) — candidate solution for · Problems
- [Unproven Style Dead Stock](/Problems/Unproven_Style_Dead_Stock) — candidate solution for · Problems
- [Specialized Floor Staff Recruitment](/Problems/Specialized_Floor_Staff_Recruitment) — candidate solution for · Problems

### Composed of

- [Berth Allocation Service](/Services/Berth_Allocation_Service) — composes · Services
- [Vessel Telemetry Agent](/Agents/Vessel_Telemetry_Agent) — composes · Agents
- [Schedule Optimization Worker](/Agents/Schedule_Optimization_Worker) — composes · Agents
- [Bulk Cargo Arrival Engine](/Software/Bulk_Cargo_Arrival_Engine) — composes · Software
- [Berth Matrix API](/Software/Berth_Matrix_API) — composes · Software

### Embodies

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

### What it offers

- [Dynamic Berth Allocator](/Services/Dynamic_Berth_Allocator) — offers · Services

### Competitors

- [Static Spreadsheet Schedules](/Competitors/Static_Spreadsheet_Schedules) — competes with · Competitors
- [Portchain](/Competitors/Portchain) — competes with · Competitors
- [Awake AI](/Competitors/Awake_AI) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors
- [Tideworks](/Competitors/Tideworks) — competes with · Competitors

### Similar Startups

- [Baywharf](/Startups/Baywharf) — similar · Startups
- [Spotterquay](/Startups/Spotterquay) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Portepoch](/Startups/Portepoch) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Jointoptimaquay](/Startups/Jointoptimaquay) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Acceleratedock](/Startups/Acceleratedock) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Cornerstonedock](/Startups/Cornerstonedock) — similar · Startups
- [Autopilotdock](/Startups/Autopilotdock) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Agriculturalharbor](/Startups/Agriculturalharbor) — similar · Startups
- [Crossyard](/Startups/Crossyard) — similar · Startups
- [Chronofxyard](/Startups/Chronofxyard) — similar · Startups
- [Congestionyard](/Startups/Congestionyard) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Autarrival](/Startups/Autarrival) — similar · Startups
- [Baarrival](/Startups/Baarrival) — similar · Startups