# Autonomywharf

*/Startups/Autonomywharf*

## Startup Overview

This terminal operating software dynamically orchestrates autonomous yard truck assignments and routing for port and logistics facilities. It replaces static scheduling and manual radio dispatch with real-time, algorithmic container movement coordination. Terminal operators use the software to continuously match available autonomous vehicles with container pickup and drop-off queues based on immediate yard conditions.

Legacy terminal systems like Navis N4 and Octopi rely on centralized, top-down instruction sets and vendor-locked hardware environments. In contrast, this approach utilizes a completely decentralized task allocation model, pushing routing logic to individual autonomous units to prevent single-point bottlenecks. Because the architecture remains fully hardware-agnostic, operators deploy mixed fleets of yard tractors from multiple manufacturers under a single orchestration layer.

## Startup Founding Hypothesis

**Approach**: that dynamically orchestrates autonomous yard truck assignments and routing
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Octopi](/Competitors/Octopi)
- [manual radio dispatch](/Competitors/manual_radio_dispatch)
**Differentiator2x2**: hardware-agnostic and completely decentralized in its task allocation model

## Startup Solution Coordinate

**Solution**: [Decentralized Yard Dispatch](/Software/Decentralized_Yard_Dispatch)

## Startup Position2x2

```mermaid
quadrantChart
x-axis "Hardware-dependent" --> "Hardware-agnostic"
y-axis "Centralized allocation" --> "Decentralized allocation"
quadrant-1 "Swarm Autonomy"
quadrant-2 "Proprietary Swarm"
quadrant-3 "Legacy Lock-in"
quadrant-4 "Cloud Dispatch"
"Autonomywharf": [0.85, 0.85]
"Navis N4": [0.40, 0.20]
"Octopi": [0.70, 0.25]
"Manual radio dispatch": [0.95, 0.10]
```

## Startup Offer

**Proof**:
- Target: Mid-sized container terminal increasing continuous container moves per hour by 20%.
- Target: Inland logistics hub eliminating 90% of manual dispatch radio chatter.
- Target: Mixed-fleet port operation routing autonomous trucks alongside human drivers without routing conflicts.
**Tiers**:
- Name: Single Terminal · Price: ~$3,000–$6,000/mo base + ~$0.15–$0.30 per automated move · Inclusions: Up to 50 active yard trucks in one geographic terminal, decentralized task allocation engine, and standard TOS integration design.
- Name: Multi-Yard Hub · Price: ~$9,000–$18,000/mo base + ~$0.10–$0.20 per automated move · Inclusions: Unlimited yard trucks across up to 5 terminals, predictive staging logic, and intended API bridging for Octopi or Navis N4.
- Name: Enterprise Fleet · Price: custom: ~$150k–$250k/yr · Inclusions: Unlimited terminals, custom hardware profiles for mixed manual/autonomous fleets, and local edge-node deployment options.
**Guarantee**: If dynamic orchestration fails to reduce average yard truck idle time by at least 15% within the first 60 days of live deployment, Autonomywharf will refund all implementation fees and release the terminal from the contract.
**Business Function**: ProvideService
**Objection Handlers**:
- Our yard relies on Navis N4; we cannot replace it. -> Autonomywharf is designed to sit underneath your TOS, receiving master moves and purely optimizing the micro-level truck execution.
- We operate mixed hardware from different OEMs. -> The decentralized allocation model is completely hardware-agnostic, issuing standardized dispatch commands regardless of vehicle brand.
- Cloud latency is too high for port operations. -> Autonomywharf is designed to deploy local edge nodes, ensuring truck routing continues seamlessly even if external internet drops.
**Pricing Architecture**: Tiered

## Startup Brand

**Voice**: Direct logistical command register characterized by unyielding mechanical precision
**Tagline**: Maximize yard throughput with decentralized autonomous truck orchestration
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: The visual identity pairs high-visibility safety yellow and asphalt black with utilitarian typography to reflect the physical scale of terminal operations.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Autonomywharf → Terminal Operator → Autonomous Yard Truck Fleet
**Gtm Motion**: Acquires mid-sized logistics yards and port terminal operators via direct technical sales, positioning the routing platform as a lightweight, hardware-agnostic overlay to existing Terminal Operating Systems (TOS). Expands by scaling licensing fees per connected vehicle as operators transition from autonomous pilot programs to fully automated fleet deployments.
**Agent Channel**: Designed to list in open fleet management API directories and ROS (Robot Operating System) component registries, enabling third-party autonomous truck control systems to dynamically discover and subscribe to the decentralized task allocation feed.
**Primary Channel**: Direct outbound targeting Terminal Operations Directors and innovation leads, alongside visibility at specialized maritime logistics conferences (e.g., TOC Worldwide) when operators actively seek routing solutions to unblock autonomous truck pilot bottlenecks.

## Startup Customer Journey

```mermaid
flowchart LR
A[Maritime Logistics Conference] --> B[Terminal Operating System]
B --> C[Single Terminal Pilot]
C --> D[Task Allocation Engine]
D --> E[Multi-Yard Hub]
E --> F[Innovation Lead]
```

## Startup Proof Points

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

**Pilot Goals**:
- 60-day single-terminal pilot with up to 50 active yard trucks: Aims to validate a minimum 15% reduction in average idle time to trigger the performance guarantee
- 90-day edge-node deployment test at a high-latency coastal port: Aims to prove zero routing interruptions during simulated external cloud connectivity drops
- 30-day API bridging pilot in an Octopi TOS environment: Aims to demonstrate the seamless translation of TOS master moves into automated micro-level truck execution
**Target Metrics**:
- Target: 15% reduction in average yard truck idle time
- Aim: 90% decrease in manual dispatch radio communications
- Target: 20% increase in continuous container moves per hour
- Aim: Zero routing conflicts between human-driven and autonomous hardware
**Target Case Studies**:
- Target: A mid-sized coastal container terminal utilizing Autonomywharf to increase continuous container moves per hour by 20% without purchasing additional yard trucks
- Target: An inland logistics hub relying on Autonomywharf's decentralized allocation engine to eliminate 90% of manual dispatch radio chatter
- Target: A mixed-fleet port operation orchestrating autonomous trucks alongside human drivers to achieve zero routing conflicts during peak throughput
**Testimonial Targets**:
- Terminal Operations Director: Expresses relief that the platform sits seamlessly underneath their existing Navis N4 TOS without requiring an operational overhaul
- Dispatch Manager: Praises the decentralized allocation model for entirely removing the cognitive load of manual radio dispatching
- VP of Port Logistics: Highlights the reliability of the local edge nodes, confirming that truck routing continues seamlessly even during external internet drops

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Legacy Terminal Operating Systems restrict API access to real-time container inventory and gate events, rendering the orchestration platform blind to freight locations. · Mitigation Status: unmitigated
- Severity: high · Description: Autonomous yard truck manufacturers refuse to open their drive-by-wire command APIs to third-party software, preventing the platform from achieving hardware-agnostic control. · Mitigation Status: in-progress
- Severity: high · Description: The decentralized task allocation model triggers routing deadlocks at high-density terminal choke points where traditional centralized traffic lights govern right-of-way. · Mitigation Status: in-progress
- Severity: moderate · Description: Longshoreman unions negotiate strict port contract clauses that explicitly ban or significantly cap the daily deployment of autonomous yard trucks at key maritime terminals. · Mitigation Status: unmitigated

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Incumbent TOS
- [Octopi](/Competitors/Octopi) — Cloud TOS
- [Manual Radio Dispatch](/Competitors/Manual_Radio_Dispatch) — Status Quo
- [Outrider](/Competitors/Outrider) — Integrated Yard Autonomy
- [Phantom Auto](/Competitors/Phantom_Auto) — Remote Operation
- [Zebra MotionWorks](/Competitors/Zebra_MotionWorks) — Yard Management System

## Startup Solution Stack

- [Decentralized Dispatch Service](/Services/Decentralized_Dispatch_Service) — Service-as-Software
- [Route Assignment Agent](/Agents/Route_Assignment_Agent) — Agent
- [Task Allocation Worker](/Agents/Task_Allocation_Worker) — Agent
- [Dynamic Routing Engine](/Software/Dynamic_Routing_Engine) — Software
- [Hardware Telemetry API](/Software/Hardware_Telemetry_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the strategic architect of a high-velocity terminal, not a manual dispatcher
- **Want**: to maximize container moves per hour without increasing yard congestion
- **Identity**: the terminal manager at a high-volume container port
**Plan**:
- Step: Input · Detail: Define your terminal layout and active yard truck fleet parameters.
- Step: Verify · Detail: Review the live move-request stream from your Octopi or Navis N4 TOS.
- Step: Execute · Detail: Release autonomous move commands to the fleet for optimized staging and retrieval.
**Guide**:
- **Empathy**: Does your yard staging still suffer from bottlenecked quay cranes due to dispatch delays?
**Problem**:
- **Villain**: manual radio dispatch
- **External**: Static move requests in Navis N4 result in yard truck idle time and bottlenecked quay cranes.
- **Internal**: You feel like you are fighting a losing battle against yard gridlock and inefficient fuel burn.
- **Philosophical**: Every logistics hub deserves autonomous precision — not the friction of human-in-the-loop routing.
**Success**: Yard truck idle time drops by 15% as decentralized routing synchronizes every container move in real-time.
**One Liner**: Manual radio dispatch costs terminal managers container throughput. Autonomywharf orchestrates autonomous yard truck assignments so terminals maximize moves per hour without congestion.
**Positioning**:
- **So That**: increase container moves per hour while reducing truck idle time
- **Unlike**: manual radio dispatch or static TOS queues
- **For Whom**: the terminal manager at a container port
- **Category**: Autonomous yard truck orchestration
**Call To Action**:
- **Direct**: Launch yard orchestration
- **Transitional**: Terminal deployment schema
**Failure Stakes**:
- Quay crane downtime
- Compounded yard congestion
- Excessive fuel consumption
**Transformation**:
- **To**: orchestrating autonomous terminal velocity instead of managing manual move bottlenecks
- **From**: a dispatcher reactive to radio chatter and static Navis queues
**Controlling Idea**: Yard truck orchestration must be decentralized to eliminate terminal bottlenecks.

## Startup Story Brand V2

**Hero**:
- **Want**: to take on more fixed-fee clients without hiring more preparers
- **Identity**: the managing partner at a regional accounting firm
**Plan**:
- Step: Upload documents · Detail: Drop unstructured K-1s, 1099s, and bank statements into the secure engagement folder.
- Step: Review staged entries · Detail: Approve the normalized, source-linked values before anything posts to UltraTax or CCH Axcess.
- Step: Accept more clients · Detail: Price the next engagement fixed-fee, knowing preparation no longer scales with headcount.
**Problem**:
- **Villain**: the billable hour treadmill
- **External**: Senior CPAs spend tax season rekeying K-1s and bank statements into CCH Axcess, so revenue stalls at whatever hours the team can bill.
- **Internal**: You feel like a headcount manager instead of an advisor, watching margin erode every time growth demands another hire you cannot find.
- **Philosophical**: A firm's earnings deserve to track the judgment it sells, not the keystrokes it performs; expertise priced by the hour is expertise capped.
**Success**: Your firm takes on new fixed-fee entities without adding preparers. CPAs review staged entries instead of keying them, and margins hold as the client list grows.
**One Liner**: Manual data entry keeps accounting firms priced by the hour. Autonomywharf turns messy client documents into review-ready, source-linked entries for UltraTax and CCH Axcess, so firms grow fixed-fee revenue without growing headcount.
**Call To Action**:
- **Direct**: Upload a K-1 batch
- **Transitional**: Download filing timeline
**Failure Stakes**:
- Another tax season lost to rekeying instead of advisory work
- Fixed-fee engagements that quietly overrun their budgeted hours
- Growth capped by preparers you cannot hire fast enough

## Startup Landing Hero Services V2

**Eyebrow**: Autonomous ledger reconciliation
**Subhead**: Normalized K-1 and bank statement data lands in UltraTax staged for your senior review.
**Headline**: Client ledgers reconciled overnight
**Supporting Proof**: Designed for direct import into CCH Axcess and UltraTax

## Startup Landing Problem V2

**Cards**:
- Body: Every busy season starts with recruiting, training, and reviewing temporary staff whose keying errors surface in April, when there is no time left to fix them. · Cost: $50k per seasonal hire · Heading: Hiring seasonal preparers · Outcome: Gone by May, retrained every January.
- Body: Offshore teams still bill by the hour and still key blind into CCH Axcess; review burden lands on your seniors, and confidentiality questions follow every engagement letter. · Cost: $12–18 per hour · Heading: Offshoring the data entry · Outcome: Cheaper hours, same hour ceiling.
- Body: Karbon and Xero Practice Manager schedule and time the work beautifully, but the K-1 still gets keyed by a person, so the engagement's cost floor never moves. · Cost: $59 per user monthly · Heading: Buying practice management software · Outcome: Tracks the hours, does none.
**Eyebrow**: The ceiling today
**Section Heading**: Your revenue is capped at the hours you can bill

## Startup Landing Solution V2

**Section Heading**: From billed hours to delivered ledgers
**Solution Statement**: Autonomywharf is an autonomous ledger reconciliation service for accounting firms. It reads unstructured client documents, normalizes every value into review-ready entries, and stages them for import into UltraTax or CCH Axcess with a source link on each number.

## Startup Landing Pricing V2

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

**Tiers**:
- Name: Starter · Model: flat · Cadence: mo · Recommended: false · Audience Tagline: Solo partners staging their first hundred documents monthly
- Name: Growth · Model: flat · Cadence: mo · Recommended: true · Audience Tagline: Firms moving whole CAS books onto fixed-fee pricing
- Name: Scale · Model: flat · Cadence: mo · Recommended: false · Audience Tagline: Multi-office practices with entity-heavy tax seasons
**Group Hint**: 2
**Section Heading**: Autonomous preparation for the whole client list

## Startup Landing Faq V2

**Faqs**:
- Answer: That is the core of the service. The extraction engine is built for unformatted, poorly scanned financial documents rather than clean templates. Values read with high confidence are staged for review; anything ambiguous lands in the exception queue for a person to resolve instead of being guessed into the return. · Question: Can it read our clients' messy scanned PDFs?
- Answer: Every staged entry links to the exact page it came from, so a reviewer can check any number in seconds. Corrections happen in the review queue before posting, and each correction tunes the firm's own extraction profile so the same document type reads better next time. · Question: What happens when a value is extracted wrong?
- Answer: No. Autonomywharf is designed to sit in front of the tax software the firm already runs, producing import-ready files for CCH Axcess and UltraTax. Reviewers keep working where they already work; there is no new ledger to migrate and no parallel system to maintain. · Question: Do we have to leave CCH Axcess or UltraTax?
- Answer: Documents live in the firm's engagement workspace and are used only to produce that firm's entries. The service takes no write access to tax software, nothing posts without a named CPA's approval, documents are deleted on request, and client files are never used to train shared models. · Question: How is client financial data protected?
- Answer: Plans are flat monthly fees sized by document volume, so busy season does not multiply the bill the way hourly staffing does. If a season exceeds the plan's volume, overflow processes at the next tier's terms rather than stopping mid-engagement. Predictable cost is the point of moving off the hour. · Question: How does pricing work at busy-season volume?
- Answer: Yes. Plans run month to month, and a firm can drop to Starter or pause once the April rush passes. Documents, staged entries, and the audit trail export in open formats before the workspace closes, so nothing about the season's work stays locked inside the service. · Question: Can I cancel after tax season ends?
**Eyebrow**: Before you upload
**Section Heading**: Questions managing partners ask first

## Startup Landing Final Cta V2

**Eyebrow**: The first engagement
**Heading**: Upload your first K-1 batch
**Subhead**: Staged, source-linked entries land in your review queue; nothing posts until a CPA approves.
**Reassurance**: Month to month, exports anytime, no write access to the firm's tax software

## Startup Landing Objection

**Coverage**:
- **Dimension**: Document types
- **Expansion Note**: New document types are added by building and testing an extraction profile against real samples, one type at a time.
**Objection**: Will the IRS or a peer review accept numbers my staff never keyed?
**Data Handling**:
- **Residency**: Documents stay in the firm's engagement workspace, deleted on request.
- **What We Never**: No write access to the firm's tax software; nothing posts without a named CPA's approval.
- **What We Touch**: Client tax documents, bank and brokerage statements, and the ledger entries staged from them.
**Honest Answer**: The firm still signs; Autonomywharf only stages. Every extracted value is designed to carry a link to the exact page and coordinate of its source document, so a reviewer can verify any number in seconds. Nothing posts to UltraTax or CCH Axcess until a CPA approves the mapping.
**Residual Risk**: Acceptance in formal peer review is untested; the audit trail is the founding bet, not a precedent.
**Mechanism Detail**: Approval is per engagement: a senior reviews the staged entries, confirms or corrects low-confidence fields, and each correction tunes the firm's own extraction profile.

## Startup Landing What You Get

**Items**:
- Icon: document · Item: Normalized K-1 extractions · Detail: Every partner item is parsed from the source PDF and typed to the right field before review.
- Icon: check · Item: Reconciled client ledgers · Detail: Bank and brokerage activity is matched to the ledger, with unmatched items flagged for a person.
- Icon: package · Item: UltraTax and CCH import files · Detail: Entries arrive formatted for the tax software the firm already runs, ready to post after approval.
- Icon: shield · Item: Source-linked audit trail · Detail: Each number carries a link to the exact page and coordinate of the document it came from.
- Icon: alert · Item: Exception queue · Detail: Low-confidence values wait in one place for senior judgment instead of hiding in the return.
- Icon: clock · Item: Engagement status timeline · Detail: A running record shows every document from intake to posted entry, per client and per filing.
**Eyebrow**: In your review queue
**Section Heading**: The artifacts that replace the keying

## Startup Landing Defensibility

**Caveat**: Autonomywharf prepares and stages entries; it does not sign returns, issue opinions, or replace CPA judgment. Extraction is built for legible documents, and anything ambiguous routes to the firm's reviewers rather than posting on its own.
**Suited For**:
- Regional firms of 1–50 staff on CCH Axcess or UltraTax
- Practices moving tax and CAS work to fixed fees
- Partners drowning in K-1-heavy entity returns
**Not Suited For**:
- Solo preparers with a handful of simple 1040s
- Firms wanting audit opinions or signed filings done for them
- Shops that refuse a review step before posting

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Manual radio dispatch costs terminal managers container throughput. Autonomywharf orchestrates autonomous yard truck assignments so terminals maximize moves per hour without congestion.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 204a641807235f3d

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Autonomous yard truck orchestration for the terminal manager at a container port. Unlike manual radio dispatch or static TOS queues — increase container moves per hour while reducing truck idle time.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 9204a1bc8939433a

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Static move requests in Navis N4 result in yard truck idle time and bottlenecked quay cranes.
Solution: Manual radio dispatch costs terminal managers container throughput. Autonomywharf orchestrates autonomous yard truck assignments so terminals maximize moves per hour without congestion.
Customer: the terminal manager at a container port
Unlike: manual radio dispatch or static TOS queues
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 128728484488a759

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

**Pain**: Static move requests in Navis N4 result in yard truck idle time and bottlenecked quay cranes.
**Metrics**: Target: Yard truck idle time drops by 15% as decentralized routing synchronizes every container move in real-time.
**Rendered**: Pain: Static move requests in Navis N4 result in yard truck idle time and bottlenecked quay cranes.
Economic buyer: Terminal Operator
Metrics: Target: Yard truck idle time drops by 15% as decentralized routing synchronizes every container move in real-time.
Competition: manual radio dispatch or static TOS queues
**Mechanism**: spine-derived-v1
**Competition**: manual radio dispatch or static TOS queues
**Economic Buyer**: Terminal Operator
**Vocab Fingerprint**: c68a3d9422f2e02d

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Autonomous yard truck orchestration for the terminal manager at a container port

the terminal manager at a container port — Static move requests in Navis N4 result in yard truck idle time and bottlenecked quay cranes. Manual radio dispatch costs terminal managers container throughput. Autonomywharf orchestrates autonomous yard truck assignments so terminals maximize moves per hour without congestion.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 9188274d7d306052

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Autonomous yard truck orchestration. Manual radio dispatch costs terminal managers container throughput. Autonomywharf orchestrates autonomous yard truck assignments so terminals maximize moves per hour without congestion. Serves the terminal manager at a container port.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: b22d5195d0b06c03

## Neighborhood

### Candidate solutions

- [Billable Hour Revenue Ceilings](/Problems/Billable_Hour_Revenue_Ceilings) — candidate solution for · Problems

### Composed of

- [Tax collation](/Services/Tax_collation) — composes · Services
- [Autonomous Compliance Service](/Services/Autonomous_Compliance_Service) — composes · Services
- [Regulatory Logic Engine](/Software/Regulatory_Logic_Engine) — composes · Software
- [Tax System Integration API](/Software/Tax_System_Integration_API) — composes · Software
- [Ledger Reconciliation Agent](/Agents/Ledger_Reconciliation_Agent) — composes · Agents
- [Unstructured Document Extraction Worker](/Agents/Unstructured_Document_Extraction_Worker) — composes · Agents
- [Compliance Logic Engine](/Software/Compliance_Logic_Engine) — composes · Software
- [Format Normalization API](/Software/Format_Normalization_API) — composes · Software
- [Document Extraction Worker](/Agents/Document_Extraction_Worker) — composes · Agents
- [Hardware Telemetry API](/Software/Hardware_Telemetry_API) — composes · Software
- [Dynamic Routing Engine](/Software/Dynamic_Routing_Engine) — composes · Software
- [Route Assignment Agent](/Agents/Route_Assignment_Agent) — composes · Agents
- [Decentralized Dispatch Service](/Services/Decentralized_Dispatch_Service) — composes · Services
- [Task Allocation Worker](/Agents/Task_Allocation_Worker) — composes · Agents

### What it offers

- [Yield Vault](/Services/Yield_Vault) — offers · Services
- [Decentralized Yard Dispatch](/Software/Decentralized_Yard_Dispatch) — offers · Software
- [Ledger Bridge](/Agents/Ledger_Bridge) — offers · Agents

### Embodies

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

### Competitors

- [CCH Axcess Practice](/Competitors/CCH_Axcess_Practice) — competes with · Competitors
- [Xero Practice Manager](/Competitors/Xero_Practice_Manager) — competes with · Competitors
- [Offshore Accounting Staff](/Competitors/Offshore_Accounting_Staff) — competes with · Competitors
- [QuickBooks Time](/Competitors/QuickBooks_Time) — competes with · Competitors
- [Offshore Staffing Agencies](/Competitors/Offshore_Staffing_Agencies) — competes with · Competitors
- [Karbon](/Competitors/Karbon) — competes with · Competitors
- [Offshore Accounting Firms](/Competitors/Offshore_Accounting_Firms) — competes with · Competitors
- [Offshore Junior Accountants](/Competitors/Offshore_Junior_Accountants) — competes with · Competitors
- [Offshore Accounting Teams](/Competitors/Offshore_Accounting_Teams) — competes with · Competitors
- [Offshore Staffing](/Competitors/Offshore_Staffing) — competes with · Competitors
- [Offshore Junior Staff](/Competitors/Offshore_Junior_Staff) — competes with · Competitors
- [Offshore Accounting Agencies](/Competitors/Offshore_Accounting_Agencies) — competes with · Competitors
- [Zebra MotionWorks](/Competitors/Zebra_MotionWorks) — competes with · Competitors
- [Phantom Auto](/Competitors/Phantom_Auto) — competes with · Competitors
- [Outrider](/Competitors/Outrider) — competes with · Competitors
- [Manual Radio Dispatch](/Competitors/Manual_Radio_Dispatch) — competes with · Competitors
- [Octopi](/Competitors/Octopi) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors

### Who it serves

- [Accounting Firm](/CompanyTypes/Accounting_Firm) — serves · CompanyTypes

### Similar Startups

- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Logisticsyard](/Startups/Logisticsyard) — similar · Startups
- [Floorsensepost](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Floorsensepost) — similar · Startups
- [Adjectival](/CompanyTypes/Terminal_Handling_Contractor/Startups/Adjectival) — similar · Startups
- [Spottercenter](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Spottercenter) — similar · Startups
- [Aeroverge](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Aeroverge) — similar · Startups
- [Basisyard](/Startups/Basisyard) — similar · Startups
- [Dynamicfuel](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Dynamicfuel) — similar · Startups
- [Etyard](/Startups/Etyard) — similar · Startups
- [Portepoch](/Startups/Portepoch) — similar · Startups
- [Coordinatorfoundry](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Coordinatorfoundry) — similar · Startups
- [Flowfield](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Flowfield) — similar · Startups
- [Depotport](/Startups/Depotport) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Stabilityard](/Startups/Stabilityard) — similar · Startups
- [Flowtower](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Flowtower) — similar · Startups
- [Activeshade](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Activeshade) — similar · Startups
- [Cadencehue](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Cadencehue) — similar · Startups