The documents behind every shipment, staffed by AI employees.
Carriers, 3PLs, shippers, ship managers, port authorities. The freight moves, the vessel sails, the gate lifts. Behind all of it sits an office reading, checking and chasing paper. Winsen One staffs that office, and your team approves every output.
Where the opportunity sits.
Not in the network. In the office behind it, where the work is real but nobody ever staffed it properly.
Audited by sampling, if at all.
A share of every freight bill is simply wrong: a lapsed rate, an accessorial the shipment record does not support, the same move billed twice. Everyone knows it. Auditing every line has never been worth a human's day, so the leakage gets priced in as a cost of doing business.
A five-day window nobody files in time.
OS&D windows close fast, and the evidence lives in three inboxes and a POD nobody scanned. Claims get abandoned because chasing them costs more than the payout. That is not a claims problem. It is a paperwork problem, and it compounds every week.
Charged on timelines nobody reconstructs.
Detention and demurrage are billed on a clock. The gate log, the SOF and the terminal record hold the real one. Rebuilding that timeline per charge is exactly the work that never gets done, so the invoice's version of events wins by default.
Assembled by email, settled at month-end.
The crew-change pack lives across an inbox and a shared drive. The settlement sheets between partners get reconciled when someone finds a day. The ship passes inspection; the office paperwork is what fails it. The operation is sound. The office behind it runs on heroics.
Core. Control. Business Support.
We organise the office behind a logistics operation into three sides, and staff each with AI employees. Control is where we are deepest today.
The document work that moves with every shipment, voyage and port call.
Pre-arrival filings, crew-change packs, requisition chasing, SOF capture and the shipment document pack, prepared for your team to submit.
Meet ZaraPrepares entries and checks HS codes; your broker signs every filing.
Collects, verifies and files proof of delivery so billing never waits on a driver's glovebox.
The checking that stops money leaking. This is where we are deepest today.
Every invoice line against contracted rates, every accessorial against the shipment record, disputes drafted with the clause attached.
Meet FreyaTracks certificate expiries and keeps PSC and vetting documentation inspection-ready before the inspector boards.
Rebuilds the actual timeline behind every D&D charge and drafts the dispute when the clock does not add up.
The back office behind the network, the fleet and the port.
Audits DAs and port-call invoices line by line against tariffs, reconciles partner and COD settlements, drafts disputes with evidence.
Meet DiaProcesses, matches and queues carrier invoices so approval is a decision, not a data-entry shift.
Keeps billed rates honest against the contracts you actually signed, amendment by amendment.
Every line of every freight bill, against the contract.
Freya reads the invoice the way your best auditor would if she had the time: linehaul against the contracted rate, accessorials against what the shipment record actually supports, D&D against the gate log. When the clock on the invoice and the clock in your records disagree, the dispute is already drafted, with the clause and the evidence attached. Your team decides what to fight. Nothing is paid or blocked by anyone but you.
The vessel call pack, assembled before anyone asks for it.
Zara keeps the pack for every call: crew certificates checked for validity, the pre-arrival declaration ready for submission, the SOF captured into a timeline you can actually dispute from. What is missing gets chased, and the chase is visible, not buried in an inbox. When the agent asks where the pack stands, the answer is a register, not a search through email. Submission is your team's click, every time.
Settlements reconciled while the month is still open.
Dia works the settlement spreadsheets that live between you and your partners: interline, franchisee, COD. Every cycle reconciled deduction by deduction against the agreement, every shortfall surfaced in days instead of discovered at quarter-end, every dispute drafted with the evidence lined up. The relationship stays yours. The arithmetic stops being a favour someone does at month-end.
Weeks to proof. Months to deployed.
On the custom arrangements, the engagement runs over 3 to 4 months with a forward-deployed team working alongside your people, in four phases. Understand: week one is a working session with nothing to sell in it. Deploy narrow: weeks 2 to 4 put one team and one workflow live inside your approval rules, with a paid pilot on a quarter of historical invoices or disbursement accounts your team has already paid, so the leakage we find is measured in money, not activity. Measure: weeks 4 to 12 track approved-work volume, time returned and error rates on shared dashboards. Expand: only when the numbers make the case. Custom deployments are single-tenant, on your infrastructure if you want it, with your data staying in your systems.
Pilot on paid historyLeakage reported in moneyNo expansion without measured resultsEvery output approved
The questions your team will ask.
Straight answers, before you ask them on a call.
We have a TMS and a freight audit vendor. Why this?+
Can it read our rate contracts and charter parties?+
Where does it run?+
What does a pilot look like?+
What does it cost?+
What does it never touch?+
Put an AI employee on the office behind your operation.
Bring one quarter of freight bills, DAs or settlement sheets. We come back with the leakage in money, the pilot design, and the deployment plan.
