AiatSea: Everybody Launched. Almost Nobody Measured. And Somebody Else Is Paying.

Fifty thousand people. Two thousand three hundred exhibitors from seventy countries. Four days in Hamburg. We went through the week's announcements looking for one thing: a number showing what a deployed system actually did.

Here is the count. A ship design study with no vessel. A survey platform with no investment figure. An acquisition with no price. A stowage tool with no saving. A performance integration with no customers. A compliance tool with no users. One safety product with real figures, published by the vendor about its own product, in reply to criticism.

That is not a scandal. It is a launch show, and launch shows are for launching. But it is now the fourth week running that we have written the same sentence in different words, and at some point a pattern stops being a coincidence and becomes the story.

Here is the part that should bother the industry more.

The published research says 81% of maritime companies are running AI pilots and only 11% have policies that let them scale. Separate work found only 14.4% of AI agents go live with full security and IT approval, and 31% of organisations cannot say whether they have had an AI breach at all.

Put that next to what you can see with your own eyes in any office or any messroom. The chief engineer drafting a defect report. The operator checking a charterparty clause. The superintendent turning three pages of notes into a job specification. It is happening now, every day, at scale, and almost none of it appears in a corporate adoption figure.

Because in most cases the person is paying for it themselves.

We have asked this question for four weeks and no manager, union or class society has published an answer. So say it plainly: if your staff are buying their own AI accounts to do your work, you are not a company with low AI adoption. You are a company with unmanaged AI adoption, and you are getting it for free while carrying all of the risk.

Company information is going into an account you do not control. There is no log, so after an incident you cannot show what the machine advised or who acted on it. When the person leaves, everything they built leaves with them. And in Europe the liability stays with you regardless of who paid the twenty euros.

The fix is not complicated. If it is company work, the company buys the account, and the company keeps the log.

And the measurement problem is not hard either. Pick five jobs that eat time. Port call paperwork, defect reports, PMS job descriptions, charterparty questions, supplier chasing. Time them now with a stopwatch and a spreadsheet. Give the tool to half the team, paid for and logged properly. Time them again in four weeks. Publish the difference. The reason nobody does this is not difficulty. It is that nobody wants the answer written down.

Our own caveat, and it is a real one. We do not have the numbers either. This is judgement built on what the surveys show, what the vendors do not publish, and what we see in our own working life in ship management. Our reader survey is open and collecting, and when we have enough responses we will publish what we find, including if it contradicts everything above. [AiatSea reader survey · AiatSea, 9 August]

This story is part of the Maritime AI Digest of 6 September 2026.