The under-rated cost of VCU and BMS firmware on small EV programs

Founders pitch hardware. Investors fund hardware. But the thing that holds first deliveries on almost every small EV program we touch is firmware — specifically the VCU, the BMS, and the glue between them and the rider app.

Mechanical and electrical have decades of suppliers, off-the-shelf parts, and known-good reference designs. Vehicle firmware does not. Every program ends up writing — or heavily customizing — its own state machine, its own diagnostics, its own OTA path, and its own cloud backend. That work is invisible until it's late.

Our working budget on a clean-sheet two-wheel program is roughly 25–35% of total engineering spend on software, end to end. That includes BMS firmware, VCU app code, mobile app, cloud, and OTA infrastructure. Programs that budget half that number usually find the other half during pilot, at the worst possible time.

Start the software architecture in parallel with the chassis, not after it. Even a thin VCU running on representative hardware, talking to a real (if ugly) cloud, will surface 80% of the integration pain while it's still cheap to fix.