FieldFlowSales
FieldFlow

Choosing field sales tracking software: a checklist for US teams

Most field sales apps look the same in a demo. The differences show up on a rep's phone in week three. Here is what to check before you sign, and how to test it.

8 min read

Field sales tracking software sits between your reps' phones and your sales manager's dashboard. It records where reps went, which customers they saw and what came out of each visit. Nearly every product in the category demos well. The question is which one still works on a real rep's phone, on a real route, a month after rollout.

Start with the problem you are paying to solve

Write down the one or two outcomes that justify the purchase before you look at vendors. Typical ones for US outside sales teams:

  • Mileage reimbursement you can verify instead of approving on trust
  • Proof that planned customer visits actually happened
  • Orders captured at the counter instead of re-keyed later
  • Visibility of coverage: which accounts are getting visited, and how often

Every feature you evaluate should connect to one of these. A long feature list that doesn't is cost, not value.

GPS that keeps recording

The most common failure in this category is quiet: the phone stops recording partway through the day and nobody notices until the mileage report is short. Phone operating systems close background apps to save battery, and some Android manufacturers are aggressive about it. Ask each vendor:

  • What happens when the rep swipes the app closed?
  • What happens when the phone restarts or the battery dies mid-route?
  • Are points stored on the phone and uploaded later, or lost when there is no signal?
  • How are stationary periods handled, so a phone sitting in a store doesn't add miles?

Offline use

Rural territories, warehouses and big-box back rooms all have dead zones. Check-ins, photos and orders should save on the phone and sync when the signal returns, without the rep doing anything. Test this yourself by switching the phone to airplane mode during a demo.

Miles, dollars and US conventions

It sounds obvious, but check that the product shows distances in miles and money in dollars throughout, including in exports and reimbursement reports. Some products built for other markets handle currency well but still report distance in kilometers. That is workable with a conversion, but you should know before rollout, not after the first month of mileage claims.

Fit with your CRM and accounting

  • Can you import your customer list in bulk, with addresses turned into accurate map locations?
  • Can you get your data out, in a format you can use, without a support ticket?
  • Does it replace part of your CRM or sit alongside it, and who keeps the customer list current?

Pricing questions to settle early

  • The price per user at your actual headcount, in writing
  • What it becomes at renewal, and whether increases are capped
  • Whether onboarding, data import or integrations cost extra
  • What happens if your team shrinks mid-contract

Run a pilot on your own phones

No demo can tell you how an app behaves on your reps' phones, in your territory. Pilot with three to five reps for two to four weeks, including at least one rep with an older Android phone and one in your worst-coverage area. Compare the recorded mileage with odometer readings, check how many visits were logged, and ask the reps what they would change. Their answers predict adoption better than any feature matrix.

Where FieldFlowSales fits

FieldFlowSales records routes with a native background service that keeps running when the app is closed, saves every point on the phone before uploading, and ignores time parked at a customer. Check-ins, photos and orders work offline. Money on the web dashboard follows your organization's currency setting. Distances are currently shown in kilometers, so US teams should plan on converting (1 km is about 0.62 miles). We are happy to run a pilot on your own phones.

Related guides