Fleet management software in India costs 150 to 800 rupees per vehicle per month as a subscription, or 12 to 35 lakh as a one-off custom build. The number that decides between them is not your fleet size on its own; it is fleet size multiplied by how unusual your operation is.
Here is the arithmetic, the crossover point, and the honest answer that most fleets should subscribe rather than build.
What the subscriptions actually cost
Per-vehicle pricing in India clusters into three bands, and the band you need is decided by what you want the software to do rather than by how many vehicles you have.
| What you get | Typical price per vehicle per month |
|---|---|
| GPS tracking only: location, trip history, basic alerts | 150 to 300 rupees |
| Tracking plus fuel, maintenance and driver records | 300 to 550 rupees |
| The above plus dispatch, route planning and client portals | 550 to 800 rupees |
Add the hardware. A tracking device costs 2,500 to 6,000 rupees per vehicle to buy and fit, usually one-off, sometimes bundled into a longer contract. AIS-140 certified units, which commercial and public transport vehicles are required to run, sit at the upper end.
So a 40-vehicle fleet on a mid-tier plan is paying roughly 16,000 rupees a month, or about 1.9 lakh a year, plus perhaps 1.6 lakh of one-off hardware.
What a custom build costs
A custom platform is a project rather than a subscription: typically 12 to 35 lakh depending on the modules, whether you need a driver app, and how many outside systems it must talk to. Add 15 to 25 percent a year for maintenance, because devices change, APIs move and regulations shift.
The important difference is not the total. It is the shape: the subscription scales with your fleet and the build does not. That single property is what the whole decision turns on.
Where the lines cross
| Fleet size | Subscription, 3 years | Custom build, 3 years |
|---|---|---|
| 20 vehicles | about 2.9 lakh | 12 to 35 lakh, plus upkeep |
| 50 vehicles | about 7.2 lakh | the same |
| 150 vehicles | about 21.6 lakh | the same |
| 400 vehicles | about 57.6 lakh | the same |
At mid-tier pricing, a fleet of roughly 100 to 150 vehicles reaches the cost of a modest custom build over three years. Below that, the products win on price and you would be buying something less mature for more money.
Above it, the arithmetic changes but the decision still should not be automatic. Software you own is software you must maintain, staff and support at 2am when a depot cannot dispatch.
Does it pay for itself? The arithmetic
Cost comparisons are easy. Payback is the question that actually matters, and it is answerable with numbers you already have.
Take a 40-vehicle fleet paying roughly 16,000 rupees a month for a mid-tier subscription, so 1.92 lakh a year.
| Where the saving comes from | Conservative annual value |
|---|---|
| Fuel reconciliation, catching entries that do not match distance | 1 to 3 percent of fuel spend |
| Avoided expiry fines and detentions, permits, PUC, insurance, fitness | 20,000 to 1 lakh |
| Route sequencing, one extra drop per vehicle per day | Varies, usually the largest line |
| Admin time saved on trip sheets, reports and customer calls | 1 to 3 hours per day of someone's time |
The first row alone usually clears the subscription. A 40-vehicle fleet burning 50,000 litres a year at 95 rupees is spending about 47.5 lakh on diesel; recovering even 1 percent is 47,500 rupees, which is a quarter of the software cost.
That is why we tell fleets to instrument fuel before anything else. It is the cheapest number to capture, the fastest to show a result, and the one that funds everything after it.
What to ask in a vendor demo
Demos are designed to show the map. The map is the part every product does well. These seven questions separate the tools that will still be useful in year three.
- Can you read our existing devices? Name your vendors and models. A product that requires replacing hardware you already paid for should have that cost added to its quote.
- Can we export everything, including history? Ask for the format. If the answer is a support ticket and a CSV of the last 90 days, you are renting your own data.
- What happens to a fuel entry that does not match the odometer? You want an exception queue, not a row in a report nobody opens.
- Show me a document expiry 45 days out. Permits, PUC, fitness, insurance and driver licences, with reminders that escalate rather than a single email.
- How does the driver app behave on a 3G connection in a basement? Offline capture and sync, or it will not be used.
- Can a client see only their consignments? If you resell visibility, this is the whole feature.
- What does the price look like at double our fleet? Ask for the tier boundaries in writing.
Answers to three and five are the ones that most reliably predict whether a rollout succeeds.
Implementation: where fleet projects actually stall
Neither buying nor building fails on software. They fail on the two months after go-live, and the pattern is consistent enough to plan around.
Device data is messier than the demo. Mixed vendors, units fitted years apart, some reporting every 10 seconds and some every two minutes, a handful silently dead. The first week of any real project is spent finding out which vehicles are actually reporting.
The master data is wrong. Vehicle lists that include sold trucks, drivers who left, and registration numbers typed four different ways. Cleaning this is unglamorous and it is the single biggest determinant of whether the reports are trusted later.
Dispatchers resist a system that adds a step. The person allocating vehicles at 6am will not use software that is slower than their WhatsApp group. If the new tool does not make their morning faster on day one, it will be abandoned regardless of what it does for management.
Drivers need a reason. Proof-of-delivery capture succeeds when it removes paperwork they already hate. It fails when it is presented as monitoring.
Plan eight weeks from go-live to trusted reports, whichever route you take. Anyone promising faster has not migrated a real fleet.
Four reasons to build that have nothing to do with size
Cost is the reason people quote. These are the reasons that actually justify it, and any one of them can override the vehicle count entirely.
- Your dispatch or billing rules are yours alone. If clients are invoiced on terms no product models, you will end up rebuilding those rules in spreadsheets beside the software you are paying for.
- It must join your other systems. An ERP, accounting, or a client-facing portal. Products with real APIs exist; many do not.
- You resell visibility to your customers. The moment your clients log in to see their consignments, you are shipping a product and a generic tool with someone else's branding stops being enough.
- Per-vehicle fees have become your largest software line. Not because the fee is unfair, but because you are now paying a growth tax on your own expansion.
What nobody puts in the comparison
Three costs sit outside both columns and decide more projects than the licence fee.
Hardware you already own. Most fleets have devices from more than one vendor, bought at different times. Any decent build reads from what is already fitted, and any product that requires replacing all of it should have that cost added to its column.
The operations team's time. Software nobody uses costs the same as software everybody uses. The fastest failure we see is a good system rejected because it added a step for the person who dispatches at 6am.
Compliance the software should handle. Permit, PUC, fitness and insurance expiry dates, FASTag reconciliation, e-way bills. If the tool ignores these, someone keeps a spreadsheet, and you are paying for the software twice.
The honest recommendation
Most Indian fleets under about 100 vehicles should subscribe. The products are competent, the price is fair, and the engineering you would spend replacing them buys nothing you cannot rent.
Build when the rules that make you money cannot be expressed in a product, when the software must talk to systems no vendor supports, or when per-vehicle fees have outgrown a build over a three-year horizon. That is the same test we apply on the first call, and it sends a fair number of enquiries back to the subscription.
AIS-140, and what compliance actually requires
AIS-140 is the Indian standard for vehicle location tracking devices, and commercial and public transport vehicles in many categories are required to run certified units. It matters commercially for two reasons beyond legality.
First, a certified device produces a consistent data stream, which is what every downstream feature depends on. Second, it constrains your hardware choice, so if you are still fitting devices, decide on certification before you decide on software rather than after.
Beyond the device, the compliance a fleet system should carry is unglamorous and expensive to miss: permit, PUC, fitness certificate and insurance expiry per vehicle; driver licence and badge validity per person; FASTag reconciliation so tolls land on the job that incurred them; and e-way bills captured with the trip where your billing requires it. If your software ignores these, someone keeps a parallel spreadsheet, and you are paying for the system twice.
Owning your data, whichever you choose
The question that decides how expensive your next decision is: can you leave?
For a subscription, ask before signing what happens on the last day. You want trip history, fuel and maintenance records, driver files and documents in a standard format, on demand, without a negotiation. Products that make export awkward are not protecting a feature; they are protecting a renewal.
For a build, the equivalent question is whether your team could take it over. Documented, deployable, with the accounts in your name from day one. A custom platform only you can run has replaced a vendor lock-in with an agency lock-in, which is worse because there is only one of us.
We put this in writing on every project, and it is a fair thing to demand from anyone quoting you.
Questions people ask
Is there free fleet management software?
Free tiers exist and are genuinely useful up to a handful of vehicles. They tend to stop at tracking, cap history to a short window, and exclude the fuel, maintenance and compliance records that make the software worth having. Treat free as a way to test whether tracking changes anything for you.
Is GPS tracking of vehicles legal in India?
Tracking vehicles your business owns is standard practice, and AIS-140 devices are mandated for many commercial categories. What needs care is tracking people: tell drivers in writing, put it in employment terms, and restrict tracking to working hours where you reasonably can. It is both the correct treatment of your staff and the version that survives a dispute.
How long does a custom fleet platform take to build?
About 10 to 12 weeks for a first usable version with tracking, trips, drivers and documents, and 16 to 20 for a full platform with dispatch, a driver app and integrations. The detail is on our fleet management software page.
Can we start with a few vehicles and expand?
Yes, and it is the sensible sequence either way. Run one depot or one route type for a month, get the operations team using it daily, then widen. Subscriptions make this trivially cheap to test. For a build, the software cost does not change with vehicle count, which is exactly why growing fleets eventually outgrow per-vehicle pricing.
What is the difference between fleet management and vehicle tracking?
Tracking answers where a vehicle is. Fleet management answers what it costs, whether it is legal to be on the road, who was driving, and whether that route makes money. Most vendors sell tracking and describe it as management, which is why the pricing bands above separate the two.
What actually reduces fuel cost?
Reconciling every fuel entry against odometer distance, which surfaces patterns within a month, and route sequencing against live traffic and delivery windows. Both need the data to be in one system, which is the real argument for having software at all.
Where to go next
If you are choosing between products, take the four reasons above as your checklist and ask each vendor about them directly. If you have decided the rules are yours, our fleet management software page covers the modules, the compliance India adds, and the honest timelines.