Problem
India's last-mile logistics operators are rapidly electrifying their fleets under FAME-III incentives and e-commerce green-delivery mandates, but small fleet operators (5–50 EVs) have no software that treats charge state as a first-class routing constraint. Existing fleet management tools (Fleetx, Raftaar) were built for diesel vehicles and cannot model range limits, charging slot conflicts, or battery degradation curves. A driver stranded mid-route due to charge exhaustion costs ₹3–10K in failed deliveries and idle hours — a failure mode diesel-era software simply does not anticipate.
Solution
A SaaS dashboard and Android companion app that ingests live vehicle state-of-charge via manufacturer fleet APIs (Ather, Ola Electric, Mahindra, Piaggio Ape Electric all publish documented fleet APIs), combines it with Google Maps Distance Matrix for route feasibility, and produces day-start dispatch plans guaranteeing every vehicle completes its run before battery drops below 15%. The v1 core flow: operator logs in → system polls charge levels → drag-and-drop route assignment with real-time feasibility check → push notification to each driver with optimised stop sequence. A secondary module tracks battery health trends and flags vehicles approaching 80% cycle degradation so operators can schedule servicing before a breakdown.
Why Now
India's commercial EV fleet grew 62% in FY2025 (SMEV data) and is doubling again by FY2027 as Zomato, Zepto, Meesho, and Shiprocket enforce green SLAs on last-mile partners. The India Startup Funding Update for May 4–8, 2026 explicitly identified "logistics firms transitioning to EV fleets" as one of the highest-conviction capital-efficient opportunities in India. Fleet APIs from Indian OEMs became stable and publicly documented only in late 2025, meaning software integration at low engineering cost is viable for the first time — the window to build the category-defining tool is open right now.
Target User
First 1,000 customers: owner-operators of 10–30 EV three-wheelers in Tier-1 logistics hubs (Delhi-NCR, Pune, Bengaluru, Chennai) who aggregate delivery jobs from Shiprocket or Porter or directly from D2C brands. Monthly fleet revenue ₹5–25L. Tech-savvy enough to use WhatsApp for dispatch coordination but with no dedicated fleet software. Primary purchase trigger: first major failed-delivery incident caused by an EV charge-out event.
Business Model
₹500 per vehicle per month (flat rate, no per-route fees — operators dislike usage billing). A 20-vehicle fleet pays ₹10,000/month; 30-vehicle fleet pays ₹15,000/month. Target 500 active fleets at month 18 → ₹5Cr ARR. Gross margin ~82% (infra + API costs ~18% of revenue). Upsell at ₹200/vehicle/month: maintenance scheduling alerts and driver incentive dashboards. Annual prepay offered at 10% discount to improve cash flow.
Competitive Landscape
- Direct (India): Fleetx (diesel-centric, no EV range modelling), Raftaar (school buses only), no pure-play EV last-mile ops tool exists today
- Direct (global reference): Samsara EV suite (US), Geotab for EVs (Canada) — both priced ₹5–10K/vehicle/month for enterprise, inaccessible to Indian SME operators and lacking Indian OEM integrations
- Why we win: India-first OEM API integrations with Ather/Ola/Mahindra (US tools simply lack them), INR pricing tuned to SME budgets, and WhatsApp-native driver notifications that eliminate app-download friction entirely
6-Month Plan
- Month 1 (₹1.5L): Integrate Ather and Ola Electric fleet APIs; build charge-state polling service; recruit 3 pilot fleet operators in Pune via Porter/Shiprocket partner networks
- Month 2 (₹2L): Route feasibility engine using Google Maps Distance Matrix + SoC data; basic web dashboard; driver Android app in React Native
- Month 3 (₹2.5L): Live pilots with 3 operators, iterate on dispatch UX; add Mahindra Treo API; instrument failure cases
- Month 4 (₹2L): Battery health trend module; WhatsApp push notifications via Twilio; first paid conversions at ₹500/vehicle/month
- Month 5 (₹2L): Referral programme (operator invites peer for 1 month free credit); begin outbound sales in Delhi-NCR and Bengaluru
- Month 6 (₹2L): 50+ paying fleets; Piaggio Ape Electric integration; evaluate Series A readiness or sustain on revenue
- Total capex: ₹12L (₹6L engineer salaries × 6 months for 2 engineers + ₹3L infra and API costs + ₹3L field sales and ops)
Risks
- OEM API instability (high likelihood, medium impact): Indian EV OEM APIs are young and change without versioning notice; mitigate by building an abstraction layer and cultivating direct OEM partnerships for advance changelog access
- SME payment discipline (medium likelihood, medium impact): Small fleet operators may churn after free pilots without a clear ROI event; mitigate with annual upfront pricing at 10% discount and a mandatory charge-out incident report shared before trial ends
- Google Maps cost creep (low likelihood, medium impact): Heavy Distance Matrix API usage could erode margins at scale; mitigate by route-caching across similar daily runs and replacing batch planning with OSRM at high volume
Score Breakdown
- Market (14/20): India's commercial EV last-mile fleet is 500K+ vehicles growing toward 1.5M by FY2028; at ₹500/vehicle/month, 10% penetration yields ₹750Cr+ SaaS TAM — large, but the 3-year path to ₹1000Cr+ requires the market to mature, earning 14 rather than 20.
- Capital (12/15): Two engineers for 4 months plus infra fits inside ₹10L MVP budget; 12-month runway under ₹20L is achievable if founders take near-market salaries; loses 3 points because Android app and multiple OEM API integrations add meaningful complexity versus a pure-web SaaS.
- Team (8/10): Two full-stack engineers and one ops/sales person can ship v1 in 4–5 months with no specialist hardware required; loses 2 points because OEM API partnership work demands non-engineering relationship management from day one.
- Trend (12/15): India Startup Funding Update May 2026 names EV fleet logistics as high-conviction; FAME-III subsidies and e-commerce green SLAs create mandatory demand, not just preference; loses 3 points because B2B fleet software adoption is slower than consumer app virality.
- Moat (10/15): Charging-pattern data per city zone and per operator accumulates into a proprietary dataset; switching cost is real once routes, batteries, and driver behaviour are tracked in the system; loses 5 points because a well-funded competitor could replicate core features in 6–9 months without a strong network-effect barrier yet.
- Economics (11/15): ~82% gross margin on SaaS; LTV of a 20-vehicle fleet at ₹10K/month over 5 years is ₹6L+; CAC via direct sales is ₹20–40K per fleet; LTV:CAC ≈ 15–30x which is healthy; loses 4 points because CAC requires active field sales and viral loop is absent at launch.
- Speed (7/10): 10-week MVP is achievable; OEM API onboarding adds 2–3 weeks of uncertainty; a functional dispatch planner can be live internally at week 6 and with a paying customer by week 10–12.