_1777711377206.png)
Why we run freight auctions on WhatsApp (and not a portal)
After 14 customer interviews, every transporter chose WhatsApp over a slick web portal. Here's the data — and what it taught us about adoption in emerging-market logistics.
Eighteen months ago, we shipped a beautiful web portal for spot freight auctions. Real-time bidding, leaderboards, an audit trail with millisecond timestamps, the whole thing. Adoption peaked at 11% of invited transporters and went sideways from there. The remaining 89% kept calling our customers' dispatchers on the phone, the way they always had.
So we did what we should have done first: we sat down with 14 transporters across four major freight corridors and asked them what was wrong.
Every single one of them — without us mentioning it — said WhatsApp.
"You want me to open an app to bid? My driver's brother answers the phone. He has WhatsApp, not your app."
What the data actually said
We thought we were building for the transporter. We were actually building for whoever holds their phone at 9pm when an indent drops. In half the cases, that's a brother, a son, a part-time clerk. They don't have an app. They don't want an app. They have WhatsApp.
A 14-person sample is not a global truth. But the qualitative gap was unambiguous: the portal lost on every dimension that mattered to them — login friction, notification reliability, the cost of a missed bid, and the simple fact that they were already staring at WhatsApp 200 times a day.
Three things we got wrong
1. We optimised for our own auditability, not their workflow
Our portal logged every keystroke. Beautiful for compliance teams. Irrelevant for a transporter who wants to type a number and get back to dinner. The cognitive cost of "open browser → log in → find indent → click bid → type → confirm" was about 40 seconds longer than "type number, hit send".
2. We assumed the bidder was the owner
In ~50% of small fleets, the actual bid decision is made by someone other than the named owner: a brother, a dispatcher, a senior driver. None of them had portal logins. All of them were already in the WhatsApp group where the indent landed.
3. We confused "real-time" with "instant"
The portal had millisecond bid timestamps. The transporter didn't care. They cared whether they'd see the indent in time. WhatsApp pushes a notification with sound. Our portal pushed an in-app red dot they only saw when they remembered to log in.
What we shipped instead
We rebuilt the whole thing as a WhatsApp Business integration. Each indent now creates a small group: the shipper's dispatcher, our bot, and the 4–12 carriers on the lane. The bot posts the load, accepts numeric replies as bids, broadcasts the running best price, and assigns the lane when the timer runs out. It also sends the LR (lorry receipt) as a PDF back into the same thread.
"Now dispatch happens in the same place where the pickup notification arrives. One screen."
What this taught us about logistics adoption in emerging markets
We've internalised three rules. They're not universal — but they've held up across the next four products we've shipped after this one.
- 1Meet the user where they already are. The cost of moving someone to a new app is much higher than the cost of building inside the app they already live in.
- 2The named user is rarely the actual user. In SMB freight, the person typing the bid is often two relationships away from the person on the contract. Build for the typist, not the title.
- 3'Real-time' is a feature only if it's also visible. Push beats pull. A notification you'll see beats a dashboard you have to open.
- 1Adoption is a venue problem before it's a UX problem.
- 2In SMB freight, WhatsApp beats every other channel — including phone — for time-critical decisions.
- 3Audit trails belong on the shipper side. The carrier should never see them.
Writes about how the world's largest shippers actually run freight — the real workflows, the stuff vendors don't put in slides.
More from the team
Our OCR pipeline turns smudged, curled, sometimes wet paper PODs into structured JSON in 30 seconds. Here's the architecture — and the failure modes nobody warns you about.
Most TMS dashboards drown ops teams in red. We rebuilt the control tower around the five decisions a dispatcher actually makes before lunch.
A teardown of the 90-day rollout — what changed in the indent process, the auction floor, and the settlement workflow.