Every software project starts with a problem. This one started with a phone call at 8am from a frustrated operations manager who couldn’t tell his client where their shipment was.<\/p>\n
This is the story of how we helped a mid-sized transport company based in Central India replace their spreadsheet-based operations with a real logistics management system \u2014 built and deployed in 11 weeks.<\/p>\n
Our client runs a fleet of 40+ commercial vehicles operating across Madhya Pradesh, Chhattisgarh, and Maharashtra. They handle B2B freight \u2014 raw materials, manufactured goods, FMCG distribution \u2014 for around 60 regular clients.<\/p>\n
For years they managed everything manually: driver assignments in notebooks, billing in Excel, client updates over WhatsApp, and fuel expense tracking on paper registers.<\/p>\n
It worked \u2014 until it didn’t.<\/p>\n
By the time they approached us, they were dealing with three serious operational issues every single week.<\/p>\n
Billing errors.<\/strong> Invoices were being raised from memory and rough notes. Discrepancies between what was charged and what was agreed were creating disputes with clients \u2014 and damaging long-term relationships.<\/p>\n No real-time visibility.<\/strong> Clients would call asking for shipment status. The operations team would then call the driver, wait for a response, and call the client back. In 2024, this was unacceptable to their larger corporate clients.<\/p>\n Fuel and expense leakage.<\/strong> Without a system tracking fuel consumption per trip against distance, there was no way to identify inefficiency or catch discrepancies. The fleet manager estimated losses of \u20b940,000\u201360,000 per month from untracked expenses.<\/p>\n The brief was simple: “We want to know where every vehicle is, what every trip costs, and be able to send our clients a proper invoice without doing maths by hand.”<\/em><\/p>\n We translated that into three core modules:<\/p>\n We spent the first two weeks doing nothing but listening. We visited their office in Jabalpur, sat with the operations team, rode along on one local delivery run, and mapped every manual process they had.<\/p>\n This discovery phase is something we insist on for every custom software project. The worst systems get built by developers who never leave their desk.<\/p>\n What we found shaped every decision we made:<\/p>\n Given the team’s profile and the need for reliability on low-bandwidth connections, we chose:<\/p>\n Backend:<\/strong> Laravel 11 (PHP) \u2014 fast to build, easy to maintain, proven in production<\/p>\n Frontend (web dashboard):<\/strong> React + Tailwind CSS \u2014 clean, fast, works well on mid-range laptops<\/p>\n Mobile (driver app):<\/strong> React Native \u2014 one codebase for Android, simple UI, offline-capable for basic functions<\/p>\n Database:<\/strong> MySQL \u2014 straightforward, well-supported, easy to back up on shared hosting<\/p>\n Hosting:<\/strong> DigitalOcean VPS (\u20b91,200\/month) \u2014 reliable, scalable, full control<\/p>\n We deliberately avoided over-engineering this. No microservices. No Kubernetes. A monolith that works reliably is worth more to a 40-truck fleet than a distributed system that needs a DevOps team to maintain.<\/p>\n Weeks 1\u20132:<\/strong> Discovery, wireframes, database schema design<\/p>\n Weeks 3\u20135:<\/strong> Core backend \u2014 trip model, vehicle model, client model, expense tracking logic<\/p>\n Weeks 6\u20137:<\/strong> Web dashboard \u2014 trip creation, assignment, live status board<\/p>\n Week 8:<\/strong> Invoice generation \u2014 PDF output, GST-compliant format, email delivery<\/p>\n Weeks 9\u201310:<\/strong> Driver mobile app \u2014 trip acceptance, status updates, expense photo uploads<\/p>\n Week 11:<\/strong> UAT with the operations team, bug fixes, staff training, go-live<\/p>\n We measured three things 60 days after go-live.<\/p>\n Billing disputes dropped to zero.<\/strong> Every invoice now generates directly from trip data. There’s no manual calculation and no room for discrepancy. The client told us two of their largest accounts specifically mentioned the improvement in billing accuracy.<\/p>\n Client update calls dropped by 80%.<\/strong> We built a simple client portal \u2014 just a URL with a trip reference \u2014 where clients can check their shipment status themselves. The operations team no longer spends 2 hours a day answering status calls.<\/p>\n Fuel expense tracking identified \u20b952,000 in monthly leakage.<\/strong> Within the first 30 days, the expense reports revealed two routes where fuel consumption was significantly higher than the distance justified. After investigation, the issue was identified and addressed.<\/p>\n The system paid for itself within the first two months of operation.<\/p>\n A few things stood out from this project that we carry into every engagement since.<\/p>\n Offline-first matters in India.<\/strong> The driver app needed to queue updates locally when connectivity dropped and sync when it returned. We underestimated how often this would happen on highway routes through MP and CG. Building this properly in week 10 was the hardest technical problem on the project.<\/p>\n Training is part of the product.<\/strong> We spent two full days on-site training the operations team. The software was useless until they trusted it. That trust came from showing them, not telling them.<\/p>\n Keep the first version small.<\/strong> The client originally wanted GPS tracking, driver performance scoring, route optimization, and a client mobile app. We talked them out of all of it for version one. Doing fewer things well meant they actually used it \u2014 and now they’re funding version two.<\/p>\n We’re currently building version two of this system, which adds real-time GPS tracking via a low-cost hardware device fitted to each vehicle, automated route planning, and a client-facing mobile app.<\/p>\n If you’re running a fleet, a logistics operation, or any business where manual processes are creating errors and costing money, we’d be glad to talk through what a custom system could look like for you.<\/p>\nWhat They Asked For<\/h3>\n
\n
Our Approach<\/h3>\n
\n
The Tech Stack<\/h3>\n
The Build \u2014 11 Weeks<\/h3>\n
The Results<\/h3>\n
What We Learned<\/h3>\n
What’s Next<\/h3>\n