Why field reps abandon CRMs, and what it would take not to

There is a meeting that happens in every commercial organisation with a field team, usually about eight months after a CRM rollout. Adoption is down. The dashboards are half-empty. Somebody proposes a refresher training, somebody else proposes making a field mandatory, and a third person says the quiet part: our reps just will not use it.

I want to argue that this is a design verdict, not a behavioural one, and that it is entirely predictable from a single property of the tool.

The exchange rate

Every tool a person uses at work has an exchange rate: what it asks of you, against what it gives back to you. Not to the organisation — to you, the person typing. A spreadsheet has a superb exchange rate; you put in numbers and it does arithmetic you would otherwise do by hand. A phone's map app has an extraordinary one; you put in an address and it saves you from being lost.

A field CRM, as usually deployed, has a terrible one. Consider what it asks a rep to do after a call: open the app, find the account, create an activity, pick a type, pick a disposition from a list somebody in marketing designed, attach the contact, write a note, set a next step, save. Call it ninety seconds if everything works, and it does not always work, because they are standing in a parking lot on one bar of signal.

Now consider what the rep gets back for those ninety seconds. Genuinely: what? The account record is now slightly more complete. Somebody two levels up can see a number on Monday. Neither of those helps the rep with the next thing they have to do, which is drive to the next office.

Twelve calls a day at ninety seconds each is eighteen minutes. That is nearly a call. You are asking a rep to give up a call a day to produce a report they will never read.

Framed like that, non-adoption is not resistance. It is arithmetic. A rep who quietly stops logging has correctly identified that the transaction is bad for them, and has decided to spend the eighteen minutes on the thing they are actually measured on.

Why mandates make it worse

The standard response is to make logging compulsory: no expense approval without activity data, a compliance number in the monthly review, a manager chasing gaps. This does raise the logging rate. It also, reliably, produces three second-order effects.

1. Batch entry. Twelve calls get logged at 17:30 on Friday from memory. The timestamps are wrong, the notes are generic, and the disposition is whichever one is least likely to generate a follow-up question. You now have data that looks complete and is not.
2. Defensive logging. Reps learn which entries produce scrutiny and which do not, and enter accordingly. The distribution of dispositions in a mandated CRM tells you more about the review process than about the territory.
3. Erosion of the manager relationship. The manager becomes the person who chases data entry. Every ride-along now opens with an administrative conversation, which uses up the part of the day that could have been coaching.

You have bought worse data at the cost of the relationship that produces good salespeople. This is not a good trade and it is the one most organisations make.

The thing that actually fixes it

Fix the exchange rate, in that order: give first.

The first thing the tool hands a rep has to be worth having before anyone asks them for anything. In field sales calling on physician offices, there is an obvious candidate, and it is the question every rep answers on Sunday night with a spreadsheet and a paper map: where am I going tomorrow, in what order, and who am I overdue with?

That question is hard. It requires knowing which providers are due against their cadence, where they all are, how long each call takes, how far apart the offices sit, and what fits in a day. A rep does it in their head, imperfectly, every week, and it takes them an hour or two. A piece of software can do it well in a millisecond. This is exactly the shape of problem software should take off a person — high computational load, low judgement content, done repeatedly.

Do that, and the exchange rate inverts. The rep opens the tool on Monday morning because the day is in it. The day is better than the one they would have built, because it is sequenced properly and it knows who is overdue. They have got their Sunday evening back.

And then logging becomes cheap

Here is the part that makes the whole thing work. Once the tool holds the plan, logging stops being data entry and becomes confirmation.

The stop already knows the practice, the provider, the date, the planned time and the reason the call was scheduled. None of that needs to be entered. What the system does not know is what happened — and that is one field, on a screen that is already open, at the stop the rep is standing outside. Ninety seconds becomes five.

There is also a motivational shift that is easy to miss. When the plan lives in the system, an unlogged call is a call the cadence still counts as missed — which means the rep's own overdue list stays wrong until they log it. The incentive to record now points the same direction as the behaviour you want, instead of against it. Nobody has to be chased into keeping their own map accurate.

Four tests for whether your tool has the right exchange rate

If you are evaluating something, or trying to diagnose why the thing you have is not being used, these are the questions worth asking. Have a real rep try each one, on a phone, rather than watching a demo.

1. Does it tell the rep something they did not already know, before it asks them for anything? If the first screen is a form, the answer is no.
2. Can a rep get tomorrow's route into their phone's map app in one action? Not "is there an integration" — can they do it, standing up, in under ten seconds.
3. Is logging a call one field or eight? Count the taps from the stop to a saved activity, including the ones for finding the account.
4. Does the rep's own view of who is overdue match the manager's? If the manager has a report the rep cannot see, the tool is a surveillance instrument with a productivity skin, and it will be treated as one.

A tool that passes those four gets used without a mandate. A tool that fails them will not be rescued by training, gamification, or a compliance metric — because none of those change the arithmetic the rep is doing in the parking lot.

The uncomfortable version of this argument: if your reps are not using the CRM, the CRM is telling you something true about itself.