Display and read aloud

A CRM nobody trusted: how we turned adoption into results

The system was already there. They had invested significantly in it two years earlier, the data was entered, the licences were running. But if you walked around the office, you’d see sales reps working from personal notes, individual spreadsheets and memory. Salesforce? “That’s for the reports.” In other words: for the manager, not for themselves.

This is a pattern that occurs more often than organisations are willing to admit. A CRM implementation is successful when the system is used: not when it’s been configured.

The situation: a system without owners

The organisation in question was a commercial B2B services company. Twenty sales reps, a field team, an inside sales team and management steering on numbers that weren’t accurate: because they didn’t reflect what was actually in the pipeline.

The symptoms were recognisable:

  • Opportunities were entered late or not at all in Salesforce
  • Contact data was outdated or incomplete
  • Activities (calls, emails, visits) were rarely logged
  • The dashboard showed an optimistic picture nobody took seriously
  • New employees didn’t learn to use the system because “that’s just not how we do things here”

The brief had two parts: fix the technical configuration and ensure people actually use the system.

Sales team discussing CRM adoption and digital work processes
Photo: Unsplash

Diagnosis before solution

Before changing anything, we listened. We spoke with sales reps, team leads and the sales manager. Not to tell them what could be better, but to understand why the system wasn’t working. What we found:

The setup didn’t match the daily reality of sales reps. Too many required fields, stage names that didn’t map to how the sales process actually worked, and mobile access that was cumbersome. The system felt like extra work: rather than support.

On top of that, no clear agreements had ever been made about what should and shouldn’t go into the system. Everyone did something different and nobody was held accountable.

The approach: technology and behaviour

We addressed both layers. On the technical side, we simplified the setup: fewer required fields, stage names aligned with the team’s own terminology, a mobile-first layout and smart automation for tasks reps were already performing.

But the real work was on the human side. Together with management we formulated clear expectations: what is the minimum that gets logged in Salesforce, when and by whom? Those agreements became part of team culture: not as a control instrument, but as a shared language.

We then ran targeted sessions per team: not classroom training, but practical formats where reps could work through their own daily scenarios. What’s the first thing you do in the morning? How do you log a conversation? How do you update an opportunity? By linking the system to real situations, it became recognisable and usable.

We also introduced an “adoption dashboard”: visible to everyone: showing per employee how actively they used the system. Not punishment, but transparency. The effect was noticeable.

Result: a system the team actually uses

Twelve weeks after the restart of the programme, a clear shift was visible. Pipeline data was current. Managers could see in real-time what was happening. Sales reps started using the system proactively: not because they had to, but because it helped them.

Concrete outcomes:

  • Opportunities are now entered on average 40% faster after first contact
  • The number of logged activities per employee tripled within two months
  • Pipeline accuracy: as assessed by management: rose from “unreliable” to “useful for steering”
  • New employees are now onboarded into Salesforce as a standard part of their induction

The lesson: technology follows behaviour

A CRM implementation that’s only approached technically rarely delivers the desired result. Technology follows behaviour: not the other way around. If people don’t understand why they need to record something, or if the system is more obstacle than aid, they’ll choose the path of least resistance.

The organisations that succeed with CRM are the ones that take the human side seriously. That ask what people need, that set clear expectations and that allow time for new habits to take hold.

Does this pattern sound familiar? We’d be happy to discuss what’s happening in your situation and what’s possible.

Take the next step

A question about “A CRM nobody trusted: how we turned adoption into results”?

Tell us which situation you recognise or what you want to improve. Your message goes directly to BlazeForce.

Read how we handle your data in our privacy and cookie policy.