EV Fleet & Logistics Services Marketplace for Enterprise Mobility
How we moved enterprise EV service sales, fleet records, and rider operations into one production platform
Executive Summary
Backend, admin web app, and rider app delivered and live in production
Enterprise service pipeline from request to rider task execution
Replaced legacy tool, spreadsheets, WhatsApp, calls, and email
From kickoff to delivered, live, and handed-over platform
The Challenge
An Indian EV mobility platform serving enterprise logistics clients needed to move its enterprise service sales and fleet operations out of fragmented tools and into a single operational system. The company served enterprise customers that needed EV logistics capacity by category, location, budget, frequency, industry, and delivery date. Each inquiry required commercial review, bundle pricing, agreement handling, and operational execution through riders and vehicles. At the same time, rider onboarding, vehicle compliance records, company structures, locations, and daily order tasks all had to be managed consistently. Before the new platform, this work depended on a legacy system plus spreadsheets, WhatsApp, calls, and email. The result was a disconnected service pipeline with no self-serve enterprise path, no unified operational view, and limited visibility across riders, vehicles, companies, locations, and tasks.
Key Pain Points
- ✕Enterprise service requests handled through calls, email, and manually assembled quotes
- ✕Agreement documents exchanged outside any system
- ✕Rider, vehicle, licensing, and compliance records tracked in separate processes
- ✕No single source of truth across riders, vehicles, companies, locations, and tasks
Our Solution
Amasa built a three-surface platform over approximately 7 months of active build: a modular Node.js and TypeScript backend, an admin web app for the platform's ops team, and a rider-facing app for daily execution. The product digitized the service-request-to-fulfillment loop end to end. Enterprise admins create service requests with category, location, budget (stored as paise integers), monthly or quarterly frequency, industry, and delivery date. Super admins review requests with filters for date range, status, location, and enterprise, then attach or detach priced service bundles with discounts. Enterprises accept a bundle by uploading agreement documents or reject it with remarks, and orders and order tasks drive execution in the rider app. The platform also covers rider lifecycle management, vehicle management, licence and registration document tracking, company and employee structures, location management, roles and permissions, AWS service integration, and push notifications. The system is delivered, live in production, and handed over.
Implementation Approach
Operations Discovery
Mapped the enterprise service sales pipeline, fleet records, rider lifecycle, and order-task execution into one product design
Platform Build
Built the modular Node.js/TypeScript backend, React admin web app, and rider-facing app
Service Pipeline Digitization
Implemented service requests, priced bundles with discounts, agreement uploads, orders, and order tasks
Production Launch & Handover
Went live with roles, permissions, AWS integration, and push notifications, then handed over to the client
The Results
The implementation delivered transformative results across all key metrics, with immediate impact on operational efficiency, accuracy, and customer satisfaction.
Impact Metrics
| Metric | Before | After | Improvement |
|---|---|---|---|
| Time per request | Manual coordination across 5 tools | Structured in-platform flow | Single pipeline |
| Turnaround visibility | Multi-touch manual handling | Tracked end to end by request status | Full visibility |
| Operational view | Disconnected tools per function | One system across fleet, riders, and sales | Unified |
| Revenue pipeline | Manually brokered service deals | Structured digital enterprise pipeline | Digitized |
Key Takeaways
- Enterprise service procurement and operational execution belong in one system, not a sales tool plus disconnected fleet records
- Structured request, bundle, and agreement flows give enterprise customers a self-serve path that calls and email never can
- Rider, vehicle, company, and location data connected in one platform removes reconciliation work entirely
- A three-surface build (backend, admin, rider app) lets ops teams and field staff work from the same source of truth
Inside the Engagement
The Workflow Before
An enterprise request typically started with a call, email, or informal service inquiry. Operations staff gathered the category, location, budget, desired frequency, industry, and delivery requirements, then manually assembled quotes or service bundles. Agreement documents were exchanged outside the system, while rider records, vehicle documents, licensing, registration, and compliance data were tracked in separate processes.
Order execution was also coordination-heavy. Ops teams assigned work to riders, managed task status, and reconciled information across tools. Because enterprise service requests, fleet records, and rider tasks lived in disconnected systems, the business lacked one reliable source of truth.
The Workflow After
- An enterprise admin creates a service request with category, location, budget, frequency, industry, and delivery date.
- A super admin reviews requests using filters for date range, status, location, and enterprise.
- The super admin attaches or detaches priced service bundles and discounts.
- The enterprise accepts with an agreement document upload or rejects with remarks.
- Orders and order tasks drive execution in the rider app.
- Rider, vehicle, company, employee, and location records remain connected inside one platform.
Riders receive assigned work through the rider app instead of relying on manual coordination. Platform operators manage fleet, rider, company, and service-request data from a single admin interface. Multi-company access is governed through roles and permissions rather than ad-hoc spreadsheet controls.
Full Results
| Metric | Before | After |
|---|---|---|
| Time per request | Manual coordination across spreadsheets, WhatsApp, calls, email, and a legacy tool | Structured in-platform request, bundle, agreement, and order-task flow |
| Turnaround visibility | Multi-touch manual service-request handling | Tracked end to end through request status and operational modules |
| Manual steps | Calls and email quotes, offline agreements, fragmented records | In-platform request, bundle acceptance, agreement upload, and task execution |
| Operational view | Fleet, rider tasks, and enterprise requests in disconnected tools | One system across riders, fleet, companies, locations, and enterprise sales |
| Revenue pipeline | Manually brokered service deals | Enterprise service sales on a structured digital pipeline |
The Impact
The platform consolidated ops coordination across enterprise service sales, riders, fleet, and order execution. Enterprise customers gained a clearer self-serve path for requests and transparent bundle pricing. Riders gained a structured task flow instead of relying on manual coordination. The client replaced a fragmented legacy setup with one operational system for service procurement and fulfillment.
The Takeaway
Amasa digitized service requests, bundle pricing, agreement handling, rider onboarding, vehicle records, and order-task execution for an Indian EV mobility platform – replacing a legacy tool plus spreadsheets, WhatsApp, calls, and email with one production platform, delivered over 7 months and handed over live.
Quick Facts
Industry
Logistics
Solution Type
Process Automation
Published
August 24, 2026
Technologies Used
Related Resources
Ready to Achieve Similar Results?
Let's discuss how we can transform your business with AI solutions tailored to your specific needs