MicroVision pitches lidar 2.0 strategy on cost, software, modularity

What is MicroVision's lidar 2.0 strategy for commercial trucks?

MicroVision is positioning its next-generation lidar systems around four operational pillars: a modular product portfolio that reuses core technology across automotive and commercial vehicle applications, design-to-cost engineering that factors in hardware, software, manufacturing, serviceability, and reliability from the start, an open software framework that lets fleet customers and OEM partners write code directly to the lidar units, and fixed-budget financial discipline. Greg Scharenbroch, MicroVision's VP of global engineering, outlined the strategy during a presentation ahead of ACT Expo.

The first pillar addresses revenue volatility. MicroVision plans to develop core lidar technology that scales across automotive, commercial vehicle, industrial, and security markets with minimal incremental engineering effort. The goal is to smooth revenue peaks and valleys by diversifying the customer base rather than relying on a single vehicle segment.

How does design-to-cost affect fleet TCO?

MicroVision's second pillar borrows from automotive engineering practice: design-to-cost places equal weight on innovation and the total burden the product imposes on the end user. That burden includes upfront hardware cost, software licensing or subscription fees, manufacturing complexity that affects replacement-part availability, serviceability in a typical fleet shop, and field reliability that determines whether the unit stays in spec through a truck's useful life.

Scharenbroch's team includes engineers from automotive OEMs, where design-to-cost is standard discipline. The approach contrasts with lidar 1.0 suppliers that prioritized range and resolution specs without accounting for what it costs a fleet to keep the sensor calibrated, replace a damaged unit, or update firmware when the truck is 400 miles from the nearest authorized service center.

What does the open software framework mean for integration?

MicroVision's third pillar is software differentiation. Scharenbroch said hardware costs will continue to fall, leaving software capability and performance as the primary competitive lever. MicroVision's lidar systems will support an open software framework that allows customers and integration partners to apply their own code directly to the sensor.

For truck OEMs and Tier 1 suppliers building ADAS stacks, the open framework reduces development time by eliminating the need to reverse-engineer or work around a closed lidar API. Fleet customers running proprietary telematics or collision-mitigation software can integrate lidar data without waiting for MicroVision to release a feature update. The tradeoff is that open frameworks require more in-house software engineering capability than turnkey closed systems.

How does MicroVision's budget discipline affect product roadmap?

The fourth pillar is financial discipline. Scharenbroch said his engineering team operates within a fixed budget, a defined spend envelope, and a run rate that the team does not exceed. That constraint forces prioritization decisions — features that don't justify their development cost relative to customer willingness to pay get cut or deferred.

For fleets evaluating lidar suppliers, budget discipline is a proxy for supplier stability. Lidar 1.0 saw multiple startups burn through venture capital on feature sets that never reached production volume, leaving early adopters with orphaned hardware and no software-update path. A supplier that can ship product within a fixed cost structure is more likely to still be in business when a truck needs a replacement sensor in year five.

Where does this leave lidar adoption in trucking?

MicroVision's strategy assumes that lidar moves from proof-of-concept to volume production in commercial vehicles. That assumption depends on regulatory tailwinds — FMCSA has not mandated lidar for any ADAS function, and the 2027 automatic emergency braking rule allows radar-only systems — and on whether fleets see TCO payback from collision avoidance that justifies the sensor cost.

MicroVision acquired two companies to expand its lidar and perception-software portfolio in early May, adding sensor hardware and perception algorithms to its existing scanning-mirror lidar technology. The acquisitions signal that MicroVision is betting on integrated sensor-plus-software offerings rather than selling lidar as a standalone component.

The open software framework may appeal to OEMs building proprietary ADAS stacks, but it also means MicroVision is competing on a different axis than suppliers like Luminar or Innoviz, which bundle lidar with their own perception software and charge for the integrated solution. Fleets that lack in-house software engineering will still need a Tier 1 integrator or OEM to turn raw lidar point clouds into actionable collision warnings.

What fleets should watch for

MicroVision has not disclosed pricing for its commercial-vehicle lidar units, warranty terms, or which truck OEMs are evaluating the technology for series production. The design-to-cost claim will be testable once units reach the field — serviceability, parts availability, and whether the sensor holds calibration through a northern winter are the metrics that matter more than the range spec on the data sheet.

Fleets running pilot ADAS programs should ask lidar suppliers three questions: what does a replacement unit cost if a road hazard takes out the sensor, how long does recalibration take after a windshield replacement or front-end collision repair, and what happens to software support if the supplier exits the commercial-vehicle market. MicroVision's modular strategy and budget discipline suggest it plans to stay in the truck segment long enough to support a multi-year deployment, but the lidar 1.0 shakeout left enough orphaned hardware that skepticism is warranted until the first high-mileage field data comes in.