Most CRM for field sales advice starts with a feature list. Start with the truck instead. Your reps spend their day in parking lots, on shop floors and at fleet yards, and most sales systems were built for someone at a desk. If you've bought software before that the reps wouldn't use, you know what that costs. Here are six plain questions to ask about any field setup before you sign.
Why a system built for the office misses the field
A rep finishes a visit and has about a minute to decide: log it now, or do it tonight. Tonight usually wins, and tonight the details are thinner. The competitor's price the buyer mentioned turns into "talked pricing." The shop that is switching suppliers never makes it into the record.
Nobody did anything wrong. The system just asked for a laptop-sized effort in a truck-sized moment. A tool that sits in the middle of that minute has to make the rep's day easier, or the rep won't open it. That's the whole test. Adoption stays voluntary, and a team that has to be pushed into using a tool has already told you what it thinks of the tool.
If your reps still keep notes in a phone app or on a yellow pad, that's fine. Start here.
Six questions to ask about any field setup
Each one has a one-sentence answer. If a vendor can't give you one, that tells you something.
- Will a rep use it between stops without being told to? Ask a rep, not a manager. Field software vendors pitch one-tap or voice logging, so ask to see it on a phone, in a parked truck. Why it matters: a tool that needs a manager's reminder gets used on the manager's schedule, not the rep's.
- How fast can a rep capture a visit, with a thumb or by voice? Count the taps. Every extra screen is a reason to wait until tonight. Why it matters: the longer capture takes, the more it slides to the end of the day, and the end of the day is where notes go thin.
- Where does the note land, and is it on the record the same day? A note in a second app that nobody reconciles is a note your manager never sees. Why it matters: a visit that isn't on the record by the next morning is hard to act on, for the rep and for the manager.
- Can the rep see what happened on the last visit before walking in? This is what makes logging worth the effort. Reps write better notes when they know they'll read them tomorrow. Why it matters: a rep who walks in knowing what was said last time sounds like someone who remembers the account.
- Can a manager see the week without chasing reps for updates? The answer should start with the rep's own view of their accounts. Managers coach from it. It isn't a way to watch people. Why it matters: reps open a tool that shows them their own gaps first, and avoid one that only reports on them.
- What happens when a rep leaves? The accounts, the history and the notes should stay with the account, not walk out with a phone. Why it matters: a territory changes hands more often than anyone plans for, and a new rep should start from the history, not a blank page.
One more question belongs on the list for any team that works rural routes: ask what the app does when there's no signal. Don't assume the answer. Get it in writing.
Here is what question 4 looks like in practice. A rep is driving to a fleet yard on Thursday. In the lot, before walking in, they open the account and read what was said on the last visit: who they talked to, what the buyer was weighing, what the rep promised to follow up on. That takes under a minute. Then they walk in and pick up where the last conversation stopped, instead of asking the same opening questions again. Ask the vendor to run exactly that scene on a phone. If the last visit is buried three screens deep, or the note is a block of text nobody can scan, reps will skip the read, and then they'll skip the write.
If your team runs HubSpot or Pipedrive
You may not need a new system of record. Most teams in this spot already have one, and it holds the accounts, contacts and deal history the business depends on. Keep it. The question is whether the people who work outside the office feed it from the field.
Voze connects to the systems teams already run through Zapier. That includes HubSpot and Pipedrive, and we build custom connections for larger teams. Check any vendor's connection the same way: ask where a note lands after a visit, and how long it takes to get there.
Where a capture layer fits
A capture layer is the app a rep opens in the field. The visit gets recorded at the stop, and it lands in the system you already run. Voze is built for outside reps this way. Reps get a pre-call brief and a quick way to log the visit, and managers get a clear view of the week. For a smaller team without a system, Voze can be the source of truth for customer and field data. Either way, the goal is a lighter day for the rep, and the platform page shows how Voze fits in.
Say a parts rep at a truck dealer finishes a stop at a fleet shop. The shop manager mentioned a competitor's price and a truck count that dropped. The rep talks it through before pulling out of the lot, and the visit is written up before the next stop. That note is the kind of thing a parts counter or a manager can use that week. Dealers can see how this works on the heavy-duty truck page.
How to test any option in a week
You don't need a long pilot to learn most of this. Pick two or three reps, and make sure at least one of them isn't excited about new software. Give them a week of ordinary visits, and then ask three things.
- Did you use it between stops, or save it for the end of the day?
- Did you read anything from an earlier visit before walking into the next one?
- Would you keep using it if nobody asked you to?
The third answer is the one that counts. If the rep who didn't want another app says yes, you've found something. If only the enthusiasts say yes, you've found a tool that will need pushing, and pushing is how the last purchase went wrong.
Set the week up so it tells you something. Before it starts, write the three questions on a card and give the same card to every rep in the test. Pick ordinary days, not a week with a trade show in it. Ask each rep to keep one running tally on the card: how many visits they logged between stops, and how many they left for the end of the day. A tally on a card is crude, but it beats a feeling, and it takes a rep 10 seconds.
At the end of the week, sit down with each rep for 10 minutes, one at a time. Start with the rep who was least excited. Ask what got in the way, and let them finish. Their answer is often one specific thing: a screen that took too long, a note that vanished, a field that didn't match how they talk about the account. Those specifics are what you take back to the vendor. If the vendor can fix the one thing, good. If the vendor shrugs, you've learned how support will go after you sign.
Then ask the manager what they saw. Could they tell, in a few minutes, which accounts got visited and what came out of the visits? If they had to message reps to find out, the capture isn't reaching the record yet. That's worth fixing before you roll anything out to the whole team.
Last, compare notes between the reps and the manager. If a rep says they logged six visits and the manager can find four, find out where the other two went. That gap, not a feature list, is what separates a tool that fits your team from one that needs a project plan.
A checklist to take to your next vendor call
- Will a rep open it between stops without being told?
- How many taps, or how many seconds of talking, to capture a visit?
- Does the note reach your sales records the same day?
- Can a rep read the last visit before walking in?
- Can a manager see the week without chasing anyone?
- What stays when a rep leaves?
Ask all six, and ask your reps to sit in on the demo. They'll spot a clunky capture screen in about 30 seconds.
Take the checklist with you
Our guide for teams that run HubSpot goes through the same questions with room for notes. Get the HubSpot field sales guide.