4 ms·
Step 1: have capital. Almost everything related to hardware has either a minimum order quantity or is uneconomic at small volumes. So you need to plan to make 1
by pjc50 5y ago
Step 1: have capital. Almost everything related to hardware has either a minimum order quantity or is uneconomic at small volumes. So you need to plan to make 1,000 units and pay for them before you receive any customer money.
Don't forget this is the supply chain crisis era, so you need to make sure you can get 1,000 units of all your parts that are actually in stock and not on 24 month back order.
The other comment that says "Scaling a hardware product is probably 10-100x harder than scaling a software product" is absolutely correct.
Once you have a prototype you can Kickstarter, but a lot of hardware kickstarter projects fail. https://help.kickstarter.com/hc/en-us/articles/115005134554-What-are-the-rules-for-hardware-and-product-design-projects- https://help.kickstarter.com/hc/en-us/articles/115005134554-...
Step 2: you need to be either a very fast learner across a lot of subjects, while spending your own money, or hire some consultants who know what they are doing. I used to work for a product development consultancy, but it's a pretty niche market.
This includes minefields like UL and CE certification.
Step 3: you need to either pick "local" manufacturing, where you can build up a working relationship and they will genuinely help you, or "remote" manufacturing which costs less but you have to diagnose all the problems over the phone or get on a plane to them. The latter is much harder in the COVID era.
Step 4: assembly, shipping, taxes, payment, etc; some of the local firms will also handle this for you (and take a cut).
- nicoburns 5y ago> you need to be either a very fast learner across a lot of subjects, while spending your own money, or hire some consultants who know what they are doing. I used to work for a product development consultancy, but it's a pretty niche market. Would it possible to learn this stuff by getting a job in one of these consultancies somehow? And if so, how might one go about doing this?
- jpm_sd 5y agoI have a couple of friends who work here https://www.synapse.com/careers https://www.synapse.com/careers
- HeyLaughingBoy 5y agoIt's also possible (and possibly faster!!!) to learn by trying to bring a product to market yourself. There are many small engineering consultancies around the US; getting a job there is like getting a job anywhere but they seem to be disappearing. I worked for one for five years then moved on as it was clear that I didn't have a growth path there. Here's one of the better-known ones in my area: https://www.linkedin.com/company/logic-pd/ https://www.linkedin.com/company/logic-pd/
- pjc50 5y agoUsual process of "find them and ask for a job, or work your contacts", I suppose. I know that's not terribly helpful. I have remembered about Bunnie Huang though, who wrote a book on the subject: https://www.crowdsupply.com/sutajio-kosagi/the-essential-guide-to-electronics-in-shenzhen https://www.crowdsupply.com/sutajio-kosagi/the-essential-gui... He blogged extensively about the "chumby" product he did about a decade ago, and the "precursor" he's working on at the moment. https://www.bunniestudios.com/blog/?cat=6 https://www.bunniestudios.com/blog/?cat=6
- embeng4096 5y agoI work for exactly one of these product development consultancies / contract engineering firms - we are a team of ~10 EEs and SWEs who work with customers from idea to design to development and then manufacturing. To the point of "lots of subjects", the above includes but is not limited to: sales, project management, electronic schematic capture and PCB layout, design for and manufacturing support, web development, and mechanical/system integration. Often we'll collaborate with our mechanical engineering counterparts who've opened their own product development and contract engineering consultancy. I can't speak for all firms but the way we find our employees is through networks of current employees and through LinkedIn recruiting. You'll want to emphasize aspects of your resume/work that mark you as a self-starting generalist with key skills. An example on the generalist side: we had a candidate say, "I don't want to do design, I just want to be handed a schematic and do PCB layout." They were passed over in favor of another candidate willing to dive in and do schematic capture if necessary, PCB layout, and speak directly to customers about requirements, timelines, budgets, and other project planning logistics. An example on the key skills side: the weakness of generalists is of course lack of depth, and we'll often contract out to SMEs based on project needs. If you know of a product consultancy near you that's, say, mechanically-focused, you can offer e.g. SWE expertise on, for example, frontend/backend development for a site that accepts RESTful HTTP requests from the IoT device they're building a mechanical enclosure for, whose customer needs software expertise that the MEs don't have. To find these companies, useful search phrases are things like "product development", "contract engineering", "engineering consultancy" and so on.
- buescher 5y agoYou found a PCB layout designer, not a design engineer. A good one is a real force multiplier that can lay out boards faster and more professionally than pretty much any EE I've worked with that lays out his own boards. You might not have enough work to keep one busy, though, and plainly that wasn't what you were looking for.
- deleted 5y ago[deleted]
- 5y ago
- smoyer 5y agoThe first 15-20 years of my career were spent as a hardware/embedded engineer and I'd like to add a few notes to the list above: 5. Unless you've got very specialized instrumentation, the power supply and case will dominate your costs. Per step 2 above, these will also dominate your timeline if you include an internal power supply. 6. FCC certification is also probably needed if your device is consumer oriented. 7. Expect development, time to first article, etc to be much slower. In my day, we couldn't have customers update their Flash-based firmware so we had to guarantee the hardware was perfect AND that the firmware was perfect. In your day, you still have to make sure the hardware is perfect and the reality is that very few of your customers will ever update the firmware (so it has to be perfect with each version. 8. For a small business, hardware returns are not only painful but have real costs. A recall will put you out-of-business (and if you're not careful with your corporate structure could put you into personal bankruptcy.)
- buescher 5y ago5. Which leads to: for small volumes (or MVPs or early-stage prototypes), if you can buy your power supply, you should! 6A. Most products with a microcontroller will need verification that they are compliant with FCC regulations on unintentional radiators. That's relatively cheap to do. If you bought your power supply (see 5) you are probably compliant. The problem is... by the time you get to this point, you are behind schedule, money is getting tight, and any respin or even adding ferrites is going to be a huge headache. Also, what got you here... might not help you solve an EMC problem. Good luck! 6B. If you need a transmitter (i.e. bluetooth or WiFi): for low volumes, if you possibly can buy a prequalified module, do so. Then certification is just paperwork at most. But don't listen to me, do a chip-down design because your industrial design requires it. YOLO and there is no other way to learn. 2.4 GHz at WiFi SoC powers is pretty forgiving. BLE with its low duty cycle practically handles compliance for you. Buy your matching networks and filters and don't go crazy with your antenna design 7. In general expect to be surprised by how the engineering - hardware, software, mechanical, etc - involved is much more exacting and demanding than you might expect from say, how conceptually difficult your problem domain might be. Especially if you are a software engineer and haven't worked with physical products 8. See #7 - you should be doing everything you can in design and procurement to minimize customer issues, from UX to field failures to any abuse of the product you can reasonably imagine. (Misuse you can anticipate has product liability ramifications also) If you are building 1000 units, any returns are going to cut into your margins. Look up typical warranty return rates for your industry and work that into your business plan and your pricing 9. They will all tell you hardware takes 10x-100x longer than software (I think this is a software engineering perspective where they expect to be able to deploy from a schematic or something), but then they will also tell you that if firmware isn't making you late, you aren't getting enough value out of firmware. You figure it out
- WastingMyTime89 5y ago> Step 1: have capital. Almost everything related to hardware has either a minimum order quantity or is uneconomic at small volumes. So you need to plan to make 1,000 units and pay for them before you receive any customer money. An interesting corrolary to this point is that somewhat counterintuitively it is often easier to aim for the highest segment of the market you target with a niche product than for broad appeal. Having a very high markup and selling price means that even small batch become feasible. Sourcing for high quality part sellers generally means you will have less issue with quality control. Selling less means shipping and inventory management is simpler. Marketing is easier because your customer base is more narrow. As a bonus, high margins give you more leeway to make mistakes.
- JoeDaDude 5y agoAll of the above, but consider if you are going international. Be aware of rules regarding exports from the US, ITAR, and EU regulations.
- sjs382 5y agoSure, all of that is true of mass market consumer electronics businesses/products. But a lot of the world makes (or peices together) fewer, higher budget products/projects and sells them to more focused markets (boutique hotels, regional CVBs, breweries, etc).