My comment wasn't about Kickstarters, I think they're irrelevant in this discussion. I'm talking about making your stuff accessible to people outside of large corporations. The world isn't two perfectly non-intersecting groups labeled "hobbyists" and "professionals". There's enormous overlap. Hell, a very large portion of HN falls into both categories.
Let's say XYZ software is only available to businesses. As a professional software engineer, if I asked to buy XYZ, it'd get bought. But since I can't use XYZ in my personal life, I've never even heard of it, and as a result when we're deciding on software to buy at the company I have no familiarity with it and it doesn't get bought.
Perhaps somewhere out there there are some 100x hardware developers, but every hardware developer I've met likes what they know, and a lot of what they know from a combination of personal tinkering and university. It's hard to explain how powerful familiarity is with designing hardware. So if you're sitting down and designing something and you need component A or B, and B uses less power and looks cool and all kinds of stuff, but you have experience with A and it works fine, well, you'll go with A. And for good reason! Things have weird quirks and spec sheets lie and all kinds of stuff happens.
So yeah, I think that having some kind of community connection can pay absolutely massive dividends. At the end of the day, if it's only accessible to large corporations, then it's not even accessible to those large corporations - because the engineers at them won't have familiarity with your thing and they'll just pick what they know.
Furthermore, it's not even that hard to sell to hobbyists. You make the spec sheet public, you make some example code public, you mail some units to Digikey and you're done. You wanna go REALLY crazy, you can mail a few free units to some well known tinkerers. It's not like you're personally offering 24 hour phone support to everyone with an Arduino. The investment of a couple of hours to deign to mail Digikey a box is quickly recovered by the first engineer that plays with your widget at home and then suggests it at $bigco.