Why sales teams don't use their CRM — and what actually fixes it

Almost every B2B team owns a CRM. Almost none capture in it at the moment that matters. We found out why — and where the real fix is.

Nearly every B2B team we interviewed owned a CRM — HubSpot, Salesforce, Microsoft Dynamics, Pipedrive, Freshsales. And nearly none of them used it at the one moment a lead is actually created: the conversation itself. Notes went onto paper, into phone apps, into voice memos and photos of business cards — and the CRM got fed later, by hand, if at all.

That gap is the real story. When a sales team "doesn't use the CRM," the instinct is to blame training, discipline, or the tool. In our interviews it was almost always something simpler and more structural: the CRM is built to store data, not to capture it in the field — and the field is exactly where the data is born.

• Owning a CRM doesn't mean capturing in it. Teams with major CRMs still take notes on paper, phones and voice memos, then re-enter later.
• The mobile CRM app is a ghost town — installed, rarely opened at the event.
• Many teams run a manual "human bridge": someone re-types cards and notes into the CRM after the event — one team hands ~5,000 cards a year to an assistant; another spends 2–3 hours per event.
• The reasons are friction, not laziness: forgotten passwords, no offline access, steep setup, and a capture moment that's noisy, mobile and tired.
• The cost is invisible: incomplete records, decaying data, and a pipeline managers can't fully trust.
• The fix isn't a better CRM — it's closing the capture gap in front of it.

Why don't sales teams use their CRM at the moment it matters?

Because a CRM is designed to store, organise and report on data — not to capture it quickly in a noisy room, on a phone, at the end of a long day. Every interviewee owned a capable CRM and still reached for something else in the moment.

One had a mobile CRM but had forgotten the password and noted it didn't work offline. Another admitted he'd "assumed the CRM could do it, but never learned how." Several used their CRM only for management reporting or mass email — never for capturing what was actually said in a conversation. The mobile app, in practice, stayed closed. Under pressure, people reach for the fastest, least awkward tool available, and a full CRM is rarely it.

The CRM is great at storing. It's just bad at capturing.

This is the distinction that matters, and it's why "the team won't use the CRM" is the wrong frame. For storing records, managing a pipeline, running reports and forecasting, CRMs like HubSpot, Salesforce, Dynamics and Pipedrive are excellent — that is what they are built for. Capturing a fast, messy, in-person conversation the second it happens is simply not the same job.

Treat a storage-and-reporting system as a field-capture tool and you guarantee the gap we kept seeing: data is created in the conversation, held in someone's notes and memory, and only much later — if ever — makes it into the system that is supposed to hold it.

The hidden cost: the "human bridge" into the CRM

Here is what fills that gap in practice. In many organisations, the connection between an event and the CRM is not software — it is a person doing manual data entry.

We collect thousands of cards a year, and someone has to type them all in afterwards.

Business-development lead · professional services

One business-development lead hands roughly 5,000 collected business cards a year to an assistant to enter. A marketing team writes post-event reports from notebooks and card photos. A BD professional in IT services named the two-to-three hours of re-typing each event's contacts into HubSpot as her single biggest pain point. Others described a relay — paper to spreadsheet to a colleague who forwards it into Salesforce — or a shared messaging group where teammates copy out each other's notes by hand.

Why "just train the team" doesn't fix it

Because the failure isn't knowledge — it's the moment. You can train a team thoroughly and still watch them revert to a notebook the instant they are on a busy show floor. One interviewee had used a CRM fully, with training, at a previous employer — and at his current one used it only superficially. Another simply never learned features he assumed existed.

When the capture moment is stressful, mobile and time-boxed, people default to whatever is fastest and least disruptive. Training can't beat a bad moment. If using the CRM in the field is slower than scribbling a note, the note wins every time.

What actually fixes it: close the capture gap, don't replace the CRM

The fix is not to rip out the CRM — it works for what it is for. The fix is to add a fast capture layer in front of it: capture the conversation in seconds in the moment (a photo, a voice note, a line of text), structure it automatically into a contact, key points and a next step, and hand clean, complete data to the CRM — so no one has to be the human bridge.

That is the difference between fighting CRM adoption and removing the reason it fails. The CRM keeps doing what it is good at — storing and reporting. The capture simply stops depending on a tired person's memory and a colleague's spare afternoon.

What good capture looks like — before the CRM

• In the moment — seconds during or right after the conversation, not days later.
• Mobile and forgiving — works in a noisy room, ideally offline.
• No re-entry — never re-typed into a second system by hand.
• Structured — produces a contact, key points and a next step, not a loose scrap.
• Unobtrusive — doesn't interrupt the conversation or make the other person uncomfortable.
• CRM-ready — feeds the CRM clean, complete data instead of a backlog of cards.

Get those right, and "our team doesn't use the CRM" stops being a problem to manage — because the CRM finally receives what it was always missing: the conversation, captured while it was still fresh.