Non-selling time is every working hour a rep spends on something other than buyer contact or preparation attached to a specific open deal. It covers CRM data entry, internal reporting, forecast submission, deal reviews, approval waiting, training, and travel. Some of it is necessary. A large share of it accumulates without anyone deciding it should.
The four buckets worth separating
| Bucket | Examples | Removable? |
|---|---|---|
| System overhead | CRM updates, duplicate entry, field maintenance | Mostly, through automation and field pruning |
| Internal process | Forecast calls, pipeline reviews, status meetings | Partly, by cutting frequency and attendance |
| Approvals and waiting | Quote approvals, legal review, deal desk queues | Yes, through thresholds and delegated authority |
| Skill and readiness | Onboarding, coaching, certification | No, and cutting it costs more later |
Why it grows on its own
Every reporting request adds a step. A board question becomes a new field, the new field becomes a weekly update, and the update outlives the question. Nothing removes it, because removing it requires someone to notice it exists. The same pattern runs through approval workflows, where a single bad discount from years ago justifies a review gate that now touches every deal.
Territory changes add a second layer. Reps rebuild account context they did not need last quarter, and that research time is real work that produces no buyer contact. ORM has seen this play out with coverage still holding in the standard 3x to 5x range while execution suffers, because the pipeline was never the constraint.
Cutting it without breaking the data
The instinct is to strip CRM requirements. That backfires, because forecasting depends on the fields that reps maintain. ORM defines meaningful activity as a change in stage, close date, or amount, and those three inputs need to stay clean. The right cut targets fields nobody queries and reports nobody opens.
Consistency matters more than completeness. Data does not have to be pristine to support an accurate prediction, it has to be consistent, which means a shorter list of required fields maintained reliably beats a long list maintained selectively. That trade releases hours without degrading forecast accuracy.
Approval queues are the other high-yield target. Raising discount thresholds and delegating standard terms removes waiting time from every deal in the pipeline at once, which shows up in sales velocity rather than in any individual rep's effort score.
Frequently Asked Questions
Is all non-selling time waste?
No. Account research, call prep, and coaching produce better buyer conversations. The waste category is process overhead that no one downstream reads, such as duplicate reporting, fields nobody queries, and status meetings that restate what the CRM already shows.
Which category is usually the largest?
The largest bucket differs by team, which is why the bucket breakdown matters more than the total. System overhead and approval waiting are the two buckets most often found to be removable once they are measured separately.
How do you measure it?
Subtract buyer-facing hours from scheduled working hours, then break the remainder into named buckets using calendar categories and system logs. The bucket breakdown is what makes the number actionable, since the total alone tells you nothing about what to remove.
Does cutting non-selling time raise quota attainment?
It raises attainment only when the recovered hours land on workable pipeline. If a rep's book is full of opportunities that have gone twelve months without a stage, close date, or amount change, extra hours produce activity on dead records instead of bookings.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like non-selling time into prescriptive action for your team.
Schedule a Demo