Skip to content
edge247

Shipowners & operators

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

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

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 works for the desk, not the bridge.

What it watches

Everything that reaches the desk overnight, read and ranked.

It reads what lands across the fleet and keeps the moving parts in one place, so the picture is current the moment you ask.

Vessel board and next open port

Every ship, current and next port, present and forward employment, prepared before the morning call.

ETA, ETB, ETC, ETD cross-check

Every time carries its source: master, agent or terminal. When they disagree, the conflict comes first.

ROB and bunkers

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

Performance against the CP

Clean noon reports checked against the charter party or TC warranty. ECA split, main engine apart from auxiliaries.

Delay and detention causation

Who caused what: vessel, charterer, terminal, weather, documents or agent. Port-event timelines with sources.

A view of the desk

Where follow-ups stall and which threads run longest, built from your own operations mail.

Source, working, answer

Every number shows its work.

Ask to see the email and it shows you. When a figure is missing, it says so instead of guessing.

Is Alder over on consumption?

Source9 clean laden noon reports from her last two passages: 23 to 25 hours steaming, below BF4. Warranty from the time charter.
WorkingSea days only. Main engine and auxiliaries counted apart. ECA and open-sea legs split by fuel.
AnswerLaden, 1.4 t/day over the warranted consumption.
For youWorth a word with the chief engineer before charterers raise it.

On the desk

What it does on an operations desk.

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

The board is ready before you are

By the time you reach the office, the overnight mail across the fleet is read and one vessel-first board is waiting: every ship, current and next port, ETA with its source, cargo, ROB, blockers.

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 shows both lines and the math first, before it costs you at the berth.

It names the real blocker

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 starts

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

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

  1. 01

    Discovery

    We map your desk: operations mailboxes, board format, who decides what. A working session, not a sales call.

  2. 02

    Connect and fit

    Live on your hardware, connected to approved sources, fitted to your format and rules. In the first weeks it checks its reading with you; corrections become lasting rules.

  3. 03

    Ask on WhatsApp

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

Questions

What owners ask first.

Does it 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, with no connection to 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 check a master's ETA against the agent's?

Yes. It labels the source of every time and shows conflicts first, with both source lines.

Does it decide or send anything on its own?

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

Where does our fleet data go?

Company files, the structured wiki, memory and working state stay on hardware you own. When a task needs the language model, only the context for that task goes to the provider you approved, on your own account, with training on your prompts switched off wherever the provider allows.

Discovery call

Walk us through a Monday on your desk.

We will show you where a Full-Time Agent gives your team time back, and where it should not be used. No pitch deck.

A person replies, not a bot.