3 ms·
Wow, that sounded so painful, and painfully obvious to anyone who has designed and built hardware. I think lesson 5 should be lesson 0 and re-written: They wro
by ChuckMcM 12y ago
Wow, that sounded so painful, and painfully obvious to anyone who has designed and built hardware. I think lesson 5 should be lesson 0 and re-written:
They wrote:
As soon as the Kickstarter money hit our account, we should have hired an experienced hardware product manager.
And it should be:
Before contemplating a Kickstarter campaign, we should have hired an experienced hardware product manager and had them price out what such a product would cost to bring to market at various volumes.
Kickstarters work when they are the "D" side of R&D and fail when they start with the "R" side and try to get to "D".
- hkmurakami 12y ago>Kickstarters work when they are the "D" side of R&D and fail when they start with the "R" side and try to get to "D". I feel like we can extend this from Kickstarters to certain types of larger companies, where their expertise is in the D phase and their R efforts are largely fruitless (though granted, this is a bit of an exaggeration on my part). In a way, it takes discipline to stick to the D phase and let others do the seemingly sexy R work.
- bsder 12y agoYeah, yet another example of "Gee, hardware is actually hard." These guys should be crucified. $100 retail means $30 BOM. This is easily a $30 BOM project provided you supply the labor. Yeah, you're going to be working your own 3D printer. Pouring your own silicone rubber for molds. Soldering your own chips. etc. However, you got $500,000. That's enough to fund two people (one hardware and one software) an entire year and still have $250K left for development. They didn't learn crap.
- jkestner 12y ago> provided you supply the labor That's the #1 lesson. You can't consult away all the challenges, especially not the core of your product. As he found out, no one else is going to give a crap like you will, and if you don't have expertise in that area yourself, you're going to pick the wrong people. I'm still trying to figure out how the BOM got so high without alarms going off.
- sliverstorm 12y agoBOM cost sneaks up on first-time projects. My first big project I was a fanatic about price and I was still shocked how fast it added up. This is one of the ways an experienced hardware engineer can really turn things around from impossible to affordable- they can handle BOM cost as a major design parameter and drive down cost in ways a novice can't.
- DanBC 12y agoYou'd have thought they'd have learnt some lessons from their first kickstarter. http://www.gizmodo.co.uk/2012/01/triggertrap-the-story/ http://www.gizmodo.co.uk/2012/01/triggertrap-the-story/
- anigbrowl 12y agoMaybe they did :-/
- an_d_rew 12y agoWhile I agree completely with having an experienced designer spec hardware costs before the campaign, having run a kickstarter campaign for a small Bluetooth device, where the campaign failed miserably, I can offer an interesting but sad observation. Everybody, but everybody, but everybody… And I do mean everybody, gave me the same advice over and over and over again. And that was to focus on the marketing and the message and to pick a price point before actually designing. Even putative campaign backers told me that they thought being able to match up specifications and deliver on promises was just a technical issue. The reality is, as many others have noted, producing inexpensive commodity consumer-electronics is a far more expensive proposition than many realize, especially when you're talking about low manufacturing volumes or surprisingly tricky and expensive operations such as FCC regulatory compliance. In the end I think this sort of thing is quite common… People hear and believe what they wanted to be true. And then they complain when companies cannot deliver on promises they made out of naïveté. Sorry for potato quality grammar and occasional incorrect homonym… And being forced to use text to speech!
- ChuckMcM 12y agoYou make a good point, and the reality is that both have to be true. A good marketer will figure out at what price a device could reasonably be sold for. A good hardware designer could then tell you how close you could come to that, given the desired price point. A number of time folks have come to me with a "really great idea" but when priced out it didn't make sense. People just wouldn't buy it for what it would cost to make it, and "betting on the come" which is to say making 100,000 to get the price down on the hope that after you've sold 10,000 or so you will be able to sell another 90,000 is a risky business indeed. This though is part of the "nice thing" about Kickstarter. Which is you can set your price point for the quantity of units you offer on KS. Don't get funded? Couldn't make the market work, get more than you needed? Might be able to add a couple of points of margin to the bottom line. Danger of course is that if you get waaay more than you needed you'll be tempted to build V2 right away. Don't do that. Ship V1, pocket the margin and use that to design V2 with less risk after you've shipped V1. I'm curious about your bluetooth experience. I've got a project I'm advising and any previous experience is always good experience in my book. The BT vendor (TI in this case) has offered to help with EMC certification although the project already has a bid for that from a local lab at a cost of about $50,000.