Fleet Turnover Monitor

Blog/

Segmenting a dealer territory by fleet age distribution

Close-up of an orange excavator's tracks outdoors in daylight.

When a sales planning manager says "territory," most dealer reporting hands them one number: average fleet age across every account in the zone. That number is almost useless for timing a replacement push. A territory with forty customer sites doesn't age evenly. Some yards turn equipment over every three years because the work is rough on iron. Others run machines into the ground because the owner hates capex. Blend those into one average and you get a figure that describes nobody's actual buying moment.

Segmenting the territory by fleet age distribution means breaking it down site by site, then grouping sites by how fast they're cycling, not by what they happen to own this quarter.

Why a territory-wide average hides the real turnover picture

Take two sites with the same average fleet age of six years. Site A has a tight cluster: every machine is five to seven years old, because the owner replaces on a schedule. Site B has a mix: two machines bought last year and three machines pushing eleven years, because the owner waits until something breaks. Same average, completely different sales conversation. Site A is predictable and you can set a calendar reminder. Site B has old iron sitting there right now that could be replaced on short notice if the right call lands.

A territory-wide number collapses both into "average age: six years" and tells the rep nothing about which one to call first. Segmentation fixes that by keeping the site as the unit of analysis instead of the territory.

Building the segments: arrival, departure, and what's still sitting there

The practical way to segment is to track three things at each site, pass over pass:

  • What showed up since the last look. New arrivals tell you the site is already in a buying cycle, and for what class of equipment.
  • What left. Departures without a matching arrival often mean a machine got sold off or moved to another job, not replaced yet.
  • What's still sitting there from several passes back. This is the group that matters most for campaign timing: equipment that has been parked at the same site across multiple quarters with no churn around it.

Once you have that per-site history, segmentation is just sorting. Frequent arrivals paired with frequent departures puts a site in the "fast turnover" bucket, and it probably isn't worth a replacement push right now since they just bought. The same old units showing up pass after pass with no churn puts a site in the "due" bucket. No visible activity at all for a year or more flags a site to check manually, not necessarily write off as dead.

This is the structure behind Fleet Turnover Monitor's quarterly deliverable: a dated turnover map per site that tracks arrivals and departures against prior passes, so the segmentation above is already done by the time it lands in a planning meeting instead of being reconstructed from a rep's notes.

This kind of segmentation produces a short list, maybe five or ten sites out of forty, where the fleet composition has stopped changing and the oldest units have been sitting that long without being swapped out. That's the list a sales planning manager hands to the territory rep ahead of the next push, instead of asking the rep to remember which yard "looked old" on the last drive-by.

Done quarterly and kept in a format that loads into the CRM against the account record, this segmentation turns into a standing view instead of a one-time project. New passes update the arrival and departure counts, sites move between buckets as their fleets age or refresh, and the "due" list stays current without anyone re-driving the territory to check.

Segmenting by fleet age distribution, not territory average, is the difference between a report that confirms what the team already suspected and one that tells them where to actually spend the next quarter's call time.

If your territory reporting still comes down to one average-age number, it's worth seeing what the site-level version looks like.