Your Salespeople Only Sell 40% of the Time
Salespeople spend under 40% of the week actually selling. Automate the repetitive admin work, keep the human relationship, and use a simple test to decide what to automate first.
設定をやめて、構築を始めよう。
AIオーケストレーション付きSaaSビルダーテンプレート。
Problem: Sales asks to hire two more people. Finance sees payroll go up while sales stay flat. Both are right, because your salespeople already spend most of the week not selling, and hiring more of them just buys more of the same paperwork.
Quick Win: You don't have a selling problem, you have a where-did-the-week-go problem. Salesforce found salespeople spend less than 30% of their time actually selling (the more generous 2026 estimate puts it near 40%), with the rest lost to updating the customer database, internal meetings, researching prospects, and email (Everstage). Automate that repetitive 60%. Leave the customer relationship alone. That one move turns a request to hire into a much cheaper fix.
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
The 60% of the Week That Isn't Selling
Here's what a sales week actually looks like when you measure it instead of assuming it.
Salesforce found salespeople spend less than 30% of their week selling. Gartner puts admin work alone at half of their time. The breakdown of the non-selling hours, drawn from Salesforce and Forrester data, is consistent enough to plan around:
| Where the week goes | Share of a typical week |
|---|---|
| Actually selling (calls, demos, negotiation) | ~30-40% |
| Admin and updating the customer database | ~20% |
| Internal meetings | ~15% |
| Researching prospects | ~15% |
| Email and inbox | ~10% |
| Other (switching between tasks, breaks) | ~10% |
Source: Landbase, citing Salesforce State of Sales and Forrester.
The number that should stop you: the teams that hit their sales targets spend about 34% of their time actually selling, versus about 23% at the teams that miss (Forrester, via Everstage). An 11-point gap in selling time separates the teams that make their numbers from the teams that don't. You don't coach that gap closed one person at a time. It's built into how the work is set up. The winning team simply protects more selling hours.
Now do the math on your own team. Ten salespeople, about 46 working weeks, 40-hour weeks, is roughly 18,400 working hours a year. The slice that's the same motion every time (database updates, logging call notes, building quotes, first-draft emails) runs around a quarter of the week. That's on the order of 4,000 to 4,500 hours a year doing work that never varies. (That figure is an illustration based on the time split above, not an outside stat, but run it against your own team and it holds.) You're paying selling salaries for filing.
Automate the Boring 60%, Protect the Closing 40%
The usual answer to this is "buy another proposal tool" or "hire two more people." Both make it worse. A new piece of software adds another place to type things in: it grows the 60%. Two new hires add two more people spending 60% of their week on admin.
The better answer is narrower, and it works: automate the repetitive work, not the relationship.
The 40% where a human sells (reading the room on a call, handling the objection nobody scripted, deciding whether to hold the line on price) is judgment. It changes every time. It's where deals are won, it's exactly the part AI is worst at, and it's the part customers most resent losing. Leave it human.
The 60% is the opposite. It's the same repetitive work over and over. The proposal rebuilt from the last proposal. The customer database updated after every call. The quote assembled from the same price list. The follow-up that should have gone out on day three and didn't. None of it needs a person. All of it is stealing selling hours from the person doing it.
The principle we run every automation decision through: if a person has done a task the exact same way twice, it's a routine, not a real job. A job needs judgment. A routine just needs a clear definition and a checkpoint. Most of what your salespeople complain about is a routine that's been mislabeled as a job and handed to someone you pay to sell.
A Simple Test: How Often, How Repeatable, How Easy to Undo
Not everything in the 60% should be automated first, or at all. Score each task three ways before you touch it. Here's the test:
| Question | What it asks | Automate first when… | Keep human when… |
|---|---|---|---|
| How often? | How frequently does this happen? | Daily or on every deal | Once a quarter, rare |
| How repeatable? | Are the steps the same every time? | Same inputs, same result | Every case is one-off |
| How easy to undo? | How cheap is it to catch and fix a mistake? | A human approves before it goes out; errors are obvious | Can't be undone, or the damage piles up unnoticed |
The rule is simple: happens often + same steps every time + easy to undo = automate now, fastest payback. A recurring proposal draft scores high on all three: it happens weekly, follows the same structure, and a human reads it before it goes out. Automate it this month.
Score low on any one of the three and the priority drops. A one-off custom price for a big strategic account (rare, and different every time) is not your first automation, it's barely your tenth. A wire transfer or a signed contract (can't be undone) keeps a hard human checkpoint no matter how often it happens.
Run your team's task list through those three questions and the order to build in writes itself. You're not automating "sales." You're automating the top few tasks on a scored list, in order, and measuring the selling hours you get back.
McKinsey's estimate for what that recovers: automating admin work can give salespeople back 15-20% of their selling time. On a ten-person team that's the selling power of one to two extra people, out of the team you already have.
What This Looks Like: The Proposal Example
Take the most common one: the proposal. Here's a recurring proposal turned from a job into a routine.
The job today: a salesperson opens last quarter's proposal, deletes the old client's name, hunts for current prices in a spreadsheet, rewrites the scope paragraph from memory, pastes in three customer examples, reformats whatever broke, and sends it 40 minutes later. Everyone does it a little differently. Quality swings with who's tired.
The routine: given the deal details (client, product, tier, how big a discount they're allowed to offer), produce a proposal in the company's standard format, with correct prices pulled from the current price list, scope wording from the approved library, the two most relevant customer examples, clean formatting, and a stop for a human to approve before it sends. Same output, produced in under a minute, identical every time, with the salesperson's judgment applied at the one moment that matters: is this the right offer for this customer?
The salesperson didn't lose the relationship. They lost the 40 minutes of formatting. That's the whole trade. Multiply it across quotes, slide decks, recap emails, and keeping the database clean, and you've rebuilt the week: more selling, same people. This is the pattern behind recurring internal work produced automatically, and it's the same logic that lets AI run a whole function instead of a single task.
Where This Breaks
Three ways it goes wrong, and they're the reason "automate the boring 60%" is a scalpel, not a chainsaw.
Automating past the point where judgment matters. The moment automation writes and sends something to a customer with no human reading it first, you've automated the relationship, the exact thing you were protecting. Klarna learned this in public: its AI cut too deep into customer support, quality dropped on the tricky cases, and the company started hiring people back. Keep the approval step on anything a customer sees or any time money moves.
The checkpoint you can't remove. Anything you can't undo, money going out, a contract signed, a discount promised, keeps a human gate forever, even if it happens constantly. The automation gets the decision ready; a person makes it. This is why so many AI projects inside companies fail: they automated the judgment along with the busywork.
Quiet drift. Automated work that nobody checks goes wrong quietly: a price gets out of date, a template breaks, and it spreads across every proposal before anyone notices. The 60% you automate still needs someone keeping an eye on it, just not someone doing it by hand. "Set it and forget it" is how a time-saver turns into a problem.
None of these are reasons to keep paying salespeople to do data entry. They're the edges of the scalpel. Automate up to the point where judgment matters, put a human on the checkpoint, and watch for drift.
Done-for-You vs. Yet Another Tool
Here's the honest fork. You can buy a proposal tool, a database-cleanup tool, an email-sequencing tool, and a research tool, four more tools, four more places to type things in, four more subscriptions, and hope your team actually uses all of them. Or you can put in one thing that produces the finished work.
The difference is what lands on the salesperson's desk. A tool gives them another screen to drive. An installed system gives them a finished proposal to approve, a clean database they didn't have to touch, and a flagged follow-up they'd have missed. One adds work disguised as a feature. The other removes it.
That's the whole idea behind the department-automation approach: we don't sell your team another tool to log into, we build the finished result into the work itself and hand it back running. What to automate comes from the how-often, how-repeatable, how-easy-to-undo test, the human checkpoints stay where the judgment is, and the selling hours come back to the people you already employ, before anyone signs off on a single new hire.
Frequently Asked Questions
How much time do salespeople actually spend selling?
Under a third to about 40% of the week. Salesforce found salespeople spend less than 30% of their time actually selling; the more generous 2026 estimate lands near 40%. The rest goes to updating the customer database (~20%), internal meetings (~15%), researching prospects (~15%), and email (~10%) (Landbase). Forrester found the split predicts results: teams that hit their sales targets spend about 34% of their time selling, versus about 23% at teams that miss.
Should I automate the whole sales job or just parts of it?
Parts. Automate the repetitive, predictable, low-risk work, database updates, first-draft proposals, building quotes, spotting missed follow-ups, and leave the real sales calls, negotiation, and judgment with the person. The test: if someone has done a task the exact same way twice, it's a routine, not a real job. If it changes every time and needs judgment, keep it human.
How do I decide which task to automate first?
Score each task three ways: how often it happens, how repeatable the steps are, and how easy it is to catch and undo a mistake. High on all three, like a weekly proposal draft a human approves before sending, automates first and pays back fastest. Rare, judgment-heavy, or hard-to-undo work keeps a human in the loop.
Won't automating admin work just let me cut jobs?
It can, but the bigger payoff is more capacity, not fewer people. McKinsey estimates automating admin work returns 15-20% of selling time, roughly one to two people's worth of selling on a ten-person team, out of the staff you already pay. You get the output of a bigger team without the payroll, and you can decide on hiring from a position of proof instead of guesswork.
Your salespeople aren't underperforming, they're under-selling, because most of their week is repetitive work mislabeled as their job. Before you approve another hire or another software subscription, get the review: which repeating tasks in your sales and operations are really just routines, ranked by how often they happen, how repeatable they are, and how easy they are to undo, with the selling hours each one gives back. We build that automation into the work and hand it back running, human checkpoints intact. See what we build for companies and what your team's week looks like when the boring 60% runs itself.
設定をやめて、構築を始めよう。
AIオーケストレーション付きSaaSビルダーテンプレート。