We built this because the spreadsheet was not working
Fleetvolts started in 2024, in Detroit, because Carlos Mendez kept seeing the same problem: fleet ops managers running 30 to 60 electric vehicles and still scheduling overnight charges manually. The vehicles were right. The electricity costs were not. The problem was the software layer between the dispatch plan and the charger.
Company story
Before starting Fleetvolts, Carlos spent six years building route optimization systems for a logistics technology company. He watched fleets add electric vehicles to their mix and hit the same wall: the vehicles performed fine, but nobody had built the scheduling layer to match. Charging was managed with a combination of static overnight timers, manual priority calls, and a lot of guesswork about what the utility bill would look like.
Yemi came from the hardware side. He had spent years on embedded systems for EV charging equipment and knew the OCPP protocol from the inside. He saw charger networks that could accept smart charging profiles and had no software sending them anything useful. The gap between what the hardware could do and what fleet operators were actually configuring was wide.
Fleetvolts fills that gap. It reads tomorrow's route plan, predicts how much energy each vehicle will actually need, and schedules charging sessions around electricity prices and depot power limits. The result pushes to the chargers over OCPP. No spreadsheet, no manual priority queue, no bill shock from a demand charge peak nobody saw coming.
The people behind Fleetvolts
Spent six years building route optimization systems for a logistics technology company before starting Fleetvolts. Watched electric vehicles arrive in fleets that had no scheduling software ready for them. That gap is what Fleetvolts addresses.
Previously led embedded systems development for EV charging hardware. Knows the OCPP protocol from the charger side. Designed the integration layer Fleetvolts uses to push SmartCharging profiles to EVSE networks.
Principles behind the product
Per-vehicle, not fleet-average
Fleet-average range assumptions will strand vehicles. Every energy prediction in Fleetvolts is specific to the route, the vehicle class, and that vehicle's consumption history. Generic estimates are what we replace.
Ops-first design
A fleet manager at 5am should see the full night's outcome in one view: which vehicles are ready, which ran on priority windows, what the depot demand curve looked like. Not a dashboard designed for a software demo.
Open protocols, no lock-in
OCPP 1.6 and 2.0 are open standards. Telematics APIs are accessible. We connect to the infrastructure you already have and we do not require you to replace it. Switching charger brands does not break your Fleetvolts integration.