October 7, 2026

How to build a territory account list for equipment sales reps

Most territory lists start the same way: a spreadsheet somebody built two sales reps ago, half the accounts dead, half the fleet sizes guessed. You inherit it, you add to it, and six months later you're still working off memory when you plan your drive loop. Here's how to build one that holds up past the first quarter.

Start with what the dealership already has

Before you drive a single mile, pull everything your DMS and CRM already know about accounts in your assigned territory. That means every customer with an open parts account, every warranty claim filed in the last two years, every unit that's come through the service bay. Cross-reference against your OEM's registered-owner list if you have access to one. This gives you names, addresses, and machine counts you don't have to go find yourself.

The gap in this data is age. A DMS record tells you a contractor bought three skid steers in 2019. It doesn't tell you whether those units are getting worked hard enough to need replacing, or sitting half the year because the job dried up. That's the part a spreadsheet can't answer and a drive-by only answers once, on the day you happen to drive past.

Sort this first pass by last service date and last parts order. An account that hasn't shown up in either column for eighteen months is either buying iron from somebody else now or running equipment into the ground with no support plan. Both are worth a call, for different reasons.

Fill in the accounts the dealership record misses

The DMS only knows who's bought from you. It says nothing about the GC who just won a bid two counties over, the ag operation that leased ground this season and needs its own fleet instead of borrowing a neighbor's, or the yard that's been quietly running a competitor's orange or yellow iron for three years and has never called your parts counter once.

County permit records fill some of this in: new commercial filings, site plans, grading permits. Local trade publications and bid-award notices catch the rest, assuming you have time to read them every week on top of a full call sheet. Plenty of reps build this layer by driving the territory on a loop, noting what's parked where, and updating the list by hand. It works. It's also the first thing that slips when the quarter gets busy, and a windshield survey only tells you what's sitting in the yard on the day you drive past it, not what showed up the week before or left the week after.

Rank the list before you start calling

A fifty-account territory list with no ranking is just a phone book. Before you start dialing, sort by something that actually predicts a sale: fleet age, recent expansion activity, a competitor rig that's new to the yard, a service history that's gone cold. Call the top ten first. A list ranked by what changed recently beats one sorted alphabetically or by account size, because size tells you who's big, not who's buying.

This is also where most reps run out of road. Building the base list from DMS and CRM data is a few hours of work. Keeping it current, re-ranking it every month as fleets turn over and competitors move in, is a standing job nobody on a 35-account territory has time to do by hand every thirty days.

That's the piece Fleet Sales Leads was built around: instead of redoing the windshield survey from memory, you get a ranked lead sheet pulled from what changed at each site in your territory this month, with coordinates attached so you're not guessing which gate to pull up to. The relationship work is still on you. What changes is the list underneath it, pulled from this month's yard instead of a spreadsheet two reps passed down.

Build the base list once, from the records you already have. Then find a way to keep the ranking honest every month, because a territory account list that doesn't update is just last year's list with a new date on the file name.

If you're tired of rebuilding that ranking from memory every month, see what a dated, ranked lead sheet for your territory looks like.

Request early access

Back to the blog