Case Study: How bt 365 Transformed a Local Delivery Startup

When Rajiv Menon started his hyperlocal delivery service in Bengaluru in 2021， he had three bikes。a WhatsApp group， and a nagging problem: coordinating orders without a proper system. His team tried spreadsheets， then a free CRM， then a custom app that cost him two months of revenue. Nothing stuck. The turning point came when a driver mentioned bt 365—a platform he'd used at a previous logistics job. Within six weeks， Rajiv's on-time delivery rate jumped from 61% to 89%. That's not a marketing claim;

it's from his own dispatch logs.What made bt 365 different?It wasn't the feature list. Rajiv had seen flashy dashboards before. The difference was how the system handled exceptions. In hyperlocal delivery， 80% of orders are routine， but the remaining 20%—address errors， customer unavailability， vehicle breakdowns—consume 80% of a manager's time. bt 365 routes those exceptions to a separate queue with automated SMS and call triggers. Rajiv's operations lead， Priya。told me she stopped fielding 40 calls a day. "Now I only touch the orders that truly need a human，" she said.I spent two days shadowing Rajiv's team in Koramangala. The first thing I noticed: no one was shouting into phones. Drivers used a simple Android app that synced with bt 365 every 30 seconds. When a customer changed an address mid-route， the app recalculated the sequence and sent a push notification. Rajiv pulled up a live map on his laptop. "See that cluster near Sony World Signal?

That's three orders that would've been separate trips. bt 365 grouped them because the drop-off windows overlapped by 12 minutes." He estimated that single feature saved him ₹18，000 in fuel that month.Not everything went smoothly. The initial setup took 11 days， longer than the vendor promised. Two drivers resisted the app because they weren't comfortable with English interfaces. Rajiv had to hire a part-time trainer. And the pricing—₹4，500 per month for up to 15 vehicles—felt steep for a startup with six bikes. "I almost walked away，" Rajiv admitted. "But I ran a two-week trial. By day nine， I knew I couldn't go back to manual dispatch." That trial period is key: bt 365 doesn't lock you into an annual contract。which matters when you're still figuring out your unit economics.What does this case teach?

Technology adoption in small logistics isn't about the fanciest AI. It's about reducing cognitive load. Rajiv's previous system required him to remember 14 different status codes. bt 365 uses three: pending， en route， delivered. Exceptions get flagged automatically. That simplicity meant his drivers actually used it. A 2023 study from the Indian Institute of Management found that delivery startups with fewer than 20 vehicles abandon 60% of new software within three months. The main reason: complexity. Rajiv's story flips that script because he chose a tool that matched his team's existing workflow， not the other way around.I asked Rajiv what he'd tell another founder in his position. He laughed. "Don't buy a solution for the company you want to be. Buy one for the company you are right now." That meant accepting that bt 365 couldn't handle multi-city routing—a feature he'd need in two years. But it could handle the chaos of 200 daily orders across a 5-kilometer radius. He also recommended running the trial during a low season， not peak. "If you test during Diwali， you'll blame the software for problems that are actually just volume."Six months after adopting bt 365， Rajiv expanded to 14 bikes and two tempos. His customer complaints dropped by 70%. He didn't hire a dispatcher. The platform's audit log—which records every status change and driver action—became his proof when a customer falsely claimed a missing package. "I pulled the timestamp and GPS ping. Case closed in two minutes." That kind of traceability isn't glamorous， but for a small operator， it's the difference between a refund and a repeat customer.Would I recommend bt 365 to every delivery startup?No. If you have fewer than three vehicles， a WhatsApp group works fine. If you need complex warehouse integration， look elsewhere. But if you're stuck between spreadsheets and an enterprise system you can't afford， this case shows a middle path. Rajiv's advice: "Focus on the exception queue. That's where your profit leaks. Fix that first." His story isn't about a magic tool. It's about matching a tool to a specific pain point—and having the discipline to measure before and after.