Fleet management software pricing: what the quote includes
A fleet software quote is only comparable once it says what is included: what is being bought, how it is billed and which costs sit outside the subscription. Separate software, connectivity, hardware, installation, setup, training and support before comparing a monthly figure.
Where ReWheel stands
Pricing starts from CAD $14.99 per vehicle per month (about US$10.70 at recent exchange rates). Final pricing depends on the vehicles, hardware, term and deployment, and is confirmed in a written proposal.
Ask ReWheel for a scoped proposal that names what is included; vehicle compatibility, data access, connectivity and installation are assessed per deployment.
Start with the quote's scope
Record the country, currency, billing period, agreement length, asset band and checked date beside each amount. A monthly payment schedule does not by itself describe the agreement duration. Ask which active, spare, seasonal and unpowered assets count toward billing. Confirm the billing unit (vehicle, asset, device or named user) and any minimum count: the same rate gives a different bill on a different unit.
For each category in the worksheet at the end of this page, record included, separate, not needed or unresolved, together with the written source. Keep unresolved mandatory charges blank in the budget rather than treating them as zero. The worksheet is a review aid, not a current supplier offer.
Total the quote yourself
The four lines behind a price per vehicle
- Software fee per month, and whether it changes with the vehicle count.
- Hardware, bought or rented, spread over the months you expect to use it.
- Connectivity: the data plan, who pays it and whether it is billed separately.
- Onboarding: installation, training and setup, spread over the same months.
Add the four lines, then divide by vehicles and months. A per-vehicle figure that leaves one line out cannot be compared with one that includes it.
Total each category in one currency and one period. If connectivity is included in a software fee, do not add it again. If devices are supplied under return conditions, use the actual written arrangement for hardware. Keep internal staff time separate from supplier charges so the same work is not counted twice.
Take the scope to a supplier discussion
Questions to resolve
- Which charges change when the asset count changes?
- What implementation work and staff training are included?
- Which integrations or optional modules need a separate scope?
- Which taxes, currency charges, returns and exit items must the buyer budget separately?
Ask for implementation as named one-time deliverables (setup, record cleanup, configuration, training and handoff), each with the person who accepts it, and keep it apart from the recurring fee.
Blank fleet software cost-scope worksheet
Fill the blank CSV with written amounts and their source. Blank amounts mean unresolved, not zero.
On a small screen, scroll this table horizontally. Keyboard users can focus the table region and use arrow keys.
| Category | Cost basis | Confirm before comparing |
|---|---|---|
| Software | Per asset, user or fixed period | Billable units, minimums, included views and renewal basis |
| Connectivity | Bundled or separate recurring charge | Coverage, allowance and any overage or roaming terms |
| Hardware | Purchased, rented or supplied | Ownership, replacement and device-return conditions |
| Installation | Per asset or project charge | Vehicle fit, labour, travel and removal responsibilities |
| Setup and training | One-time or staged service | Configuration, import, staff time and named deliverables |
| Support and modules | Included, recurring or usage based | Support scope and optional module boundaries |
| Exit | Only the charges in the applicable agreement | Notice, remaining commitment, export and return costs |
Sources and review context
- BDC: planning the complete technology budget. Checked .
What ReWheel provides
ReWheel FMS connects supported vehicle information with equipment and operational records for field and institutional operations. Vehicle compatibility, data-access requirements, connectivity and installation are assessed per deployment, never assumed.
Continue with ReWheel: How a ReWheel workflow discussion works
Discuss your workflow