Custom fleet management software with no per-vehicle SaaS fees.

A typical fleet management build includes four parts. The dispatcher web portal: live map showing every vehicle's real-time position, job assignment and route planning, driver status and availability, and a notification system for exceptions like delays or breakdowns. The driver mobile app: iOS and Android, job list and navigation, proof of delivery (photo, signature, barcode scan), offline mode that queues all activity and syncs when signal returns, and push notification for new job assignments. The back-office dashboard: vehicle utilisation reporting, driver behaviour logs (speed, harsh braking, idle time), fuel consumption tracking, maintenance schedules and service alerts, and compliance reporting (driver hours, vehicle inspection records). Integrations: TMS, ERP, or job management system via API, plus telematics hardware integration for live OBD-II data where vehicle telematics is needed.

The driver app stores the full job queue, route, delivery instructions, and form templates on the device when a connection is available. In a dead zone (no 4G, no Wi-Fi), the driver works normally: checking off deliveries, capturing proof of delivery (photo and signature stored locally), logging vehicle checks, and adding delivery notes. Every action is timestamped on-device. When signal returns, the app syncs all queued activity to the server in order. The dispatcher sees the delivery completions appear in sequence. No lost data. No driver having to redo steps when they get back into coverage. This is built into the core architecture, not bolted on as a feature, because most logistics dead zones are predictable and routes run through them every day.

Common TMS integrations: Oracle Transportation Management (OTM), SAP TM, TMW Suite, MercuryGate, and Descartes. Common ERP integrations: SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics 365 Business Central, and NetSuite. Custom job management systems: we build the integration against your API or database schema directly. Telematics hardware: Samsara, Verizon Connect, CalAmp, and generic OBD-II readers via CAN bus. For operations not on a standard platform, we build middleware that reads from your existing data source, whether that's an Excel export, an SFTP feed, or a legacy system REST endpoint. Integration scope and method are confirmed in week-one discovery before any code is written, so you know the exact data flows and dependencies before development starts. We test every integration against a staging environment before production cutover.

Yes, and we've done it. The typical trigger is cost: per-vehicle fees on a large fleet get expensive quickly, and the features you get are the same features every other Samsara customer gets. A custom platform built for $120,000 recovers its cost in under two years on a 200-vehicle fleet compared to a $40 per vehicle per month subscription. The migration path we follow: we build the new platform alongside the existing one, run them in parallel on a subset of drivers for 4-6 weeks to validate data accuracy, then cut over the full fleet. No overnight hard cut that leaves the operations team with no fallback.

Maintenance scheduling works from two inputs: mileage thresholds (service every X miles) and time intervals (monthly, quarterly, annual). The system tracks each vehicle's odometer reading via telematics integration (or manual driver input if no telematics hardware), computes the next service date or mileage trigger, and sends alerts to the fleet manager and the driver at configurable lead times. The maintenance log records every service: date, type, mileage, cost, and service provider. Inspection forms are assigned to drivers on a schedule (daily pre-trip, weekly checks) and completed in the driver app. Failures are flagged immediately and the vehicle can be locked out of job assignment until the issue is resolved. The full inspection history is stored and exportable for regulatory compliance.

A focused build, covering GPS tracking, driver app (iOS and Android), and a dispatcher web portal with no external system integrations, typically runs $60,000-$90,000 and takes 16-20 weeks. Adding TMS or ERP integration, vehicle maintenance scheduling, and fuel tracking typically runs $100,000-$150,000 and takes 20-28 weeks. A full platform with telematics hardware integration, compliance reporting (driver hours, inspections), multi-depot support, and a custom analytics dashboard typically runs $160,000-$250,000. All builds are fixed price: the quote in the project brief is the final invoice. Per-vehicle infrastructure costs (GPS polling, push notifications) run approximately $1-3 per vehicle per month at scale, not the $30-50 per vehicle typical of commercial SaaS.

Yes. For multi-state US operators, IFTA (International Fuel Tax Agreement) mileage and fuel data is recorded per jurisdiction automatically from telematics, generating the quarterly IFTA report from actual data rather than driver estimates. For US commercial motor carriers subject to FMCSA Hours of Service rules, ELD (Electronic Logging Device) integration retains driving hours, on-duty time, and violations for the required 6-month period and makes the record available for roadside inspection. For HGV fleets under EU tachograph regulations, driver card data uploads automatically or manually, with infringement detection covering driving time, break, and rest violations. Predictive maintenance alerts are also raised from persistent engine fault codes (DTCs) read via OBD-II, ahead of the next scheduled service.