Call the fleets closest to a rebuild, not the ones closest on the map.
Every known machine in your territory, scored each quarter on estimated age, a duty proxy and trend, with the components shown.
- Age band estimated from visible cues and condition
- Duty proxy read from site intensity
- Trend the change since the previous quarter
The call list is built from what you already know
Your call list starts from the installed-base register. It has the serial numbers, the last owner you recorded, the warranty and service history, and the parts orders that came through your own channel. For the newest machines there may be telematics too.
What it does not have is the rest of the fleet. Older machines that changed hands twice. Units sitting on a site whose owner buys parts wherever the price is best. A contractor who is working his machines much harder than the last time anyone rang him. None of that shows in the register, so the register cannot rank it.
So the list gets built the way it always has. Reps are spread across the territory by region and account size, and they call on the customers who pick up the phone. It works well enough until a fleet owner sends a machine to an independent shop for a rebuild you never heard about, or a site shows up in your parts data only after the work has been done. When the quarterly planning meeting asks why one account got the attention and another did not, the honest answer is that it was on the route.

This page describes a score meant to add a second opinion to that list. From high-resolution imagery, each machine we can see in your territory gets a rough age band, a read on how hard its site works, and a direction of travel over the quarters. You get the ranking and the three components behind it, so the list can be argued with in the meeting.
What arrives each quarter
The offer is at an early stage and is shaped with the first territories that sign up. What follows is what we are building towards and what early access customers would see.
2.1Ranked machine list
CSV or spreadsheet
One row per machine we can see, per territory, highest service opportunity first. It is meant to join to your installed-base register on a site or account ID, so the order can sit next to the records you already work from.
2.2Score components
Three columns
Age band, duty proxy and trend are shown as separate columns next to the rank. A planner can see why a machine is at the top, and can override the order where they know something the imagery cannot.
2.3Quarterly refresh
Every quarter
The list is re-run on each quarterly pass, so a site that has gone quiet drops and one that has ramped up rises. Sites the pass missed are marked as not refreshed, with the date of their last read.
How it works
Send the territory
Your service area as a boundary, or an account list with site locations.
Imagery pass
A high-resolution satellite or aerial pass over the territory each quarter.
Machines scored
Each machine we can detect is scored on an estimated age band, a duty proxy read from site intensity, and the change since the previous quarter.
Ranked list delivered
The list comes back with the score components, ahead of your planning meeting.
Where it fits
Use the list before you build the quarter's call plan. It gives you a reason for who gets called first that you can put in front of the regional manager, and it sits alongside the parts forecast rather than replacing it. Where a score disagrees with what the account manager knows, the account manager wins.
Limits
These are the ways the score can mislead you.
- L1This is not a fault signal
- The score says nothing about whether a component is failing. It ranks fleets that look closer to a rebuild or a parts spend, using age and duty only. It is a ranking, not a forecast.
- L2Duty proxy is inferred
- It comes from how busy a site looks in imagery. It is not operating hours from the machine, and a quiet-looking site can still run its machines hard.
- L3Age is a band, not a date
- Age is estimated from visible cues and condition. It is not a build date or a maintenance record, and it cannot replace the serial number.
- L4Units, not models
- Machines are scored as detected units. We do not confirm make, model or serial from the image. Matching a unit to your register is done on site or account.
- L5Resolution sets the floor
- At 0.3 m a pixel covers about a foot of ground, so small machines are only a few pixels across. Very small machines may not be separated from their surroundings.
- L6Quarterly, and a pass can slip
- Cloud or a missed tasking can leave a site's score one quarter old. The list says which sites were not refreshed.
Who it's for
Who it's for
- Service network and aftermarket planners who assign call priority to field technicians or reps.
- Aftermarket teams that want a second source of evidence next to the installed-base register.
Who it's not for
- Teams that need fault detection or predictive maintenance on a specific machine.
- Teams that need operating hours or telematics data. Those come from the machine, and this does not.
- Teams that need the exact model or serial of each machine identified from imagery.
Questions planners ask
Does it detect a specific fault?
No. The score is built from age and duty proxy, and a diagnosed failure is outside it.
What counts as duty proxy?
Visible site activity, used as a stand-in for how hard the fleet works. It is not a telematics feed.
How is age estimated?
From visible cues and condition, as a proxy. It is not a maintenance record, and it is shown as a band.
Can it identify the exact machine model?
No. It scores detected units, not a confirmed model or serial.
What happens if a site is missed in a pass?
Its score stays from the last read and is marked as not refreshed, so you know how old it is.
How do we check it against our own records?
Compare the ranking with your installed-base register and your parts and service history for the accounts you already know well. The components are shown so you can see where the score and your records disagree.
Does it plug into our CRM?
The list is delivered as a file that joins on site or account. A direct CRM feed is something to discuss during early access.
Who owns the list?
Ownership and use of the delivered list is set in the agreement before any work starts.
How is it priced?
Terms are agreed in writing before a pilot begins. Ask us and we will talk it through.
Get your territory's first score list.
Tell us the territory and how you build the call list today.