AI automation for freight forwarders and customs brokers in the UAE.

Every pack leaves complete, and the shipment stops waiting on the one page nobody noticed.

The bill of lading, the certificate of origin, the delivery order and the commercial invoice are read as they arrive and checked against what this consignee and this lane actually require. What is missing is named before the pack goes anywhere, and what cannot be resolved stops at a person with the reason attached.

Book a meeting

Book a meeting

Book a meeting

Thirty minutes. Nothing to prepare.

Or email hello@runbook.ae

The work

Four jobs a forwarder repeats.

The customs pack
Checked before it goes, not after it comes back.
Every consignment arrives as a pile: the bill of lading, the packing list, the commercial invoice, the certificate of origin, and whatever this particular consignee wants attached. Each one is read and checked against the lane and the consignee’s own rules, and what is missing is named while there is still time to get it.
The rate request
Priced and out while the enquiry is still warm.
A request lands and someone opens the rate card, checks what was agreed with this customer last time, and builds the quote around the exceptions one person remembers. The assembly and the follow up run on their own, and the price stays yours.
The carrier invoice
What was billed, against what was agreed.
The invoice, the rate agreed and the job file rarely say the same thing, and the difference is found by someone reading three screens. Records are matched as they arrive, and only the lines that disagree reach a person.
The new customer file
Live in every system before the first booking.
The trade licence, the VAT certificate, the credit terms and the delivery instructions are collected, checked and entered once, into every system that needs them. What is missing is chased without anyone having to remember to.
The alternative
Freight software ends at the login.
It holds the file, and the checking still happens in someone’s head. Runbook arrives knowing your business, because writing down how you actually clear a pack is where we start.
What you own
You own it. No seat bill.
It runs in your cloud account. If you stop paying us, it keeps running. What stops is us watching it, fixing it and extending it.

What we get asked

Questions freight operators ask.

No. Runbook reads the systems you already have, wherever the work lives: the freight system, the shared drive, the mailbox, the rate card in Excel. Moving your data somewhere new is a different project and it is not this one.
The checking still happens, and it happens on every consignment rather than on the ones there is time for. Your people move to the exceptions, which is where the judgment was needed in the first place.
It stops and tells a named person, with the reason and the document attached. Every agent has a line it will not cross alone, and you decide where that line sits.
That is the work. The rules a forwarder runs on are rarely written down anywhere, so writing them down, consignee by consignee and lane by lane, is the first thing we do. You read it and correct it before anything is built.
The scope, the fee and the finish date are agreed with you in writing before anything starts. We do not publish a length, because it follows the size of the operation, how many systems the work touches and what condition the data is in.
You do. The code, the credentials and the documentation sit in your accounts and under your name from the day we start. It runs in your cloud account, and if you stop paying us it keeps running.
Nothing. It is thirty minutes, and you leave with a one-page sketch of the job you brought: the steps as they run today, where the line would sit, and what we would measure.
We work across the UAE. Dubai and Abu Dhabi are where we are, and the first meeting is in person wherever that is practical.