Fleet software is easy to overcomplicate. Every provider talks about visibility, automation, reporting, dashboards, integrations, and innovation. But for Andrew Holgate, CEO at Jaama, the real test is much simpler.

Does the software help fleet teams run safer, more controlled, more efficient operations in the real world?

That was the focus of Andrew’s recent conversation with Fleet1000, where he discussed the pressures facing fleet professionals today and what technology needs to do to genuinely help.

 

The fleet software discussion

The discussion covered compliance, connected systems, AI, customer proximity, and the future of fleet technology. But the underlying message was clear. Good fleet software shouldn’t add more complexity. It should help teams manage the complexity they already have and make the important things easier to see, act on, and evidence.

 

Key takeaways

  • - Compliance should be built into everyday fleet workflows and not treated as a bolt-on

  • - The biggest gains come when systems connect people, tasks, and decisions

  • - Reporting only matters if it helps teams act earlier and with more confidence

  • - AI has a role in fleet management, but only when it’s secure, auditable, and genuinely useful

  • - Good software is shaped by close relationships with the people using it every day

  •  

Compliance is the foundation

Andrew is clear on this point. Compliance isn’t something fleet software should treat as an extra. For fleet teams, compliance is central to the job.

Vehicles need to be safe, drivers need to be properly managed, checks need to be done on time, defects need to be followed up on, and evidence needs to be available when required.

The compliance environment around duty of care, vehicle safety, driver risk, emissions, and operational responsibility isn’t getting lighter. Fleet directors and managers are now expected to keep the operation moving while also proving that the right controls are in place, which can be a tough act to balance.

If compliance data sits in spreadsheets, inboxes, paper forms, disconnected systems, or individual knowledge, that’s a challenge.

Instead, good fleet software should build compliance into the workflow itself. If a driver completes a usual vehicle check and reports a defect, the system should make the next step clear for them.

That means they should notify the right person, the issue should be recorded, the follow-up should be clear, and if the business needs to evidence what happened later, the information should be there too.

The best compliance processes are consistent, visible, and reliable. Or, as Andrew puts it, compliance should become almost boringly reliable.

 

Good software connects workflows, not just data

Many fleet systems claim to centralise information. But Andrew’s point is that data alone isn’t enough, as the real value comes when software connects the people and workflows behind that data.

Fleet operations involve far more than the fleet team. Drivers, managers, suppliers, workshops, finance, procurement, compliance teams, and senior leaders all need different information at different times.

For example, a connected workflow could look like this:

  • - A driver reports an issue during a typical daily check
  • - The fleet team can see it right away
  • - A workshop or supplier gets the right information
  • - The vehicle status is then updated
  • - Managers can see what has been done and what’s still outstanding
  • - Senior leaders can review the bigger picture without asking someone to build another report

That’s very different from simply storing a record somewhere. Good fleet software should reduce the amount of chasing, rekeying, checking, and manual updating that happens between teams. It should make the next action clear and make ownership easier to see.

When workflows are connected, teams can move faster because they don’t need to rely on memory, inboxes, or disconnected documents to keep things moving.

 

Reporting should help people act, not just look back

Fleet teams don’t need more reports for the sake of it or to tick a box. They need information that helps them make better decisions.

A dashboard only has value if it actually helps someone understand what needs attention. That could be rising maintenance costs, repeated defects, poor utilisation, overdue inspections, supplier delays, downtime patterns, or driver risk.

For example:

  • - If a vehicle is repeatedly off the road = the system should help the team spot the pattern

  • - If maintenance spend is increasing = it should help show where the cost is coming from

  • - If compliance actions are overdue = it should make that visible before it becomes a bigger issue

  • - If utilisation is low = it should give managers evidence to question whether the fleet is structured correctly

This is where connected data becomes important. When vehicle, driver, workshop, compliance, and cost information all live in different places, the full picture is harder to see. When that information is connected, teams can make decisions with more confidence.

For Andrew, that’s where fleet software needs to keep moving. Away from passive reporting and towards action-led management.

 

AI has to earn its place in fleet

AI is now part of almost every technology conversation. But Andrew’s view is that AI in fleet management needs to be treated with discipline. It has to be secure, auditable, and useful to the people running fleets day-to-day.

That means AI shouldn’t be added simply because it sounds impressive, but to actually solve practical problems. For fleet teams, useful AI might help spot patterns, flag anomalies, surface risks, support forecasting, or help teams understand large amounts of operational data more quickly.

However, AI can’t fix poor data. It also can’t replace weak processes and it shouldn’t create uncertainty around how your decisions are made. The value actually comes when you build AI on reliable data, clear workflows, and deep fleet knowledge.

Fleet operations are full of unique nuances, so your system needs to understand the realities and every detail of your vehicles, workshops, compliance, downtime, drivers, suppliers, maintenance, cost, and risk. Without this operational context, AI risks becoming another layer of unnecessary noise.

Used properly, AI can help fleet teams move from report-led management to more proactive, action-led management. But it has to support the people making decisions, not replace the need for experience, judgement, and accountability.

 

Good technology is built close to the customer

One of Andrew’s strongest points is that technology businesses can’t lead from a distance. Fleet software has to be shaped by the people using it. That means staying close to customers, listening to where the product works well, understanding where it creates friction, and using that insight to keep improving.

Good software is built from real conversations, real processes, real problems, and real feedback. That customer proximity matters because fleet operations are busy, pressured, and often complex.

A fleet manager doesn’t need vague promises about innovation either. They need software that helps them keep vehicles compliant, reduce downtime, control cost, manage risk, and support the people involved in the operation.

That’s why sector knowledge matters.

The best software partners understand the job behind the system. They know why a missed inspection matters, why a defect process needs to be clear, why workshop visibility affects vehicle availability, why cost data needs to be accurate, and why compliance evidence can’t be difficult to find.

In Andrew’s view, that closeness to customers is what helps technology stay useful.

image (1)

Where Key2 fits in

Key2 is designed to help fleet teams bring vehicles, drivers, maintenance, compliance, costs, workshop activity, and reporting into a single connected environment.

It supports the workflows that underpin fleet control, from daily checks and defect reporting through to licence checking, compliance activities, workshop processes, cost management, and business intelligence.

That means teams can reduce manual admin, improve visibility, and build stronger evidence trails across the operation. But good software is also about the people behind it.

Jaama works closely with customers through implementation, training, support, and long-term account management, helping teams shape Key2 around the way their fleet operates.

That combination of technology, sector knowledge, and customer proximity is central to Andrew’s view of what good fleet software should be.

Want to see what connected, compliance-led fleet software could look like for your operation?

Speak to a Key2 specialist and get a clearer view of how Jaama can help your team reduce admin, improve visibility, and manage fleet activity with more control.

Speak to the team

 

Frequently asked questions

What should good fleet software do?

Good fleet software should bring vehicles, drivers, maintenance, compliance, costs, workshops, and reporting into one connected system. It should reduce manual admin, improve visibility, and help teams act earlier when something needs attention.

 

Why does Andrew Holgate say compliance is so important?

Andrew’s view is that compliance isn’t an add-on or isolated feature. It should be built into the everyday workflows that keep vehicles safe, drivers supported, actions visible, and evidence easily accessible.

 

Why are connected workflows important in fleet management?

Fleet operations involve drivers, managers, workshops, suppliers, finance teams, and senior stakeholders. Connected workflows help each person see what they need, when they need it, without relying on manual handovers.

 

What role should AI play in fleet management software?

AI should help teams spot patterns, flag anomalies, support forecasting, and act earlier. It should be secure, auditable, and based on reliable fleet data.

 

How do I know if my current fleet software is holding us back?

Common signs include duplicate data entry, spreadsheet-based reporting, missed compliance actions, poor visibility between teams, and too much time spent chasing updates manually.

 

What should fleet teams ask before choosing software?

Fleet teams should ask whether the system supports compliance evidence, reduces admin, integrates with existing tools, provides useful reporting, and adapts as the fleet changes.