Case study
ELYN — EV Charging Platform
Strategic focus · Unify fragmented EV charging under one OCPI-native eMSP
Full eMSP ecosystem for Armenia and Georgia — mobile app, operator admin panel, and OCPI 2.2.1 roaming. Discovery through development-ready handoff with 170+ features and 390 screens defined.
Role
Lead PM · UX Lead · Technical Researcher
Duration
5 months
Phase
Discovery + design (dev-ready handoff)
Team
1 designer (PM-managed)
Markets
Armenia · Georgia
Domain
IoT · EV infrastructure · OCPI 2.2.1 · B2B
Key distinction
Before any design started, I built a small MVP using vibe coding to validate how the system would work — covering station discovery, session control, and admin panel structure. This MVP became the foundation for the full feature specification and design system.
Problem Statement
What was broken — and what we built instead.
The Problem
- No unified EV charging app for Armenia/Georgia — users needed separate apps per CPO network
- No roaming capability — EV drivers couldn't charge across operator networks seamlessly
- No standardized billing — each CPO had different pricing and settlement models
- Station operators had no unified admin panel to monitor multi-CPO sessions in real time
- No accessibility features — platform excluded users with disabilities
The Solution
- Single eMSP app aggregating all CPO networks under OCPI 2.2.1 — one app, all stations
- Full B2B roaming capability — drivers charge across ChargePoint, EVgo, Hubject, and local Armenian CPOs
- Standardized CDR billing and settlement — transparent pricing per session regardless of CPO
- Unified admin panel — real-time session monitoring, revenue tracking, OCPP charge point management
- Accessibility module — wheelchair filters, voice navigation, easy mode for simplified UX
Discovery
Research & Discovery
OCPI 2.2.1 protocol research, a vibe-coded MVP prototype, and stakeholder workshops — before any of the 390 screens were designed.
Delivery
Execution & Artifacts
Phase 1
MVP Prototype (Vibe Coding)
Before committing to 170+ features and 390 screens, I personally built a functional MVP to understand how OCPI 2.2.1 would operate within the system — specifically how charging sessions start, how stations communicate status, and how the admin panel would monitor live data.
MVP Admin Panel — Dashboard
Total stations, active sessions, revenue (AMD), energy delivered, and live charging sessions.
MVP Admin Panel — Charging Sessions
Live data per station: connector type, duration, energy (kWh), cost (AMD), and status.
MVP Admin Panel — Transactions
Top-ups, charges, refunds, and net revenue tracking per user.
MVP Web — Station Map
OCPP charge point management, real-time connector status, and coordinate-based station search.
System Architecture
Full stack: mobile/web → API gateway → core services → OCPI hub → CPO backends → physical stations → data layer.
Figma Feature Specification
Module-by-module breakdown with screen-level feature tables and design previews across flows.
Mobile Application
Mobile App Screens
Station Discovery Map
Station card preview with availability, distance, price per kWh, partner logo, and photos.
Session Start — QR Scan
QR scan with NFC tap option, manual entry fallback, connector legend, and error states.
Search Filters
AI-powered "My Perfect Charger", connector types, speed tiers (L2/DCFC/Ultra/Hyper), and amenities.
User Profile
Profile completion, account settings, vehicle telematics, sessions, wallet, and safety tools.
Product Screens
Station Detail & Partner Experience
Station Detail — States
Live energy sold chart, busy times, and week-over-week comparison on the States tab.
Station Detail — Reviews
Reliability score, ratings, photo reviews, and tabbed navigation (Overview / Specs / States / Review).
Accessibility — Easy Mode
Simplified station detail UX for easier reading and interaction.
Partner Offers Module
Offers Hub, Hotel Directory (Stay & Charge), parking deals, retail rewards, and business vault on the map.
Core Features Delivered
What I Built
Station Discovery
Map view, search, filters (connector type, speed, amenities), AI-powered My Perfect Charger, availability markers
Session Control
QR scan, NFC tap, manual station ID, session start/stop, real-time energy and cost tracking, error states
Station Detail
Overview, specs, live states, reviews, reliability score, directions, call, and website
Payment Methods
Wallet top-up, card management, Apple Pay/Google Pay, transaction history, invoices, QR Pay
Vehicle Management
Add vehicle wizard, multi-vehicle switcher, telematics, connected dashboard, range on map
Multi-CPO Payments
OCPI 2.2.1 CDR billing, roaming payments, settlement processes, and billing schema documentation
Partner Offers
Offers Hub, Hotel Directory (Stay & Charge), parking deals, retail rewards, business vault analytics
User Profile & Settings
Profile gamification, addresses, notifications, auth, wallet, privacy, security, refer & earn
Accessibility & Inclusivity
Wheelchair accessible filter, voice navigation, easy mode, high contrast, font size controls
My role
What I owned vs what I delegated
My Ownership
- OCPI 2.2.1 protocol research — personally studied and mapped to system requirements
- Full product discovery — stakeholder workshops, client meetings, requirements gathering
- Feature specification — 170+ features across 9 modules, all documented with screen-level detail
- MVP prototype — personally built using vibe coding to validate system behaviour pre-design
- System architecture diagram — full stack from client to CPO backends and databases
- UX direction — wireframes, user journey flows, design system direction
- Design management — screen-by-screen review, feedback, iteration with designer
- Bilingual technical documentation (EN/RU) — API specs, CDR schemas, settlement processes
- B2B partnership presentations — executive-level stakeholder alignment for roaming agreements
Team Execution
- 1 Designer — visual execution of 390 screens based on my UX direction and feature specs
- Development not started — full handoff package delivered to future development team
Outcomes
Impact & Metrics
Approach
- Self-taught OCPI 2.2.1 and mapped protocol requirements to product modules, billing, and session flows.
- Built a vibe-coded MVP before design to validate station discovery, sessions, and admin monitoring.
- Specified 170+ features across 9 modules with screen-level documentation for design handoff.
- Managed end-to-end UX direction, design QA, and bilingual technical documentation (EN/RU).
Outcomes
- Single eMSP app design aggregating CPO networks under OCPI 2.2.1 — one app, all stations.
- B2B roaming flows for international and local CPO partners with standardized CDR billing.
- Unified admin panel for live sessions, revenue, and OCPP charge point management.
- Accessibility built in: wheelchair filters, voice navigation, and easy mode.
- 100% development-ready handoff — 390 light/dark screens, zero dev started.
Skills demonstrated
PM competencies proven in this project
Domain Research
OCPI 2.2.1, CPO/eMSP, OCPP session flows
MVP Development
Vibe-coded prototype pre-design
Feature Prioritization
170+ features across 9 modules
Technical Documentation
Bilingual API specs & CDR schemas
Wireframing & UX
Journeys, flows, design system direction
Stakeholder Management
Workshops & B2B roaming negotiations
Product Lifecycle
Discovery → design → handoff
Accessibility Design
Wheelchair, voice nav, easy mode
Platform Capabilities