Some sales work is essential but always the first thing dropped when people get busy. Six jobs account for most of it. Automate those, keep people on the conversations, and selling time goes back up.
Every sales team has a set of jobs that everyone agrees are important and that quietly stop happening the moment the team gets busy. Nobody decides to stop following up, or to let the CRM drift, or to skip the research before a call. It just happens, because when time is short people prioritise the urgent over the important.
These are the jobs worth automating first. Not because they are unimportant, but because they are important and humans reliably fail to do them consistently.
Where the week goes
Salesforce’s State of Sales research has found that sales reps spend only around 28% of their week actually selling. The rest goes to research, data entry, internal coordination and administration. That is the pool of time these automations draw from.
The six
1. Speed-to-lead
What it does: gets a researched, personalised first reply in front of a new enquiry in minutes, held for the rep’s approval.
What breaks without it: buyers wait hours or days and move on. Covered in depth in speed-to-lead.
2. Follow-up engine
What it does: runs follow-up sequences until there is a human answer — yes, no, or a dated “later” — rather than until the rep remembers.
What breaks without it: most deals die of silence rather than rejection. Follow-up is the first thing to lapse when a rep gets busy, and nobody notices it lapsing.
3. CRM hygiene
What it does: keeps records, stages and fields accurate by updating them from real activity — emails sent, meetings held, calls logged — instead of relying on manual entry.
What breaks without it: forecasts drift from reality, reports lose credibility, and every other automation inherits the bad data. This one underpins all the rest.
4. Prospect intelligence
What it does: compiles a short brief before each meeting — who they are, what has changed at their company, what happened in previous conversations, what to cover next.
What breaks without it: reps either spend selling hours on research, or walk into calls unprepared. Usually both, at different times.
5. Routing and handoff
What it does: assigns leads to the right person based on clear rules, with deadlines and escalation, and carries the context across when a lead moves between people.
What breaks without it: leads sit in shared inboxes, ownership is unclear, and handoffs lose everything the previous person learned.
6. Pipeline review autopilot
What it does: compiles the weekly pipeline picture — movement, coverage, stalled deals, untouched leads — before the meeting starts.
What breaks without it: the weekly review becomes an hour of people reading the CRM aloud to each other. It is usually the easiest hour on the list to get back.
How much time comes back
The working estimate AutomateSales uses is roughly 11 hours per rep per week returned once all six are running, drawn from time that typically goes to research, outreach, CRM administration and reporting. Treat that as an indication rather than a promise. The only honest baseline is your own: have the team keep a simple time log for one week before you start. It takes little effort and it tells you exactly where the hours are going — and afterwards, whether they came back.
Which to build first
Not all six at once. The right first automation is whichever addresses your binding constraint:
- If leads wait too long for a first reply, start with speed-to-lead. It is commonly the highest-return automation of the six.
- If your data cannot be trusted, start with CRM hygiene — automating on top of bad data only industrialises the problem.
- If deals stall without anyone noticing, start with follow-up.
- If reps are losing hours to research, start with prospect intelligence.
Then build one at a time, verify it works, and move to the next. That rhythm is described in audit, sprint, scale.
The guardrails that apply to all six
Every one of these automations follows the same rules: nothing is sent to a buyer without a person approving it, every action is logged, and anything can be switched off. Those rules are what let a team move faster without gambling its reputation. They are covered in guardrails that make speed safe.
Where to go next
Build versus buy explains why these are usually best built inside the tools you already use. The sales pipeline automation guide goes deeper on implementation. And AutomateSales is the practice built around exactly these six.