Field notes
Your sales team won’t use the CRM. That’s information, not insubordination.
Reps in a spreadsheet instead of the system is not a discipline problem. It is a signal the CRM costs them more than it gives back.
When reps keep their real pipeline in Excel, the CRM has lost a straight fight on speed. Every field you require is time they could spend selling, and most of them get nothing back for it. Mandates do not fix that. Cutting the cost and paying the rep back does.
On this page
Every so often we get called in because the sales team will not use the CRM. The reps are living in a spreadsheet, the pipeline in the system is fiction, and leadership wants to know how to make people comply. It is the wrong question. A team that keeps its real pipeline in Excel is telling you something specific, and it is worth listening to before you reach for a mandate.
Here is the read. The CRM lost a fair fight on speed. Excel wins because it is fast and it is theirs - a deal is one row, entered in the two seconds between calls. The CRM asks for twelve fields and a stage update and hands the rep nothing back for the trouble. Nobody is being difficult. They are doing the thing that lets them sell more this afternoon.
Why reps flee to the spreadsheet
Reach for the least generous explanation - the reps are lazy, undisciplined, allergic to process - and you will fix nothing, because it is not true. Salespeople are ruthless about their own time. They keep the tool that helps them close and drop the one that slows them down. When a whole team has drifted to Excel, that is not a character flaw showing up in a dozen people at once. It is a verdict on the system.
What the CRM actually costs a rep
Every required field is a small tax, paid at the worst possible moment - mid-deal, between meetings, when the rep would rather be selling. Required fields they see no payoff from are the worst kind. So they fill them in wrong, or at 5:55 on a Friday to clear the nag, and now the data is bad on top of being late.
The cost is real, and it lands on the rep. The benefit, when there is one, usually lands somewhere else - a manager’s report, a forecast, a board slide. Ask anyone to pay a cost today for someone else’s benefit tomorrow and you get exactly the effort you are seeing. It does not help that half those fields are noise; we once found a portal carrying 722 properties when about 200 were doing any work (the story is here).
Why “just use it” never works
You can mandate entry. You will get entry - the thin, wrong kind, done to clear the reminder. A CRM-police role, a compliance dashboard, a Monday review where the laggards get named: all of it raises the cost of using the system without adding a cent of benefit. So reps pay the new minimum and the data gets worse, not better. Adoption is not a willpower problem you can shame your way out of. It is a trade, and right now the trade is bad.
Make the CRM pay the rep back
The fix is to change the trade, not tighten the screws.
- Cut required fields to the few that actually drive routing and the forecast. Make the rest optional or fill them automatically. Fewer, better fields beat a wall of mandatory ones every time.
- Let the system do the typing. Enrichment, email and calendar sync, activity capture - anything the CRM can know without a human keying it in, it should. The rep should type less than they did in the spreadsheet, not more.
- Give the rep something back inside the same tool. Their pipeline, their next steps, their follow-ups queued and waiting. If the CRM saves them a tab instead of adding one, they open it without being told.
- Make Excel unnecessary, not forbidden. If the spreadsheet has a column the CRM cannot show, that is a gap in the CRM, not a fault in the rep. Close it and the spreadsheet dies on its own. The clean-up order is in how to clean up a messy HubSpot CRM, and moving off spreadsheets for good is its own job (covered here).
What good adoption actually looks like
Good adoption is boring. Nobody brings it up, because the fight is over. Reps update the record because the update helps them - the follow-up is already queued, the handoff to the next person is clean, the pipeline view is the one they plan their week from. Clean data and trust move together, which is the other half of this (we wrote about that here). You will know it worked when adoption stops being something anyone brings up. If you want an outside read on why yours is a fight, that is a fair use of a diagnostic session.
Common questions
Why won't my sales team use the CRM?
Usually because it costs them more than it gives back. Every required field is time taken from selling, and the payoff tends to go to a manager report rather than the rep. When the spreadsheet is faster and returns more, reps use the spreadsheet. That is a rational trade, not a discipline problem.
How do I get sales reps to update the CRM?
Change the trade. Cut required fields to the few that drive routing and the forecast, auto-fill everything the system can know on its own, and give the rep something useful back in the same tool - their pipeline, their next steps, their follow-ups. When updating the record saves the rep time, they do it without a mandate.
Is it bad that reps use Excel instead of the CRM?
It is a signal, not a crime. A spreadsheet beating your CRM means the CRM is slower and gives less back. Treat it as information: find what the spreadsheet does better, close that gap in the CRM, and the reps move on their own. Banning Excel without fixing the CRM just hides the problem.
Should I force CRM usage with a mandate?
Mandates buy compliance, not good data. You will get fields filled in to clear the reminder, entered fast and often wrong. That is worse than an empty field, because people trust it. Lower the cost of using the CRM and raise what the rep gets out of it, and usage follows without the enforcement.