Distribution companies have a specific operational problem that doesn't show up in board decks or sales projections. It shows up in the gap between what management believes the sales team is doing and what the sales team is actually doing.
I spent time building software for one such company. What I found wasn't shocking โ not if you've worked in field sales operations before. But it was systematic, and nobody was naming it out loud.
What the company believed
The assumption was straightforward: sales reps cover their territory every day, visit their accounts, take orders, collect payments, and return. The daily route is planned. The numbers should follow.
The company had people in the field, vehicles on the road, and reports coming in. From the inside, it looked like a functioning operation. It wasn't wrong exactly. It was incomplete.
What was actually happening
Four problems, each running independently, each costing the company real money.
The phone visit
Some reps had figured out that calling a customer to ask "do you need anything?" and getting a "no" counted the same as driving to the customer, walking in, and actually selling. The call takes four minutes. The visit takes an hour. The daily quota doesn't care which one you did. So they called.
The problem is that a phone call and an in-person visit are not the same thing commercially. Customers reorder more when they're standing in front of a rep who can show them what's moving, what's new, what their competitors are buying. The phone call is a passive check. The visit is an active sale.
The noon clock
A subset of the team had a number in their head โ a personal daily target, usually set below what the company actually expected. Once they hit it, the day was effectively over. Not officially. They'd still be listed as "in the field." But the activity stopped. Some went home. Some parked somewhere quiet and ran the clock.
Nobody in the office knew. There was no mechanism to know.
The ghost route
Field reps understand that their supervisors can't physically verify their location every hour of the day. Some of them used that gap deliberately. They reported visits that didn't happen and accounted for time that wasn't spent on the route. The paperwork looked fine. The customers weren't seeing them.
The cash delay
When a rep collects payment from a customer โ especially cash โ it doesn't always reach the company the same day. Sometimes it's "I'll bring it next visit." Sometimes it's "end of the week." The rep has the money. The company doesn't. Across a team of 15 or 20 people, that floating balance adds up to a number that would make any finance director uncomfortable.
This isn't always malicious. Sometimes it's just the path of least resistance โ the rep doesn't want to make a detour to the office, so they hold it until it's convenient. But convenience for the rep is a cash flow problem for the company.
The solution
I built an end-to-end field operations system. Not complicated in concept โ comprehensive in coverage.
The system tracked what time each rep started their day and where they were when they did. Every customer visit required a GPS check-in at the customer's location, with a timestamp in and a timestamp out. Orders placed during the visit were logged against that visit. Payments collected were recorded at the moment of collection โ not at handover, not at end of day.
The rep's phone became the source of truth. Not self-reported notes, not reconstructed from call logs โ live, structured, continuous.
You can't fix what you can't see. Most distribution companies can't see their field.
The phone-visit workaround stopped working immediately. A visit now required a GPS check-in within the customer's physical location. A four-minute call from the car didn't qualify.
The noon clock problem disappeared within weeks. Activity was visible. Reps who stopped early were visible. The conversation became factual instead of accusatory โ here's what the data shows, here's what the expectation is. That's a much easier conversation to have.
Ghost routes became impossible to sustain. Location was tracked continuously during working hours. A visit that didn't happen left an obvious gap in the record.
Cash collection was logged digitally at the moment of collection, with the customer's confirmation on record. The money stopped sitting in transit, because the record of it existing was immediate โ and the company could see it.
What the numbers showed
Within a few months of running the system, the results were visible without any special analysis. Sales went up. Not because the reps had changed โ the same people were doing the same routes. But they were completing the routes now. More visits per day. More time per customer. Orders that previously weren't placed because a phone call got a "maybe" and the rep moved on.
Collections improved sharply. Cash that had been floating in transit for days or weeks started arriving the same day it was collected. The float the company was unknowingly extending to its own team closed.
The team wasn't happy at first. That's expected โ being measured when you weren't before is uncomfortable. But after a few months, the good reps started to appreciate it. They'd been competing on equal terms with people who were gaming the system. Now they weren't. The numbers reflected the actual work, and the people doing the actual work started to show up clearly in the data.
That's what real accountability infrastructure does. It doesn't punish the whole team for the behavior of a few. It makes the difference visible.
