Why Your Team Isn't Using Salesforce (and How to Fix It)

You paid for Salesforce. You paid someone to set it up. Six months later your best rep still runs his pipeline out of a spreadsheet, the forecast meeting is half guesswork, and the reports you pull don’t match what’s actually happening in the deals. When you ask why nobody keeps the CRM current, you get the same shrug every time: “I’ll get to it.”

You won’t fix this with another reminder or a stern email from the top. Low Salesforce adoption is almost never a discipline problem. It’s a signal that, for the people you’re asking to use it, Salesforce currently costs more than it gives back. Fix that trade and adoption follows on its own. This is how.

Adoption isn’t a willpower problem

The standard response to low adoption is to push harder. More training. A required-fields policy that won’t let a rep save a record until every box is filled. A dashboard that shames whoever hasn’t logged their calls. All of it treats the rep as the problem.

Sometimes a rep is genuinely careless. Mostly they’re rational. A salesperson is measured on closed revenue, not on CRM completeness. Every minute spent typing into Salesforce is a minute not spent selling, and if that typing doesn’t visibly help them win, they route around it. Required fields don’t change the math; they just teach reps to type “asdf” to get past the block, which is worse than a blank field because now the data is confidently wrong.

So the real question isn’t “how do I make them use it.” It’s “why is using it a bad deal for them right now.” In small and mid-sized teams, the answer is almost always some mix of these five.

Reason 1: Every field costs them something and returns nothing

Open the new-opportunity screen in your org and count the fields. In a lot of SMB orgs that started with a template and grew by accretion, there are thirty of them, half required, most of which no one has looked at in a year. To log a single deal a rep fills in amount, close date, lead source, competitor, next step, a couple of picklists somebody added for a report that’s since been abandoned, and three fields whose purpose nobody can explain anymore.

The rep does that math instantly. Two minutes of typing per deal, several deals a day, in exchange for nothing they can feel. The forecast it feeds is the manager’s tool, not theirs. So the record gets created at the last possible moment, half-filled, right before the pipeline meeting.

The fix has two halves. Cut the friction, then give them something back.

Cut first. Go through every field on the objects reps touch and justify it out loud. If you can’t name the report or automation that consumes a field, make it optional or retire it. Ruthlessly. A lead capture form with six fields gets filled; one with sixteen gets abandoned. The same is true inside the CRM.

Then automate the capture that’s left. Most of what you’re asking reps to type already exists somewhere. Call notes live in Gong, Fathom, or Otter. Emails live in their inbox. Meeting outcomes get spoken aloud on the call. A transcript-to-CRM automation writes the summary, the next step, and the follow-up tasks back to the opportunity without the rep touching a keyboard — that’s automation #4 in our ten automations every Salesforce admin should build, and it’s one of the fastest ways to make Salesforce feel like it’s working for the rep instead of the other way around. When the CRM starts filling itself in and handing back a pre-sorted lead queue every morning, the deal changes. Now it’s giving them time instead of taking it.

Reason 2: The stages in Salesforce aren’t the deal they actually run

Open your opportunity stages. If they read “Prospecting, Qualification, Needs Analysis, Value Proposition, Proposal, Negotiation, Closed” — that’s the out-of-the-box default, and there’s a good chance nobody ever changed it to match how your team really sells.

When the stages don’t map to the actual sale, reps can’t place their deals honestly. Is a verbal yes with the contract in legal “Negotiation” or “Proposal”? Nobody knows, so everyone guesses differently, and the forecast becomes noise. Faced with a set of stages that don’t describe reality, a rep does the reasonable thing and stops caring which one a deal sits in. The pipeline report turns into fiction, and once a report is fiction, no one trusts it enough to maintain it.

Make the CRM match the sale, not the other way around. Sit with your two or three best reps for an hour and have them walk you through a real deal end to end. Write down what actually moves a deal from one step to the next — the demo booked, the security review passed, the champion confirmed, the quote accepted. Those transitions are your stages. Name them in the language your team uses on calls, and define one clear exit criterion for each so there’s a right answer to “what stage is this in.” When the stages describe the sale a rep is actually running, updating them stops being a translation exercise and starts being a natural checkpoint.

Reason 3: The data is bad, so nobody trusts what comes out

Adoption and data quality feed each other, in both directions. Reps stop updating a CRM whose reports they don’t believe, and the reports get worse because reps stopped updating it. Somewhere in that loop is the moment a manager pulls a pipeline report, spots three duplicate accounts and a “$0” deal that closed last month, and quietly goes back to running the business off a spreadsheet. Once leadership works around Salesforce, the reps have all the permission they need to do the same.

You break the loop on the data side. Duplicate accounts and contacts, stale ownership, dead picklist values, deals stuck in a stage for two hundred days — these are the things that make the system feel untrustworthy, and they’re fixable. This is the same discipline we describe in our guide to auditing your data: find the specific dimensions where the data is wrong, fix those, and put a validation rule at the one point that matters rather than a wall of them everywhere.

The key word is specific. “Improve data quality” is a project that never ends. “Merge the 400 duplicate accounts, reassign the 60 orphaned opportunities from reps who left, and add one validation rule so close dates can’t be set in the past” is a week of work with a visible payoff. Do the visible cleanup first. Cleaner data is only half of why; the other half is rebuilding enough trust that people start believing the reports at all.

Reason 4: Leadership doesn’t live in it either

This is the one nobody wants to name. If the sales manager runs the Monday pipeline review off a spreadsheet a rep emails over the weekend, every rep in the room learns the real system of record in about four seconds. Salesforce is theater; the spreadsheet is where the actual conversation happens. No amount of encouragement survives that. People do what leadership does, not what leadership says.

The fix is that leadership has to move into Salesforce first, visibly, and refuse to leave. Run the pipeline meeting off a live Salesforce dashboard, on the shared screen, every week. If a deal isn’t in the CRM, it doesn’t get discussed — not as a punishment, but because the dashboard is the only agenda. The first meeting or two will be rough because the data is thin. That roughness is the point; it’s the fastest way to make it everyone’s problem that the data is thin.

For this to hold, the dashboard has to answer the questions leaders actually ask — where’s the forecast, what’s slipping, which deals are stuck — not a wall of vanity charts. That’s the same standard we hold automations to in measuring Salesforce automation ROI: build the view leaders will genuinely run their decisions off, and the underlying records get maintained because now they visibly matter. When updating a deal is the difference between it being in the forecast or invisible to your boss, reps update the deal.

Reason 5: The training didn’t stick

Most Salesforce training is a two-hour session at go-live where an admin clicks through every screen while thirty people watch and forget. It fails for the same reason every all-at-once training fails: people can’t absorb a system they haven’t needed yet, and by the time they need it, the session is a memory.

Training that sticks is role-based, short, and delivered in the flow of the actual work. A rep needs to know how to work a lead, log a call, move a deal, and read their own pipeline. That’s it. They don’t need the reporting deep-dive the ops person needs, and cramming both into one session guarantees neither lands. Teach each role only the handful of things that role does, in fifteen-minute pieces, using their real records and not a demo sandbox.

Then reinforce it where the work happens. A short Chatter post or Slack note when a new field goes live. An in-app prompt on the screen where people get stuck. A one-page “how we use Salesforce here” that documents your actual conventions, not Salesforce’s generic ones. The goal is that the answer to “how do I do X” is always thirty seconds away at the moment someone needs it, not buried in an onboarding deck from last year.

A 30-day turnaround

You don’t fix all five at once. You sequence them so momentum builds:

• Week 1 — Cut and clean. Strip the opportunity and lead layouts down to fields you can justify. Run the duplicate merge and reassign orphaned records. Nothing rebuilds trust faster than the org visibly getting lighter and cleaner in a week.
• Week 2 — Fix the stages. Sit with your best reps, rebuild the opportunity stages to match the real sale, and write one exit criterion for each. Retire the picklist values nobody uses.
• Week 3 — Automate the capture. Ship one automation that removes typing — transcript-to-CRM, or auto-drafted next steps. Give reps their first taste of the CRM working for them.
• Week 4 — Move the meeting. Run the pipeline review off a live dashboard and keep it there. Roll out role-based micro-training tied to what each person actually does.

Thirty days won’t get you to perfect. It will flip the trade for your reps from “Salesforce takes time and gives nothing” to “Salesforce saves me typing and keeps me out of trouble with my manager,” and that flip is the whole game.

Where to start

Pick the reason that sounds most like your org and start there. If reps openly avoid it, you almost certainly have a friction problem — start with Reason 1. If the reports are the thing nobody trusts, start with Reason 3. If the honest answer is that leadership works around it too, start with Reason 4, because nothing else will hold until that changes.

If you’ve inherited an org that’s been drifting for years and you’re not sure which thread to pull first, that’s exactly the kind of rescue we do — see Salesforce special projects and org rescue. Or get in touch and we’ll spend 30 minutes looking at your actual adoption numbers and telling you the one change that will move them most, whether you hire us or not.