> In the hardware-lite case, you're basically starting a software company that needs to set up a supply chain for a few parts, built by others, which provides t

> In the hardware-lite case, you're basically starting a software company that needs to set up a supply chain for a few parts, built by others, which provides the most cost-effective platform for your software to run on. You might then package that up, brand it, and sell it. This can be relatively capital nonintensive. True to a point. Beware that even if you're putting your software on to someone else's hardware, it is ultimately you who becomes the "manufacturer" in the eyes of the consumer and the law. So if your batch of Widgets that you bought from XYZ suddenly start setting fire to people's houses, that falls on your doorstep (yes you may have an upstream claim against the actual OEM, but it is you who will be responsible to the end users). Similarly if you're getting involved in safety critical stuff, then buying OEM hardware will only take you so far. Regulatory approval for the final package will still be on your watch and your tab.