Sales productivity tools earn their place by taking typing off the rep

Sales productivity tools are the software a team buys so its reps spend more of the week selling: the CRM, the scheduler, the contact database, the call recorder, the sequencer, and lately an AI layer on top of all of them. Vendors sell the same category as sales productivity software. Sales productivity itself is easy to state and hard to measure. It's what a team sells for the hours it puts in, and most teams track it as pipeline or revenue per rep.

Each of these tools takes a step out of the rep's day or adds one. It might be a field to fill, a record to feed, one more login. That test sorts the category better than a feature list does. One tech sales rep ranked the tools they'd actually pay for into four tiers. The first two columns are theirs. The third is our reading.

The condition the rep put on tier two, "high ROI if you use them", carries most of the argument. A call recorder asks nothing of the rep once it's set up. A sequencer asks for the sequence, once. Nothing on the list earns its tier while it sits unopened.

Another seller disagreed with the order. ZoomInfo belonged in tier one, they said, and the scheduler could drop to three or four. The author agreed: booking a meeting by hand is easier than finding someone's contact details by hand. What they were really ranking was which chore they'd least like to do themselves.

Contact databases and list builders fail in their own ways, which we went through in sales prospecting tools. This piece stays with the tool every tier leans on, the CRM, and with the question of who ends up typing into it.

Four of the cases we researched disagree about the CRM. One decided the software was cheaper than losing a single account. The other three describe what it cost them.

The seller's line is the case for paying: "The software was cheaper than one lost account." On the spreadsheet, follow-ups slipped and brands went cold because the seller forgot to get back to them. The field-business owner saw the same chore from the other side. Their reps kept sticky notes and notecards and tried to type them in once they got home. The owner tried mobile apps, morning stand-ups, forms and text messages, and none of it was easy enough to keep up every day.

These two owners are describing one problem. For the seller, keeping the record by hand cost accounts. For the field-business owner, the reps simply wouldn't type into one. The critic's complaint is about hours of entry too. None of the four argued against keeping a record. Three of them argued about the typing and whose job it is, and the fourth never got the system working at all.

The field-business owner, whose reps opened the CRM only under threat, had run out of things to try by 2023. So they asked what everyone in the company could use with no login and no training. The answer they landed on was a phone.

They built a phone line. A rep or a crew member calls a number and answers up to ten questions the owner has picked. For a sales rep, two of them might be "What was the major objection?" and "When is the date of the followup?" The owner's point was that a question the line asks is a question that always gets answered. The answers turn into a short report, sent by email or Slack to the person who called and to management.

They could have piped the reports into the CRM. They chose not to, at least at first: "simpler is better in the beginning." The reps' side of the record was spoken, and none of it had to be typed.

A founder with a sales team took the same idea further and spent $22,000 on it, a figure that covered setup and the running cost so far. Their sales assistant is built on the company's own calendars, CRM, past calls and messages, and it handles these jobs around each call.

The founder gave no result for any of this: no close rate, no hours saved. So it's a list of jobs, and that's how to read it. Most of the jobs on it are ones a rep would otherwise type up or go looking for.

A go-to-market seller carrying Salesforce opportunities spent a quarter on what they called a mission to never update the CRM again. They called CRM admin "universally the most hated action across the entire sales industry". Their answer was a Claude agent built up from separate skills. The skill that handles the day's call log runs in seven steps.

Step six is the one worth copying. Other people rely on the CRM: the manager building a forecast, the colleague who inherits the account. A wrong amount or stage does more damage than a blank one, because nobody thinks to check it. With the stop in place the agent does the typing and the seller keeps the decision, so the seller's part of the job changes from typing to reading.

It's also a clean case of where a model fits better than a fixed rule. The input is messy, with recaps in the trash and deals mentioned in chat, and every output is one proposed change a person can check. AI vs automation draws that line in more detail. The seller claimed no hours saved, and their own write-up ends by asking what they're missing, so treat this as a method they are still tuning.

The largest sums in these cases went on implementations and reporting. A RevOps consultant took two calls in one week that show where that kind of money goes wrong.

The first call was a review of a tool stack. The stack had a dialer, enrichment, SMS and a configured CRM, and nobody could say what a rep should do in the first ten minutes after a lead comes in.

The second was a team of about a dozen sellers, with roughly $200K already committed to a CRM implementation and around $15K a month going to the implementer. Nobody could explain how the key systems and integrations worked. The consultant summed up both calls: "Tools don't fix an undefined process. They make it visible. And expensive." Deciding what the selling should look like comes first, and we made that case in sales automation.

Two other cases left a system they were paying for and went custom.

• A small-business owner in India billed under 20 lakh a year by their CRM vendor got no visits and no implementation partner. The consultant they hired failed too, and they dropped the CRM after nine months. A small firm then built them a custom CRM, in their words at half the price.
• A firm that buys small businesses is replacing a Salesforce add-on it used "essentially just" for pipeline reporting, which cost over $100k a year. The first plan was to switch to another deal CRM. They decided to build instead, with an engineer and a product manager fitting it around other projects, and it took a few months to reach a pilot with real users.

Say a head of sales comes to us with eight tools and reps who fill in the CRM from memory on Friday afternoon. We would start with two questions. What should a rep do in the first ten minutes after a lead arrives? And which of these tools does the rep have to type into? A tool that helps with the first and takes a chore off the second stays. Whatever typing is left moves to something that drafts the update and asks before it writes. Anything that exists only to produce a report is the first thing we would look at cutting, since a report can usually be pulled from a record the team already keeps.