Custom fleet management software with no per-vehicle SaaS fees.
An operations manager refreshing a spreadsheet to know where the fleet is has a visibility problem, not a staffing problem. A 200-truck operation paying $40 per vehicle per month on a SaaS platform that doesn't connect to the job system has a cost problem and a visibility problem. RaftLabs builds custom fleet management software for logistics operators, field service companies, and transportation businesses. Real-time GPS tracking, driver apps, route optimisation, and maintenance scheduling, all integrated with your TMS or ERP. Fixed price. No per-vehicle SaaS fees.
Real-time GPS tracking with no sync delay, every vehicle on a live map
Driver app works offline in dead zones, syncs when signal returns
Custom integration with your TMS, ERP, or job management system
No per-vehicle SaaS fees on a large fleet: you own the platform
Vehicle maintenance scheduling, fuel tracking, and compliance built in
2,000+ shipments, 70+ countries Logistics platform·200+ accounts, zero disruption Migration
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
01
Operations manager refreshing a spreadsheet to know where the fleet is because tracking doesn't connect to jobs?
02
Driver app requiring signal in the exact zones where most of your routes run?
03
Per-vehicle SaaS fees on a 200-truck fleet that cost more than the platform creates value?
Plain answer
RaftLabs builds custom fleet management software for logistics operators, field service companies, and transportation businesses across the US, UK, Ireland, and Australia. A focused v1 with real-time GPS tracking, an offline driver app, and a dispatcher portal launches in about 16 to 20 weeks from around $60,000, then grows into TMS integration, maintenance scheduling, and compliance. Adjacent work includes UrShipper: 2,000+ shipments across 70+ countries.
What to remember
A focused v1 launches in about 16 to 20 weeks from around $60,000, then grows into the full platform
Driver app works fully offline in dead zones and syncs all activity when signal returns
No per-vehicle SaaS fees: you own the platform outright after delivery
Built UrShipper, a multi-carrier logistics platform handling 2,000+ shipments across 70+ countries, adjacent to fleet work
Migrated 200+ existing merchant accounts onto the new UrShipper platform with zero service disruption
Integrates with TMS, ERP, and job management systems including Oracle OTM, SAP TM, and Microsoft Dynamics 365
A spreadsheet refresh is not a tracking system.
An operations manager refreshes a spreadsheet to find out where the fleet is. The tracking tool does not connect to the job system, so the answer is always a few minutes stale, and a few minutes is a missed delivery window.
Out on the route, a driver hits a dead zone. The app needs signal in the exact places the routes run, so the proof of delivery never gets captured and the record has a hole in it.
Meanwhile the per-vehicle SaaS bill keeps climbing on a 200-truck fleet, for a product nobody owns.
Three problems, one fix: a platform built around the operation, not rented by the vehicle.
A fleet manager with no real-time visibility is deciding on stale data. A driver app that drops offline mid-route leaves gaps in the proof-of-delivery record. A platform that does not talk to the job system means dispatchers maintain two systems instead of one. Custom fleet management software solves all three, not by adding another SaaS subscription, but by building the platform around your operation.
According to the US Department of Energy's Argonne National Laboratory (2024), commercial vehicles waste 6 billion gallons of fuel per year through unnecessary idling alone, costing fleet operators over $20 billion annually. For logistics businesses running dozens or hundreds of vehicles, that waste compounds quietly until it shows up as a budget line item nobody can explain.
According to the American Transportation Research Institute's 2024 Analysis of the Operational Costs of Trucking, fuel alone accounts for $0.481 per mile, roughly 21% of total truck operating costs, making it the single largest controllable expense for most fleets. For operators without real-time tracking and route optimisation, a meaningful share of that spend is waste: idle time, suboptimal routing, and undetected driver behaviour that compounds over thousands of miles.
RaftLabs builds these platforms for logistics operators, field service companies, and transportation businesses. We built UrShipper, a multi-carrier logistics platform handling 2,000+ shipments across 70+ countries, and migrated 200+ merchant accounts onto it with zero service disruption. That is the neighbouring logistics problem to fleet: live tracking, driver and dispatcher workflows, and integrations that cannot drop data. RaftLabs is rated 4.9/5 by clients on Clutch. The team that scopes it ships it.
This works when per-vehicle fees have outgrown the value they return.
Everything on the left should already be true for your operation. Even one thing on the right, and an off-the-shelf SaaS is the smarter first step.
A fit
01
A fleet of dozens to hundreds of vehicles where per-vehicle SaaS fees have outgrown the value they return.
02
Routes that run through dead zones every day, so the driver app has to work offline, not just online.
03
An existing TMS, ERP, or job management system the tracking has to integrate with, not replace.
Not a fit
01
A handful of vehicles a spreadsheet still covers.
02
You want a month-to-month subscription with no upfront build, not a platform you own.
03
No integration needs and no dead-zone routes, where an off-the-shelf SaaS already fits.
Commercial fleet platforms charge $30-50 per vehicle per month. On a 200-vehicle fleet, that's $72,000-$120,000 per year for a product you don't own, and a custom build typically recovers its cost in under two years.
02
Offline-first driver app
Built for the routes your drivers actually run, not the routes with consistent 4G coverage. Every action queues on-device and syncs automatically, no driver training required for offline behaviour.
03
Built around your dispatch workflow
Samsara and Verizon Connect are built for the average fleet. Your job types, your route constraints, your proof of delivery requirements: all built in from day one, not worked around.
04
Telematics integration done right
OBD-II, CAN bus, and third-party telematics hardware all feed into one data layer. We've integrated with Samsara APIs, CalAmp, and generic GPS trackers. Your TMS, ERP, or job management system stays in place, and data flows without manual re-entry, giving you one source of truth for dispatch, tracking, and delivery.
05
Parallel cut-over, no hard stops
Fleet operations don't get a maintenance window. We run the new platform alongside the old one, validate data accuracy on a subset of drivers, then cut over the full fleet with a tested rollback plan.
06
Compliance built in, not retrofitted
DOT hours of service, DVSA tachograph rules, and vehicle inspection requirements are scoped in week 1. The driver app inspection forms, HOS logs, and driver records are compliance-grade from launch day.
Custom build vs off-the-shelf SaaS
Off-the-shelf fleet SaaS
Custom platform (RaftLabs)
Cost model
$30-50 per vehicle per month, forever
Fixed build cost, then roughly $1-3 per vehicle per month in infrastructure
Ownership
You rent access; the vendor owns the code and data model
Code, infrastructure, and API contracts transfer to you at handover
Dead-zone routes
Offline behaviour varies by product and is rarely the priority
Offline-first driver app, sync-on-return built into the core architecture
TMS/ERP fit
Standard connectors; your custom job system may not be supported
Integration built against your API or schema, confirmed in week-one discovery
Workflow fit
Your operation adapts to the average-fleet feature set
Your job types, route constraints, and proof-of-delivery rules built in
How much are per-vehicle fees costing you this year?
Tell us your fleet size, your current tools, and your integration requirements. We'll scope the platform and give you a fixed price.
How it works
From scope to live fleet
Week 1
01
Operations audit
We map your dispatch workflow, job types, driver app needs, and integration requirements. You leave week 1 with a written scope document and a fixed-price quote. Development starts only after sign-off.
Weeks 2-4
02
Design and architecture
UI design for the dispatcher portal and driver app approved in Figma before any code is written. Data model, integration architecture, and offline sync strategy documented and reviewed.
Weeks 5-16
03
Build the core platform
Dispatcher portal and offline driver app built in parallel: live map, job assignment, proof of delivery, and vehicle status. QA runs alongside every sprint, not at the end. TMS or ERP integration lands here when it is in the v1 scope, otherwise it follows as an expansion module.
Weeks 17-20
04
Parallel run and cut-over
New platform runs alongside your existing system on a subset of drivers. Once data accuracy is validated, the full fleet cuts over. Post-launch monitoring and 8 weeks of support included. Your validated v1 is live; integrations, compliance, and telematics modules follow as the fleet grows.
Pitfalls we plan around
Fleet software fails in predictable places. We scope for these before the build, not after a driver files the first complaint.
Device and hardware variance
Fleets run mixed hardware: different OBD-II dongles, telematics vendors, and phone models bought over several years. We normalise the data at one ingestion layer so a CalAmp reading and a Samsara reading land in the same schema, and we test on the oldest phones actually in the field, not just a new test device.
Connectivity gaps
Routes run through tunnels, rural stretches, and loading bays with no signal. The driver app is offline-first by default: every action is timestamped on-device and synced in order when signal returns, so a dead zone never leaves a hole in the proof-of-delivery record.
Driver adoption
A driver who finds the app slower than paper will route around it, and your data goes dark. We design the driver flow with the people who use it, keep the daily path to a few taps, and pilot with a subset of drivers before the full rollout so the friction surfaces early.
Data accuracy at cut-over
The risk in replacing a live system is silently wrong data. We run the new platform in parallel on a subset of drivers for several weeks, reconcile it against the old system, and only cut the full fleet over once the numbers match, with a tested rollback plan in hand.
Proof it works
RaftLabs has shipped production software since 2015 for clients across the US, UK, Europe, Canada, and the UAE. For fleet work specifically, the closest proof is UrShipper, a multi-carrier logistics platform we built end to end.
Adjacent logistics work
shipments processed across 70+ countries in year one on a multi-carrier platform we rebuilt
2,000+
UrShipper, multi-carrier shipping platform
live merchant accounts migrated to the new platform with zero service disruption
200+
UrShipper phased migration
new business signups in the first two months after launch
92
UrShipper, post-launch
We rebuilt UrShipper, a multi-carrier logistics platform, in 14 weeks after four vendors had failed to ship it. Two hundred merchant accounts moved across with zero service disruption, and the platform now handles shipments across 70+ countries. Fleet management is the neighbouring problem: the same live tracking, driver and dispatcher workflows, and integration discipline, pointed at vehicles and routes instead of parcels and carriers.
What clients say
What our clients say
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
Gil Nugraha
Indonesia
Founder at UrShipper
“
I definitely recommend RaftLabs, especially to solo founders like me. Their clear communication and detailed discussions have always helped me make better decisions.
Where you land on price depends on scope, not negotiation:
Focused build, $60,000-$90,000
GPS tracking, driver app (iOS and Android), and a dispatcher web portal, with no external system integrations. 16-20 weeks.
With integrations, $100,000-$150,000
Adds TMS or ERP integration, vehicle maintenance scheduling, and fuel tracking. 20-28 weeks.
Full platform, $160,000-$250,000
Telematics hardware integration, compliance reporting (driver hours, inspections), multi-depot support, and a custom analytics dashboard.
What it costs
Custom fleet software, starting at $60,000.
GPS tracking, driver app, and dispatcher portal at the core, with TMS or ERP integration, maintenance scheduling, and compliance reporting added as your operation needs them.
Commercial platforms charge $30-50 per vehicle per month for a product you never own. Start with the core dispatch platform, own it outright, then add TMS integration and compliance reporting as your fleet grows.
Starting investment
Starts at $60,000
A focused v1 launches in about 16 to 20 weeks. Per-vehicle infrastructure runs roughly $1-3 per vehicle per month at scale, not the $30-50 per vehicle typical of commercial SaaS. Start with GPS tracking and dispatch, then add compliance and maintenance modules as your fleet grows.
No hourly billing
Once we scope your first phase, that price is locked in writing. No hourly billing, and scope changes are priced and agreed before any additional work starts, so your capital budget stays under control.
You own it
All code, infrastructure, and API contracts transfer to you at handover. No per-vehicle SaaS fees, no ongoing licence fees, no vendor lock-in: your operations team controls the platform.
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.
Work with us
Tell us where the work is stuck.
Bring the rough workflow, half-built product, or messy brief. We will map the smallest useful first move, then send scope, timeline, and price in plain English.
Scope and cost agreed before work starts. No surprises. No obligation.
Working prototype within 3 weeks of kickoff.
Pay by milestone. You see progress before each invoice.
60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
