Better Fleet: Decide what has to be true instead of relying on supplier promises

A fleet business senior leadership team in a boardroom.

A 10% fuel saving. Fewer collisions. Lower downtime. Hundreds of pounds saved per vehicle.

Fleet suppliers increasingly sell measurable outcomes rather than simply products, which is a positive development. But it also makes procurement more demanding, because the question is no longer simply whether a system can perform a particular function.

Experienced fleet managers need to ask something more difficult:

How much confidence should we have that the result being presented will transfer to our operation?

This isn’t about distrusting supplier claims, because the strongest procurement teams know how to deconstruct them.

Start with the baseline

A percentage improvement means very little without knowing where it started.

A fleet with high idling levels may have considerably more opportunity to reduce fuel consumption than one that has spent several years actively managing driver behaviour. Similarly, a business with fragmented accident processes could achieve substantial administrative savings from digitisation, while a fleet that already operates an efficient claims process may see a smaller benefit.

That does not make the supplier's result inaccurate. It means the starting position is part of the result.

FleetWise Success Stories illustrate this well. Lanes Group, for example, reports annual insurance and administration savings exceeding £300,000 after introducing Samsara technology. Video evidence reduced disputed liability, annual insurance premiums fell by £250,000, while digitising 111 forms generated further administration savings.

See how Lanes Group cut claims costs and administration

Those are compelling results, but another fleet should not simply ask whether Samsara could save it £300,000. The more useful question is:

Which conditions at Lanes created those savings, and how many of those conditions exist within our operation?

Separate different types of evidence

Supplier evidence becomes easier to interrogate if fleets divide it into four distinct categories.

Feature evidence shows that the product can perform the function being sold. Can the platform identify idling? Can cameras detect particular behaviours? Can the software integrate the required datasets?

Performance evidence shows that customers have achieved measurable improvements after implementation.

For example, Gigaclear reports £236,000 of savings through its relationship with Fleet Operations, including lower downtime and maintenance costs, while further savings were created by challenging repair costs, reducing end-of-lease charges and consolidating fuel-card provision. Accidents also fell by 70%.

Read the Gigaclear Success Story

That demonstrates performance, but it does not by itself prove that another fleet will achieve the same result.

Causal evidence asks why the improvement happened. Fleet technology rarely creates savings in isolation. Telematics may identify excessive idling, but it does not physically stop the engine running. A camera can identify risky behaviour, but somebody still has to intervene with the driver.

The result is often created by a combination of technology, management process, supplier support and employee behaviour.

That matters because if the customer in the case study had a highly engaged management team making daily interventions, while your own operation has little capacity to act on alerts, installing the same technology may not reproduce the same result.

Finally, transferability evidence asks whether the reference operation is sufficiently similar to your own. Fleet size matters, but so do vehicle type, duty cycle, driver profile, operational geography, internal resource, starting performance and existing technology.

A strong case study from a 2,000-vehicle distribution fleet may be useful evidence, but it may still have limited relevance to a 200-vehicle engineering operation.

Ask for the calculation behind the claim

A credible ROI figure should be interrogable.

If a supplier predicts savings of £400 per vehicle per year, the fleet should be able to understand how that number has been built. Depending on the proposition, that may mean asking:

  • What reduction in fuel or energy consumption is assumed?
  • How many incidents are expected to disappear?
  • What average collision or downtime cost has been used?
  • How many administrative hours are expected to be removed?
  • Does improved utilisation genuinely allow vehicles to leave the fleet?
  • Which assumptions depend on managers or drivers changing behaviour?

The distinction between different types of saving is especially important.

If a system saves an employee 30 minutes every week, that creates capacity. It does not automatically remove 30 minutes of payroll cost. Both outcomes can be valuable, but they should not be presented as though they are financially identical.

Watch for stacked benefits

There is also a danger of double-counting.

Suppose safer driving reduces collisions. The business case might then include lower accident frequency, lower repair cost, reduced downtime and lower insurance premiums. All of those benefits may be legitimate, but the fleet needs to make sure the same underlying saving has not been counted twice.

The same applies to productivity. If an administrative system releases fleet-team time, avoid treating every task subsequently completed in that time as an additional cash saving unless there is a clear economic basis for doing so.

Look for several outcomes, not one headline number

Strong evidence often includes a range of operational effects rather than one spectacular figure.

SMS Energy's use of FleetCheck, for example, is associated with an estimated £19,000 annual saving from better management of hire-vehicle damage, alongside improved accident reporting, auditability and visibility across maintenance, fuel and compliance information.

See how SMS Energy improved fleet visibility and control

This matters because fleet technology often creates value through several smaller improvements rather than one dramatic saving.

When assessing supplier evidence, fleet managers should therefore ask:

  • What actually changed?
  • How was it measured?
  • What else changed at the same time?
  • Which benefits were genuinely cashable?
  • Which depended on management action?
  • What would prevent our fleet from achieving the same result?

These questions turn a sales claim into something that can be tested.

Trusted supplier does not mean guaranteed outcome

Supplier credibility still matters.

FleetWise's 100 Trusted Brands in Fleet research provides a useful starting point for identifying suppliers that fleet decision-makers know and trust, while category shortlists can help narrow a crowded market.

Explore FleetWise Trusted Brands

But trust should begin due diligence, not replace it.

A credible supplier with excellent references can still be the wrong solution for a particular operating environment. The stronger procurement formula is therefore:

trusted supplier + relevant evidence + transferable operating conditions + credible financial assumptions.

Turn the supplier claim into your own hypothesis

Before moving to pilot or procurement, rewrite the supplier proposition in language specific to your fleet.

Instead of:

“The platform can reduce fuel costs by up to 15%.”

Try:

“Based on our existing consumption and driver profile, we believe this intervention can reduce fuel consumption by at least 5% within six months without materially increasing journey time or management workload.”

The second statement is much harder to sell, but much easier to test.

And that is the point.

The best supplier claims should survive scrutiny. Fleet managers should not be trying to disprove them; they should be establishing exactly what would have to be true for the promised result to become their result.

Read part two of this Better Fleet series to design a fleet trial that proves value before rollout.

Similar Stories

Back to blog