There is a number that should bother every sales leader in distribution, and it rarely gets the attention it deserves. According to Salesforce's 2025 State of Sales Report, which surveyed thousands of sales professionals across industries and geographies, the average sales representative spends only 28 percent of their working week on direct selling activities. The remaining 72 percent goes to administrative tasks, internal meetings, reporting requirements, travel time, and the slow accumulation of small obligations that fill a calendar while revenue sits waiting. Less than a third of the week, on a good week, is spent in front of a customer or moving a conversation toward a close.
Most sales leaders who hear this number for the first time assume it describes someone else's team. The assumption is understandable. A field sales rep looks busy. The calendar is full, the mileage is accumulating, and the CRM shows a respectable volume of logged activity. Busy and productive are not the same thing, and the difference between them is precisely where most distribution sales organizations are losing.
The problem is structural, not personal. That distinction matters more than most managers are willing to admit, because a structural problem cannot be solved by coaching the rep harder or setting a more aggressive quota. It requires looking at what the organization has built around the sales function and asking whether that structure supports selling or simply resembles it.
What the Day Actually Looks Like
The typical distribution sales rep begins the morning answering emails and responding to internal requests that accumulated overnight. There are pricing questions from the inside sales team, an order discrepancy that needs resolution before a customer notices, a delivery complaint that has been escalated and requires a call. None of these tasks are optional, and none of them are selling. They are the organizational overhead that accumulates when the sales function is also the customer service function, the expediting function, and the first line of internal communication.
By midmorning, the rep is in the car. The first call is a courtesy stop at an account that has been buying steadily for years, a relationship maintenance visit that will produce no new business today and was scheduled out of habit rather than purpose. The second call is a legitimate opportunity, a dealer who has been evaluating a new product line, but the meeting runs long and the afternoon compresses. There is a branch managers meeting at two o'clock that the regional director expects everyone to attend, and the drive from the morning's last account back to the office takes forty-five minutes.
The afternoon meeting runs ninety minutes. The agenda covers market share data that everyone in the room already knows, and a reminder about the quarterly reporting deadline that is two weeks out. By the time the rep is back in the car, there are three hours left in the working day and two accounts still on the list. One of them gets a windshield call, a phone conversation conducted from the parking lot of a fast food restaurant, and one gets rescheduled to next week.
This is not a failure of effort. It is a failure of design.
Where the Time Goes and Why
The administrative burden on distribution sales reps has grown steadily over the past decade as companies added technology without removing the manual processes the technology was meant to replace. CRM systems that should have eliminated call reporting instead created a second layer of documentation, because the system requires input that the old paper process also required. Order management portals that were supposed to free up rep time added a new category of error resolution, because the portal introduced new ways for orders to be entered incorrectly.
Internal meetings expanded to fill the time that technology was supposed to create. When a sales organization has more tools, it tends to have more conversations about how the tools are performing, which means more meetings. The rep who was supposed to gain two hours of selling time each week from a new routing software instead spends an hour each Monday in a meeting discussing why the software's recommended routes do not match how the territory actually works.
Territory design compounds the problem. Most distribution territories are built on geography and historical account assignments rather than on a realistic assessment of where the selling opportunity is concentrated. A rep covering a large geographic area spends a disproportionate amount of time in transit between accounts that are far apart and may represent modest revenue individually. The territory that made sense fifteen years ago, when the account base looked different, has not been redesigned to reflect where the business actually is today.
The Measurement Problem
Organizations reinforce this pattern by measuring the wrong things. Activity metrics, call counts, mileage logs, and number of accounts visited per week, are easy to track and satisfying to report. They create the appearance of rigor without requiring anyone to examine what the activity is actually producing. A rep who makes twenty calls a week and closes three of them is harder to evaluate than a rep who makes twenty calls a week and logs all twenty in the CRM, but the second description tells you almost nothing about whether the company is getting a return on the compensation it is paying.
Sales managers who inherited activity-based measurement systems rarely eliminate them, because activity metrics provide political cover. If a rep is not performing, the activity log shows whether they were at least working. This is useful for managing out an underperformer, but it is a poor tool for building a team that consistently sells above expectation, because it trains reps to optimize for logged activity rather than for revenue outcomes.
The companies that have closed the gap between what their reps are paid to do and what their reps actually do share a common characteristic. They went through the uncomfortable exercise of mapping where sales rep time actually goes, not where managers assumed it goes, and they redesigned the territory structure, the internal support model, and the reporting requirements around the answer. It is not a quick process, and it produces findings that are inconvenient for everyone involved. It also produces a sales team that sells.