Transport & logistics

Value that slips away today - and what changes

Logistics rarely lacks the willingness to drive or coordinate. What costs the most is the gap between yesterday's plan and today's reality. Four places where agents do something different from traditional TMS and routing tools:

A route plan that actually plans itself

Daily route planning is a puzzle of stops, drivers, vehicles, delivery windows and load - one that takes hours to build and falls apart on the first disruption. Agents take in all the variables at once and can re-optimize in minutes when something changes. The coordinator uses their head on the exceptions instead of starting from zero every morning.

Disruptions that re-plan themselves while the vehicles are moving

A resource drops out, a main route is blocked, an urgent delivery appears, a recipient cancels - each disruption today means a calling round to move stops around. The agent catches the change from GPS, dispatch or the customer, suggests a reallocation among available resources, and notifies the affected parties. The disruption goes from hours of panic to an adjustment that is in place before the next vehicle rolls.

The customer knows when the vehicle will arrive - before they call to ask

When ETA changes or a delivery deviates from the plan, the customer often finds out by calling first. The agent sees the changes continuously and notifies in the customer's preferred channel - with the new ETA, signed proof of delivery or a photo from the delivery point. Fewer calls to dispatch, fewer customers waiting for something that never arrives.

The driver has all the information before she starts the engine

A driver has stops, addresses and a packing list - but rarely special instructions, access codes, return pickups or where the delivery should actually be placed. The agent gathers it from emails, previous deliveries and dispatch notes, and presents it in the driver app as the next thing she needs to know. Fewer return visits, fewer calls to dispatch, less time per stop.

None of this is small-margin value. The biggest opportunity lies in a plan that can absorb disruptions, and in both customer and driver knowing what is happening without having to call anyone.

Why an agentic platform

All of the above assumes the agents have somewhere to live. The platform is that layer. What matters is whether it is built so the value stays with you over time.

The platform should be the easiest thing to replace in the whole setup. The value should live in your logic and your data, decoupled from a vendor roadmap or pricing model. Four properties determine in practice whether you actually own what you build.

Your logic, governed by you

Each business plans, prioritizes stops and communicates deviations in its own way. The agentic part is that this way of working can be expressed as it actually is, free from the limits of a standard field or a built-in route optimizer. The company's own routines, customer preferences and exceptions determine what the agent does.

Data you do not have to force into a schema

Much of what drives good dispatching sits outside TMS fields: GPS traces, customer SMS messages, supplier messages, driver notes, weather and traffic sources. Agents use it as it is. You do not need to build dashboards or bridge integrations in systems that were never meant for it - or wait for a vendor to prioritize exactly your data source.

The platform is the easiest thing to replace

We prefer open source that you can run yourselves. What matters most is that the logic and data live with you - in your own account, your own infrastructure. If you replace TMS, routing tools or the agent platform itself in three years, the work should move with you. The plug should always be possible to pull.

The cost follows the infrastructure you use

Per-action and per-message pricing starts to hurt at scale precisely when you begin to succeed - and logistics is volume. Open infrastructure lets cost follow actual resource usage - based on the infrastructure you already have. That makes it realistic to let agents take over work at real volume, far beyond pilot size.

Questions worth sitting with

None of them has a single right answer - but they make it easier to see where the value actually sits.

1. How long does it take from a disruption hitting the plan until a re-planned route is out with the drivers?
2. How many of your customers discover delays by calling you - before you have notified them?
3. How large a share of a dispatcher's day goes to coordinating exceptions by phone?
4. How much of your route and dispatch logic lives in a setup you own yourselves - and how much in a TMS vendor account?

Built once - together with you

The building blocks extend beyond logistics. The same agentic layer also powers marketing, sales, service, project and data, and production - with different agents on top. The capability is built once and used in many places.

We are the ones who build them with you - a build team that takes the agents from first version into operations, and keeps developing them when you find the next place they should take over work, on an open foundation you own yourselves.

This becomes easier to understand if you stop thinking of it as tools.

"The future's capacity is built with agentic workflows."