How to Choose the Right Field Sales Software: A Buyer's Guide for FMCG Leaders

Last month a regional sales director in Lagos told me he'd spent $180,000 on a field sales platform his reps refused to open. Three months in. Adoption rate: 12%.

He's not alone.

I've watched maybe 40 FMCG companies buy field sales software over the last four years, and the pattern is depressingly consistent. The demo looks incredible. The pilot goes fine. Then rollout hits reality — patchy 3G in tier-3 towns, reps who've been selling for 20 years without a smartphone, distributors who won't share secondary data, a sales manager in head office who wants dashboards nobody in the field cares about.

So let's talk about how to actually pick the right tool. Not the shiniest one. The one your reps will still be using in month nine.

Start with the problem, not the product

Here's the thing most SaaS buyer guides get wrong. They hand you a feature checklist. Route optimization. Order capture. Attendance tracking. Reporting. E-detailing. And you tick boxes.

But features don't drive adoption. Fit does.

Before you look at a single vendor, write down — in one paragraph — what specifically is broken. Is it that you don't know which outlets your reps actually visited? Is it that secondary sales data arrives three weeks late from distributors? Is it that new SKU launches never get proper shelf placement because reps forget the planogram? Each of these problems needs a different kind of software.

I got this wrong at first myself. Early on I assumed "field sales software" was one category. It isn't. There's DMS-adjacent software built for distributor visibility. There's SFA (sales force automation) built for rep productivity. There's trade marketing software built for merchandising audits. And there's retail execution software built for perfect-store scoring. Most vendors claim to do all four. Almost none do all four well.

Pick the one problem that's costing you the most money right now. Solve that first.

The questions vendors don't want you to ask

Once you've got a shortlist, forget the sales deck. Ask these instead:

"Show me your offline mode with the wifi off. Right now, on this call." If they hesitate, or if the app crashes when reconnecting, walk away. Field reps in Karachi, Kampala or Kinshasa lose signal constantly. An app that needs connectivity to log an order is useless. Platforms built for emerging markets — Zivni's approach at zivni.com is a good reference point here — treat offline-first as the default, not a bonus feature.

"How long does onboarding a new rep take, in minutes, on the actual device they'll use?" Not the iPad in your demo. The $80 Android their reps carry. If it takes more than 20 minutes for a rep to log their first order end-to-end, you've got an adoption problem waiting to happen.

"What's your median customer's DAU-to-MAU ratio?" Daily active users divided by monthly active users. Anything below 0.6 means the software isn't part of the daily routine — it's a compliance checkbox. And compliance-driven tools always decay.

"Can I talk to a customer who churned?" Nobody asks this. Everyone should. The reasons customers leave tell you more than the reasons they stay.

"What's your API story for connecting to my ERP and my distributors' systems?" If they say "we have APIs" without specifics, dig deeper. FMCG runs on ugly integrations. SAP, Oracle, Tally, custom Excel sheets emailed at midnight. The software has to bend to that reality.

Total cost is never the license fee

A license at $15 per user per month sounds cheap until you add up what actually gets spent. Change management. Training. Hardware refreshes because the old phones can't run the new app. Integration costs. Data cleanup (this one always gets underestimated — I've seen master data projects consume 40% of a rollout budget).

A realistic all-in cost for a mid-sized FMCG rollout with 300 reps across three markets? Somewhere between $340,000 and $600,000 in year one. The license fee is often less than 30% of that. If a vendor won't have this conversation honestly, they're not the partner you want.

And honestly, this is where the best route to market for FMCG conversations always end up. The software is the easy part. The routing logic, the beat plans, the incentive structures tied to what the software measures — that's the hard part. Good vendors will push back on your process. Bad ones just say yes.

The 90-day test that predicts everything

Run a pilot. But run it in your hardest market, not your easiest. Everybody wants to pilot in the metro city with good connectivity and educated reps. Do the opposite. Pilot in the market with the worst infrastructure, the oldest reps, the messiest distributor relationships.

If the software works there, it'll work anywhere. If it fails there — which most fail — you've saved yourself an eight-figure mistake dressed up as a rollout.

Measure three things during the pilot: order accuracy versus manual baseline, time spent per outlet visit, and — this is the one everyone forgets — how many times reps call the helpdesk. High support tickets aren't a sign the vendor is responsive. They're a sign the product isn't intuitive.

One more thing. Involve two or three of your most cynical reps in the buying decision. Not the eager ones. The skeptics. The guys who've seen four systems come and go. If they nod (even reluctantly), you've probably picked the right one.

And if they don't? Listen carefully to why. They're usually right.