TL;DR
Every minute a rep spends writing call notes and updating CRM records is a minute they're not selling, building relationships, or moving deals forward.
Most teams treat this as a minor overhead. It isn't. When you multiply the time it takes to track sales activity by the number of calls, the number of reps, and the cost of those reps, the number is uncomfortable. It's a real hit to sales productivity. We built a calculator so you can see exactly what it's costing yours.
The Hidden Line Item
There's a cost buried in every sales team's operating model that never shows up on a P&L.
According to Salesforce's State of Sales report, sales productivity is poor with reps spending only 28% of their working week actually selling. The rest goes to admin, meetings, and preparation. CRM data entry is the single largest category of non-selling work, with 68% of sales reps citing note-taking and CRM input as their most time-consuming task (Salesroom). A separate study found that 32% of reps spend more than an hour a day on manual data entry and activity logging alone (CRM.org).
The per-call numbers make it tangible. After a customer call, a rep needs to write up what was discussed, update the relevant CRM fields, log next steps, and draft a follow-up. Research consistently puts this at 10-15 minutes per call. For a rep running 6 calls a day, that's 60-90 minutes of admin. Every day. Five days a week. Fifty weeks a year.
Here's what that looks like for a single rep earning $120,000 OTE:
6 calls/day x 12 minutes/call = 72 minutes of daily admin. That's 6 hours per week, or 300 hours per year. At $57.70/hour (based on $120k OTE), that's $17,300 per year, per rep, spent on manual documentation instead of selling.
For a team of 10, that's $173,000. For 20, it's $346,000. The equivalent of nearly three full-time employees who generate no revenue. Ghost employees on the payroll that nobody budgeted for.
And this assumes every rep actually does it. They don't. 37% of sales staff admit to fabricating CRM data because the burden of manual entry conflicts with the pressure to hit quota (AskElephant). 75% of sales teams have less than 80% confidence in their own CRM data (Salesroom). Only 2% feel more than 90% confident. The logging tax doesn't just cost time. It produces data that nobody trusts.
Calculate Your Logging Tax
The Activity
On average, how many customer calls does a single rep take per day?
What the Number Means
The figure you just saw isn't theoretical. It's what your team is spending, right now, every year, on the manual work of turning conversations into records.
The "ghost employees" metric puts it in terms that are harder to ignore. If your logging tax is $180,000, that's the equivalent of a full-time employee whose entire job is manual CRM data entry, paid at your average rep's rate, producing zero revenue. Most teams are carrying one or two ghost employees without realising it.
And this only counts calls. It doesn't include the time spent updating records from emails, Slack messages, research sessions, or the context that never gets logged at all because the rep was already behind. The real number is higher. It's also one of the biggest contributors to weak organisational memory: the knowledge exists, it just never makes it into a system where anyone else can access it.
The Cost You're Not Counting: Lost Revenue
Salary is the visible cost. The bigger number is what that time would have generated if it was spent selling.
Take the same rep from earlier. $120,000 OTE with a 4x quota means they're expected to generate $480,000 in annual revenue. That's roughly $240/hour of revenue capacity when they're doing their actual job.
That rep is spending 300 hours per year on post-call admin. At $240/hour in revenue capacity, that's $72,000 in potential revenue lost to documentation. Per rep. Not because they're underperforming. Because they're doing data entry instead of selling.
For a team of 10, the maths gets uncomfortable fast. $720,000 in revenue capacity redirected to CRM updates. That's not a rounding error. That's a territory. That's a product line. That's the kind of number that changes a forecast.
And this is the conservative version. It assumes every non-admin hour is equally productive, which understates the real impact. In practice, the hours lost to logging are often the highest-value ones: the 15 minutes immediately after a call when the rep should be sending a sharp follow-up, not typing up notes. The 30 minutes between meetings when they could be prepping for the next conversation. The momentum that gets broken every time they switch from selling to documenting.
A Breakdown of The Cost of CRM Updates
The table below uses a single rep earning $120,000 OTE, running 6 customer calls per day, spending 12 minutes on post-call admin per call, with a 4x quota ($480,000 annual target). Scale by headcount for your team.
Metric | Per Rep | Team of 10 | Team of 20 |
|---|---|---|---|
Daily admin time | 72 min | 720 min (12 hrs) | 1,440 min (24 hrs) |
Weekly admin time | 6 hrs | 60 hrs | 120 hrs |
Annual admin time | 300 hrs | 3,000 hrs | 6,000 hrs |
Salary cost of logging | $17.300 | $173,000 | $346,000 |
Revenue capacity lost | $72,000 | $720,000 | $1,440,000 |
Ghost employees (FTE) | 0.14 | 1.4 | 2.9 |
% of working week spent on admin | 15% | 15% | 15% |
The salary cost are what you're paying sales reps to do data entry. The revenue capacity lost is what that time sales could have generated if it was spent selling. Combined, a team of 10 is looking at nearly $900,000 in direct cost and forgone revenue. Every year.
Why This Keeps Getting Ignored
Three reasons.
The cost is distributed. No single rep is spending their entire day on CRM updates. It's 10 minutes here, 15 minutes there, scattered across the day. Individually it feels minor. In aggregate, across a team, across a year, it compounds into a serious number.
It's framed as discipline, not cost. When CRM data is incomplete, the instinct is to push for better logging habits: more training, mandatory fields, manager check-ins. 71% of reps already say they spend too much time on data entry (Toutapp). Pushing harder on compliance doesn't solve a structural cost. It makes it worse by adding friction to a task people already resent.
There's no visible alternative. If the only way to get call context into the CRM is for a human to type it in, then the logging tax feels inevitable. The question isn't whether to pay it, but how to minimise it. That framing keeps the conversation inside a box where the answer is always "ask reps to be more efficient at admin."
The answer outside the box is to stop asking reps to do it at all.
What If the CRM Updated Itself?
The logging tax exists because there's a gap between where knowledge is created (on the call, in the conversation, on the screen) and where it needs to live (the CRM, the follow-up, the deal record).
Right now, humans are the bridge. They hear something, they remember it (hopefully), they switch apps, they type it in. Every step in that chain is a place where time gets spent and context gets lost.
The alternative is ambient knowledge capture: capturing what was discussed, what mattered, and what needs to happen next as a byproduct of the interaction itself. No typing. No switching apps. No relying on someone to remember to do it before the next call starts.
The CRM fills itself. The follow-up gets drafted. The context is preserved. And the logging tax drops to zero.