01Case studies
How real deployments are put together
The constraints, the decisions and what changed — written for operators evaluating whether the same approach would work for them.
Cutting field dispatches in half on a 46-connector highway corridor
A corridor operator with sites spread over 600km of national highway rebuilt its fault-handling around remote triage — and stopped driving to reset chargers.
National highway corridor, North India
46
DC connectors across 17 sites
600km
Corridor length
~4 hrs
Average drive time to a site
Automating revenue share across a 12-property retail portfolio
Twelve malls, twelve different revenue-share agreements, and a finance team spending a week a month on statements nobody trusted.
Tier-1 and tier-2 cities, West India
12
Properties under one operator
~1 week
Finance time per month, before
3
Different revenue-share structures
Fitting a full depot behind an existing sanctioned load
Adding buses meant either upgrading the connection — eighteen months and substantial capex — or making the existing one go further.
Municipal depot, South India
28
Buses charging overnight
1
Sanctioned connection, unchanged
4 hrs
Departure window every morning
From installed hardware to paying drivers in six days
Eight connectors, no software team, and a loan repayment schedule that started before the chargers did.
Tier-2 city, North India
8
Connectors at launch
6 days
Hardware connected to first paid session
0
Software engineers on the team
Building an eMSP on roaming connections rather than capital
A fleet-card business already had the drivers. What it did not have was a charging network — and no intention of building one.
Multi-state, West and South India
0
Chargers owned
6
Roaming partners connected
1
Invoice per fleet, per month
Shipping hardware with a platform already attached
Every buyer asked "what software runs it?" and the answer was always somebody else. That answer was costing the recurring revenue.
Manufacturing in North India, buyers nationwide
2
Product lines, AC and DC
1
Tenant provisioned per buyer
100%
Under the manufacturer’s brand
Guest, staff and public charging on the same eight bays
Charging was installed because guests asked. Two years later nobody could say whether it was earning or losing.
Nine properties, North and West India
9
Properties
3
Audiences on the same hardware
0
Dedicated headcount
Low-power charging at the volume India actually runs on
The segment that dominates Indian electrification is three-wheelers — and almost nothing in charging software is built for it.
Four hubs, National Capital Region
140
Three-wheelers
4
Hubs
2
Shift changeovers a day
Public charging under a tender, with the reporting it demands
Subsidised public charging comes with reporting obligations. They are discovered late, and reconstructing them from incomplete records is painful.
Public charging under a state tender
38
Public sites under the tender
Quarterly
Reporting obligation
Per site
Granularity required
Resident charging billed to the flat, not to the sinking fund
Sixty residents with EVs, one common electricity meter, and a managing committee meeting that came round every month.
Gated community, Tier-1 city
60+
Resident EVs
1
Common connection
Monthly
Billed with maintenance
Territory-scoped operations across 240 connectors
Individually every charger was manageable. Collectively they produced more exceptions per day than the team could chase.
Four states, North and Central India
240
Connectors
4
States
5
City managers
Charging in a car park where the average stay is four days
Airport parking inverts every assumption in charging: the dwell time is enormous, and that is the problem rather than the opportunity.
Long-stay car park, major airport
4 days
Average stay
18
AC bays, 2 DC
24×7
Arrivals and departures
Repricing 60 connectors on evidence rather than instinct
The headline rate was competitive and the sites were busy. Realisation per kWh was still well below what the tariff implied.
Two metros, South India
60
Connectors repriced
3
Time-of-day windows
0
Change to the headline rate
Would this work for your network?
Bring your sites, hardware and partner structure. We will tell you honestly which parts translate and which do not.