Transport operators have more fleet management software options today than at any point in history. Off-the-shelf platforms promise real-time GPS tracking, driver compliance, route optimisation, and passenger information, all configurable in an afternoon and priced per vehicle per month.
For many operators, the off-the-shelf option is the right one. For others, particularly regional bus operators, specialised logistics providers, and transport companies with unusual operational requirements, the generic platforms fit badly, force expensive workflow changes, and leave real business value on the table.
This guide is for operators who are weighing custom fleet management software against off-the-shelf platforms. It is based on our experience building the GTV BUS fleet management platform and helping transport operators decide when custom makes sense and when it does not. If you are a CEO, COO, or Head of Operations at a transport company, this is the brief you should read before taking the next vendor meeting.
What Off-the-Shelf Fleet Platforms Do Well
Before arguing for custom software, it is worth being honest about what the generic platforms already do well:
- Real-time GPS tracking with maps and geofencing
- Basic driver behaviour monitoring (harsh braking, speeding, idling)
- Vehicle maintenance scheduling and inspection records
- Fuel management and cost reporting
- Standard compliance reports for regulators
If your operation fits cleanly into the standard categories these platforms were built for (small to mid-sized delivery fleets, generic commercial transport, simple compliance environments), a platform like Samsara, Geotab, or Verizon Connect will give you most of what you need for a fraction of the cost of custom development.
The honest question is not "custom vs off-the-shelf in general" but "does your specific operation fit the assumptions the platform was built around?" For many transport operators, the answer is mostly yes with frustrating exceptions. For others, the answer is no, and the exceptions are where the business actually lives.
When Off-the-Shelf Stops Working
We see a consistent pattern of situations where off-the-shelf platforms fail to deliver what the operator actually needs.
1. Bus transport with passenger-facing requirements
Generic fleet platforms are built for trucking and logistics, where the cargo does not care about arrival times. Bus operations have passengers, and passengers need real-time information, reliable scheduling, accessible stops, and sometimes tickets. None of this is well-served by platforms designed for freight. Operators end up duct-taping together a fleet management tool and a separate passenger information system, with the integration between them a constant source of data inconsistency.
This was the core problem GTV BUS faced: a bus operation running on phone calls, spreadsheets, and whatever generic tracking tool they had at the time, with no coherent link between dispatch decisions and passenger-facing information.
2. Complex driver compliance and certification
Transport operators in regulated EU markets deal with driver working time directives, rest period tracking, certification expirations, and per-country compliance variations. Off-the-shelf platforms offer compliance tools built for the operator's home market, which are usually underpowered when the operation crosses borders or runs unusual shift patterns.
We have seen operators spend thousands of euros per month on a platform whose compliance module they cannot actually use, while still running the real compliance tracking in Excel.
3. Dispatcher workflows that are the business
In many transport operations, the dispatcher is the most important role in the company. Their screen is where the business runs. Off-the-shelf platforms offer generic dispatcher views that show every fleet operator the same thing, when what each operator actually needs is a dispatcher view tuned to their specific routes, their specific decision criteria, and their specific integrations with ticketing, scheduling, and driver communication.
A dispatcher workflow that fits your operation perfectly is worth several staff hours per day, every day. A generic dispatcher workflow that requires clicking through five screens to make a decision costs those same hours, forever.
4. Integration with legacy systems
Transport companies often run legacy scheduling, ticketing, or accounting systems that were built for their specific operation over years or decades. Off-the-shelf fleet platforms offer generic integration APIs; what you actually need is integration with your specific legacy system, which may or may not be possible depending on what connectors the platform provides.
The workaround is usually a manual data bridge: someone exporting from one system and importing into another, daily, forever. This is invisible in vendor demos and becomes a persistent operational tax after rollout.
5. Data ownership and lock-in
Off-the-shelf platforms own the data. You can export it, but you do not control the storage, the schema, or the integrations. If the vendor raises prices, goes out of business, or changes direction, your operational data lives somewhere you do not control. For operators whose data is an actual competitive asset (route profitability analysis, passenger patterns, driver performance history), this dependence becomes a strategic concern over time.
What Custom Fleet Management Software Looks Like Done Well
A custom fleet management platform is not a replica of an off-the-shelf platform. It is a system built around the specific workflows, data, and decisions of your operation. Done well, it has six characteristics:
1. Dispatcher-first design
The dispatcher view is the centre of gravity. Every decision a dispatcher makes dozens of times per day should be fast, obvious, and well-supported by data. This means custom-designed screens built around your actual workflow, not a generic map with pins on it.
2. Real-time data with honest latency
GPS positions update in seconds, not minutes. Driver status changes propagate immediately. Dispatcher decisions flow back to drivers through integrated communication channels, not a separate messaging tool. The architectural work here (message queues, websocket connections, efficient data streaming) is the difference between a system that feels alive and one that feels like a delayed report.
3. Compliance built for your regulatory environment
EU driver working time directive compliance, ADR transport compliance, cross-border rules for specific corridors, company-specific policies layered on top. Custom software lets you encode these exactly, with automated alerts when a driver is approaching a limit, rather than a compliance officer running reports weekly and catching issues after they have happened.
4. Integrations that actually fit
Connections to your legacy scheduling, ticketing, and accounting systems built to match their actual interfaces, not a generic API adapter. Data flows automatically; staff do not run exports and imports.
5. Passenger-facing systems where relevant
For bus operators, the fleet management platform and the passenger information system should share a single source of truth. Real-time arrival information on a passenger app comes from the same GPS feed the dispatcher uses. There is no data bridge, no delay, no inconsistency between what the dispatcher sees and what a passenger sees.
6. Data you own and control
The database is yours. The servers run in your AWS account or similar. Custom reports, custom analytics, custom integrations with future systems are all possible because you own the schema and the code. There is no vendor lock-in risk because there is no vendor platform to lock into.
The Technology Decisions That Matter
If you are seriously considering custom fleet management software, three architectural decisions shape the outcome more than others:
Backend framework choice. The backend handles GPS ingestion at scale, dispatcher logic, compliance rules, integrations, and reporting. We use Symfony (PHP) for ours because 10 years of production experience have proven it reliable at this kind of scale with this kind of complexity. Alternatives include Django (Python) and Spring (Java). What matters most is that the team you hire has deep, long production experience with whatever they choose, not broad familiarity across many options.
Frontend framework choice. The dispatcher view is a complex, data-heavy interface that will live for a decade. Angular is our choice for this kind of application because of its discipline around structure, TypeScript-first data handling, and long-term stability. React can work too; what matters is that the framework fits a long-lived, data-complex application, not a consumer-facing one.
Real-time infrastructure. GPS feeds, driver communication, and dispatcher updates all need real-time delivery. This means websocket connections, message queues (we use AWS-native services like SQS and SNS), and careful attention to backpressure when the fleet is large. The architecture you design here determines whether the system scales from 30 vehicles to 300 without a rewrite.
The Honest Bottom Line
Custom fleet management software is not the right choice for every transport operator. For small delivery fleets and operators whose needs map cleanly to off-the-shelf platforms, the generic option is faster, cheaper, and perfectly adequate.
But for bus operators, specialised logistics providers, and transport companies whose real business lives in the gap between off-the-shelf assumptions and their actual operational reality, custom software is often the only way to get software that actually fits. The question is not whether off-the-shelf platforms are cheaper (they are) but whether they deliver the outcome your operation needs (often they do not).
If you are sitting with a generic platform that sort-of-works and a growing list of manual workarounds, the honest next step is to estimate what those workarounds actually cost you per year. Staff hours, error rates, missed opportunities, passenger complaints, compliance risk. When you add those up and compare to the cost of a custom platform built once and owned forever, the economics often look different from what the per-vehicle monthly fee of the off-the-shelf platform suggested.
