EV Software Lives or Dies in the Field. We Engineer for the Field.

It is the engineering of software systems that run electric mobility — charging network platforms (OCPP, OCPI, ISO 15118), fleet management and telematics, battery analytics, route and energy optimization, V2G and smart-grid integration, and connected vehicle apps for OEMs. AddWeb builds production-grade EV systems for charge point operators, fleet operators, and EV OEMs across North America, Europe, and APAC.

Discovery Sprints start at $15,000 USD. Single-platform production builds (a charging back office, fleet AI module, or OEM driver app) typically range from $85,000 to $145,000 USD. Multi-platform engagements (multiple capabilities or multi-region rollouts) start at $360,000 USD. Annual support contracts start at $9,500 USD per year. Final pricing is calibrated during your Discovery Call.

Yes. AddWeb Solution maintains its US headquarters in Greenville, South Carolina, with additional offices in New Jersey and Melbourne, Australia. Our delivery center is in Ahmedabad, India. This US-registered structure simplifies procurement, contracting, and IP transfer for North American and European EV clients — including NEVI-funded public charging programs.

OCPP 1.6 and 2.0.1 for station-to-cloud communication. OCPI 2.2.1 for roaming and inter-network interoperability. ISO 15118 for Plug & Charge. OpenADR 2.0b and IEEE 2030.5 for utility and demand-response programs. We also integrate OEM telematics APIs (Geotab, Samsara, Verizon Connect) and major charging network APIs.

A 2 to 3 week Discovery Sprint validates feasibility and produces a fixed-scope proposal. Standard production builds run 12 to 18 weeks from PO to live deployment. Multi-platform engagements run 4 to 6 months. Multi-region or multi-OEM rollouts run 6 to 12 months and are delivered in phases.

Three primary buyer types: charge point operators (CPOs) deploying public, workplace, and depot charging networks; fleet operators electrifying logistics, delivery, ride-share, and corporate fleets; and EV OEMs and Tier-1 suppliers building telematics, driver apps, and connected-vehicle data products. We also serve energy utilities running smart-charging programs and public-sector agencies managing municipal fleet electrification.

Yes — fully. On final payment, all source code, AI models, training data pipelines, integrations, and runbooks transfer to your team. No retention. No lock-in. Master Service Agreement assigns 100% of IP to your company. Hardware vendor warranties pass through from the OEM as standard.

Yes. Our EV practice is built to work with major ecosystem platforms — AMPECO, EV Connect, Driivz, ChargePoint Network for charging; Geotab, Samsara, Verizon Connect for telematics; and OEM telematics APIs. We support major cloud platforms (AWS IoT Core, Azure Digital Twins, GCP IoT) and standard payment processors (Stripe, Adyen). We adapt integrations to your existing stack — we do not force you onto ours.

Data residency is a first-class architectural decision. We support EU, UK, US, India, and Australia data-residency requirements. Default architecture: customer and driver data never leaves your environment. We design for GDPR, CCPA, and DPDP compliance from day one — including driver consent management, location-data minimization, and driver-app privacy controls.

V2G is shipping in production today, but only for specific use cases — managed depot charging for fleets, virtual power plants for utilities, and bidirectional vehicles approved for V2G operation. We build the orchestration layer (OpenADR signaling, IEEE 2030.5, dispatch scheduling) and integrate with the bidirectional chargers and approved vehicles in your scope. We do not promise V2G economics that depend on regulatory approvals you do not have.

Most charger integration is software-side via OCPP. We test against major manufacturers (ABB, Siemens, Wallbox, ChargePoint hardware, Delta, ENGIE Eways, Tritium, Kempower) during Discovery and Factory Acceptance Testing. For deep integrations or custom firmware coordination, we work directly with the OEM during your station selection. We document supported and unsupported chargers in the Discovery deliverable before any procurement.

Packaged platforms are excellent for standardized network operations under ~500 stations. Custom builds make sense when you need: differentiated driver UX, multi-network roaming logic that the platform does not support, custom pricing or revenue-share models, deep integration with your existing fleet or energy system, or sovereign data residency. We assess fit honestly during Discovery — if a packaged platform serves you better, we will tell you.

For CPOs: typical payback in 9 to 14 months, driven by uptime improvement, reduced support cost, and roaming-revenue capture. For fleet operators: 6 to 12 months, driven by charging-cost optimization, reduced range incidents, and fleet utilization. For OEMs: longer (18+ months) but higher strategic value, driven by connected-vehicle data products and customer retention. Discovery includes a calibrated ROI model based on your actual operations.

Yes. Schedule a Discovery Call with our EV practice. We will review your buyer type (CPO / fleet / OEM), your existing stack, your data, and your regulatory environment, and tell you directly whether build, buy, or partner is the right answer for your specific problem. No sales pitch.