Blog Point of view

Visibility was only the beginning.

Knowing where the truck is doesn't make the work around it go away. What we learned building a tracking company, and why we stopped calling it one.

Param SandhuCo-Founder & CTO·6 min read

The short version: a location answers "where is it?" It doesn't answer the driver's question, update the TMS, chase the POD, or tell the customer. Freight operations have scaled with headcount because the work around visibility never went away. That's the part worth automating.

Chain started as a tracking product. Before that, Annalise and I ran a trucking company, and the problem we wanted to fix was small and specific: a broker would call our driver four times a day to ask where the truck was. So the first version did one thing. It texted the driver a link, and the broker got a location back. No app, no login, no phone call.

It worked. Brokers liked it. And then we watched what happened next on their floors.

The dot didn't stop the calls

Even when a load was tracking perfectly, the work didn't stop. Somebody still had to ask the driver if they were loaded. Somebody still had to type the arrival time into the TMS, because the customer's EDI feed fires off that field and nothing else. Somebody still had to notice the reefer temp in the photo, ask for the second page of the POD, and tell the shipper the appointment moved.

A dashboard that shows a late load is useful. But it hands the late load back to a person, along with every on-time load that still needs its paperwork. Visibility answered "where is it." It didn't answer "what happens next."

The work lives in the conversation

So we built the thread. Every driver text, dispatcher email, photo and document on the load, in one place, in order. That turned out to matter more than we expected, because the conversation is where the work actually happens. It's where the driver says they're running late, where the dispatcher swaps drivers, where the lumper question comes up.

Once the conversation lived in one place, an agent could work it. That's Autopilot: checkpoints across the load lifecycle that read the load, the tracking and the whole conversation so far, then decide whether anything needs to happen. Sometimes the right answer is to say nothing.

Freight has always scaled with headcount

More loads meant more check calls, which meant more people. That's the equation our customers live with, and it's the one worth changing. Not by asking people to work harder, but by moving the routine work off their desks so they can spend their time on exceptions, carriers and customers.

Where it goes from here

Booking is the same idea, pointed at the other end of the load: the agent that already knows a carrier's history works the offer, vets the carrier, negotiates inside your numbers and hands the covered load to tracking without a seam.

We still track trucks. It's the deepest thing we build, and five years in production taught us most of what Autopilot knows. But tracking was never the job. Moving the freight was.

See Chain in action.

We'll open a live production environment, walk a real load from first offer to final POD, and show you what Autopilot would do with yours.