CRMCRM AdoptionSmall BusinessAI

Why won't my team use the CRM?

JUL 18, 2026·9 min read·Alex Boquist

The honest answer to 'why won't my team use the CRM,' from a founder with no CRM to sell you. It is not a discipline problem, and no amount of training, gamifying, or executive buy-in fixes it. The tool is asking for something humans do not reliably give. Here is the reframe, and what to demand instead.

Your team will not use the CRM, and it is not because they are undisciplined. It is because you bought a machine that only works if everyone stays disciplined forever. That was never going to happen, and it is not their fault. The CRM was designed to run on a human input it can never actually count on, and you are watching that design meet reality.

That is the whole answer. The rest of this is why it is true, why every fix you have been sold treats the wrong thing as broken, and what you can demand instead.

The problem is real, and it is expensive

First, so you know you are not imagining it and not alone. About one-third of CRM projects fail, an average across a dozen analyst reports whose individual estimates run anywhere from 18 to 69 percent (Harvard Business Review, citing CIO Magazine). Forrester puts it at 49 percent of CRM projects failing to hit their objectives, with people-related issues like poor adoption behind a big share of that (Forrester Research, via Cynoteck). And the adoption gap is not a rounding error at the top: fewer than 40 percent of organizations get end-user adoption above 90 percent (Destination CRM, via Cynoteck). The author of that HBR piece adds his own field observation, which will sound familiar: ask executives whether the CRM actually helps the business grow, and the failure rate feels closer to 90 percent.

You know the shape of it without the numbers. The deal board is accurate for about a week after the kickoff meeting, when everyone is fresh and the consultant is still in the room. By the next quarter it is a museum. Stages that stopped moving months ago. Contacts who left their jobs. A "hot" lead nobody has touched since spring. The board is not lying on purpose. It is just showing you the last day anyone had time to feed it.

Notice what every answer to this question tells you to do

Search this exact question and read the advice. Train the team harder. Get executive buy-in. Gamify it with leaderboards and points. Hire a dedicated CRM admin. Run a change-management program. Simplify the fields, then re-train, then follow up on the re-training.

Every one of those helps a little, and I want to be fair about that. Cleaner fields lower the tax. A manager who checks the board makes people update it. A good admin catches rot before it spreads. At the margin, all of it works.

But look at what they have in common. Every single fix points at your people. The tool is assumed to be fine, and the humans are the defect to be corrected through enough pressure, incentive, or oversight. So here is the quiet part none of those articles will say: if a tool only works when humans stay perfectly disciplined, the tool is asking for something humans do not reliably give. Especially this ask. The person who is supposed to update the record is the same person doing the actual work, and the update is a tax on the work. You are asking your best closer, mid-slammed-week, to stop and testify about the call they just finished, instead of making the next one. They will choose the next call every time. They are right to.

The real diagnosis

Here is what a CRM actually is, underneath the features. It is testimony-based software. It only knows what a human stops to tell it. Every stage, every note, every "next step" is a statement someone made after the fact, by hand, on top of everything else they had to do that day. The CRM does not witness your business. It waits for depositions.

And testimony rots the instant people get busy, which is always. Not because anyone is lazy. Because testimony is a second job layered on the first one, and the first one always wins when the week gets hard, which is exactly the week the record matters most. This is why more discipline is not the fix. Discipline is the thing the machine runs on, and it is the thing that runs out.

Now hold that against the alternative. The calls happened. The emails are sent and sitting in a thread. The bookings are on a calendar. The payments cleared. All of that is evidence, and evidence does not need anyone to remember it. It already occurred, and it already says what is going on. A record that reads that stream and derives itself from it has nothing to adopt, because nobody has to remember to log what the system already saw. The question "why won't my team use it" simply stops being askable. There is no "it" to use. There is only a picture that stays current on its own, and a team that reads it.

The honest exception

Let me give you the case where none of this applies, because it is real and the vendor articles bury it.

If you run a high-volume sales floor, twenty reps pushing hundreds of short deals a month, with a paid operations person whose entire job is keeping the pipeline clean, then the discipline can be sustained. You have bought the discipline as a full-time role. The reps live in the tool because the tool is their assembly line, and the ops person scrubs behind them. For that business, the classic CRM is genuinely the right machine, and adoption is a solved problem because someone is paid full-time to solve it.

That is the exception, not the rule. Most small service businesses, the coaching practices and law firms and consultancies I build for, do not have a full-time person whose only job is keeping the record true. The owner is still close to the work. Everyone is billable. Nobody has a spare forty hours a week to be the human keeping the database honest. For that business, "just get everyone to use it" is not a plan. It is the thing that keeps failing.

Stop trying to fix the people

So here is the move, and it is not a better CRM. It is a different premise entirely.

Stop trying to fix your team. Change what the machine runs on. Instead of a record your people maintain, use a record that maintains itself. The events already exist. Software can read them and derive the whole picture: who this client is, what stage they are actually in, what happened last, what is overdue. In the system I build, Funal, the record is computed from real events instead of typed in, and one pattern from real deployments still catches people off guard: when staff stop updating records by hand, the data gets more accurate, because it stopped depending on anyone remembering.

Then the follow-through arrives already drafted. Not a reminder that says "check in with Sarah," which still leaves you the whole job. The actual message to Sarah, grounded in her real history, waiting for you to approve or change it. You stay in charge of everything that goes out. Your team's job stops being to feed the system and starts being to read it and decide. That is a job people will actually do, because it is the job they wanted in the first place: judgment on real information, not data entry about work they already finished.

Adoption was never the goal. It was the workaround for software that could not see. Remove the blindness and the adoption problem dissolves, because there is nothing left to adopt.

Frequently asked questions

What is a good CRM adoption rate?

Most teams treat 80 percent or higher on behavioral measures, records kept complete, activity logged each week, as a realistic target, and hitting it puts you ahead of most comparable businesses, since fewer than 40 percent of organizations get past 90 percent end-user adoption (Destination CRM, via Cynoteck). But notice what the metric is measuring: how reliably your people perform an unpaid second job. A high adoption rate is a sign your team is disciplined, not a sign your business is healthy. The better question is why the record needs feeding at all.

How do I get my team to use the CRM?

The standard answers, train harder, get executive buy-in, gamify it, hire an admin, run change management, all help at the margin, and if you are stuck with a testimony-based tool you should do the boring ones: cut the fields to the few that matter, and have a manager actually look at the board. But understand what you are doing. You are raising the pressure enough to force an input the tool cannot get on its own. The moment the pressure drops or the week gets busy, the record rots again. You are not fixing the problem. You are paying its interest.

Why do CRM implementations fail?

Because the mechanism depends on human discipline that no team sustains forever, so the record decays the moment people get busy. About one-third of CRM projects fail across the analyst averages (Harvard Business Review, citing CIO Magazine), and Forrester puts it near half, with poor adoption a leading cause (Forrester Research, via Cynoteck). The deeper reason is that the tool asks the busiest people in the building to stop and testify about work they already did. The failure is not a bug in the rollout. It is the design meeting reality.

The best CRM adoption strategy is a system nobody has to adopt.

I run Funal, so read my conclusions as an argument, not a verdict. The industry figures above come from the public sources cited below, each opened and checked directly; the claims about Funal describe what runs in production today, nothing more.

Sources

Back to Journal