The part of CRM that field sales teams actually touch — and the reason most rollouts stall.
Sales force automation covers the execution side of selling: call planning, visit logging, territory and beat plans, order capture in the field, targets and performance. It is a subset of CRM focused on what a field salesperson does during a day, usually on a phone, frequently without reliable connectivity.
SFA rollouts fail for a consistent reason: the app is designed for the reports management wants rather than the work the salesperson does. If logging a visit takes four minutes in a car park, it will be done from memory at the end of the week, and the data becomes fiction. Adoption is a design problem before it is a training problem.
Which customers, which days, which route. Coverage against plan is the measure of whether the territory is being worked.
Fast capture at the point of visit — a few taps, not a form. Geotagging where appropriate.
Taking the order in the field against live pricing and credit, so it reaches the ERP without re-keying.
Visible to the salesperson, not only to management. People manage what they can see.
The app must work without signal and sync when it returns. Field sales does not happen in good coverage.
A distributor rolls out SFA and reports beat plan compliance of 92 percent within three months. Field activity is clearly being captured. Sales are unchanged, and the project is judged a disappointment.
The measurement is the problem. Compliance counts visits made against visits planned — it says nothing about what happened during them. Looking at productive call rate instead shows 34 percent: two thirds of visits produce no order. Looking further, the lines-per-call figure shows reps are taking repeat orders for the same three fast movers and not introducing anything else, because the app makes reordering easy and discovery hard.
SFA that measures activity produces activity. The metrics that change behaviour are productive call rate, lines per call, new-outlet activation and range penetration — outcomes rather than attendance. The second lesson is about the app itself: if reordering takes two taps and adding a new line takes eight, the data will faithfully record reps doing the easy thing.
| Term | What it means |
|---|---|
| Beat plan | The planned route and call schedule for a field representative. |
| Call report | The record of a visit — who was seen, what was discussed, what was ordered. |
| Geo-tagging | Capturing location with a call report, so visits can be verified. |
| Productive call | A visit resulting in an order, as distinct from a visit that merely happened. |
| Secondary sales | Sales from distributor to retailer, which is the number that actually reflects demand. |
Every field management wants adds seconds to each capture. Seconds compound into non-adoption.
An app that fails without signal is an app that fails in exactly the places field sales happens.
If data goes in and nothing useful comes back, capture quality degrades quickly.
If the field manager still asks for a separate weekly spreadsheet, the system has not replaced anything.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Productive call rate | Share of visits producing an order. The honest version of compliance. | |
| Lines per call | Whether reps are selling range or taking repeat orders for the same few items. | |
| New outlet activation | Growth in distribution rather than growth in visits. | |
| Order-to-delivery fill rate | Whether what reps sell can actually be supplied. Poor fill rates train reps to stop selling range. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.