At 500 vehicles, the feature list is the least useful thing to compare. Every serious supplier at this end of the market does live tracking, driver behaviour scoring, maintenance scheduling, and reporting. Put three of them side by side and the tick boxes will look nearly identical.
What separates them is whether the thing works once it is deployed across your business: whether it can mirror how you are actually organised, whether it fits your existing systems without a project, whether it covers the vehicles you hire as well as the ones you own, and whether anyone is accountable when a depot quietly stops using it.
This guide covers the criteria that matter at that scale, the questions worth asking in a demo, and the mistakes that only show up once you are past a few hundred vehicles.
What actually changes at 500 vehicles
Most fleet software is evaluated as though scale were a pricing question. It is not. Three things change qualitatively somewhere between one hundred and five hundred vehicles.
The fleet stops being one thing. At 500 vehicles you almost certainly run a mix: HGVs, vans, cars, trailers, and possibly plant. Different vehicles carry different obligations, different data sources, and different people responsible for them. A platform that handles one type well and the others approximately will show that gap quickly.
Nobody sees the whole fleet any more. A single fleet manager can hold twenty vehicles in their head. At 500, the operation is run by regional managers, depot supervisors, and a central team, each needing a different view of the same data. This is the single most underestimated requirement at scale.
The data becomes an input to other systems. Below a certain size, fleet software is a place you go and look. Above it, the data has to reach finance, HR, and maintenance planning without anyone exporting a spreadsheet. That turns integration from a nice-to-have into a requirement.
Our guide to fleet management covers the fundamentals that apply at any size. What follows is specific to operating at scale.
Six criteria that separate suppliers at this scale
1. Whether permissions can mirror your organisation
This is the requirement most often discovered late, and it is expensive to discover late. A regional manager should see their own vehicles and drivers, not a national list they have to filter every time. A depot supervisor should see their site. A central team should see everything, and should be able to compare sites against each other.
What good looks like: groups and sub-groups that reflect your actual structure, permissions set by role rather than per user, and reporting that can be scoped to a group without being rebuilt. Ask to see it configured for a structure like yours rather than described.
2. Whether integration is a configuration or a project
At 500 vehicles you will want fleet data reaching ERP, HR, fuel card, and maintenance systems. The question is not whether a supplier can integrate, because everyone says yes. It is whether they have done it before with the systems you actually run, and whether it is a standard connector or a bespoke build. Our guide to fleet management APIs and integrations covers what to look for technically.
What good looks like: named, existing connectors for the systems you use, a documented API for the ones they do not cover, and a straight answer about which of the two applies to you.
3. Coverage of mixed fleets, and of vehicles you do not own
Large operations accumulate vehicle types, and most also run hired vehicles, subcontracted vehicles, or grey fleet. A platform that covers your owned HGVs beautifully and nothing else leaves you managing part of the operation outside the system, which defeats the point of having one. Check coverage across every category you run, including EV transition and management if electrification is on your roadmap.
What good looks like: hardware options suited to each vehicle type, a sensible answer for short-term hire, and visibility of subcontracted movements even where you cannot fit hardware.
4. Data ownership, governance, and what happens if you leave
At this scale the platform will hold several years of location, behaviour, and personal data about your drivers. Three questions follow. Who owns it. Where it is hosted, and under which jurisdiction. And what you get back, in what format, if you switch supplier. Our guide to fleet data management covers the wider picture.
What good looks like: clear contractual data ownership, a stated hosting location, recognised security certification, and an exit provision that returns your data in a usable format rather than a proprietary one. The exit question in particular tends to produce revealing answers.
5. How rollout actually works across sites
Installing hardware in 500 vehicles is a logistics exercise, not a purchase. Vehicles are in different places, on different shifts, and cannot all come off the road at once. Getting 500 drivers to use an app is a change management exercise on top of that, and it is where most large deployments underdeliver.
What good looks like: a phased plan by site or region rather than a single go-live, installation that works around your operation, training that reaches drivers rather than only managers, and a named person accountable for the rollout who is not your account manager.
6. The support model, and who is accountable after go-live
Software is bought once and used every day. At 500 vehicles the difference between a supplier who sells you a licence and one who stays involved is usually larger than any feature gap. Six months in, someone has to notice that one region has stopped logging walkaround checks or that driver behaviour scores have drifted at one depot.
What good looks like: a named contact who knows your operation, a review cadence agreed in advance rather than on request, and clarity about whether analysis is included or chargeable.
Questions worth asking in a demo
Demos are designed to show a product at its best, usually on a clean dataset with a simple structure. These questions tend to move past that.
- Can you configure this now, in front of me, for a structure like ours? Three regions, two depots each, with a manager who sees only their region.
- Which of our existing systems do you already have a working connector for, and which would be a build?
- Show me a report for a fleet of 500 rather than the demo fleet. How long does it take to load?
- What happens with vehicles we hire for three weeks?
- If we leave in three years, what do we get back, and in what format?
- Who is accountable for the rollout, and is that the same person as our account manager?
- Six months after go-live, who notices if one depot stops using it?
The last two are the ones that most often change how a shortlist looks. It is also worth agreeing which fleet KPIs you will judge the deployment on before you sign, rather than after.
Mistakes that only show up at scale
- Buying on feature count. At this end of the market the lists converge. Features you never configure are not capability, they are cost.
- Piloting on the easiest depot. A pilot at your best-run site tells you very little. Pilot somewhere difficult, with mixed vehicles and a sceptical team, because that is where the deployment will actually be tested.
- Treating rollout as the supplier’s problem. Hardware installation is theirs. Getting 500 drivers to change how they work is yours, and it needs an internal owner with authority.
- Leaving the data question to legal at the end. Driver location data is personal data. Hosting, retention, and access should be settled during evaluation, not discovered during contract review.
- Skipping the exit conversation. It feels premature during a purchase and it is the cheapest insurance available. A supplier confident about their exit terms tends to be confident for a reason.
Several of these connect to the wider challenges fleet managers face rather than to software specifically, which is usually a sign they are the ones that matter.
How to decide
Score suppliers on the six criteria above rather than on features, weight permissions and support higher than you instinctively will, and insist on seeing the platform configured for a structure like yours before you shortlist. If two suppliers look equivalent on paper, the difference will be in rollout and in what happens afterwards, and neither of those appears in a feature matrix.
At MICHELIN Connected Fleet we work with fleets at this scale across transport and logistics and beyond, and the platform comes with a dedicated expert rather than a licence and a login: someone who reviews your data with you, notices when a site drifts, and is accountable for the outcome rather than the installation. You can see how that works in practice in our customer stories.
If you are building an evaluation framework for a fleet of this size, or you want to see the fleet management software configured against a structure like yours, then be sure to make an enquiry into our services today.
.svg)
.png?width=600&height=400&name=MCF%20Content%20Image%20(9).png)
-1-1.png?width=461&height=443&name=ses_pictograms_ecosystem%20partners_black%20(002)-1-1.png)
.jpeg?width=301&height=341&name=Untitled%20design%20(95).jpeg)
