The moat is not the charger. The moat is the data loop around every charge.
Hardware can be copied. The stronger advantage comes from site selection data, fleet demand visibility, charger uptime, dynamic pricing and power procurement discipline.
Load balancing engine
Routes demand across chargers to reduce peak demand charges and protect power margins.
Predictive maintenance
Uses fault patterns to schedule service before uptime penalties hit fleet contracts.
Fleet API
Integrates vehicle, route and battery data so fleet customers can reduce idle time.
Engineering economics
In this case, a 1% improvement in uptime adds more value than a 1% reduction in head office costs. Why? Because uptime protects the revenue engine and avoids contract penalties.
| Technical metric | Valuation link | Student question |
|---|---|---|
| Uptime | Higher fleet renewal and kWh throughput | What uptime level is needed to justify premium pricing? |
| Charging speed | More sessions per location | Does faster charging increase margin or only revenue? |
| Demand forecasting | Better site capex allocation | Can management avoid low-return expansion? |
| Energy procurement | Improved spread per kWh | How stable is the power cost advantage? |
Moat scorecard
Fleet switching cost
Route integration and usage history make switching painful for fleet customers.
Location rights
Good sites matter, but leases can be renegotiated by large landlords.
Data advantage
The data moat grows only if SparkGrid has enough dense usage history.
Hardware exclusivity
Chargers alone are not a durable moat.