Why your CRM fails in the field — and what to run instead
Every CRM ever built assumes four things about a salesperson. Field sales breaks all four before 9am. This is what actually goes wrong, how to measure it in your own organization this quarter, and what to put in front of your CEO.
Ask a VP of Sales why CRM adoption in their field team is poor and you'll usually hear a version of "the reps are old school." That answer is comfortable and it is wrong. Field reps adopt tools instantly when those tools save them time — the scanner gun, the mobile printer, WhatsApp. What they reject is software that asks them to do unpaid administrative work in the evening so a dashboard looks complete.
The problem is structural. CRM was designed for inside sales — a person at a desk, connected, typing, moving named opportunities through stages. Field sales is a different job with different physics.
1. The four assumptions that break
Assumption one: there is a connection
Your reps work in warehouses, basements, freight docks, rural highways and industrial parks with one bar. A CRM that goes read-only — or blank — without signal is not a system of record for the place where your commitments are actually made. What happens instead is universal: the rep writes it on paper and enters it at 9pm, or never.
Assumption two: typing is fine
A desk seller types all day anyway. A field rep is standing, holding a tablet, with a customer in front of them and eleven more stops to make. Every text field you add to a visit form is a field that gets skipped or filled with "ok." Three taps is a spec; a form is a wish.
Assumption three: the unit of work is an opportunity
In distribution, building products, dental or ag, the same customer buys again and again for fifteen years. There is no pipeline stage for "they've stopped ordering the second SKU and haven't mentioned it." The unit of work is coverage and reorder, not a deal moving through stages — and almost no CRM reports on it natively.
Assumption four: territories are a static attribute
In most CRMs a territory is a text field on the account. In reality it's the single biggest determinant of how much revenue each rep can physically produce. Territories grow by accident: an acquisition here, a departure there, a favor to a senior rep. Ten years later one rep drives 400 miles a week for 70 accounts and another has 210 inside one metro. Nobody decided that.
The result is not "bad CRM hygiene." It's an organization whose most expensive resource — people in cars — is allocated by history rather than by data, and whose customer knowledge lives in four people's heads.
2. "We already have Badger Maps" isn't an answer
Route apps are good products. If your reps use one, they've solved the daily sequencing problem: which twelve stops, in what order, with the least driving. Keep it. But notice what it doesn't touch.
A route app takes the territory as given. It optimizes movement inside a container somebody drew by hand years ago. If that container holds twice the workload of the one next to it, the app will efficiently drive your rep through an impossible week. Mapping add-ons inside a CRM have the same boundary plus a harder one: they assume connectivity and they price per seat on top of a platform fee.
Three different jobs, three different categories:
3. The 30-minute coverage audit
You don't need software to find out whether you have a problem. Export accounts with rep assignment, city or ZIP, and last 12 months' revenue. Then answer five questions.
What is the spread in account count between your heaviest and lightest rep? Above 15%, you have a design problem, not a performance problem.
How many accounts had revenue last year and no recorded visit this year? Sum their revenue. That's your exposure.
How many accounts are assigned to a rep who has left in the last 24 months? Who is actually calling them now?
Plot each rep's accounts. Do any two territories interleave — two reps driving past each other's customers? Every overlap is paid windshield time.
Ask three reps what a customer bought last quarter, without opening anything. If they can't say, your order history isn't reaching the field.
If questions one and two both come back ugly — which is the common case — the fix is sequenced: rebalance the book first, then get execution into a system. Doing it the other way around digitizes a bad map.
4. What to put in front of your CEO
Sales managers feel this problem daily; CEOs and COOs sign for it. Those are different conversations. The one that gets approved has four lines and no software features in it.
"Accounts worth $X billed last year received no visit this year."
"Before we hire rep number 21, two existing territories are drawn wrong. Here is the model."
"If our top three reps resign this year, we lose the working record of 40% of our customer base."
"$149 a month, cancel monthly, no rollout to the field required." That's a rounding error against one recovered account.
The short version
Keep your CRM for what it's good at: marketing, inside sales, the funnel. Stop asking it to run the field. Field sales needs a system that works with no signal, produces its own paperwork, carries order history to the door, and treats territory design as a quantitative decision rather than an inheritance. That's a different category of software, and until recently nobody built it properly for organizations under a thousand reps.
Start with the audit. Even if you buy nothing, you'll be the only person in your next leadership meeting with the map.
Want the audit done for you? It's free.
Connect HubSpot — you never hand us your customer list. Three business days later you get the coverage map, the workload spread, the uncovered accounts and one modeled rebalance. Customer names, contact information and CRM notes never leave your environment.
Request the free territory audit