A charging network rarely stalls between 10 and 100 sites because drivers stop coming. It stalls because systems built for ten sites are still running at sixty: site judgement living in one person’s head, spares in one cupboard, support in one inbox, records in a spreadsheet nobody else can read. Scaling is replacing each of those with a written system — before it breaks, on evidence from the sites you already run.
Key Takeaways
- Growth breaks systems, not demand: judgement, installation, spares, reporting, support and purchasing each need a written system.
- Build each replacement before the break, from the first sites’ records — utilisation, faults, contacts, cost per session.
- Standardising models per site pattern is the quiet multiplier: one spares logic, one document set, one training story.
- There is no staff-to-sites ratio to copy; the queue inside your own system is the hiring signal.
What Breaks, Stage by Stage
| System | How it runs at 10 sites | What breaks as sites multiply | The system to build before it breaks |
|---|---|---|---|
| Site selection | The founder walks a site and judges it | Judgement does not travel; new regions get sites chosen on hope | An evidence template written from the first sites’ records: dwell, parc, supply, host terms |
| Installation delivery | One trusted installer, booked by phone | One crew cannot be in five places; quality varies by who showed up | A partner bench plus a commissioning standard every install is signed off against |
| Spares and field service | A cupboard of parts and a familiar technician | The cupboard serves one geography and one model; waits grow with distance | Tiered holding per part class, contracted field cover, and a per-port fault log |
| Platform and reporting | The founder glances at one dashboard | Hosts, funders and programme duties ask for per-site evidence nobody assembles | A reporting rhythm per port: uptime, sessions, faults — produced routinely, not on request |
| Driver support | One inbox, answered by whoever is free | Contacts scale with drivers, not sites; cases age unseen | A published promise, staffed hours, and a categorised contact log that is audited |
| Purchasing | Chargers ordered as each site lands | Every new model multiplies spares, documents and training across the estate | Model standardisation per site pattern, with supplier terms confirmed in writing |
The Evidence Comes From the First Ten
None of these systems is designed from theory. The first sites’ records — utilisation, fault pattern, contact categories, cost per session — are the template inputs: what a good site looked like becomes the site-selection checklist, and what actually failed becomes the spares list. That is the difference between scaling and merely adding. The single-site discipline in our guide to opening a charging station still applies at every new site; what changes is that a system, not a person, carries it there. Profitability questions get the same treatment — answered per site from its own ledger, as our look at whether a charging station business is profitable sets out, then rolled up, never assumed across the estate.
Standardise the Hardware, Multiply Less
Purchasing is where scale is won quietly. A network that standardises models per site pattern keeps one spares logic, one document set and one training story per class of site. In the EVDANCE range, the EV-AC03201T dual-connector AC station (two Type 2 connectors, up to 43 kW shared, OCPP 1.6J, RFID, IP54) and the EV-RHDC30K-L compact DC charger (22 kW DC, OCPP 1.6J, IP54) both state OCPP 1.6J, so a mixed AC-and-compact-DC estate still reports into one platform discipline. EVDANCE, founded in 2011 with a 3-year standard warranty, offers no platform of its own — the platform, and the reporting built on it, remain the operator’s arrangement, as the OCPP explainer describes. Networks standardising a purchase can work through our commercial EV charging team, the reseller and distributor programme, or contact us.
Frequently Asked Questions
Which system usually breaks first?
The one your own records already strain. In practice it is often records and support, because both scale with driver contacts and reporting duties rather than with sites. Read the strain from your first sites’ logs — missed rounds, ageing cases, reports assembled by hand — and build there first.
Should a scaling network standardise on one charger model?
Standardise per site pattern where sites are alike; a single model everywhere is neither possible nor necessary. What matters is discipline: every additional model multiplies spares, documents and training, so each one admitted should earn its place in writing.
When should we hire dedicated operations staff?
When decisions queue on one person and the records show it — rounds slipping, cases ageing, reports late. No sourced ratio of staff to sites exists to copy; the queue inside your own system is the signal, and it appears before the crisis does.
Related Reading
- How to Open an EV Charging Station: Step by Step
- Is an EV Charging Station Business Profitable?
- How Do Commercial EV Charging Stations Work?
- OCPP Explained: What Charge Point Operators Need From EV Charger Hardware
