Six things: maintaining carrier relationships, quoting and negotiating, booking and documentation, tracking and exception handling, claims, and cost analysis. Software handles the repetitive middle of that list well and the relationship and judgement ends of it poorly. Which is why the honest question isn't whether to automate logistics, but which parts.
Most businesses that ship freight don't have a logistics department. They have someone in operations, or purchasing, or occasionally the founder, who picked it up because it needed doing and never put it down.
If that's you, it's genuinely useful to know what the function looks like when it's someone's actual job — partly to see what you're not doing, and partly to work out which parts are worth solving.
A logistics team knows who moves what, where. Which carriers are strong on which lanes, who is reliable in December, who answers the phone when a delivery fails, who has capacity when everyone else is full.
This is the least visible part of the job and often the most valuable. It's also the part that takes years and doesn't transfer — it walks out of the building when the person does.
Getting prices, and getting them to mean the same thing. On regular lanes that means negotiating rates in advance rather than pricing each shipment cold. On ad hoc shipments it means going to several carriers, normalising what comes back, and knowing which number is actually the best one.
The normalising is the part outsiders underestimate. Quotes arrive in different formats with different inclusions and different assumptions, and comparing them properly is real work every single time — see why two quotes for the same shipment differ.
Confirming the shipment, producing the paperwork, and getting the right documents to the right party before they're needed rather than after.
Domestically this is light. Internationally it isn't: commercial invoices, packing lists, certificates of origin, customs declarations, and whatever the destination country specifically requires this year. A missing document doesn't slow a shipment down, it stops it, and it stops it somewhere expensive.
This is where the hours go, and it's the part nobody puts in the job description.
Knowing where things are. Noticing that a shipment hasn't moved in three days. Working out whether that matters. Calling the carrier. Calling the customer before the customer calls you. Rebooking the delivery that failed because nobody was on site.
A good logistics person is measured almost entirely on how early they find out about problems. Everything downstream of that — the cost, the customer conversation, the options still available — is decided by how much warning there was.
When freight is damaged, lost or delayed, someone has to establish what happened, work out who is liable, gather the evidence, and file within the time limit. Those limits are short and unforgiving.
This is the part where knowing the difference between carrier liability and cargo insurance stops being academic. Liability is usually capped by weight; insurance is a separate product you bought or didn't. Businesses discover which one they have during their first serious claim.
Understanding what freight actually costs, per lane, per customer, per unit — and noticing when that changes. Freight spend that nobody analyses drifts upward quietly, because each individual invoice looks reasonable.
Being specific about this matters more than being enthusiastic about it.
That's the honest split, and it's the reason we describe what we build as removing the coordination work rather than replacing the function. A person still picks the winning quote here before it's presented to a client. That isn't a limitation we're apologising for; it's where the judgement belongs.
There's a volume at which a dedicated logistics person pays for themselves, and it's lower than most people assume once you count the hours currently going into it invisibly.
Rough signals that you're at it: freight is consuming more than a day a week of someone's time; you're shipping on enough regular lanes that negotiated rates would beat spot pricing; your shipments are complex enough that judgement is being exercised weekly rather than monthly; or freight problems are reaching customers before they reach you.
If several of those are true, hire. Software will make that person substantially more effective, but it isn't a substitute for them, and anyone telling you otherwise is selling something.
If none of them are true — freight is a few shipments a month, handled by someone whose real job is something else — then a dedicated hire is hard to justify and the coordination work is the thing worth removing. That's the case we built the platform for.