About

A container standing still is an invoice growing

CargoIQ was built after watching operations teams discover demurrage on the statement rather than on the day it could still be prevented.

Most teams already have the data. It sits in a terminal export, a carrier portal, an agent's email and a spreadsheet that one person keeps. Nothing in that stack answers the only question that matters on a Monday morning: which of these boxes will cost me money this week, and who do I call?

CargoIQ answers that question and then keeps score. It applies the free-time terms you actually negotiated, ranks the portfolio by exposure, pushes the follow-up to whoever is responsible, and at the end of the month shows where the money went by cause, carrier, port and party.

We build it alongside working operations teams during controlled pilots rather than in isolation, which is why the board looks like a shift handover and not a dashboard.

What we hold to

Show the number, not a colour

Every flagged container carries a currency figure and the rule that produced it. If we cannot explain a warning in one sentence, it should not be on the board.

Fewer, better alerts

An inbox nobody reads prevents nothing. The same problem is not repeated daily, quiet containers stay quiet, and there is a firm cap on how much any person receives.

Most delays sit outside your team

So the tool does not stop at telling your staff. It writes the chase to the agent, transporter or line, records the reply-by date and escalates when it passes.

Savings must be recorded, not claimed

We separate money actually avoided from estimates. A report you can defend in front of a finance director is worth more than a flattering one.

Who it is for

Freight forwarders

Managing many clients' boxes at once, where one overlooked container erodes the margin on a whole shipment.

Clearing agents

Where customs holds and missing release paperwork are the recurring cost, and accountability has to sit with someone.

Importers and manufacturers

Paying the demurrage invoice at the end without ever seeing which link in the chain caused it.