So you want to develop a new electronic hardware product?
Let me start with the good news – it’s possible. You can develop a hardware product regardless of your technical level and you don’t necessarily need to be an engineer to succeed (although it certainly helps).
Whether you’re an entrepreneur, startup, maker, inventor, or small business this guide will help you understand the new product development process.
I won’t lie to you, though. It’s an incredibly long, difficult journey to launch a new hardware product. Although hardware is known for being hard, it’s also easier now than ever for individuals and small teams to develop new hardware products.
However, if you are looking for an easy, quick way to make money then I suggest you stop reading right now because bringing a new hardware product to market is far from easy or quick.
Although the steps are presented here in a linear fashion, product development is never a smooth linear progression and at times you will find yourself taking two steps back for every step forward.
Through my years spent developing my own hardware product and then helping other entrepreneurs develop their products one of the most important lessons I’ve learned is that you need to simplify your product as much as possible.
You must embrace product simplification in order to have a realistic shot at getting your product to market in a timely fashion and without going bankrupt doing it.
Product complexity can be a death trap for hardware startups!
Most entrepreneurs, and even most engineers, don’t understand all the consequences of various product features. The addition of what seems like a minor feature can often drastically increase your development cost and the time it takes to get to market.
For example, something as simple as the position of a button could cost you thousands of dollars extra for the injection molds required for production of the enclosure.
Another example comes from an entrepreneur who asked me and the other experts in the Hardware Academy for feedback on his product concept.
He was very technically minded and had spent a lot of time specifying his product in great detail. But he didn’t understand all the future implications of these features.
We quickly explained to him why one feature of his product was going to drastically drive up all of his costs including: development, prototyping, electrical certifications, and mold costs.
Several more feasible alternative solutions were proposed, and he was off to a much better start. These changes made his product about 3 times easier to bring to market. Overall, he saved at least $50,000 with this one change, perhaps as much as $100,000!
The catch is that unless you understand the entire development and manufacturing process it’s difficult to know the future implications of all of your product decisions.
If you outsource product development be aware that asking your primary developer(s) to help simplify your product may create a conflict of interest. The more complex your product the more money they get paid.
Instead, work with independent experts to help you simplify your product and better understand the long-term impacts of your early product decisions.
There are essentially five options for entrepreneurs and startups to develop a new hardware product. However, many times the best overall strategy is a combination of these five development strategies.
If you don’t have the technical knowledge to properly manage product development and to judge the quality of work being done, then having a technical advisor is a must regardless of which of these development strategies you follow.
This technical advisor can help you make key technical decisions and provide oversight of your primary developers. Even if you are an experienced engineer it’s highly beneficial to have an advisor who understands the entire process from idea to market.
This is rarely a viable strategy completely by itself. Very few people have all of the skills needed to develop a market-ready electronic product completely on their own.
Even if you happen to be an engineer, are you an expert in electronics design, programming, 3D modeling, injection molding, and manufacturing? Probably not. Also most of these specialties are made up of numerous sub-specialties.
That being said, if you have the necessary skills, the farther you take the development of your product yourself the more money you will save.
For example, I brought my own hardware product to market about 6 years ago. The product was more complex mechanically than it was electrically. I’m an electronics engineer by training and not a mechanical engineer, so I initially hired a couple freelance mechanical engineers.
However, I quickly became frustrated with how slow things progressed. After all, I was thinking about my product almost every waking hour. I was obsessed with getting my product developed and on the market as fast as possible. Sound familiar?
But the engineers I hired were juggling it with lots of other projects and not giving my project the attention I felt it deserved.
So I decided to learn everything needed to do the mechanical design myself. No one was more motivated than myself to get my product developed and on the market. Ultimately, I was able to complete the mechanical design much faster (and for much less money).
The moral of the story is to do as much of the development as your skills allow, but also don’t take that too far. If your sub-expert skills cause you to develop a less than optimal product then that is a big mistake.
Also, any new skills you must learn will take time and that may ultimately lengthen the time to market. Always bring in experts to fill in any gaps in your expertise, but be sure to remain involved in all key decisions.
If you are a non-technical founder then you would definitely be wise to bring on a technical co-founder. One of the founders on your startup team needs to at the very least understand enough about product development to manage the process.
If you plan to eventually seek outside funding from professional investors then you definitely need a team of founders. Professional startup investors know that a team of founders is much more likely to succeed than a solo founder.
The ideal co-founder team for most hardware startups is a hardware engineer, a programmer, and a marketer.
Bringing on co-founders may sound like the perfect solution to your problems, but there are some serious downsides as well. First of all, finding co-founders is difficult and will likely take a tremendous amount of time. That is valuable time that isn’t being spent developing your product.
Finding co-founders is not something you should rush and you need to take time to find the right match.
Not only do they need to compliment your skills, but you also really need to like them personally. You are essentially going to be married to them for at least a few years so be sure you get along well.
The major downside of bringing on co-founders is they reduce your equity in the company. All founders of a company should really have equal equity in the company. So if you are going solo right now, be prepared to give any co-founder half of your company.
One of the best ways to fill in any gaps in your teams technical ability is by outsourcing to freelance engineers.
Just keep in mind that most products will require multiple engineers of different specialties so you will need to manage the various engineers yourself. Ultimately, someone on the founding team will need to serve as the project manager.
Make sure you find an electrical engineer that has experience designing the type of electronics required by your product. Electrical engineering is a huge field of study and many engineers lack any experience with circuit design.
For the 3D designer make sure you find someone that has experience with injection molding technology, otherwise you’re likely to end up with a product that can be prototyped but not mass manufactured.
The best known product design firms such as Frog, IDEO, Fuse Project, etc. can generate fantastic product designs, but they’re insanely expensive.
Startups should avoid big design firms at all costs. Top design firms can charge $500k+ to fully develop your new product.
Even if you can afford to hire an expensive product development firm, don’t do it!
However, there are many smaller, less known design firms that I’ve worked with that can develop your product at a much more reasonable price. The cost for these smaller firms usually falls closer to the cost of hiring freelancers yet with more oversight and better quality procedures in place.
One final comment on working with product design firms. You must discard the false belief that you can just have someone else handle all of the development while you just wait on the sidelines.
Those that attempt that path almost always get burned and lose a lot of money and time. You absolutely need to be involved in development and understand at least the basics of the development process as well as the various design tradeoffs being made.
One avenue to pursue is partnering with an overseas manufacturer that already makes products that are similar to your product.
Large manufacturers will have their own engineering and development departments to work on their own products. If you can find a manufacturer already making something similar to your own product, they may be able to do everything for you – development, engineering, prototyping, mold production and manufacturing.
This strategy can lower your upfront development costs. Manufacturers will, however, amortize these costs, which means adding an additional cost per product for the first production runs. This essentially works like an interest free loan, allowing you to slowly pay back your development costs to the manufacturer.
Sounds great and easy, so what’s the catch? The main risk to consider with this strategy is you are putting everything related to your product into a single company.
They will surely want an exclusive manufacturing agreement, at least until their costs have been recovered. This means you can’t migrate to a cheaper manufacturing option when your production volume increases.
Also be warned that many manufacturers may want part, or all, of the intellectual rights to your product.
NOTE: If you're serious about developing a new electronic hardware product then download the PDF Summary of the Costs to Develop Your Electronic Product.
Development of the electronics for your product can be broken down into seven steps: preliminary production design, schematic diagram, PCB layout, final BOM, prototype, test and program, and finally certification.
When developing a new electronic hardware product you should first start with a preliminary production design. This is not to be confused with a Proof-of-Concept (POC) prototype.
A POC prototype is usually built using a development kit like an Arduino. They can sometimes be useful to prove that your product concept solves the desired problem. But a POC prototype is far from being a production design. Rarely can you go to market with an Arduino embedded in your product.
A preliminary production design focuses on your product’s production components, cost, profit margin, performance, features, development feasibility and manufacturability.
You can use a preliminary production design to produce estimates for every cost your product will need. It is important to accurately know the costs to develop, prototype, program, certify, scale, and manufacture the product.
A preliminary production designwill answer the following pertinent questions. Is my product feasible to develop? Can I afford to develop this product? How long will it take me to develop my product? Can I mass manufacture the product? Can I sell it at a profit?
Many entrepreneurs make the mistake of skipping the preliminary production design step, and instead jump right into designing the schematic circuit diagram.
By doing so, you may eventually discover you’ve spent all this effort and hard-earned money on a product that can’t be affordably developed, manufactured, or most importantly, sold at a profit.
When creating the preliminary production design you should start by defining the system-level block diagram. This diagram specifies each electronic function and how all of the functional components interconnect.
Most products require a microcontroller or a microprocessor with various components (displays, sensors, memory, etc.) interfacing with the microcontroller via various serial ports.
By creating a system block diagram you can easily identify the type and number of serial ports required. This is an essential first step for selecting the correct microcontroller for your product.
Next, you must select the various production components: microchips, sensors, displays, and connectors based upon the desired functions and target retail price of your product. This will allow you to then create a preliminary Bill of Materials (BOM).
In the U.S., Newark,Digikey,Arrow,Mouser, and Future are the most popular suppliers of electronic components. You can purchase most electronic components in ones (for prototyping and initial testing) or up to thousands (for low-volume manufacturing).
Once you reach higher production volumes you will save money by purchasing some components directly from the manufacturer.
You should now estimate the production cost (or Cost of Goods Sold – COGS) for your product. It’s critical to know as soon as possible how much it will cost to manufacture your product.
You need to know your product’s manufacturing unit cost in order to determine the best sales price, the cost of inventory, and most importantly your profit.
The production components that you’ve selected will of course have a big impact on the manufacturing cost.
But to get an accurate manufacturing cost estimate you also must include the cost of the PCB assembly, final product assembly, product testing, retail packaging, scrap rate, returns, logistics, duties, and warehousing.
Now it’s time to design the schematic circuit diagram based upon the system block diagram you created in step 1.
Figure 5: Example of a schematic circuit diagram.
The schematic diagram shows how every component, from microchips to resistors, connects together. Whereas a system block diagram is mostly focused on the higher level product functionality, a schematic diagram is all about the little details.
Something as simple as a mis-numbered pin on a component in a schematic can cause a complete lack of functionality.
In most cases you’ll need a separate sub-circuit for each block of your system block diagram. These various sub-circuits will then be connected together to form the full schematic circuit diagram.
Special electronics design software is used to create the schematic diagram and to help ensure it is free of mistakes. I recommend using a package called DipTrace which is affordable, powerful, and easy to use.
For a free, open-source PCB design tool also be sure to check out KiCad.
Once the schematic is done you will now design the Printed Circuit Board (PCB). The PCB is the physical board that holds and connects all of the electronic components.
Development of the system block diagram and schematic circuit have been mostly conceptual in nature. A PCB design though is very real world.
The PCB is designed in the same software that created the schematic diagram. The software will have various verification tools to ensure the PCB layout meets the design rules for the PCB process used, and that the PCB matches the schematic.
In general, the smaller the product, and the tighter the components are packed together, the longer it will take to create the PCB layout. If your product routes large amounts of power, or offers wireless connectivity, then PCB layout is even more critical and time consuming.
For most PCB designs the most critical parts are the power routing, high-speed signals (crystal clocks, address/data lines, etc.) and any wireless circuits.
Although you should have already created a preliminary BOM as part of your preliminary production design, it’s now time for the full production BOM.
The main difference between the two is the numerous low-cost components like resistors and capacitors. These components usually only cost a penny or two, so I don’t list them out separately in the preliminary BOM.
But to actually manufacture the PCB you need a complete BOM with every component listed. This BOM is usually created automatically by the schematic design software. The BOM lists the part numbers, quantities, and all component specifications.
Creating electronic prototypes is a two-step process. The first step produces the bare, printed circuit boards. Your circuit design software will allow you to output the PCB layout in a format called Gerber with one file for each PCB layer.
These Gerber files can be sent to a prototype shop for small volume runs. The same files can also be provided to a larger manufacturer for high volume production.
The second step is having all of the electronic components soldered onto the board. From your design software you’ll be able to output a file that shows the exact coordinates of every component placed on the board. This allows the assembly shop to fully automate the soldering of every component on your PCB.
Your cheapest option will be to produce your PCB prototypes in China. Although it’s usually best if you can do your prototyping closer to home so as to reduce shipping delays, for many entrepreneurs it’s more important to minimize costs.
For producing your prototype boards in China I highly recommend PCBWay,Bittele Electronics,Seeed Studio, or Gold Phoenix PCB. They all offer fantastic pricing on quantities from 5 up to 8,000 boards. In the U.S. I recommend Sunstone Circuits,Screaming Circuits, and San Francisco Circuits which I’ve used extensively to prototype my own designs.
It usually takes 1-2 weeks to get assembled boards, unless you pay for rush service which I rarely recommend.
Discounts are available in the Hardware Academy for many of these services, so you may wish to join before ordering any custom boards.
Now it’s time to evaluate the prototype of the electronics. Keep in mind that your first prototype will rarely work perfectly.
You will most likely go through several iterations before you finalize the design. This is when you will identify, debug and fix any issues with your prototype.
This can be a difficult stage to forecast in both terms of cost and time. Any bugs you find are of course unexpected, so it takes time to figure out the source of the bug and how best to fix it.
Evaluation and testing are usually done in parallel with programming the microcontroller. Before you begin programming though you’ll want to at least do some basic testing to ensure the board doesn’t have major issues.
Nearly all modern electronic products include a microchip called a Microcontroller Unit (MCU) that acts as the “brains” for the product. A microcontroller is very similar to a microprocessor found in a computer or smartphone.
A microprocessor excels at moving large amounts of data quickly, while a microcontroller excels at interfacing and controlling devices like switches, sensors, displays, motors, etc. A microcontroller is pretty much a simplified microprocessor.
The microcontroller needs to be programmed to perform the desired functionality. Microcontrollers are almost always programmed in the commonly used computer language called ‘C’. The program, called firmware, is stored in permanent but reprogrammable memory usually internal to the microcontroller chip.
Now we’ll cover the development and prototyping of any custom plastic pieces. For most products this includes at least the enclosure that holds everything together.
Development of custom shaped plastic or metal pieces will require a 3D modeling expert, or better yet...
Originally published at predictabledesigns.com on February 27, 2017.