At some point in the last year, someone in your organisation said something like: “We need to get better at using Salesforce.”
Maybe it was you. Maybe it was a frustrated sales manager watching their team log calls three days late. Maybe it came up in a board meeting when someone asked why the forecast numbers never quite matched reality.
Whatever the trigger, the diagnosis was the same: we’re not using the platform properly. We need more training. Better processes. Someone to own it. The team needs to lift.
It’s a reasonable conclusion. It’s also usually wrong.
The adoption problem is almost never an adoption problem.
When a team isn’t using Salesforce the way it was intended, the instinct is to look at the people. Are they trained? Are they accountable? Do they understand why it matters?
Those are fair questions. But they’re the second questions, not the first.
The first question is whether the system was actually built for the people who have to use it. Whether it reflects the way they work, or the way someone hoped they would work when they scoped the project two years ago. Whether it takes longer to log an activity in Salesforce than it does to just send the email and move on.
Because if it does, your team isn’t failing Salesforce. The implementation is failing your team.
A poorly configured CRM doesn’t announce itself as a configuration problem. It shows up as low adoption, missing data, workarounds, and a slow accumulation of distrust in anything the platform produces. The reports look off. The pipeline feels unreliable. Someone builds a spreadsheet to track what Salesforce was supposed to track, and six months later the spreadsheet is the source of truth.
None of that is a people problem. It’s a platform problem wearing a people problem’s clothes.
Most implementations are built to be delivered, not to be used.
This is the uncomfortable truth that most Salesforce partners won’t say out loud: a lot of implementations are scoped to hit a go-live date, not to drive long-term adoption.
The requirements get gathered. The features get configured. The training gets run. The project gets signed off. The partner moves on. And then, slowly, reality sets in.
The workflows made sense on a whiteboard but create friction in practice. The fields that were marked mandatory slow down the reps who are moving fast. The dashboards show data that nobody trusts because it was only ever partially filled in. The system was built for a version of your business that doesn’t quite match the actual one.
None of this is unique to you. We see it constantly. Organisations that invested seriously in Salesforce, had a reasonable implementation, and are now three years in wondering why the platform still feels like it’s working against them rather than for them.
The gap between a technically complete implementation and one that actually delivers is almost always found in the same places: processes that were configured around the platform’s defaults rather than your team’s reality, and users who were trained on what to do rather than why it matters.
The good news is that this is fixable.
You don’t need to start over. You don’t need to run a company-wide retraining programme. You don’t need to find a way to force adoption through accountability and dashboards and weekly check-ins that make everyone feel like they’re being watched.
You need someone to look honestly at what you’ve got, understand how your team actually works, and close the gap between the two.
That’s most of what we spend our time doing. Not selling new implementations, but making existing ones worth what was paid for them. Finding the friction, removing it, and rebuilding the trust between your team and the platform that was supposed to help them.
After 1,000+ projects, we know what a well-configured Salesforce environment looks like for a team that actually uses it. We also know what the warning signs look like when one isn’t. Most of the time, the distance between those two things is shorter than the people living with the problem think.
If your team isn’t using Salesforce the way you hoped, it’s worth getting a straight answer on whether the problem is the people or the platform.
In our experience, it’s usually the platform. And that’s the easier problem to solve.
