Most field sales apps don't fail on launch day. Launch day goes fine: there is training and a manager watching. The failure comes three or four weeks later, when nobody is watching any more. Orders start arriving by phone again. Visit notes get typed in at 10 p.m., all at once, from memory.
The usual explanation is that reps resist change. In our experience building BernSFA, the field sales platform we develop at BernSoftware, that is rarely the real reason. Reps are practical: if the app makes their day longer, they drop it. If it makes their day shorter, they defend it.
We have written separately about the architecture behind offline-first field software. This piece is about the people side: why reps walk away, and how a manager can see it happening before the monthly report does.
The phone call is your real competitor
When a rep decides whether to use the app, they are not comparing it with other software. They are comparing it with calling the office and saying "same as last week, plus two boxes of the large ones".
That call takes fifteen seconds and never fails. Whatever the app does, it has to beat that for the orders reps place most often. A useful exercise before rollout: write down the five things a rep does at almost every visit, then time each one in the app and on the phone. Any task where the phone wins is a task where the app will be skipped.
Watch one real visit, not the demo
Demos are run by people who know the software, on office Wi-Fi, with a tidy test customer. A visit is run by a rep who has eight more stops today.
Ride along for half a day. Don't help, just watch. Note every moment the rep hesitates, scrolls back, or says "I'll fix it later". Those moments are the backlog. They rarely show up in a requirements meeting, and they are usually cheap to fix once someone has seen them.
One frozen screen is remembered for months
Reps forgive a missing feature. They don't forgive being embarrassed in front of a customer. One order that seemed to vanish, one screen that hung while the store owner waited, and the rep starts keeping a paper notebook "just in case". Once the notebook exists, the app becomes the second copy, and second copies get filled in later or not at all.
That is why reliability under bad signal matters more for adoption than any feature on the roadmap, and why the app should always say plainly whether an order has reached the office yet.
Tracking feels like surveillance
Managers often ask for a live map of every rep. To the rep, a dot that follows them through lunch and the drive home feels like being watched, and the battery drain makes it worse: a phone that dies mid-afternoon sends the last visits back to paper.
Verifying presence at the customer, at the moment the visit starts, gives managers what they actually need, which is proof that the visit happened. It also gives reps a fair deal they can accept. In one BernSFA deployment, reworking the location logic this way cut battery use by 45%.
Nothing comes back to the rep
If the app only collects data for head office, reps experience it as extra admin. It has to give something back in the field:
- The customer's history, balance and last order before walking in.
- A clear day plan, already in a sensible order.
- Their own numbers: visits done, orders entered, how close they are to target.
When the app is the fastest way to answer "what did this customer buy last time?", reps open it without being asked.
Let reps sell it to each other
Reps trust other reps more than they trust a slide deck from head office. Start with a small group in one region, fix what they find, and let them be the ones who show the rest of the team. A rep saying "it saves me twenty minutes at the end of the day" does more for adoption than any training session.
Measure use, not logins
Logins tell you almost nothing. A rep can open the app every morning and still take every order by phone. Signals that actually show adoption:
- Where orders are entered. Orders entered during the visit, at the customer, versus in a batch in the evening.
- Which channel orders arrive through. Count phone and WhatsApp orders for the same customers. If they don't fall, the app isn't replacing anything.
- Time from visit to order. Long gaps usually mean the order was written on paper first.
- Notebooks. Ask. Reps will tell you if they still keep one.
Look at these per rep and per region in the first month. A problem caught in week two is a conversation; caught in month three, it is a relaunch.
What adoption looks like
The goal is reps entering orders at the customer, not in the evening. At Tekmak İstif Makinaları, a material handling company using BernSFA, the team put it this way:
"With BernSFA we track our field sales team's visits, orders and collections in one place. The team adopted it quickly, and they are always there when we need support."
Takeaways
- The app's real competitor is the phone call; make the common orders faster than calling.
- Watch real visits, not demos, and fix the hesitations you see.
- Protect the rep from embarrassment in front of customers; that is where trust is won or lost.
- Verify the visit, don't track the person.
- Measure where and when orders are entered, not how often people log in.
Planning a project like this?
Plan it in 10 steps