Comparing software quotes in this market is genuinely difficult, because vendors deliberately price on different units. A per-vehicle quote and a per-user quote cannot be compared without modelling, which is exactly the point.
The six models
1. Per vehicle per month. The most common in fleet and telematics. Predictable, scales with fleet size, and it means every vehicle costs you whether it is used or not.
Favours: fleets with high user-to-vehicle ratios. Watch for: minimum vehicle counts, and whether spare or off-road vehicles still incur charges.
2. Per user per month (seat-based). Common in route accounting and field service. Charged per named or concurrent user.
Favours: operations with many vehicles and few system users. Watch for: whether drivers count as users, whether occasional office users need full seats, and the price gap between tiers.
3. Per stop or per transaction. Usage-based. Common in routing engines and API-delivered optimisation.
Favours: seasonal and variable operations. Watch for: what counts as a chargeable event — is a re-optimisation a new charge? Is a failed delivery? Peak-season bills can be several times the average month.
4. Tiered bands. Fixed price within a range, stepping at thresholds.
Favours: stable operations sitting comfortably inside a band. Watch for: the cliff. Adding one vehicle at a threshold can raise the price significantly, and the tier boundaries are rarely where you would choose them.
5. Module-based. A platform fee plus charges per functional module.
Favours: buyers who genuinely need a subset. Watch for: essential functionality classified as a premium module — SSO, API access, and advanced reporting are the usual candidates.
6. Perpetual licence plus maintenance. Increasingly rare. Large upfront cost plus annual maintenance, commonly around a fifth of licence value.
Favours: organisations with capital budgets and long-term stability. Watch for: upgrade costs, and whether the product still has an active roadmap.
Take every quote and model it over five years using your own projected vehicle count, user count and volume, including uplifts, implementation, hardware and exit costs.
Where the money hides
| Item | Typical impact |
|---|---|
| Implementation and configuration | Can equal or exceed first-year licence |
| Data migration | Frequently quoted separately, often underestimated |
| Integration development | The largest variable in complex environments |
| Training | Per-session or per-user charges |
| Hardware | Devices, mounts, installation, replacement |
| Connectivity | SIMs, data plans, roaming |
| Annual uplift | Compounds; uncapped uplifts are common |
| Premium support | Response-time SLAs often cost extra |
| Sandbox environments | Sometimes chargeable |
| API access or call volumes | Occasionally metered |
| Additional entities or depots | Sometimes charged per legal entity |
| Exit and data extraction | Ask explicitly; some charge for it |
The annual uplift deserves particular attention. An uncapped uplift clause tied to a vendor's discretion, compounded over a five-year term, can substantially exceed the headline saving you negotiated at signature.
Questions that clarify a quote
- What exactly is included in the per-unit price, and what is not?
- Is there a minimum commitment, and what happens if we fall below it?
- What is the mechanism and cap for annual price increases?
- What does it cost to add a vehicle, a user, a depot mid-term?
- What does it cost to reduce those numbers mid-term?
- Is implementation fixed-price or time-and-materials?
- Which features are in our tier, and can that be fixed contractually?
- What are the support hours, response times and escalation paths at this price?
- What are the exit terms, including data extraction format and cost?
- What has this product's price done over the last three years for existing customers?
Question 10 is the most revealing and the least often asked. Ask for a reference customer of three or more years and ask them directly.
Negotiation levers
- Term length. Multi-year commitments earn discounts; balance against the risk of being locked into a product that turns out to be wrong.
- Payment timing. Annual upfront payment typically earns a discount worth more than the interest cost.
- Uplift caps. Fix them to a published index with a ceiling. This is frequently conceded and rarely requested.
- Implementation scope. Fixed price with defined deliverables rather than day rates.
- Reference and case study rights. Vendors value these and will trade for them.
- Timing. Quarter and financial year ends genuinely affect flexibility.
- Pilot conversion. Agree the production price before the pilot, not after your data is already in the system.
Frequently asked questions
What should route and fleet software cost?
The range is wide enough that a single figure would mislead: simple tracking sits at the low end of per-vehicle monthly pricing, while route accounting with ERP integration runs to a substantial multiple of that. The useful discipline is modelling five-year total cost for each option against your own numbers rather than comparing headline rates.
Is per-vehicle or per-user pricing better?
Whichever suits your ratio. A fleet with 80 vehicles and 6 system users is better served by per-user pricing; one with 20 vehicles and 30 users is better served by per-vehicle. Vendors know this, which is why the model chosen often reflects their target customer's shape.
Should we pay annually or monthly?
Annual payment usually earns a meaningful discount and is worth taking if cash flow allows, provided you are confident in the product. During a first year with a new vendor, the flexibility of monthly payment can be worth more than the discount.
How much should implementation cost?
It varies with integration complexity, but a useful sanity check is that implementation frequently approaches or exceeds first-year licence cost for anything involving ERP integration or data migration. Quotes that show minimal implementation cost for a complex scope are usually incomplete rather than competitive.
Can we negotiate?
Nearly always, and more effectively on terms than on headline price: uplift caps, contract length, included modules, implementation scope and exit rights. Leverage exists before signature and effectively disappears once your data and processes are inside the platform.
