CRM in sales: why the team still sticks with Excel.
When sales doesn't use the CRM, it's almost never the tool. It's because the system was built for reporting and not for the people who are supposed to maintain it every day. As long as contacts end up in Excel, WhatsApp and in people's heads, another training won't help. What helps is a CRM that takes work off the sales rep's plate.
What does CRM adoption in sales mean?
CRM adoption means sales maintains contacts, meetings and deals in the system because it helps them, not because it's mandatory. Only then do pipeline, reporting and forecast add up.
The tools are rarely the problem. Salesforce, HubSpot, Pipedrive or Microsoft Dynamics all do enough. What matters is whether fields, workflows and views fit real everyday selling.
The CRM is live. Three months later nobody looks at it.
The demo was convincing, the integrator paid, the team trained. The first weeks go fine. Then one rep keeps everything in a personal Excel sheet only he understands, another has her contacts in a notebook, the next keeps it all in his head until he quits.
The licences keep running. Nobody says it out loud, and in the end the system often takes the blame. With a different tool you usually end up in the same place if the road there stays the same.
Four symptoms we see in many sales teams.
We know these situations from many companies.
Data that never lands anywhere
Meetings, calls, deals and tasks happen, but they aren't maintained consistently. The CRM shows a pipeline, the real one lives in the sales rep's head. Without complete data there's no reporting that's right and no forecast anyone trusts.
Reporting nobody believes
Management needs numbers, sales delivers them somehow. Because everyone knows not everything is maintained and everyone uses the system differently, decisions end up in long forecast calls where every deal is gone through one by one.
Knowledge loss when someone leaves
A sales rep quits, and contacts, context and relationships go with them. The successor starts from zero or with poor data quality. Knowledge that belongs to the company leaves the company.
Awkward moments with customers
Whoever calls on a poor data basis reaches the customer who decided otherwise three months ago. Or promises something a colleague already meant to deliver. What sticks with the customer: nobody here knows what the others are doing.
Mandatory CRM or user CRM?
| The mandatory CRM | The user CRM |
|---|---|
| Sales sees the system for the first time in training | Sales is at the table from the start |
| Fields for management reporting | Fields the sales rep needs themselves |
| Ideal process from the workshop | Workflows from real everyday selling |
| More mandatory fields when usage drops | Automations that take typing off their plate |
| Reporting first, benefit someday | Benefit first, reporting follows by itself |
We don't start with the tool.
We start with how sales really works.
Listen
Conversations with the people who are supposed to use the CRM daily: what info do you need, what annoys you, where do you lose time?
Declutter
Fewer fields, clear views. The CRM shouldn't feel like writing a thesis.
Take work off
Automations and data from other systems, such as revenue from the ERP, so maintaining it pays off.
Let reporting run
When usage is right, pipeline and forecast are right too.
No new tool. No more training. A CRM that gets used.
A sales team has had a CRM for a year, hardly anyone maintains it. Sales leadership and management are frustrated, the next tool evaluation is already on the table.
Typically we don't touch the CRM at all in the first week. We talk to the sales reps and ask one question: what annoys you every day at work? That leads to a few clear changes and one or two automations. If the ERP needs connecting, see our page on the ERP interface.
- No more training
- No new tool
- Shared pain points found and solved
- Automations that take real work off
- Teams bring their own use cases
- Dashboards that match reality
A CRM gets used when it gives the sales rep an advantage. Reporting follows by itself.
What you usually ask us about CRM in sales.
Usually not. In most cases the problem isn't the tool but how it was configured and rolled out. Before we talk about a new system, we look at what's possible with the existing one. A switch costs a lot of money and time and often doesn't solve the actual problem.
We get a first analysis with concrete recommendations done in one to two weeks. For that we talk to the people who use the CRM every day. First visible improvements in usage usually come in the weeks after, as soon as the most annoying points are solved and the first automations are live.
We rarely see that when the solution is truly better than the status quo. People aren't against change in principle. They resist changes that make their daily work worse. When the CRM makes their day easier and takes work off their plate, they use it. That's why we ask sales first.
Depends. If it's a simple configuration question, you solve it internally in an afternoon. If it goes deeper, into the process, adoption or data quality, an outside view pays off. We don't have to consider internal politics and we ask the people who use the system directly.
Your CRM is running. Your sales team doesn't use it.
Describe your situation briefly. We'll tell you in a conversation where the lever is, so the CRM does what you bought it for.