Blog · 2026-07-05 · Sahil Sidat

TMS Case Study: One System Replaced 5 Tools

Case study: a Gujarat logistics TMS that replaced WhatsApp, Excel, GPS trackers, paper registers, and phone calls with one unified system.

The problem: running transport operations across 5 disconnected tools

A Gujarat-based logistics company came to us with a familiar problem. They were running their entire transport operation using five different things: WhatsApp groups for drivers to check in, Excel sheets for trip planning, a separate GPS tracking system for vehicle locations, paper registers for trip expenses and advances, and phone calls whenever something went wrong. The owners had no single place to see which trips were active, which drivers had not checked in, or what a particular trip actually cost after all expenses. Reconciling trip expenses at the end of the month took days. Driver advances were tracked in a notebook. And when a customer called asking where their material was, someone had to call the driver, hope he answered, and call the customer back. They knew they needed a proper system, but they did not want a complicated ERP that would take months to implement and require their team to learn completely new ways of working.

What we built: a unified TMS with web admin and mobile app

We built a Transport Management System that replaced all five tools with one platform. The system has two parts. On the web side, an admin panel where office staff create trips, assign drivers and vehicles, manage advances, track trip expenses, and see live status of all active trips on a single dashboard. On the mobile side, a Flutter app for drivers — they log in, see their assigned trip, mark check-in and check-out, record expenses with photo receipts, and confirm delivery with a photo and signature. The GPS location is captured automatically at key events so the office knows where the vehicle is without a separate tracking system. Everything syncs even when the driver is in areas with poor network coverage. The office dashboard updates in real time as drivers complete each step. What used to require calls to five different people and tools now shows up on one screen automatically.

How offline sync solved the biggest adoption risk

The biggest challenge was network connectivity. Drivers travel through rural Gujarat highways, GIDC industrial areas, and remote delivery locations where mobile signals are weak or nonexistent. If the app needed internet to work, drivers would skip using it and fall back to WhatsApp and phone calls. So we built the driver app with offline-first sync from day one. The driver opens the app, does his work — check-in, record expense, mark delivery — all without internet. The data is stored safely on the phone. When the driver reaches an area with signal, the app syncs everything to the server automatically. The office never loses visibility, and the driver never has to think about connectivity. This single design decision was the reason the app was adopted. In the first month itself, drivers were using it consistently because it never blocked them from doing their job.

The results: what changed after the system went live

Within two months of going live, the transport company saw measurable changes. Trip expense reconciliation that used to take two to three days at month end now happens in under an hour because every expense is recorded in the app with a receipt photo at the time it happens. Driver advance tracking that was done in a notebook is now visible in the admin panel — the owner can see exactly how much each driver has taken and what is pending settlement. Customer inquiries about delivery status now get answered in seconds by checking the dashboard instead of calling the driver and waiting for a callback. The GPS location capture at trip events eliminated the need for a separate GPS tracking subscription, saving a monthly cost. And because the system replaced WhatsApp-based coordination, the owners stopped needing to monitor multiple chat groups to know what was happening in their fleet.

What the client said after using the system

The feedback that mattered most was from the operations team. The person who used to spend the first two hours of every morning calling drivers to confirm they had started their trips now opens the dashboard, sees which trips are active, and spends that time on actual planning instead. The drivers reported that the app was simple enough to use without training — they filled expenses, marked deliveries, and moved on. The owner said the single biggest improvement was being able to see the complete picture of the day's operations on one screen without having to ask anyone for updates. For us as builders, the best sign was when the client asked for additional features after the first month — not because something was broken, but because they wanted the system to do even more now that they trusted it.

What we learned that can help other Gujarat transport businesses

Three lessons from this project apply to any transport or logistics business considering a similar system. First, offline sync is not optional if your vehicles travel through areas with patchy network. Without it, the app will fail on the first trip and your team will go back to WhatsApp. Second, keep the driver app simple — drivers are not office staff. They should open the app, tap two or three buttons, and be done. Complex multi-step forms will not be filled on the road. Third, start with trip management and expense tracking before adding advanced features like route optimization or customer portals. Get the core workflow right first, prove it works, then expand. The same approach works whether you manage 5 trucks or 50. If you run a transport business in Gujarat and want to see what a similar system could look like for your fleet, WhatsApp us. We can discuss your specific requirements and give you a clear proposal.

Ready to scope a build?

WhatsApp AS Infosolution in Ankleshwar — detailed quote within 48 hours.

Chat on WhatsApp →