Whitepaper for your new fleet management software

Comparing Excel spreadsheets, reviewing quotes from individual vendors, answering questions from fleet management—and doing all of this alongside day-to-day operations: This is what everyday life looks like for many fleet managers when it’s time to implement new fleet management software. As a result, there’s often little time left to address the actual question of what requirements the new solution must meet and how the incoming quotes can ultimately be compared objectively.

The real problem rarely arises during the vendor comparison itself, but rather one step before that: Anyone who launches a request for proposals without first clearly defining their own requirements for vehicle management, driver’s license verification, or a logbook will end up comparing offers that are virtually impossible to evaluate against one another. A statement like “we need a vehicle management system” sounds specific, but leaves open whether a simple booking platform is intended or a system with automated driver’s license verification and damage management—and it is precisely this gap that later results in offers that are hardly comparable.

Fleet management has different priorities than IT, which focuses primarily on interfaces and data security, while the procurement department looks at contract terms and pricing models, and the works council also wants a say whenever location tracking or driving data is involved. A real-world example illustrates just how quickly this can become an issue: After implementing a new solution, a company discovered that there was no interface with its existing SAP accounting system, meaning that entries had to be transferred manually from then on—an avoidable extra burden. Software that is suitable for the fleet but fails due to IT integration issues usually delays implementation much more significantly than a provider that doesn’t offer every desired feature.

When evaluating competing solutions for fleet management and fleet control, the decision is rarely based solely on price; it also depends on how well vehicle management, driver’s license verification, and trip logs can be integrated, how existing systems such as ERP or telematics can be connected, and what the situation is regarding certifications, hosting location, and access management. An offer that appears 20 percent cheaper at first glance may end up being more expensive if it becomes apparent only after implementation that an interface to the existing ERP system is missing and must be integrated later at considerable expense. The weight given to each criterion in a particular case depends on the company’s own strategy; generic checklists are rarely very helpful here.

In the past, the search for new fleet management software usually began with a few Google searches; today, many fleet managers also use AI-powered search assistants to get an initial overview of providers and common pitfalls. This significantly shortens the research process, but it does not replace the actual work of clarifying your own requirements and comparing offers in detail. Those who want more certainty before the actual request for proposals can also send a non-binding Request for Information (RFI) to individual providers to inquire about technologies, security standards, and implementation timelines without committing to anything yet.

Inquiries from vendors during the bidding process often seem like a mere formality, but in practice they are a good indicator of how clearly your own requirements are actually formulated. If several bidders ask the same question independently of one another, this usually points to a gap in the requirements specification that can still be addressed before bids are submitted. Oliver Riedmüller, Key Account Manager at AZOWO, regularly oversees such bidding processes and sums it up as follows:

Many requirements for fleet management software only become apparent during actual operation, not during the bidding process. If a company later switches to electric vehicles, charging infrastructure, range management, and electric vehicle management become new considerations that often weren’t a factor at the outset. The same applies to real-time data from the vehicle: Companies that focus only on basic functions during the bidding process often have to retrofit their systems as reporting requirements or sustainability reporting needs grow. It is therefore worth not only considering current needs when selecting a provider but also asking how flexibly the software can be adapted to future requirements. For more on how electrification and real-time data are transforming fleets, see the articles on the transition to electric vehicles and on live data in fleets.

The AZOWO Guide walks you through the bidding process in twelve steps, from the initial needs analysis to ongoing operations after go-live: Needs Analysis & Goal Setting, Market Research & Request for Information, Bidding Phase, Responding to Inquiries & Adjusting the Requirements Specification, Evaluating Vendors Using an Evaluation Matrix, Product Presentation, Renegotiation, Final Decision, Contract & Proposal Clarification, Kick-off Meeting, Implementation Phase, and Go-Live with Ongoing Support. For each step, the guide provides specific guiding questions and practical tips, supplemented by a questionnaire with 50 questions for potential vendors.

The selection of new fleet management software rarely fails because of what’s available on the market, but rather due to a lack of preparation on the part of the organization: unclear requirements, a lack of coordination between the departments involved, and criteria that are only established during the bidding process instead of being defined beforehand. A structured approach with clearly defined requirements, transparent evaluation criteria, and the right questions for vendors makes the difference between software that fits the fleet and software that only looks good in a presentation.

For anyone currently tackling the bidding process, AZOWO has compiled a practical guide featuring an evaluation matrix and a list of questions for vendors.