Atlas Freight 

Atlas Freight brokers cargo between shippers, carriers, and ports. Their operation ran on a patchwork of legacy tools, email threads, and a 20-year-old terminal app that only three people fully understood.

They were moving two billion dollars of cargo a year on software that could lose a container in a forwarded reply.

Logistics is unforgiving: a single shipment touches customs, carriers, warehouses, and finance, each with its own system of record. The platform had to orchestrate all of them without ever becoming the bottleneck.

And it had to be adopted by dispatchers who'd used the old terminal for a decade and were, reasonably, skeptical of anything new.

We modeled every shipment as a single timeline that every party reads from and writes to, replacing the email chains with one source of truth. Integrations push and pull from carrier and customs systems automatically.

We rolled it out lane by lane, sitting with dispatchers as they worked, so the platform earned trust on real shipments before it was ever mandated.

Atlas now runs its entire book through one interface. Exceptions that used to surface days late are flagged the moment they happen, and the time to quote and book a complex multi-leg shipment dropped from hours to minutes.

The old terminal app was finally switched off — quietly, with no one mourning it.

An event-sourced core in Go keeps an immutable history of every shipment, with a Next.js operations console on top and a queue of adapters integrating carrier, customs, and ERP systems.

Idempotent event handling means a flaky third-party API never corrupts a shipment's state — the system simply retries until the world agrees.