Ask a sales leader how their best rep spends the week and you'll get an answer built almost entirely from selling: calls, meetings, negotiations, the close. Ask the rep, and you'll get a very different week — one where more than two-thirds of it disappears into logging a call that already happened, chasing a reply that should have arrived three days ago, and rebuilding a forecast number nobody quite trusts. The gap between those two answers is the busywork tax, and it's the single biggest lever most revenue teams never pull.
This guide is the audit we run with teams before we ever talk about piRevenue. It doesn't require our software to complete — you can run every step of it with a shared spreadsheet and a bit of discipline. What it requires is the willingness to actually measure the week instead of assuming it, because the number that comes out the other side is almost always bigger, and more expensive, than anyone expected.
Start With the Number
Start with the number sales teams already half-believe: a fully quota-carrying rep spends a minority of the working week actually selling. Directional research from Salesforce's State of Sales puts the figure at roughly 28% of a rep's week in direct selling activity — meetings, calls, negotiation — with the other 72% consumed by administrative and support work: logging activity, updating records, chasing internal approvals, hunting for the right attachment, rebuilding the forecast by hand.
72% is a big, uncomfortable number, and the instinct is to distrust it. Don't distrust your own team's version of it — go find out what it actually is on your floor, because the fix only works if it's aimed at your real number, not somebody else's benchmark.
Audit the Week
You cannot redesign a workload you haven't measured. The audit itself takes one week and costs nothing but a bit of friction.
- Pick a representative week — not the week after a product launch, not the week before quarter-end. An ordinary one.
- Ask every rep to log their time in 30-minute blocks for five working days, using a simple shared sheet: time, activity, one-line description. Nothing fancier than that; complexity kills compliance.
- Sit in on a few calls and shadow one rep for half a day. Self-reported logs undercount the busywork, because reps stop noticing it once it becomes habitual.
- Pull whatever activity data your current CRM already has — logins, record edits, timestamps between calls — and compare it to the self-reported log. The gap between the two is itself useful data.
- Don't frame this as a performance review. It isn't one. It's an audit of the system reps are working inside — frame it that way, or you'll get a sanitized week instead of a real one.
By Friday you'll have a rough but real map of where the week actually goes — the raw material the rest of this audit runs on.
Categorize: Sell vs. Busywork
Every logged block falls into one of two buckets, and the line between them is stricter than most teams draw it.
Selling is any activity where the rep is actively building or advancing a relationship with a buyer: discovery calls, demos, negotiation, a genuinely personalized follow-up, in-person visits, proposal conversations. If a human on the other end forms an opinion of your company because of what the rep just did, it's selling.
Busywork is everything else that exists to make the selling visible or trackable to the rest of the business: data entry, updating deal stages, writing up call notes from memory an hour later, chasing a colleague for a discount approval, rebuilding a pipeline export for Monday's forecast call, searching for a contract template, re-typing a message thread into the CRM so it "counts."
Two categories surprise people every time: internal admin — approvals, expense reports, CRM hygiene — is busywork even though it feels like "real work," and most pipeline review meetings are busywork unless a rep is genuinely rehearsing how they'll move a specific deal forward in the room. A pipeline review is usually just a slower, more expensive version of updating a spreadsheet.
Quantify the Tax
This is the step that changes the conversation with finance, because it turns a vague complaint about admin into a number a CFO will act on.
Take the fully loaded monthly cost of a rep — salary, benefits, tools, the works — and multiply it by the busywork percentage your audit found. That's the monthly busywork tax per rep. Multiply by headcount and you have the tax on the whole floor.
Two more numbers worth pulling alongside the cost figure: the count of quiet deals — open opportunities that went silent for more than five business days without a logged follow-up — and the delay between a deal-relevant conversation happening and it appearing anywhere the rest of the business can see it. Both are usually worse than anyone guessed, and both are direct consequences of the same tax.
Redesign the Workflow
With real numbers in hand, resist the instinct to fix this with a policy. A new CRM mandate, a stricter logging deadline, a leaderboard for hygiene — none of it survives contact with a rep who is busy actually selling. The fix has to change what the workflow demands, not how hard reps try to comply with it.
Walk the audit data category by category and ask, for each busywork item: does this need to exist as a task at all, or does it only need to exist as a record? Most of it turns out to be the second kind. A call happened; something needs to remember that it happened, structure it, and move the deal forward — but nothing requires a human to type it in by hand. Once you've separated "needs a record" from "needs a person," you've drawn the map for what gets automated and what stays human — the design principle behind agentic revenue software itself.
"The goal of the audit isn't to prove your reps are lazy. It's to prove, in your own numbers, that the workflow — not the person — was built wrong."— piRevenue Editorial
Hand the Busywork to Agents
This is where agentic revenue software earns its name. The categories that came out of your audit as pure record-keeping — logging a deal from a call or forwarded thread, drafting the follow-up on a quiet deal, updating the pipeline stage, rolling the numbers into a live forecast — are exactly the work an agent can absorb without a rep ever touching a form.
In practice, that looks like: a voice note or forwarded email becomes a structured deal automatically (auto-capture); a deal that's gone quiet gets flagged and a draft nudge is written before it's cold (agentic follow-up); the pipeline view and forecast update themselves continuously instead of waiting for a Friday ritual (live forecast). None of it requires the rep to stop and go type — it requires the system to build the record from the work they were already doing.
See piRevenue absorb your audit
Keep Humans in the Close
The audit's most important guardrail is the one it doesn't touch: everything that involves judgment, persuasion or a customer-facing commitment stays with a person. Agents draft; humans approve. Agents flag; humans decide. Agents update the number; humans still own the deal and the relationship behind it.
This isn't a compliance footnote — it's the whole point. The busywork tax is expensive precisely because it steals hours from the part of the job that can't be automated: the conversation. Give reps those hours back, and don't hand the close to a machine in exchange. You didn't hire people who are good at typing. You hired people who are good at selling.
The Busywork Audit Checklist
Print this, or copy it into your own audit doc. A completed busywork audit should be able to check every line:
- ☐ A representative week logged in 30-minute blocks across the whole team
- ☐ At least one rep shadowed for a half-day to catch what self-logging misses
- ☐ CRM activity data cross-checked against the self-reported log
- ☐ Every logged block sorted into selling or busywork, with a written definition for each
- ☐ A monthly and annual busywork-tax figure calculated per rep and for the floor
- ☐ Quiet-deal count and conversation-to-record delay measured, not estimated
- ☐ Each busywork category tagged as "needs a record" or "needs a person"
- ☐ A short list of what moves to agents first, ranked by tax saved
- ☐ A clear, written line for what never automates — the close and every customer-facing commitment
The audit takes a week to run and, for most teams, produces a number large enough to make the redesign obvious. That's the honest case for doing it before you buy anything, from us or anyone else: know your real 72% before you try to give it back.
Stop feeding the CRM. Watch it feed you.
