By the RAAD team
Why modular fleet telematics beats the monolith
Listen to this article
Modular fleet telematics means running vehicles and connected assets on independent components: live tracking, fuel and energy, cameras, site sensors. It beats the monolith because you keep the hardware you already own, switch on only the pieces you need, and, if you resell, the product still carries your brand.
The monolith problem in fleet software
For two decades, fleet telematics defaulted to a single closed stack: one vendor's devices, one data pipeline, one set of dashboards. Resellers handed out logins and competed on price and local service, and that was survivable while the product was little more than a vehicle's position on a map.
That era has ended. A construction fleet wants idle-time rules and site geofences. A cold chain operator wants temperature excursions on the same screen as the trucks. A rental business wants its own workflows, its own documents, its own expiry reminders. The monolithic answer never changed: configure what the vendor allows, request the rest, and wait for the roadmap.
Resellers pay the highest price. When three providers in the same region resell the same closed stack, the product is identical, so they compete on price and service alone. Margins compress, and customers work out that the software down the road is the same. Differentiation drifts from product to salesmanship, which is a fragile place to build a business.
What modular fleet telematics actually means
A modular system assembles the estate from components that each work on their own and work better together. The word only earns its keep if three things hold: each component runs independently, each exposes its functions to the others, and any component can be swapped or extended without breaking the rest.
That is not the same as customisable. Customisable means adjusting settings inside a fixed product. Modular means choosing the product. RAAD is built this way: Track for the live map, trip and stop history, geofences, rules and remote commands; Power for fuel and energy on one ledger; Cam for AI dashcams; Meter for prepaid smart metering; Sense for temperature, humidity and door state at fixed sites; and AI Insights reading every alert across all of them. Assets, Drivers, Documents and Maintenance come with every account, so the paperwork travels with the vehicles instead of living in a separate system.
Resellers feel this question most. A single fleet operator has one set of requirements. A telematics service provider serving dozens of customers across different verticals and regions has to fit each of them or turn work away, and reusable components are what make that profitable rather than exhausting.
The three layers that decide your flexibility
Whatever a vendor calls its architecture, three layers determine whether it is genuinely modular: how data arrives, how data becomes decisions, and what the customer sees.
The data layer: any hardware in
A modular data layer accepts the devices already fitted to the fleet rather than a vendor's approved list. RAAD takes over the hardware customers already run instead of replacing it, which turns a migration project into an onboarding exercise.
Normalisation, the discipline of landing every device's signal in one consistent structure, is what makes the layer composable. The rules, reports and screens downstream never need to know which tracker sent the data, so devices can change without rewriting anything. The pipe also runs both ways: remote commands go back down to the vehicle through the same layer that collected the position.
The automation layer: your rules, not templates
Templates cover the common cases, such as geofence entry, speeding, or a document nearing expiry, and they fall over the moment a customer describes how their operation really runs. Composable automation combines signals into workflows that match one specific business.
RAAD keeps rules and geofences in Track while Sense supplies the sensor readings, so a rule can treat a cold store's temperature and its door state as one condition rather than two disconnected alerts. Power goes further on its own ground: RAAD checks every fill against what the tank actually took, and fuel loss with the engine off opens a case without anyone filing a report.
Alert volume is where automation projects usually die, so AI Insights reads every alert first, holds back what does not need a person, and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until someone approves it, which keeps the automation fast without making it reckless.
The experience layer: your brand, their loyalty
White-label in this industry often means a logo swap. Genuine ownership goes further: customers log in on the partner's domain, see the partner's brand, and receive the partner's invoice, never needing to know what runs underneath. RAAD is resold exactly this way, with each tenant walled off and per-screen roles across the Platform, Partner and Account hierarchy.
Ownership matters most at renewal. When the product is genuinely yours, customers judge your service rather than comparison-shop for identical software from a rival down the road.
Monolith, DIY or modular: the tradeoffs
Three architectures, three legitimate use cases, three real costs. Which one suits depends on which work deserves your team's hours.
| What matters | Closed monolith | Full DIY build | Modular platform |
|---|---|---|---|
| Time to market | Fast, inside the vendor's template | Slow, measured in years | Weeks, on proven components |
| Hardware choice | The vendor's approved list | Anything you integrate yourself | Existing devices taken over |
| Differentiation | Low, rivals sell the same thing | High, if you ever finish | High, through your rules and brand |
| Engineering burden | Low but capped by the roadmap | Every protocol and scaling problem is yours | Configuration, not code |
| Suits | Price-led resellers | Businesses that are software companies already | Partners who want product margin without a dev team |
A closed monolith gets you live quickly and caps you at the vendor's priorities. A DIY build gives total control and makes you a software company, because every device protocol and every scaling problem becomes yours to maintain. The modular middle path hands you components that have already solved the hard problems, including ingestion, normalisation and real-time alerting, and leaves the composition to you. The honest cost is a learning curve: working out how the pieces fit and how to package them for customers takes investment, just far less than building the pieces yourself.
What modularity changes for resellers and operators
For resellers, composition converts into four outcomes you can measure. Differentiation: an offering built from your market knowledge cannot be copied by a rival renting the same stack. Speed: a cold chain package or a construction fleet bundle ships in weeks because the components already exist. Margins: you decide what sits in the base bundle and what earns premium pricing, instead of discounting identical software. Retention: customers stay because the workflows fit their operation, not because leaving would hurt.
There is also a structural change to the revenue. A one-off hardware sale ends the relationship at the invoice; resold on RAAD, the same installation becomes monthly recurring revenue billed by the partner under the partner's name. The partner model turns an installation business into a subscription business.
Fleet operators get a version of the same freedom. You take the modules this year's operation needs and add the rest when it changes: Cam when the insurer asks, Power when fuel prices bite, Sense when a cold store joins the estate, ESG for indicative carbon reporting when a customer demands it. Everything stays on one map, one alert queue and one ledger, so a new module adds capability without adding another place to check.
Where to start
A move to modular architecture does not have to begin with a migration. It can begin with one wedge.
- Audit what your current setup refuses to do. List the customer requests you declined and the verticals you avoided because the implementation cost never justified the sale.
- Name one wedge. Not everything: one vertical you know well, or the integration your largest prospects keep requesting.
- Check skills, not headcount. Day-to-day composition is configuration and rules rather than development, though comfort with APIs helps once an ERP or dispatch integration enters the plan.
- Move on the hardware you own. RAAD takes over existing devices rather than replacing them, so the first customers switch without new boxes, new wiring or new capital.
- Start with one layer. If device support is the constraint, start at the data layer. If alerts are drowning your team, start with rules and AI triage. If the brand is the asset, start white-label.
Common questions
Three questions come up whenever resellers and operators weigh this move.
Is modular just another word for customisable?
No. Customisable is choosing from a fixed menu; modular is a kitchen with interchangeable ingredients. Customisation adjusts settings inside a product someone else defined, while modular components are independent, replaceable and able to work in combinations the vendor never imagined.
Can I keep the trackers already fitted to my fleet?
Yes. RAAD takes over the hardware already installed rather than forcing a device swap. That removes the largest cost and the longest delay from any move, whether you are a single operator or a reseller bringing a whole book of customers across.
Do I need developers to run a modular estate?
Not for daily operation. Rules, geofences, reports, roles and screens are configuration work done by operations people. Some technical comfort helps for third-party integrations, but composing an offering for a customer is not software development.
Fleet infrastructure does not have to arrive as one vendor's fixed vision. Assembled from modules that each earn their place, run on the hardware you already own and delivered under your own brand, it becomes an asset that no competitor can simply rent from someone else.
One platform for every connected asset
Tracking, power, cameras, metering and compliance in one console — resold under your own brand and billed by you.
Explore the RAAD platform

