Why "sales acceleration" usually misfires outside the office.

Almost everything written about sales acceleration in the last decade was written for inside sales. Hiring formulas. Training curricula. Lead-scoring models. Tech stacks built around a CRM the rep is expected to live inside of. Useful work, much of it — and we've borrowed plenty of it ourselves. But almost none of it survives contact with a rep who drives between accounts and talks to buyers face-to-face.

The reason is simple, and it's structural. The whole playbook assumes the rep is at a desk. A field rep isn't. They've got a phone in one hand, a coffee in the other, and a customer waiting. They're not skipping the CRM because they're lazy. They're skipping it because typing eight structured fields in the cab of a truck isn't a workflow — it's a tax. And taxes get paid late, partially, or not at all.

So the "acceleration" you actually get from porting an inside-sales playbook onto a field team is small. You get a slightly better training program, a slightly cleaner lead list, and a CRM nobody updates. The thing that would actually accelerate the field team — a real, high-volume record of what's being said at every account — never shows up, because the system that was supposed to produce it was never going to work outside the office.

This guide is a rewrite. Same name as the original. Different argument. Field sales runs on different physics than inside sales, and accelerating it means starting with the physics, not the formulas.

The three physics rules of field selling.

Before you can accelerate a field motion, you have to be honest about how it actually works. Three things are true of every outside team we've worked with, regardless of vertical or DMS.

One: the rep talks all day, doesn't type.

A field rep has 8–15 conversations a day. They talk to dispatch, to the buyer, to the shop manager, to themselves in the truck between stops. Talking is the medium of the job. The act of typing — which is the only way most software captures information — is a foreign function the rep has to context-switch into. It's why typed-CRM adoption has been stuck at 20–40% after 12 months for 30 years running, and why every "easier mobile UI" project produced the same number.

Two: the signal lives in the truck, not the database.

The fleet manager mentioning a Goodyear quote in the parking lot. The shop foreman pointing at six retreadable casings. The buyer hinting they're scoping a third location next quarter. None of those signals exist in your DMS, because none of them are transactions yet. They're early. They're verbal. And they evaporate the second the rep gets in the truck to drive to the next stop — unless something captures them right there, in the medium the rep is already using.

Three: adoption is a vote, not a mandate.

You can require a rep to log in. You can't require a rep to leave a real note. The difference between a checked box and a useful capture is the rep's own decision to actually describe what happened. Every mandate-based system loses that vote, every quarter. The system that wins it is the one the rep would keep using even if you took the mandate away tomorrow.

Capture comes before every other formula.

The original Sales Acceleration Guide walked through five formulas borrowed from a well-known inside-sales playbook: hiring, training, management, demand generation, and technology. They're all defensible on their own. The problem is they all run on a hidden input — a real record of what's happening in the field — and outside teams have never had one.

Hiring decisions made off rep self-reported activity? Noisy. Training programs that can't show a rep what their top peer actually did on a similar visit? Generic. Coaching conversations built on Monday-morning recall instead of a real timeline of the week? Mostly vibes. Demand-gen funnels disconnected from what the field is hearing about buyer intent? Slower than they need to be. And a "tech stack" of acceleration tools, every one of which assumes the data going in is reliable?

None of the five formulas is wrong. They're just sitting on top of a missing layer. Once you have a real, high-volume record of field conversations — captured the way reps actually communicate, not the way the database wishes they did — every one of those formulas gets sharper. Until you have it, they're optimizing the wrong inputs.

The numbers above are the gap that matters. The 60% of reps who never adopt the typed CRM aren't a margin-of-error problem — they're most of your sales coverage operating off-system. Close that gap and the rest of the playbook becomes useful for the first time.

What an accelerated field motion actually looks like.

It's easier to show than to define. Three days, three points of view — the same day from the rep's seat, the manager's seat, and the company's seat. This is the motion every Voze customer ends up running.

The rep's day.

A rep pulls out of a customer's lot at 10:47 a.m. They just had a 20-minute conversation. The buyer mentioned they're switching brake suppliers next quarter and that two trucks need new tires by month-end. The rep has eight more stops today. They tap the 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. Drive to the next stop. The account, the product, the follow-up date, the competitor signal — all parsed out, all updated, all teed up for Tuesday. The rep didn't type a thing, and they'll sound prepared on the next visit.

The manager's day.

It's Friday afternoon. The manager has eight reps. Instead of guessing what happened this week, they open the manager view and see every visit, every competitor mention, every follow-up the team committed to. Two reps both mentioned a new competitor in the last 10 days. The manager catches it on Friday instead of next quarter — that's a coaching conversation Monday morning, not a postmortem after losing the account. The dashboard exists because the reps captured by choice, which means the signal is real.

The company's day.

The DMS knows who bought what. Voze knows what was said at the account. Connect those two and account spend dropping at a top-50 customer shows up with context attached — "rep heard them mention a competitor twice in the last 60 days" — before the quarter closes. That's not a report. That's the system the business runs on, and it's the thing no other layer in your stack can produce.

The proof point lives in the numbers Bauer Built ran. In their first 12 months on Voze, they captured 97 distinct competitive-intel signals from the field. Roughly 15% of those signals traced to new business won within 90 days — deals saved that were quietly leaving, or closed that would have gone elsewhere. The acceleration didn't come from a clever algorithm. It came from finally having a record of what the field was telling them.

Test the thesis in 90 days.

The honest way to find out whether any of this holds for your team is a small pilot you can pull the plug on. The shape that works:

• One region. Pick somewhere with a sales manager who'll be a real partner — not the place with the most fires.
• Three to five reps. Mix a top performer, a steady middle rep, and a struggler. The signal is the spread.
• 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 reason the pilot has to be small is the same reason it has to be voluntary. The answer you're testing for is whether reps would push back if you took the tool away. If yes, the rest of the rollout gets easy. If no, you haven't earned it — and better to find out in 90 days with five reps than in 18 months with the whole team.

If you want the full pilot framework — exit criteria, weekly check-ins, the one number that tells you whether it's real — there's a dedicated piece on designing a 90-day Voze pilot.