Owners & Operators

Walk in to a clean vessel board,
not a full inbox.

Your operations mailboxes fill all night with noon reports, port updates, master itineraries, and agent mail. Your agent has already read all of it. You sit down to one vessel-first board on WhatsApp, conflicts first, every figure sourced.

Overnight scan
Live · Local
Reading mailboxes
0 emails
VesselNext portETA · sourceROBWatch
MV MERIDIANSingapore16 May 2000 LTmasterVLSFO 338Clean
MV HALCYONAlgeciras13 May 1200 LTagentVLSFO 74Bunker after ops
MV ODYSSEADischarge berth14 May 1800 LTterminalVLSFO 364Draft +0.20 m over max
MV AURORARotterdam18 May PMmasterVLSFO 309Cleaning window
MV KESTRELCanal transit06 Jun 1400 LTagentVLSFO 575Slot deadline
Mac Mini · Local · No cloud

This is office software, not vessel software. The agent runs at your shore-side desk and reads your operations mail. It has no connection to navigation, the engine room, or vessel sensors. It automates the desk, not the bridge.

What it watches

Everything that hits the desk overnight, read and ranked

It reads thousands of emails a day across the fleet and keeps the moving parts in one place, so the picture is current the moment you ask.

Vessel board & next open port

One source-backed board: every ship, current and next port, present and forward employment, prepared before the morning call.

ETA / ETB / ETC / ETD cross-check

Every timing carries its source role, master, agent, or terminal. The same ETA means something different depending on who sent it. Conflicts first.

ROB & bunkers

Remaining on board, next bunkering, grades and price when known, tracked per vessel across the fleet.

Performance vs CP basis

Actual noon consumption normalized and checked against the charter party or TC fuel sheet. ECA split, main engine versus auxiliary, the gap highlighted.

Delay & detention causation

Who caused what: vessel, charterer, terminal, weather, documents, or agent. Source-backed port-event timelines, not a thread to scroll.

Operator KPIs

Communication efficiency and bottlenecks across the desk, built from your own ops mail. A management view no inbox gives you.

Source · Math · Answer

Every number shows its work

The same ETA means something different from the master than from the agent. So every timing and figure comes with its source, the math, and the answer. Ask to see the email, and it does. When the data is missing, it says so.

Source
  • "ETA 1800 LT 14th" (master)
  • "max draft 8.50 m" (terminal)
  • "arrival draft 8.70 m" (agent)
Math
  • 8.70 − 8.50 = +0.20 m
  • Arrival draft over the terminal maximum
Answer

The discharge berth is about 20 cm over the stated max draft. Flagged as the sharpest item before the berth, with the source line for each number.

On the desk

What it does on a real operations desk

Patterns from real use, anonymized. Your fleet, your formats, your rules.

Before you are

The board is ready before you are

By the time you reach the office, the agent has already read the overnight flood across the fleet and handed you one vessel-first board: every ship, current and next port, ETA with the source labelled, cargo, ROB, blockers. You start the day on top of the fleet, not buried under it.

Conflict first

It catches the conflict you would have missed

Two emails, two numbers, an arrival draft and a terminal maximum that disagree by a hair. It surfaces it first, with both source lines and the math, before it costs you at the berth.

Management view

It tells you which operators are dropping the ball

Ask it to rank your operators on how well they communicate. From your own ops mail it builds an evidence-based scorecard of patterns and bottlenecks, from data you already own.

Real blocker

It names the real blocker, not the obvious one

For a vessel approaching a canal, it flags the booking slot, the arrival deadline, and the clearance certificate as the true gates on sailing, not the berth everyone was watching.

How it works

A colleague that joins the desk, not a platform to adopt

No migration, no dashboard to learn. The agent reads the material you already handle and prepares the work.

STEP 01

Discovery

We map your desk: your operations mailboxes, your board format, your decisions. Not a sales call, a diagnostic.

STEP 02

We connect and tune

The agent goes live on your hardware, connected to your approved sources, tuned to your format and your rules. Month one, it asks before acting. Month three, it runs the routine. Month six, it anticipates.

STEP 03

You chat on WhatsApp

“Which ships are open next week?” “Compare actual consumption to the CP basis.” “Who caused the delay?” It answers with source and math.

Questions

The things owners ask first

Does this run on the ship or in the office?

In the office, on a Mac Mini at your desk. It reads your approved operations mailboxes and files. It has no connection to vessel navigation, the engine room, or onboard systems.

Do I have to forward it my emails?

No. It is connected to your approved operations mailboxes and reads mail as it arrives. Nothing to forward, nothing to upload.

Can it cross-check a master ETA against the agent's?

Yes, that is the point. It labels the source role on every timing and surfaces the conflict first, with both source lines and the math.

Does it decide or send anything on its own?

No. It prepares the vessel board, the calculations, and the evidence. Your people approve, send, and decide.

Where does my fleet data go?

Nowhere. It stays on your hardware. We maintain the system over an encrypted tunnel for maintenance only. Your positions and fixtures never leave your office.

Start the day on top of the fleet.

Your desk keeps the judgment. The agent does the reading. Bring one day of your operations mail and we will show you the board.