Salesforce's 2026 State of Sales report gives managers a more useful workload picture than a single headline about selling time. Sales professionals reported spending 40 percent of an average week selling and 60 percent on nonselling work. The chart assigns 18 percent of the week to manual data entry and 16 percent to planning. Training takes 11 percent. The remaining time sits in other work, while customer meetings, prospecting, and quote creation make up the selling side of the chart.
Those figures put sales rep administrative time in context, but they do not say that every nonselling task should leave the rep's desk. Account planning, deal judgment, and customer conversations depend on context that support staff should not own. The better target is repeatable work with clear inputs, rules, and review points.
What the Salesforce time breakdown measures
The Seventh Edition surveyed more than 4,000 sales professionals worldwide. Its time chart is a self-reported allocation of the average workweek, so it works best as a diagnostic benchmark, not a promise that every company can reclaim the same number of hours.
The largest named nonselling category is manual data entry at 18 percent. In a 40 hour week, that share is equivalent to 7.2 hours. This is a simple conversion of the survey percentage, not a separate Salesforce finding. Planning accounts for another 6.4 hours on the same basis, but managers should not treat all planning as administrative work.
The distinction matters. A rep deciding how to position a proposal for a buying committee is doing sales work even if the activity happens away from the customer. A rep copying contact details from meeting notes into required CRM fields is doing record maintenance. Both may appear outside customer meeting time, but only the second task has a clean support handoff.
Salesforce also reports a generation-level difference. Its announcement says Gen Z sellers spend 35 percent of their time selling, compared with the 40 percent average, and lose about two more hours each week to manual data entry than senior reps. That comparison does not prove why the gap exists. It does show why a manager should inspect role level, process familiarity, and support coverage instead of assuming the same burden across the team.
The work that can move to support staff
Manual data entry is the clearest starting point because the report names it and because the work can be checked against source records. A support specialist can create contacts, standardize fields, attach activity to the right account, enter meeting outcomes supplied by the rep, and flag missing information. The rep remains responsible for the substance of the customer interaction.
Support staff can also prepare work without making the decision behind it. They can assemble account records, collect approved public information, format a quote from an approved price list, route it for approval, schedule follow-up tasks, and produce a list of opportunities with no recent activity. For a broader task inventory, see the daily sales virtual assistant task guide.
A good transfer candidate has four traits:
- The input is visible and available to the support specialist.
- A written rule determines the expected output.
- The completed work leaves an audit trail.
- An exception can be routed to a named sales or operations owner.
This test keeps the scope grounded in process. It also prevents a support role from quietly absorbing pricing judgment, qualification calls, or commitments to customers.
High volume alone is not enough. Prospect research can move when the company has a written ideal customer profile, approved sources, required fields, and a rule for unknown values. The same task should stay with the rep when it involves interpreting a buyer's political position, deciding which stakeholder can champion the deal, or changing the account strategy.
The work that should stay with sales reps
The Bureau of Labor Statistics describes sales representatives as identifying customer needs, answering questions, negotiating terms, and following up after a sale. Those duties rely on product knowledge and relationship context. They are not clerical residue.
Keep customer discovery, deal strategy, negotiation, final qualification decisions, and promises about price or delivery with the accountable seller. Support staff may prepare the record or surface an overdue action, but they should not infer what a customer meant or change a commercial commitment.
Planning needs the same split. A specialist can gather inputs for an account plan and keep the document current. The rep should decide which stakeholders matter, what the buying risk is, and how to approach the next conversation.
Quote work also needs a boundary. A support specialist can populate an approved template, verify required fields, and route the document. The seller or authorized manager should approve discounts, nonstandard terms, delivery promises, and any statement that changes the commercial offer.
A workload transfer model
Start with one week of task capture for a small rep group. Record the task, minutes spent, system used, input, output, and whether the task required customer or commercial judgment. Do not ask reps to estimate the whole week from memory at the end. A lightweight daily log is more likely to catch the short updates that create the administrative load.
Classify each task into one of three lanes:
| Lane | Ownership | Examples |
|---|---|---|
| Transfer | Support staff completes the task under a written rule | CRM field updates, contact creation, activity attachment, report preparation |
| Prepare | Support staff assembles inputs; the rep approves or decides | Quote drafts, account research, stale opportunity review, follow-up task lists |
| Retain | The rep completes the work | Discovery, negotiation, deal strategy, final qualification, customer commitments |
Then choose one high frequency workflow from the transfer lane. Write its source of truth, required fields, quality check, deadline, and exception owner. The sales support productivity metrics guide explains how to turn that scope into a small operating scorecard.
Avoid starting with a target such as "give every rep seven hours back." The 7.2 hour conversion describes the survey's average manual entry share in a 40 hour example. Your recoverable time depends on current automation, record quality, sales motion, and the work reps already delegate.
Pilot the process with one rep or one territory before expanding it. A narrow pilot makes rework visible and keeps an unclear field rule from affecting the entire pipeline. It also lets the support specialist document recurring exceptions while the sales owner is still close to the work.
How to measure the handoff
Measure the workflow before and after the transfer. Four numbers are enough for an initial review:
- Rep minutes spent on the selected task each week
- Percentage of records completed by the agreed deadline
- Error or rework rate from a fixed sample
- Number of exceptions returned to the sales owner
The first number tests whether the transfer reduced seller workload. The next two protect quality. The exception count shows whether the written rule is complete or whether the support specialist is being asked to make decisions outside the role.
Review the first sample after one week, then review again after the process has run for a full month. If rep time falls but errors rise, the task moved before the rule was ready. If exceptions remain high, narrow the scope or add a decision rule. If quality holds and rep time falls, add the next task from the transfer lane.
Do not claim revenue impact from this small process review. Revenue changes for many reasons, and a workload handoff is only one input. The direct evidence is operational: less rep time on the selected task, stable completion quality, and a manageable exception queue.
A four week implementation sequence
Week 1: observe
Capture actual work for a representative set of reps. Separate time spent making a sales decision from time spent recording or preparing it.
Week 2: define
Choose one repeatable task. Write the trigger, inputs, completion evidence, deadline, access boundary, review sample, and escalation owner.
Week 3: pilot
Move a limited queue to the support specialist. Review every exception and a fixed sample of completed records. Track rework time separately.
Week 4: decide
Compare rep minutes, completion rate, errors, and exceptions with the baseline. Expand only when the rule is stable and the rep is no longer repeating the work.
Limits and source notes
The Salesforce time allocation is self-reported and global. It does not describe the workload of every role, country, company size, or sales motion. The 40 hour conversions in this article are arithmetic illustrations and are not additional survey findings.
The Salesforce announcement adds context about the survey and manual entry burden by generation. The Bureau of Labor Statistics profile is an occupational reference for core sales duties. It does not define a universal delegation policy. The transfer, prepare, and retain model is our operational interpretation of the cited categories.
Map one workflow before adding headcount
Bring a one week task log to a free consultation. We can help separate record work from seller judgment and turn the first transferable queue into a bounded role scope.