Why Your Delivery Fleet Does Not Need Another Dashboard

Fleet software vendors all sell the same idea, that more data means a better-run delivery business. Then you watch a courier owner sit through a week of their demos and walk out more confused than when he walked in.

My friend Dev runs an eight-van courier service in the suburbs outside Raleigh. Last fall he asked me to help him pick tracking software, and I said yes because I assumed my tech background would help him sort the good platforms from the bad ones. I didn’t expect every vendor to push so hard on things he would never use.

The Demo Parade

The first vendor opened on a dashboard packed with widgets. Heatmaps of delivery density by zip code sat next to a maintenance calendar tied to odometer readings. The salesperson then spent what felt like most of an hour on driver scorecards that graded braking and idle time and color-coded every driver by risk level. Dev leaned over and whispered, “I don’t need a dashboard, I need a map with dots.”

I had been steering him toward that exact platform.

It looked like the serious choice, and I figured more data couldn’t hurt. That thinking holds up at a logistics company with analysts whose whole job is reading fleet reports. Dev manages eight vans from his kitchen table. He also answers the customer line, and when a driver calls in sick he drives the route himself.

Who These Dashboards Are Built For

Most of this software grew up serving companies with hundreds or thousands of vehicles. At that size, shaving a little fuel off every route or catching a worn brake early adds up to real money, and there’s an operations team ready to act on the reports. Driver scoring makes sense when somebody’s job is to read the scores and then go have the awkward conversation with the driver.

Small operators don’t have that person. Dev certainly doesn’t. Nobody at his company is going to set alert thresholds or build a custom report, and the vendors know it. The full set of panels still ships switched on, because a packed screen sells better in a demo than an empty one. Adding another panel costs them very little, and the monthly price per vehicle doesn’t drop if you ignore half of them.

What Dev wants to know is whether a van is heading to its next drop or parked somewhere odd. If it’s parked somewhere odd, he calls the driver. The idle-time report would tell him that same van sat at a red light on the way to a pickup, which he has never needed to know. Not once.

Dev’s List

After the last demo I asked him to write down the questions he actually asks himself during a workday, the ones software should answer for him. It took him about two minutes. Where is everyone right now? Is anybody running late?

Both of those come down to a live map with each driver on it and some idea of when they’ll get where they’re going.

He went with the plainest option we looked at. Months later he still opens one screen, the map, a few times a day and closes it again after a minute or so. When I asked last month, he said he has never clicked into anything else. The dashboard-heavy platforms would have cost him noticeably more each month, and he’d have stopped opening most of those panels by the second week.

Why the Screens Keep Filling Up

Software like this gets judged in an hour-long demo, and a crowded screen wins demos. I don’t think anyone at these companies is being dishonest about it. Nobody in that conference room is picturing a Tuesday morning with a driver on hold. The salesperson with the scorecards clearly believed in them. Dev spent the last part of her pitch texting a driver who had stopped answering his phone.

If you run a small delivery operation and have another demo booked, bring Dev’s two questions. Some tools are barely more than a map with dots, one dot for each driver’s phone with an arrival time beside it. Which of the other panels on that big screen would you still be clicking a month from now?