01
Connect
Bring the charger online and map the right workflow before the session begins.
Launch QR-led charging, payment-linked sessions, and live operator control without forcing your teams into a generic EV suite. Built for subtractive operations: fewer screens, clearer actions, tighter visibility.
Session 0482
Energy delivered
Authorized budget
Remote stop state
Charger health
Session log
Charging flows in one stack
Operator control plane
Session-linked traceability
The customer journey and operator view should describe the same session. Charger state, payment state, support state, and logs need to move together instead of drifting apart.
Bring the charger online and map the right workflow before the session begins.
Tie QR flow, payment confirmation, and operator rules into one decision point.
Monitor telemetry, budget guardrails, and remote controls from the same live session.
Finish with payment state, logs, and support context still attached to the session.
Borrow the best lesson from subtraction-first product design: the platform should inhabit your workflow instead of forcing your people to work around software.
Generic EV Suite
Forces every site into the same interaction model
Separates charger state, payment state, and support context
Adds screens faster than it removes friction
Workflow-Native Platform
Maps each site to the right charging flow
Keeps session, charger, payment, and logs in one operational story
Optimizes for operator clarity before visual excess
Static QR, dynamic sessions, and hybrid rollout logic should live in one coherent frontend and one operator model.
Touchless charging for fixed locations where charger identity is stable and the journey must stay simple.
Site-wide QR deployment
Fast mobile handoff
Low-friction public charging
Session-first charging for operators who need explicit authorization, live control, and traceable payment steps.
Session-aware start
Live telemetry coupling
Precise charger-session linkage
Use both static and dynamic behavior inside one operator platform instead of forcing a single model everywhere.
Mixed site strategies
Migration-friendly rollout
One operational layer
The interface should surface the next right action and the evidence behind it. Session, charger, payment, and logging views have to feel like one system.
Live Layer
Watch the charging lifecycle as one continuous operational thread instead of a set of disconnected screens.
Pending to completed state progression
Budget-aware stop behavior
Remote start and stop visibility
Live Layer
Keep operator actions close to machine state so interventions are clear, fast, and auditable.
Remote actions with intent
Charger status awareness
Reduced operator hesitation
Live Layer
Bring payment verification, pre-auth, and settlement into the session story instead of burying them in finance tools.
Razorpay-native flow
Session payment checkpoints
Refund and stop context together
Live Layer
Keep logs close to the charger and session they belong to so support and operations can reason from evidence.
Session-related filtering
Charger-specific visibility
Structured operational events
The same frontend language should work for public charging, managed properties, fleet operations, and campus deployment without turning into a catch-all product.
Standardize operations across public chargers while still leaving room for site-specific flow design.
Support controlled charging windows, operational visibility, and less guesswork around charger readiness.
Run shared charging for employees, residents, or visitors without turning the interface into a training problem.
Deploy QR-led charging in apartments, hotels, and mixed-use sites with a cleaner customer journey.
This first page defines the visual and messaging system for the full route map. The next pages extend the same language into product, solutions, pricing, support, and public charging flows.