The wound every VP has.

Every VP of Sales at a distributor or dealer has the same wound. You paid for a CRM. You mandated it. Your reps either ignored it or filled it with junk. You blamed the reps. The reps blamed the tool. After a while, everyone stopped talking about it — but the visibility problem never went away.

Walk a Monday meeting at almost any industrial distributor and you'll hear the same set of questions: what did we hear last week, what's competition doing, what accounts are at risk. The answers are mostly memory and guessing, because the system that was supposed to surface them — the CRM — was never actually capturing what was happening in the field.

The standard explanation — "reps are bad at admin" — is comfortable but wrong. The reps are doing exactly what you'd expect any sane person to do when handed a tool that fights them. The problem is upstream of that. It's an architecture problem.

Why the old model was built backward.

The 30-year assumption behind CRM was simple: if you can get the rep to type into a database, you'll have data. Every distributor in the country has tried that. It doesn't work, and the failure mode is structural, not cultural.

A field rep has a phone in one hand, a coffee in the other, and a customer waiting. They've just had a 20-minute conversation about brake suppliers, fleet rates, and a possible trade-in next quarter. Typing eight structured fields into Salesforce in the cab of a truck isn't a workflow. It's a tax. So they pay the tax late, partially, or not at all — and the system fills with junk that nobody trusts.

Worse, the tool was sized for a different buyer in the first place. CRM was built for the inside-sales motion: sit at a desk, work a queue, log everything. When that pattern got bolted onto outside reps — people who drive between accounts and talk for a living — it never fit. We just kept blaming the people instead of the design.

You can see this play out in the numbers. Most CRM rollouts hit 20–40% rep adoption after twelve months, and that's with mandates. The other 60–80% of field activity — pricing pressure, competitor moves, account migrations, follow-ups committed in the parking lot — never gets captured. The visibility gap isn't a reporting problem. It's a capture problem.

What changed about voice.

The piece that finally cracked field capture isn't AI in the headline sense. It's voice. Reps will talk. They already talk — to themselves, to dispatch, to whoever picks up. They've been talking after every visit for as long as outside sales has existed. The 30-year mistake was asking them to do something different. The fix is to let them do what they already do, and have the software handle the rest.

A rep pulls out of a customer's lot. They tap an app, hit record, and talk for 30 seconds: "Just left Acme Trucking. They're switching brake suppliers next quarter, want to talk pricing. Need tires on units 4 and 7 by month-end. Follow up next Tuesday." Done. They drive to the next stop.

Under the hood, the AI parses out the account, the contact, the product, the competitor signal, the follow-up date. It updates the right records in your DMS. It tees up Acme as a priority for next week with the context loaded. The rep didn't type a thing. They sound prepared on the next visit. They keep using the tool because it makes them sound smart, not because their boss told them to.

It's worth being honest about what voice doesn't fix. It doesn't fix bad rep coverage. It doesn't fix the wrong DMS. It doesn't fix a sales process nobody's run since 2018. What it fixes — and the reason it matters — is the capture problem. Once capture is real, every downstream system gets better, because for the first time the data going in is actually a record of what happened in the field.

The order that actually works.

The mental model most software vendors push is "get adoption so management gets visibility." That order is wrong, and it's why so many of these rollouts die. The order that actually works is:

1. Build a tool the rep wants to use. The bar is brutal: it has to make their day easier on day one, not after a six-week ramp.
2. Let adoption be voluntary. If the rep would only use it under threat, the data isn't real anyway. Voluntary is the entire point.
3. Let manager visibility emerge as a byproduct. Once 80%+ of the team is voluntarily capturing 5–10x more activity, the dashboards you've been begging for show up on their own — and they reflect reality, not compliance theater.

That last step is the one VPs underrate. The pattern recognition managers want — competitor mentions rolling up across reps, account risk surfacing weeks earlier, product gaps becoming visible before they show up in lost deals — only exists when capture is high-volume and high-fidelity. You don't get there by forcing reps to type. You get there by getting out of their way.

What this means for your stack.

If you're running Salesforce, HubSpot, Microsoft Dynamics, or a homegrown CRM today — none of this is an argument to rip it out. Most Voze customers keep their CRM and stop fighting it. Here's the role each tool ends up playing once capture is real:

The CRM becomes the record of opportunity.

Pipeline stages, forecast calls, contract values — the structured stuff that already lived in your CRM stays in your CRM. The job it was actually good at is unchanged.

The DMS or ERP becomes the record of transaction.

MaddenCo, Karmak, CDK, Procede, NetSuite, Eclipse — whatever runs your business already knows who bought what. That doesn't move either.

Voze becomes the record of conversation.

What was said, by whom, at which account, with which competitor mentioned and which follow-up promised. That layer didn't exist before, because nobody was capturing it. With it, the picture finally connects: what your customers are telling you, side by side with what they're actually buying.

That third layer is the part that's been missing for thirty years. Not because nobody noticed. Because the tool to capture it didn't exist in a form reps would actually use.

How to test the thesis cheaply.

The honest answer to "is this real for us?" isn't a sales deck. It's a small pilot you can pull the plug on. The shape that works:

• One region. Pick somewhere with a sales manager who's willing to be a real partner — not the place with the most fires.
• Three to five reps. Mix your top performer, a steady middle rep, and a struggler. The signal is the spread across all three.
• Ninety days. Long enough for adoption to be voluntary, short enough that nobody's career rides on it.
• One exit criterion. If voluntary capture isn't above 70% by day 60, end it. No expansion, no "let's give it another quarter." The whole thesis lives or dies on that number.

The reason the pilot has to be small is the same reason it has to be voluntary. If the answer the pilot gives you isn't "the reps would push back if you took it away," you haven't earned the rollout. Better to find out in 90 days with five reps than in 18 months with the whole field team.