Most field sales apps do not fail at installation. They fail six weeks later.
Week one, everybody checks in. There is a bit of novelty; the manager is watching, and compliance looks excellent. By week six, half the team has quietly stopped, the reports have gaps in them, and the owner concludes the software does not work.
Usually the software works fine. What went wrong is something else, and it is predictable enough that you can prevent it — or reverse it if you are already in the middle of it.
Look at it from the rep’s side
Here is what the first six weeks looked like for a field rep in an average rollout.
They installed an app on their own phone because they were told to. Every morning since, they have checked in. In return, over six weeks, the following things have happened to them:
- They were marked absent once because GPS was poor inside a client’s building
- An expense claim was questioned because the location did not match what they had written
- Their manager mentioned in a review that their visit count was lower than someone else’s
And that is the complete list. Nothing else happened. No claim settled faster. No dispute resolved in their favour. No incentive attached to it.
From where they are standing, they took on a daily task and a battery cost, and the only outcomes have been negative. Of course they stopped.
This is the whole mechanism. People keep using systems that pay them back, and abandon systems that only take. It is not more complicated than that, and no amount of enforcement fixes it — enforcement is just more of the thing that caused it.
The four ways adoption decays
1. The app only ever punishes
Covered above, and it is by far the most common. If the first three consequences of the app are all negative, you have taught the team that the app is a risk to them. That lesson is very hard to unteach.
2. The first month was spent enforcing instead of fixing
In week one you will get complaints. Battery. GPS showing the wrong address. Someone who cannot find the check-in button. If those are treated as resistance rather than as bugs to be solved, the team learns that raising a problem gets them nowhere, and they stop raising problems. They do not stop having them — they just work around the app instead.
3. Nobody was actually taught the app
A download link on WhatsApp is not training. Reps learn the one screen they were told to use and never discover the rest. This is why you often see a company where everyone checks in, nobody records a visit note, and the owner assumes the feature is useless when in fact nobody knew it was there.
4. The manager stopped looking
This one is underrated. If the manager checks the dashboard daily in week one and never again by week five, the team notices within days. Nothing signals “this does not matter” faster than data that is collected and never used. Adoption follows managerial attention almost exactly.
The seats nobody is using
There is a version of this problem that is invisible unless you go looking for it: licences that are paid for and never assigned to a person at all.
Across our own customer base, a meaningful minority of paid seats have never been given to an employee. The company bought for the team they planned to have, or for the team they had before a few people left, and the seats have simply sat there.
That is money leaving the business every month for nothing, and it is almost always a symptom rather than a cause. An account with unassigned seats is usually an account where the rollout stalled partway through.
If you are paying for field software right now, this is worth five minutes: count the licences you pay for, count the people actually using them this week, and see whether those two numbers match.
How to diagnose it in your own account
Three checks, all of which you can do from your dashboard today.
Check one: the trend, not the total. Compare daily check-ins in week one against the most recent week. A total looks fine. A trend tells you the truth.
Check two: who stopped. Adoption rarely decays evenly. Usually it is concentrated — one territory, one manager’s team, or the reps on older phones. That pattern tells you the cause. If it is one manager’s team, it is a management problem. If it is one territory, it is probably network. If it is scattered by handset, it is technical.
Check three: what they never used. Look for features nobody has touched in a month. That is almost never a feature nobody needs. It is a feature nobody was shown.
A 30-day recovery plan
If adoption has already fallen, this is the sequence that works. It is deliberately not an enforcement plan.
Week 1 — ask, do not instruct. Call five reps who have stopped. Not to tell them to restart, but to ask what got in the way. You will get a real answer from at least three of them, and it will usually be one of the four causes above. Say nothing about compliance in these calls.
Week 2 — fix the technical complaints and say so publicly. Whatever came out of those calls, fix what can be fixed and tell the whole team you fixed it because they raised it. This one action does more for adoption than any policy, because it establishes that raising a problem produces a result.
Week 3 — create the payback. Pick one thing and connect it visibly. The easiest and fastest is expense settlement: claims filed through the app get settled in a defined number of days, claims sent by WhatsApp join the normal queue. Announce it, then actually do it on time. The first person who gets paid quickly will tell everyone else.
Week 4 — restart the management habit. The manager reviews the dashboard daily and references it in conversation. Not to catch people out — to say “good week in the north territory” out loud. Attention is the signal.
Then set a target rather than a rule. Seventy percent daily compliance this month, eighty next, ninety the month after. A target gives you room to coach. A rule gives you nothing but confrontation.
The short version
Adoption does not collapse because the software is bad or because your team is difficult. It collapses because using the app costs the rep something every day and gives them nothing back.
Fix that one thing and most of the rest resolves itself. Skip it and you will be having this same conversation with the next app you buy.
Still to roll out, or rolling out again? Our field app rollout guide covers the two-week sequence that prevents this, with a ready-to-send announcement message in English, Hindi and Bengali and the eight questions your reps will actually ask. https://twib.online/field-app-rollout-guide/