Research Brief · August 2026
A teardown of onebharatcharge.com — an EV-charging aggregation play for India — checked against the live 2026 market, the competitive field, the protocol stack, RBI's payment rules, and the actual unit economics. Written to be built from, not pitched from.
00 — Plain English
EV charging has an unusually dense acronym soup, and the original site uses all of it without explanation. Read this once and the rest of the brief is straightforward.
Someone owns the physical charger (CPO). Someone sells you access to lots of chargers through an app (eMSP — this is what One Bharat Charge wants to be). OCPI is the language those two speak so your app can start a stranger's charger and the money ends up in the right place. UEI is India's free, government-backed version of that same idea. Everything else below is detail.
locations
(where the chargers are), sessions (a charge in progress), cdrs
(the receipt), tariffs (pricing), tokens (who's allowed to charge),
commands (start/stop remotely), credentials (the handshake).token_aEvery term above, in the order it appears in real life:
01 — Teardown
Read carefully, the site is a fundraising and CPO-recruitment landing page — not a live consumer product surface. That distinction matters enormously for anyone copying it.
~87 KB, one file, no framework, no build step. Google Fonts (Playfair Display / DM Sans / DM Mono). Nine anchor sections: Opportunity, Platform, Investors, For CPOs, Bharat, USP, App, About, Contact.
The page states the Android app is "fully functional" with station map, booking, live sessions and a unified wallet. No Play Store link, no iOS, no web app, no public API docs, no pricing page.
An independent studio positioning itself around telecom infra, enterprise architecture and AI/RAG.
Three contact addresses on the onecharge.in domain — investors@, partners@, hello@.
/locations sync and Beckn /search, over a claimed 10,000+ charge points across 35+ CPO networks.START_SESSION, the Beckn confirm flow, or direct REST per CPO; automated CDR reconciliation.token_a credential exchange → /locations sync → live.Several headline numbers on the site are stale or soft. If you reuse this narrative, fix these first — an investor who checks will find them in one search.
02 — Market reality, mid-2026
This is the strongest part of the thesis. India crossed double-digit EV penetration in 2026 and charging supply is being funded aggressively. The market timing argument holds up.
Public charging demand is overwhelmingly a four-wheeler and commercial-fleet phenomenon. 1.4M electric two-wheelers sold in FY26, but they charge at home off a 5A socket. The ~194k electric cars — plus e-3W fleets, e-cabs and last-mile delivery — are what fill a DC bay. Sizing your app to "40M EVs by 2030" is a category error; size it to public sessions.
The market is genuinely fragmented, which is the premise the whole idea rests on — and that premise checks out. No single CPO holds above 20% network share; the top five (Tata Power, Tecso ChargeZone, Sharify, Fortum, Kazam) together hold roughly 55–60% of active public charge points. A driver genuinely does need multiple apps.
03 — Competitive field
This is the part the original site does not mention at all. Every element of its pitch — one app, one wallet, OCPI roaming, UEI membership — is already shipped by someone with funding.
| Player | Type | Scale / traction | Capital | Threat to a clone |
|---|---|---|---|---|
| UEI / Beckn Alliance |
Open network | ~13,000 sessions/day, 60 MWh/day, 30 members. Launched Apr 2024, MoP-endorsed. | Public good | Existential It commoditises discovery + roaming — the exact layer you'd charge for. |
| ElectricPe | Pure aggregator | 25,000+ live stations, 60+ partner networks. Founded 2021. Has diversified into EV retail, finance, servicing, 126+ stores. | ~$8M+ disclosed | Direct Same pitch, five years of head start. Note the pivot into retail — the aggregator alone didn't pay. |
| Pulse Energy | Aggregator + CPO SaaS | Positions as India's largest aggregator of fast charging; carries Tata Power EZ, Electreefi, PlugShare and others. Vocal UEI advocate. | VC-backed | Direct Owns both the consumer app and the CPO back-end — the strategy you'd want. |
| ChargeZone | CPO turned network | 13,500+ stations reachable via OCPI roaming deals with Statiq, Bolt, Kazam, Pulse Energy. | ~$97.8M | High Proves CPOs can roam bilaterally and skip the aggregator entirely. |
| Statiq | CPO, app-first | 7,000+ charge points, 60 cities. Won a BPCL tender. $18M round Feb 2026 (Tenacity Ventures, Y Combinator, Shell Ventures). | $45.5M total | High Best consumer app UX among CPOs; drivers may never feel the need for a layer above it. |
| Kazam | CPO SaaS / asset-light | ₹40 Cr revenue FY25, tracking ₹100 Cr run-rate, guided to profitability by early 2026. IFC-backed. Strong in 2W/3W and residential. | IFC + VC | High The only one with proven revenue discipline. Owns the low-cost network layer. |
| Tata Power EZ, Jio-bp Pulse, BPCL, Ather Grid, Bolt.Earth | OEM / oil-major captives | Balance-sheet-funded, bundled with vehicle or fuel-retail footprint. | Corporate | Structural Zero incentive to let an aggregator own their customer. Hardest to sign. |
Discovery through aggregators reportedly drives 40–60% of first-time sessions at a station. That is real leverage over a CPO — it is the single strongest argument you have in an integration call, and it is why CPOs sign roaming deals at all.
04 — The honest case against
None of these are reasons not to build. They are the things that will actually decide the outcome, and none of them appear on the original site.
The site argues OCPI integration creates "high switching costs." It does the opposite — OCPI is a standard. A CPO that integrated with you in 48 hours can integrate with your competitor in 48 hours, and with a roaming hub in one. Standardisation lowers switching costs for everyone, including away from you.
Beckn/UEI exists precisely to make cross-network discovery and settlement a free public protocol, backed by the Ministry of Power and the people who built UPI and ONDC. Building a private toll booth on a rail that is being deliberately made free is a strategically exposed position. Better to build on UEI and sell what UEI doesn't: reliability, UX, fleet tooling.
The "48-hour onboarding" flow assumes a CPO wants to be listed. Tata Power, Jio-bp and Ather have their own apps, their own wallets, and their own customer relationship to defend. The independents will list with you happily — but they're also the ones with the worst uptime. Coverage of the good chargers is the bottleneck, and it is commercial, not technical.
A CPO's gross margin is roughly ₹8–16/kWh. Your slice of that is a few percent of the session. At a realistic ₹15–25 per session, ₹10 Cr of revenue needs on the order of ~5–7 million sessions a year — versus the entire UEI network's ~4.7M/year today. See §10 for the full arithmetic.
A stored-value prepaid wallet spendable at third parties is a semi-closed PPI under RBI's Master Direction — net-worth thresholds, escrow rules, audits, KYC. "Wallet float revenue" is not a casual revenue line; it is a regulated business. There is a clean way around this — see §9.
Public DC charging skews to premium four-wheeler owners — disproportionately iOS in India. Shipping Android-only excludes a meaningful slice of exactly the highest-value cohort.
05 — Where a copy could actually win
If you build the same consumer aggregator, you are competing on app-store marketing spend against six funded teams. These are the positions where the same codebase wins instead.
~5,000 of India's 27,737 registered stations are non-operational. Every EV driver's top complaint is arriving at a dead or blocked charger. Discovery is solved and free; trust is not. Build a verified-uptime layer: OCPP/OCPI telemetry, crowdsourced check-ins, a per-station reliability score, and a "we'll refund your detour" guarantee. That is a consumer reason to open your app instead of Google Maps — and it is defensible, because it's a data asset that compounds.
e-cab, e-3W and last-mile delivery fleets charge daily, on contract, at predictable volumes — the opposite of the retail driver who charges twice a month. Sell a fleet console: driver RFID/token management, per-vehicle spend limits, consolidated GST invoicing, charge-vs-route planning, reimbursement. Subscription + per-session, invoiced monthly. No PPI licence needed. Ten fleets beats a hundred thousand app installs.
Instead of a consumer brand, be the roaming/settlement middleware: one integration for a CPO, reach into every eMSP, automated CDR clearing and dispute handling. Charge per settled CDR. This is unglamorous, hard to displace, and the layer Pulse Energy is already reaching for — which is evidence it works, not that it's taken.
The trip planner is the one genuinely under-served feature on the site's list. Nobody in India does credible SoC-aware NH routing with live availability, real tariffs, and a booked slot at arrival. Intercity range anxiety is the actual blocker to 4W EV adoption. Narrow, emotional, marketable — and a legitimate reason for a CPO to want to be in your index.
Tata, Mahindra, MG, Ather and every mid-size CPO need a charging app and none want to build one. Licence yours: their brand, your rails, your roaming index underneath. Recurring revenue, and it converts your worst competitors into distribution.
Build the consumer app as the demo and data-collection surface, monetise through Wedge 02 (fleets) from month one, and let the reliability dataset (Wedge 01) become the thing that's actually hard to copy. Skip the prepaid wallet at launch (§9).
06 — The credits & partner network
A driver on a DC fast charger is physically immobilised for 30–45 minutes, within walking distance of one specific set of shops, with nothing to do. There is almost no other retail context this captive. The charging session is the loss-leader. The dwell time is the business.
You take ₹15 on a ₹300 charging session — a 5% slice of a low-margin commodity. A ₹400 meal at the dhaba 80 metres away, at a standard 15% food-service commission, is ₹60. The samosas are worth four times the electricity. And unlike the electricity, nobody is currently competing for them at that location, at that moment.
Call the currency Bharat Miles for now (placeholder — but the airline-miles mental model is exactly right, and drivers will understand it instantly). Four mechanics define it:
Roughly 2% of session value — a ₹300 charge yields ~6 Miles at ₹1 each. Bonus multipliers for the behaviour you want: off-peak charging, first session at a new CPO, filing a station reliability report, a completed highway trip.
This is not a design preference, it is the compliance boundary. The moment a user can buy credits and spend them at a third-party merchant, you have re-created a semi-closed PPI and dragged the RBI licensing problem from §9 back in. Earned-only, non-transferable, non-refundable, expiring loyalty points sit outside that perimeter. Confirm the current position with counsel — but design to this line from day one.
Miles are spendable during the charge, within ~500 m. This single constraint does three jobs at once: it manufactures urgency, it guarantees the merchant the footfall is a real nearby customer, and it makes credit-farming fraud structurally hard. Unspent Miles fall back to a smaller general balance.
"38 minutes left. ₹120 in Miles. Café Rasoi is a 90-second walk."
The failure mode of every loyalty scheme is funding rewards out of your own thin margin. Here you don't have to — the merchant is buying guaranteed, timed, walking-distance footfall, and the CPO is buying utilisation on a dead bay. See the funding table below.
| Funder | What they're buying | Cost to you | Use it for |
|---|---|---|---|
| Merchant-funded The default |
Guaranteed footfall in a known 40-minute window, from a customer already standing 80 m away. Far better targeting than any ad they can buy. | Zero | Everyday redemption. This should be 80%+ of all Miles spent. |
| CPO-funded The clever one |
Utilisation on dead chargers. Indian CPOs' single biggest pain is bays sitting idle. Let them bid Miles to route drivers to under-used sites — a demand-routing auction. | Zero | Filling low-utilisation stations. Also your strongest CPO sales pitch: you bring demand, not just a listing. |
| OEM / co-brand | Owner delight and post-sale engagement. Tata or Mahindra funds Miles for its own drivers as a bundled ownership perk. | Zero | Launch campaigns, cohort acquisition, white-label deals (Wedge 05). |
| Platform-funded Use sparingly |
Behaviour you want and can't otherwise buy: off-peak shifting, reliability reports, first session, new-corridor seeding. | Real | Treat as a marketing line with a hard cap. It is CAC by another name — but far cheaper CAC than app-install ads. |
Your addressable merchant market is not "restaurants in India." It is "businesses within 500 m of a charger you already index" — and you know the exact coordinates of every one of those chargers, because you pulled them over OCPI.
Map the buffer, and the national list is a few thousand merchants; the NH-48 / NH-44 / NH-19 / NH-8 charging corridor is a few hundred. That is a sales list a two-person BD team can work through in a year — as opposed to the unwinnable land-grab against Zomato and Swiggy in the general case.
| Category | Why it fits the 40-minute window | Priority |
|---|---|---|
| Highway restaurants, dhabas & food plazas | Perfect duration match. Zero existing digital demand-gen. Desperate for footfall. Driver is hungry, stationary and has no alternative within 20 km. | Beachhead |
| Cafés & QSR near urban DC hubs | A coffee is exactly a 30-minute purchase. High repeat frequency. Easy to sign, easy to redeem. | Beachhead |
| Highway hotels & resorts | Big basket, high margin, and they'll often install the charger themselves to get the listing — turning a merchant into a site host. | Phase 2 |
| Convenience / fuel-station retail | Chargers increasingly sit at BPCL/HPCL/IOC forecourts. The shop is already there. Institutional deals, not one-by-one BD. | Phase 2 |
| Malls, cinemas, family entertainment | Dwell time far exceeds the charge — the charger becomes their parking amenity. They pay for anchor footfall. | Phase 2 |
| Car care: wash, detailing, tyres, service | Contextually perfect — the car is already parked and idle for 40 minutes. Genuinely additive service, high ticket. | Phase 3 |
| EV-adjacent: insurance, accessories, tyres, AMC | Miles as a discount on things only EV owners buy. High intent, and the data to target it is already yours. | Phase 3 |
| Stream | Model | Note |
|---|---|---|
| Redemption commission | 10–20% of the partner bill when Miles are redeemed | The core line. Bigger per event than the charging fee itself. |
| Merchant listing / placement | ₹2,000–8,000 per outlet per month | Predictable recurring revenue that does not depend on redemption volume — the healthiest line on this table. |
| CPO demand-routing auction | CPOs buy Miles to pull drivers to idle bays | Sells the one thing CPOs desperately need. Pure margin; costs you nothing to fulfil. |
| Sponsored placement | Promoted merchant in the in-session panel | Only ~3 slots exist per location, which makes them scarce and therefore valuable. |
| Dwell-time footfall analytics | Reports to site hosts, mall operators, oil majors | "Chargers here drove 1,840 walk-ins last month." That's the number a site host renews a lease on. |
| Co-branded OEM programmes | OEM buys Miles in bulk for its owners | Large single contracts; pairs naturally with white-labelling. |
| Breakage | Miles that expire unredeemed | Real accounting reality — but never build the plan on it. A programme optimised for breakage is one drivers stop trusting. |
Reworking the §10 model with a commerce layer attached. Attach rate is the share of sessions where the driver actually redeems at a partner — assumed conservatively.
The commerce layer roughly doubles revenue per session; it does not make a volume-starved platform viable. 7,200 sessions/day is still a very large number in 2026 India. What it genuinely changes is three things: it makes each session worth fighting for, it gives you a merchant-funded reason for drivers to open your app instead of Google Maps, and — via listing fees — it adds recurring revenue that doesn't wait for session scale.
Note also the urban row barely moves. This business is a highway-corridor business. That is a real strategic constraint, and it happens to align exactly with Wedge 04.
Once Miles can shift driver behaviour, you own a demand-response lever — and that has buyers well beyond restaurants. India's grid peaks in the evening; solar is abundant midday. CPOs pay punishing demand charges at peak.
Offer 3× Miles for charging 11am–4pm. The CPO's demand charges fall, its solar utilisation rises, and it funds the Miles happily because the saving exceeds the reward.
Distribution companies fear EV load stacking onto the 6–10pm peak. A platform that can provably move charging demand by time of day is a policy-relevant asset, not just an app.
Restaurants have their own dead hours. Align Miles multipliers with the merchant's empty 3–6pm window and you're arbitraging two idle assets against each other with the same token.
This is now a three-sided network — CPOs, drivers, merchants — and each side is waiting for the other two. That is the single biggest risk in this section. The sequencing matters more than the design.
Start issuing Miles from session #1. It costs nothing, it's an unfunded liability of trivial size at low volume, and it quietly builds a balance drivers want to use. Show the balance prominently. Say "partners coming soon" honestly.
Walk into highway restaurants with a specific, local, verifiable number: "1,340 drivers stopped within 500 m of you last month and they are holding ₹2.1 lakh in credits they can only spend nearby." That is a far better opening than any commission deck, and it is a claim only you can make.
A driver needs to find a partner at their stop, not somewhere in India. Saturate one corridor — say Delhi–Jaipur on NH-48 — until redemption is near-guaranteed at every stop on the route. Then market that corridor as a complete experience and repeat.
Once the corridor works, the pitch to a reluctant CPO inverts: you're no longer asking for a listing, you're offering a footfall-and-utilisation package their own app cannot produce. This is the point where the merchant network stops being a feature and becomes the moat.
§4 argued that the aggregation layer has no moat: OCPI makes integrations cheap and UEI makes discovery free. Both are true, and neither touches this. UEI will never build a merchant network. It is a protocol, not a business — it standardises the transaction and stops there.
A local, physical, contract-by-contract network of a few thousand merchants next to specific chargers is slow to assemble, geographically defensible, and gets more valuable with every driver. It is precisely the kind of asset a protocol cannot commoditise — and the only thing in this entire brief that a well-funded competitor can't replicate in a quarter.
07 — Product scope
| Capability | Priority | Notes |
|---|---|---|
| Map + station discovery live availability, connector type, power, tariff | P0 | Table stakes. PostGIS + a tile provider. Cache aggressively — CPO APIs are slow and rate-limited. |
| OCPI 2.2.1 eMSP versions, credentials, locations, sessions, cdrs, tariffs, tokens, commands | P0 | The core asset. Build it as a standalone service with a conformance test suite from day one. |
| Session start/stop + live telemetry | P0 | Remote start over OCPI commands; poll sessions for kWh/SoC. Handle the failure modes — this is where the UX is won or lost. |
| Payments (UPI per-session, no wallet) | P0 | Pre-auth via UPI mandate or card, capture on CDR. Avoids PPI licensing entirely. See §9. |
| Station reliability score | P0 | Your differentiator. Start collecting from session #1 — it can't be backfilled. |
| Fleet console tokens, spend limits, GST invoicing, reports | P1 | Where the revenue is. OCPI tokens module already models driver credentials. |
| Beckn BAP on UEI search / select / init / confirm / status | P1 | Joins you to the public network for free coverage. Also strong credibility signal. |
| CDR reconciliation + settlement ledger | P1 | Double-entry, immutable, dispute workflow. Get this wrong and CPOs leave. |
| Trip planner with SoC simulation | P1 | Valhalla/OSRM + elevation + a per-model consumption curve. High marketing value. |
| CPO SaaS dashboard | P2 | Utilisation, revenue, downtime alerts. Cheap to add once you hold the data; a retention hook. |
| iOS app | P2 | Do not repeat the original's Android-only choice for long. Use a cross-platform stack so this is nearly free. |
| 8-language localisation | P2 | Cheap and good optics, but the 4W public-charging cohort is largely English-comfortable. Don't front-load it. |
| Prepaid wallet | P3 | Only after a PPI licence or a licensed BaaS partner. Not a launch feature. |
08 — Technical architecture
The protocol work is well-specified and genuinely not that hard. The difficulty is that every CPO's OCPI implementation is subtly wrong in a different way, so the architecture must isolate that mess behind an adapter boundary.
┌─────────────┐ ┌─────────────┐ ┌──────────────┐
│ Mobile app │ │ Fleet web │ │ CPO dashboard│
│ (RN/Flutter)│ │ console │ │ (Next.js) │
└──────┬──────┘ └──────┬──────┘ └──────┬───────┘
└────────────┬────┴─────────────────┘
▼
API Gateway · JWT + refresh rotation, rate limits, idempotency keys
│
┌───────────┬───────┴────┬─────────────┬──────────────┐
▼ ▼ ▼ ▼ ▼
Discovery Session Payments Ledger Routing
PostGIS orchestr. pre-auth / double-entry Valhalla +
+ Redis state m/c capture CDR recon SoC model
│ │ │ ▲
└─────┬─────┘ │ │
▼ ▼ │
PROTOCOL ADAPTER LAYER ── normalise every CPO quirk here ──┘
┌──────────────┬──────────────┬─────────────────┐
│ OCPI 2.2.1 │ Beckn BAP │ Direct REST │
│ eMSP module │ on UEI │ per-CPO shims │
└──────┬───────┘──────┬───────┘────────┬────────┘
▼ ▼ ▼
CPO OCPI UEI / ONDC legacy CPO
endpoints network private APIs
| Layer | Pick | Why |
|---|---|---|
| Mobile | React Native or Flutter | iOS parity for near-zero extra cost. The original's Android-only stance is a self-inflicted wound. |
| Backend | Go, or Node/NestJS | OCPI is I/O-bound HTTP plumbing. Either works; pick what your team ships fastest in. |
| Primary DB | Postgres + PostGIS | Geospatial radius/bbox queries, plus a strict relational ledger. One database until it hurts. |
| Cache | Redis | Availability state has ~30–60s useful life. Never call a CPO on the map-pan path. |
| Events | NATS or Kafka | Session state changes and CDR arrival are async and must be replayable for reconciliation. |
| Maps | Mappls (MapmyIndia) or Google | Mappls has materially better Indian addressing/POI density; Google has better familiarity. Abstract behind an interface. |
| Routing / SoC | Valhalla or OSRM, self-hosted | You need elevation-aware costing and custom consumption curves. Hosted routing APIs won't give you that. |
| Payments | Razorpay or Cashfree | UPI mandates / pre-auth, RuPay, cards. Both support the auth-then-capture flow that charging needs. |
| Auth | Phone OTP + JWT w/ refresh rotation | India-standard. Don't build email/password. |
1. CDR arrival is asynchronous and unreliable. A session ends; the CDR may arrive seconds later, hours later, or never. Your money flow cannot assume it. Design an explicit reconciliation state machine with timeouts, estimated-vs-final amounts, and a dispute path.
2. Pre-auth sizing. Hold too little and you eat the shortfall; hold too much and UPI users see a scary block. Model it on connector power × expected dwell, and refund the delta the instant the CDR settles.
3. Every CPO's OCPI is non-conformant somewhere. Missing tariffs, wrong timezones,
stale EVSE status, UNKNOWN connector types. Write a per-CPO conformance
suite and a quirks registry before you write feature #2.
09 — Regulatory & compliance
Under the MoP Guidelines of 17 September 2024, setting up and operating an EV charging station is an unlicensed activity — no electricity trading licence needed. The same guidelines lay down interoperability standards. As a software aggregator you're further removed still: you sell no electricity, you route a transaction.
A stored-value balance that a user tops up and spends at third-party CPOs is a semi-closed prepaid payment instrument under RBI's PPI Master Direction — which carries minimum net-worth thresholds, escrow requirements, KYC tiers, audits and reporting. Confirm current thresholds against the live Master Direction before you plan around it; they have been revised more than once.
Don't hold customer money. Run pay-per-session: a UPI Autopay mandate or card pre-authorisation at session start, captured against the actual CDR at session end, settled to the CPO through your payment aggregator. You lose the "wallet float revenue" line — which was never material at low volume anyway — and you gain the ability to launch without a licence, an escrow account, or a compliance hire. Add a wallet later via a licensed PPI partner if retention data justifies it.
This section is a research summary, not legal advice. Every item here needs confirmation with Indian counsel against current text before you rely on it.
10 — Unit economics
The original lists five revenue streams and no numbers. Here is what one session is actually worth, using published Indian margin ranges. Treat these as an order-of-magnitude model to challenge, not a forecast.
To make ₹10 Cr on session fees alone, you would need to route more sessions than the whole government-backed UEI network currently clears in a day. Session take-rate is a real revenue line but it is not a business on its own at 2026 volumes. It becomes one around 2028–2030 if penetration keeps compounding.
This is precisely why ElectricPe diversified into EV retail, financing and 126+ physical stores. It is the strongest single piece of evidence in this whole brief.
| Stream | Model | Viability now |
|---|---|---|
| Fleet subscriptions | ₹X per vehicle/month + per-session fee, invoiced | Strong — contracted, predictable, no app-store CAC, daily usage |
| CPO SaaS dashboard | Per-charge-point per-month | Strong — Kazam has proven Indian CPOs pay for software |
| White-label app licensing | Setup fee + annual licence | Medium — long sales cycle, large contracts |
| Session platform fee | 3–8% of GMV | Medium — real but volume-starved until ~2028 |
| Reliability/utilisation data | Reports to CPOs, OEMs, site hosts, lenders | Medium — genuinely scarce data; needs scale first |
| Wallet float | Interest on prepaid balances | Weak — needs a PPI licence; escrow rules constrain it; immaterial below huge scale |
11 — Build plan
Assumes 2 backend, 1 mobile, 1 full-stack/web, plus a founder doing CPO business development full time. That last role is not optional — it is the actual bottleneck.
Sign 2–3 independent CPOs to a non-binding test integration. Complete one real OCPI
credentials handshake and pull live /locations. Register interest with the UEI
alliance. If you cannot get three CPOs on a call in a month, stop here — that
signal is worth more than six months of code.
Full 2.2.1 eMSP: versions, credentials, locations, tokens, sessions, cdrs, tariffs, commands. Per-CPO conformance suite and quirks registry. Ship a map app that only finds chargers — no payments. Start recording reliability data immediately.
Remote start/stop, live session telemetry, UPI pre-auth → capture-on-CDR, the double-entry ledger, and the reconciliation state machine. Launch in one city, not sixty-five. Target: 100 clean sessions with zero manual settlement intervention.
Driver token management, spend limits, consolidated GST invoicing, usage reports. Sell to 3–5 e-3W or e-cab fleets in your launch city. This is the first month you have real income. Beckn BAP goes live on UEI in parallel for free coverage.
Publish the station reliability index — it's your marketing and your moat in one artefact. Ship SoC-aware NH corridor routing. Ship iOS. Add the CPO dashboard as a retention hook. Expand city two and three only once city one's unit economics are legible.
Miles have been accruing silently since Phase 2 — that's deliberate, and by now drivers hold a balance you can point at. Pick one corridor, walk the 500 m buffer around every charger in it, and sign every viable merchant. Ship QR redemption with an offline fallback and weekly merchant settlement. Do not open a second corridor until redemption at the first is near-guaranteed at every stop.
12 — Risk register
| Risk | Severity | Mitigation |
|---|---|---|
| Major CPOs refuse to list Tata Power, Jio-bp, Ather defend their own apps |
Critical | Lead with the 40–60% first-session discovery stat. Offer them fleet demand they can't source alone. Accept partial coverage and be honest in-app about what you don't cover. |
| UEI makes your layer free | Critical | Join it rather than fight it. Monetise above the protocol — reliability, fleet tooling, UX, settlement ops — not the routing itself. |
| Session volumes stay too low to fund the company | Critical | Do not depend on take-rate before 2028. Fleet subscriptions and CPO SaaS carry the P&L in years 1–2. |
| Reconciliation errors burn CPO trust | High | Immutable double-entry ledger, daily automated recon reports, a named dispute SLA. Over-invest here; it's the thing that keeps partners. |
| PPI licensing blocks the wallet | High | Launch pay-per-session. Treat the wallet as a year-two feature behind a licensed partner. |
| A funded incumbent copies your reliability layer | Medium | Data compounds and can't be backfilled — start collecting from session one. Publish the index publicly to make it the reference. |
| Poor CPO API quality degrades your UX you get blamed for their downtime |
Medium | Show freshness timestamps and confidence, never a false "available". Honesty about stale data is a feature drivers will notice. |
| CAC exceeds lifetime value on retail drivers | Medium | Don't buy installs. Acquire through fleets, OEM bundles and highway-corridor content. |
| Three-sided cold start on the credits network no drivers → no merchants → no drivers |
Critical | Accrue Miles from day one with nothing to spend them on, then use the accumulated balance as the merchant pitch. Saturate one corridor before opening a second. Never launch the partner network before ~300 sessions/week in that corridor (§6). |
| Credits get classified as a prepaid instrument | High | Hard design rule: earned-only, never purchasable, non-transferable, non-cashable, expiring. Get the structure reviewed before the first Mile is issued, not after. |
| Credit-farming and merchant collusion | Medium | Bind every redemption to a verified CDR, a live geo-fence and the session time window. Per-session and per-day caps. Monitor redemption-to-session ratios per merchant. |
| Merchants churn over slow settlement | Medium | Weekly payouts minimum. Small highway businesses run on cash flow and will quietly stop honouring Miles long before they tell you. |
| Tariff/policy change compresses margins | Low | You take a percentage, not a spread. Regulated tariffs actually reduce your risk. |
13 — Before writing code
The problem is real, the timing is defensible, and the technical build is a solved, well-documented four-to-six-month exercise for a competent team. The idea's weakness is that it is a distribution and commercial-agreements business wearing a protocol-engineering costume. Copy the codebase premise; do not copy the go-to-market. Win on reliability data and fleet contracts, and let discovery be the free thing you give away.
Sources
All figures retrieved August 2026. Market projections are third-party estimates; verify anything load-bearing before it enters a deck.