Volteum

If you need a full telematics and safety platform in a single purchase

• Consider vendors such as Samsara, Verizon Connect, Motive, or Geotab for combined hardware and software safety/compliance solutions; Volteum may be better used as a complementary EV optimization layer.

If procurement requires public proof of security certifications

• If SOC 2 or ISO 27001 documentation must be publicly available, Volteum’s public materials (based on the reviewed sources) may not meet that requirement without additional vendor-provided evidence.

If you require fully transparent pricing for quick procurement

• Vendors that publish standard pricing or simpler packaging may reduce procurement friction.

If EV operations are minimal or still exploratory

• For organizations with only a handful of EVs and limited depot constraints, the ROI of advanced scheduling and forecasting may not justify the implementation effort.

Current limitations acknowledged or implied by the vendor and research

• No explicit limitations page was found in the official sources reviewed.
• The platform’s dependency on OEM API coverage implies not all vehicle data fields will be available for every vehicle type or region; refresh rates and reliability can vary.

Roadmap

• Public roadmap details and timelines were not found in sources reviewed.

Scale limitations

• Performance characteristics at very large scale are not publicly documented; request reference architectures and performance SLAs for enterprise procurement.

Security or compliance gaps

• Public documentation of security certifications and formal trust-center materials was not found in the sources reviewed.

Integration constraints

• OEM API dependence implies integration variability: incomplete data fields, varying refresh rates, and possible regional restrictions.

• The vendor describes an approach that can avoid installing telematics devices by using OEM APIs to collect vehicle data. This approach can reduce vehicle downtime from hardware installation where API coverage is sufficient. Buyers should validate OEM coverage and data field availability for their vehicle mix.

• The platform combines planning (simulation, TCO, infrastructure planning) and operations (range forecasting, charging schedule optimization, dynamic allocation) capabilities.

• Presence on the Geotab Marketplace suggests a path to integrate with existing Geotab telematics deployments or to complement them with EV-specific planning and operations features.

• "the interface feels dated" (user describing Geotab)
• Complaints about device battery life for trackers in one fleet ("swapping them every few months… became a whole thing")

Royal Mail trial (reported by Fleet News)

• Fleet News reported Volteum expanded services to UK fleets after a Royal Mail trial.
• Critical evaluation
  • This indicates real-world testing with a large organization, which is a positive signal. Public details are limited: scope of the trial, duration, KPIs, baseline comparison, and independent measurement were not fully documented in accessible excerpts.

OTP Bank (vendor-published news item)

• The vendor published a news item titled "OTP Bank builds cost-efficient EV strategy with Volteum."
• Critical evaluation
  • As vendor-published content, it likely emphasizes positive outcomes. Without third-party validation or detailed metrics, treat results as directional and verify claims with references during procurement.

Vendor award announcement

• The vendor published an award announcement regarding a recent fleet software award.
• Critical evaluation
  • Awards can assist with shortlisting, but they do not guarantee suitability for specific operational constraints (OEM diversity, charging topology, compliance requirements).

• Likely best fit for mid-market to enterprise fleets where electrification planning and ongoing EV operations optimization materially affect cost and service levels.
• Indicative ranges (subject to vendor validation):
  • Mid-market fleets: fleets on the order of several dozen up through low-thousands of vehicles
  • Enterprise fleets: larger fleets in the thousands with multi-depot operations

• Corporate fleets transitioning to EVs.
• Leasing and fleet-portfolio stakeholders.
• Postal and last-mile logistics (suggested by a reported Royal Mail trial).
• Enterprises running sustainability or electrification programs (vendor-published OTP Bank example).

• Decision makers
  • Head of Fleet / Fleet Director
  • Sustainability/ESG lead
  • Operations leadership
  • Finance (CFO) for TCO analysis
• End users
  • Fleet managers
  • Depot managers
  • Dispatch and route planners

• Operational uncertainty when deploying EVs (range forecasting and charging management).
• Charging scheduling complexity and depot optimization.
• Selecting appropriate EV models for real duty cycles.
• Consolidating visibility across mixed fleets.

• Adequate OEM API coverage across the fleet vehicle mix.
• Meaningful electricity cost variability or constrained charging capacity where scheduling optimization can yield measurable benefits.
• Need for both planning and operational tooling rather than only basic telematics.

• Requirement for a single-vendor full telematics and safety platform (ELD/HOS/DVIR, dashcams) as a primary buying criterion.
• Fleets comprised primarily of older vehicles or OEMs without robust API access.

What the product does (core value proposition in objective terms)

• Volteum is a fleet electrification and EV fleet management software platform focused on two primary workflows:
  • Planning the transition from internal combustion engine (ICE) vehicles to EVs (vehicle suitability assessments, route/duty-cycle simulation, charging infrastructure planning, TCO comparisons).
  • Operating EV and mixed fleets day-to-day (range and energy forecasting, charging schedule optimization, vehicle allocation, and live fleet telemetry insights).
• The vendor states the platform can operate without installing additional telematics hardware by connecting to vehicles via OEM APIs and aggregating data (mileage, fault codes, charging sessions, maintenance intervals, costs) in a single platform. This is a vendor-reported capability and should be validated for specific vehicle makes, models, and regions.

Target market and market positioning

• Positioned for organizations operating EV or mixed fleets and for stakeholders managing fleet portfolios (corporate fleets, leasing companies, staff/benefit car fleets) seeking EV operational visibility and electrification planning without installing telematics devices in every vehicle.
• The vendor reports short deployment timelines (described in marketing as "live in days") and emphasizes reduced capital expenditure and installation downtime by using OEM APIs instead of telematics hardware. These are vendor claims and should be validated during procurement.

Company background (founding year, HQ, key leadership)

• Volteum lists founders Dávid Kertész, Krisztián Putti, Zsófia Tóth, and Kornél Kálmán on the About page.
• Public materials indicate ties to Hungary (e.g., Budapest address in the privacy policy; Hungarian job postings on LinkedIn).
• LinkedIn indicates a small team size.
• Founding year is not clearly stated on official site pages reviewed; third-party directories may provide estimates but are not authoritative.

Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public

• Funding information is not clearly disclosed on official website pages reviewed.
• Third-party startup directories report modest disclosed funding totals that vary by source and may be incomplete.
• Customer count and revenue are not publicly stated in official materials reviewed.

Pricing model with specific tiers and costs where available

• The vendor does not publish transparent, self-serve pricing on the official site pages reviewed. Calls-to-action reference contacting the vendor and a free-trial offering; the terms and limits of the trial were not specified in the accessible pages.

Total cost of ownership considerations (implementation, training, hidden costs)

• Potential cost reducers (vendor-reported)
  • Avoidance of telematics device purchase/installation and associated vehicle downtime by using OEM API connectivity is a stated benefit.
  • The vendor reports potential per-vehicle savings compared with traditional telematics installation and significant avoided capital expenditure per depot; these figures are vendor-provided and were not independently validated in the sources reviewed.
• Potential cost adders / buyer considerations
  • OEM API data coverage varies by vehicle make/model and region; gaps may require fallback solutions (for example, integrating with existing telematics providers or installing hardware for unsupported vehicles).
  • Integration, data normalization, and change management can create implementation overhead, particularly for large fleets with heterogeneous OEMs and multiple charging/energy providers.
  • If pricing is quote-based, budget predictability can be more challenging than vendors with published per-vehicle monthly pricing.

Key competitors in the space (list 4-6 direct alternatives)

• Geotab
• Samsara
• Verizon Connect
• Motive
• Chevin FleetWave
• RTA Fleet