What 7 Days With Fleetzz Actually Looks Like: A 2-Truck Free POC Walkthrough (India 2026)
Anand runs 25 trucks out of Coimbatore. Last month he picked 2 of them for a free Fleetzz POC. Here is exactly what happened, day by day, and why he signed up for the rest of the fleet a week later.
Anas Nadeem

What 7 Days With Fleetzz Actually Looks Like: A 2-Truck Free POC Walkthrough
Anand From Coimbatore
Anand runs 25 trucks out of Coimbatore. Garment loads to Tirupur for export packing, then onward to Chennai port. He has been running on a basic GPS tracking setup for three years. The setup shows him a moving dot on a map. Nothing else.
Last month, he signed up for the Fleetzz 2-truck free POC. He did not have to commit his whole operation. He picked 2 trucks. One running the Tirupur-Chennai lane. One running Tirupur-Bangalore. Both stayed on his existing GPS hardware (Anand did not want to disturb anything physical), with Fleetzz adding SIM-based tracking on top of the driver SIMs.
By Tuesday evening, both trucks were live on Fleetzz. The following Tuesday, after the end-of-week analyst call, Anand signed a 12-month subscription for all 25 of his trucks.
This blog is a day-by-day account of what happened on those 2 trucks. No marketing voice. Real timestamps, real numbers, real conversations from one Tamil Nadu fleet's first week with Fleetzz.
If you are thinking about the 2-truck POC yourself, this is what you are signing up for.
What You Already Know About Fleet Trials
Most "free trials" in Indian SaaS are not really trials. They are aggressive sales funnels. You give your phone number. You get a call within 5 minutes. The trial gets gated behind a "configuration call" that becomes a 90-minute pitch. By the end of week one, you are exhausted, your fleet is barely tracking anything, and the salesperson is sending you "Sir, when can we discuss the proposal?" messages every other day.
This is not what the Fleetzz trial is. The Fleetzz trial is built on one principle. Your data has to make the decision, not us. Which means the system has to actually run on 2 of your trucks for 7 days, surface real findings, and then we sit with you on the analyst call to walk through what we found, and what those findings imply across your full fleet.
That is the model Anand experienced. Here is how it played out.
Day 1, Tuesday. The Signup
11:14 AM. Anand fills out the form on fleetzz.io. Three fields. Name, phone, fleet size. He selects "SIM-based tracking" as his preferred mode and notes that he wants to keep his existing GPS hardware untouched. The form takes 30 seconds.
12:48 PM. Lokesh, a Fleetzz onboarding rep, calls him. The call lasts 14 minutes. Lokesh asks about the fleet. 25 trucks, primarily Ashok Leyland 16-tonners, running South India routes. Lokesh asks Anand to pick the 2 trucks for the POC. Anand picks one Tirupur-Chennai truck and one Tirupur-Bangalore truck so he gets data across two lanes. Lokesh asks for the SIM numbers of the assigned drivers. Anand sends them on WhatsApp after the call.
3:22 PM. Fleetzz activates SIM-based tracking on both driver SIMs. No hardware shipped. No install. The trucks continue running their existing GPS while Fleetzz layers SIM-based location data on top.
6:04 PM. Anand gets his login credentials. The Fleetzz dashboard opens with 2 dots on a map of South India. The Tirupur-Chennai truck is on NH-44 near Salem. The Tirupur-Bangalore truck is on NH-948 near Hosur. He spends 30 minutes clicking around. His fleet manager Jaganathan joins him in the office.
8:30 PM. Jaganathan installs the Fleetzz mobile app. He flags the Tirupur-Chennai truck on the dashboard. It shows "stopped near Salem" though the trip sheet said it should have crossed Salem 90 minutes ago. He calls the driver. The driver was at a roadside dhaba. Jaganathan tells him to move. The truck starts moving 12 minutes later.
The first surprise of the trial happened on day 1, on one of the 2 POC trucks, before any AI features had even kicked in.
Day 2, Wednesday. First Full Day
8:00 AM. Both POC trucks are live and have been transmitting overnight. Anand opens the dashboard with chai. The Chennai-bound truck is on its return leg. The Bangalore-bound truck is on its outbound leg. Both running normal speeds.
11:45 AM. First idle alert lands on his phone. The Chennai-bound truck has been idle for 22 minutes near Krishnagiri toll plaza. Anand checks. The driver is in queue at the toll. Normal. He dismisses the alert.
1:18 PM. Second idle alert. Same truck, now idle 47 minutes at the same location. Anand calls the driver. The truck cleared the toll 35 minutes ago and pulled into a dhaba. Driver said "saab, lunch." Anand tells him 30 minutes max, no exceptions. The system continues tracking.
4:50 PM. Daily summary lands on Anand's WhatsApp. 2 trucks tracked. 4 idle events flagged. Total idle time across the 2 POC trucks for the day: 2 hours 14 minutes. Average idle time per truck for the day: 1 hour 7 minutes. Top idler: Karthik (driver of the Chennai-bound truck) at 1 hour 47 minutes total.
Anand sends the summary to Jaganathan with one message. "Yeh number normal hai kya?"
Jaganathan does not respond for an hour. Then he sends back. "Sir, i think yes. But we never measured before."
That sentence is the entire reason the POC exists.
Day 3, Thursday. Patterns Start
9:30 AM. AI Chat becomes active on Anand's account (the system has now seen enough data on the 2 trucks to generate useful answers). Anand opens it and types in Tamil-English mix. "Yesterday top idle driver please."
The system replies in seconds. Karthik. With locations of his longest idle for the day. One of those idles was 2 hours 11 minutes near a fuel station outside Tiruchirapalli, on the Chennai run, that is not on any approved route.
Anand calls Jaganathan. "Karthik ko bulao."
By noon, Karthik is in the office. He is not denying anything. He says he stops at that fuel station because the owner is his cousin's friend and lets him sit in the AC waiting room. Anand asks him to stop. Karthik agrees. "The system will tell us if you do not," Anand says.
3:00 PM. First route deviation pattern alert from the AI on the same truck. The Tirupur-Chennai route has had 2 trips this week take a 14-km detour through Walajapet. The detour adds 18 minutes and approximately Rs 240 in extra fuel per trip. Same truck, same driver.
Anand calls Jaganathan. They Google Maps the route together. The detour avoids a particularly bad construction stretch on NH-32. Karthik had been doing this for weeks. Anand had been silently absorbing the 18 minute and Rs 240 hit per trip without knowing.
Anand decides to make the detour an officially approved route. Adds it to the system. The route deviation alerts stop. The 18-minute delay becomes a planned 18-minute addition that the customer can be informed about.
This is what visibility does, even on 2 trucks. It does not always mean catching wrongdoing. Sometimes it means recognizing a real problem and absorbing it formally.
Day 4, Friday. The First Real Fix
7:00 AM. Anand checks the morning report on his phone before leaving home. Today's top "most expensive driver" by idle time and overspeeding has been auto-emailed.
Karthik again. From yesterday's data. He had idled 1 hour 22 minutes after the noon conversation. Two of those idle events were at the same Tiruchirapalli fuel station Anand had told him to stop using.
Anand drives directly to the office. By 9 AM, Karthik is in the room. The data is on the screen. Two idle events. Same location. Same dates. After the warning.
There is no argument. Karthik knows the system saw it.
Anand puts him on a final warning. Documented in writing. Cc'd to the HR person. Signed by Karthik.
Three things happen because of that meeting.
One. Karthik never idles at that fuel station again during the trial.
Two. The other 23 drivers, who are not even on the POC, hear about the meeting through the driver WhatsApp group within the day. Fleet-wide idle awareness goes up sharply. Anand starts getting unsolicited "saab, main toh nahi kar raha" messages from other drivers.
Three. Anand realizes for the first time that the fleet's culture had been built on the assumption that nobody could check. Once that assumption changes (even via 2 trucks being publicly checked), the culture changes.
Day 5, Saturday. FASTag Reconciliation
5:30 PM. First FASTag reconciliation report lands. Fleetzz has pulled the toll charges for the 2 POC trucks from his ICICI FASTag account for the past 30 days and cross-checked each charge against the GPS path of the corresponding truck.
The report shows:
24 charges with no GPS path mismatches. Normal. 2 charges flagged for review. Charges that occurred at toll plazas the GPS does not show the truck crossing on that date. Total flagged value across 2 trucks: Rs 1,555.
Anand opens the 2 flagged charges with Jaganathan that evening. They cross-check by calling drivers. One charge of Rs 615 was deducted at Krishnagiri toll on a Sunday. The Chennai-bound POC truck was at the Coimbatore yard the entire day, confirmed by the fleet's CCTV. Another charge of Rs 940 was deducted at a toll on the Chennai-Trichy stretch at 2:47 AM. The truck was on its scheduled overnight halt at Salem at that time.
Both are flagged with ICICI through the dispute portal. Both come back as confirmed errors within 18 days. Anand recovers Rs 1,555 directly.
Now, the extrapolation. The mismatch rate on these 2 trucks was roughly 7.7 percent of charges (2 out of 26). Applied across all 25 trucks at his average toll spend, that projects to roughly Rs 18,000 to 24,000 per year in disputable charges across the fleet. That number was zero before the trial.
Day 6, Sunday. The Anomaly Catch
11:42 AM. Anand is at home. His phone buzzes with an anomaly alert on the Tirupur-Bangalore POC truck. Power supply has been cut for 14 minutes near a location identified as "Jolarpet, Vellore district, Tamil Nadu."
This is unusual. The truck's trip sheet says it should be on the Bangalore return leg, on NH-44, nowhere near Jolarpet. The location is 28 km off the highway. Power cuts for more than 10 minutes are flagged because they often signal device tampering.
Anand calls Jaganathan. Jaganathan calls the driver. The driver does not pick up. After three attempts, the cleaner picks up. He says the driver has gone to "drop something" at a friend's place near Jolarpet. The truck has been parked for 90 minutes.
Jaganathan tells the cleaner to put the driver on the call immediately. The driver picks up. He is sheepish. He had taken a 28 km detour to drop a personal package at a relative's house.
Anand documents the event. The driver gets a written warning. More importantly, the fleet now has a pattern. Power-cut alerts on Sundays in unusual locations are the system's signature for "driver doing personal work on the company's truck."
Without the anomaly alert, this 90-minute detour would have shown up only as a slightly extended trip time. The dashcam-style observability that Fleetzz layers on top of basic GPS tracking is what catches these patterns. Caught on 2 trucks. Will catch many more once the system is on all 25.
Day 7, Monday. The Analyst Review
4:00 PM. Anand and Jaganathan join a Zoom call with Aparna, their assigned Fleetzz analyst. The call is scheduled for 30 minutes. It runs 47 minutes because Anand has more questions than the agenda allows.
Aparna walks through the findings on the 2 POC trucks, then extrapolates across the full 25 truck fleet.
Idling. Total idling on the 2 POC trucks reduced 31 percent over the trial week (driven mostly by the Karthik intervention). Extrapolated across the fleet at the same reduction rate: approximately Rs 1.8 lakh in annual fuel savings.
FASTag mismatches. 2 charges flagged out of 26 in the first 30-day backfill on the POC vehicles. 7.7 percent mismatch rate. Extrapolated to the full fleet: Rs 18,000 to 24,000 in annualized recoverable charges.
Route optimization. Tirupur-Chennai detour formally adopted as the standard route. Customer ETA expectations updated. Recovered: 18 minutes per trip on 4 trips per truck per week. If Anand applies the same audit logic to the other 23 trucks (the AI Chat will help him do this in 2 hours of work), he likely recovers another 50 to 80 hours of fleet capacity per week.
Driver behavior. Two drivers (Karthik plus the Bangalore route driver) on documented warnings. The fleet-wide effect from awareness alone (the WhatsApp group conversations) had already reduced overall fleet overspeeding indirectly, even on non-POC trucks.
Document tracker. Demo of the document expiry calendar. 4 of his 25 vehicles have documents expiring in next 30 days. One commercial insurance had already expired 3 days ago, missed in Jaganathan's manual sheet. Avoided fines: Rs 30,000 to 50,000.
Power-cut anomaly. One major case detected on 2 trucks. Pattern now established for the system to catch repeat occurrences.
Total identified savings, annualized, extrapolated across the full 25 truck fleet. Rs 6.8 lakh. Cost of Fleetzz subscription for 25 trucks for 12 months. Rs 1.5 lakh.
Aparna closes the projection slide and says one sentence. "These are conservative numbers based on 2 trucks for a week. Most fleets see 20 to 40 percent additional savings in the first 90 days as drivers and managers adjust to having a system that watches."
Anand asks for the contract. He signs by Wednesday. The trial-to-paid transition takes 24 hours. The 2 POC trucks roll forward without a tracking break, and the other 23 trucks are added through the week.
What Happened Next
It has been 5 weeks since Anand signed his subscription. Some specific updates from his fleet.
Karthik is still on the fleet. His idling has dropped to fleet average. Anand says, "the system did the conversation I should have had with him two years ago."
Anand has added 4 hire-vehicles to his SIM-based tracking, vehicles he does not own but uses on certain Chennai routes. Visibility on those vehicles was previously zero.
Fleet-wide fuel cost has dropped 8 percent month-over-month. Customer ETA accuracy has improved to a point where two of his three large garment exporter clients have stopped sending the daily "where is the truck" calls.
He has referred two other Coimbatore-based fleets to Fleetzz. Both are now in their own 2-truck POC weeks.
How To Start Your Own POC
If you have read this far, the question is no longer "should I evaluate fleet management software?" The question is "what would 2 of my own trucks reveal in 7 days?"
The only way to find out is to run the POC.
Start your free 2-truck Fleetzz POC. The form takes 30 seconds. We onboard your 2 chosen trucks within 24 hours. No card. No commitment. SIM-based tracking can go live the same day, no hardware to install.
Open to any fleet owner running 10 or more trucks, anywhere in India.
By next Monday, you will know what 2 of your own trucks have been hiding.
Frequently Asked Questions
Is Anand's experience typical for a 25-truck fleet running a 2-truck POC?
The specific findings vary fleet by fleet, but the pattern is consistent. Most fleets above 20 trucks discover at least 3 to 5 distinct sources of leak from just 2 POC trucks in the first week. The most common are idling, route deviations, FASTag mismatches, and document tracking gaps. The 12-month savings projection (extrapolated across the full fleet) is generally between 4x and 8x the annual subscription cost.
Why only 2 trucks for the POC?
Because the goal of the POC is not to track your whole fleet for free. It is to surface enough patterns on a representative sample to give you (and us) an evidence-based view of what scaling will deliver. 2 trucks is enough to see real patterns, while keeping the commitment small for the fleet owner. If a system can't show you something useful in 7 days of tracking 2 of your trucks, it won't show you anything when you scale to 200.
How does SIM-based tracking compare to GPS hardware for the POC?
For most POC purposes, SIM-based tracking is sufficient. It activates faster (hours instead of days), requires no hardware install, and provides location accuracy in the 50 to 500 meter range, which is adequate for fleet management decisions. GPS hardware is more accurate (2 to 5 meters) and provides additional data points like driver behavior (harsh braking, harsh acceleration, sudden stops). Most fleets start with SIM-based tracking for the POC and upgrade to GPS hardware on owned vehicles after subscribing.
What happens to my POC data if I don't subscribe after 7 days?
You can export all data from the 2 POC trucks at the end of the trial. After 30 days, the data is purged from Fleetzz servers unless you ask for an earlier deletion. There are no aggressive follow-up calls. The system simply deactivates at midnight on day 7.
Can I add more trucks to the POC after I have started?
The default offer is 2 trucks for 7 days. If you have a specific use case during onboarding (multi-route comparison, hire fleet validation, etc.) we will accommodate up to 5 trucks where it makes sense. We do not encourage running the POC across the whole fleet, because that defeats the purpose of a low-friction trial.
Is the end-of-week analyst review actually useful, or just a sales pitch?
The analyst review is a working session, not a sales call. The analyst opens your 2-truck data with you, walks through findings, and extrapolates across your full fleet. There is no slide deck. There is no contract pushed during the call. We have built the POC on the conviction that the data should sell itself, and our job is to help you read the data, not sell against it.
Who is eligible for the POC?
Any fleet owner running 10 or more trucks, anywhere in India. There is no minimum fleet size beyond 10 trucks, and no geographic restriction within India.
How do I sign up for the Fleetzz 2-truck free POC?
Visit the free trial page, or send "POC" to our WhatsApp number. You will be on a call with our onboarding team within 2 hours.