Owning the Building Control Layer
Lee Hoffman, co-founder of Runwise, on the operating system for buildings
The key move was turning a single painkiller product into control of the whole building stack. Runwise started with heating because owners would pay fast for a tool that cut fuel bills in months, then used the same wireless hardware layer to add cooling, leak detection, gas monitoring, and other controls. That made each new product cheaper to install, easier to sell, and harder to replace than a standalone app or dashboard.
-
The wedge worked because old buildings rarely have one standard system. Runwise spent years learning the handful of major heating and cooling architectures, then built sensors, controllers, and software that could drop into those legacy setups in a day or less instead of requiring weeks of rewiring.
-
This is the opposite of most building tech startups, which sell one narrow feature on top of existing controls. Runwise is trying to own the control layer itself, because that is where the live equipment data sits and where software can actually change boiler runtime, chiller behavior, leak alerts, and gas shutoff risk.
-
The comparable on the other end of the market is incumbents like Johnson Controls and Honeywell, which already span HVAC, fire, security, and controls, but historically through heavier hardware and contractor led installs. Runwise is attacking the same budget with a faster retrofit path aimed at older multifamily and commercial buildings.
From here, the logic is expansion through installed base. Once the wireless control network is in place, more products can be added at low marginal cost, and the company can evolve from saving heating dollars to becoming the default software layer for how existing buildings are monitored, automated, and eventually opened to third party applications.