Proof-of-concept development

When to develop a proof-of concept-device?

We recommend development of proof-of-concept devices to customers who aren’t completely sure of the feasibility of their idea. The same device development process of is also recommended for small quantity production and devices for internal use. As these devices aren’t intended to be sold on the market, they don’t require all the certification. The small product run also means that there is no need to optimise the whole process for mass production. To produce such a device, we often use readymade development boards or modules. All the above facts enable us to develop such a device much cheaper and quicker than if it was developed for mass manufacturing. 

Process of developing a proof-of-concept device

We start the process with an analysis of the customer’s wishes and their expectations for the device’s functionality. Together, we find a solution that will be cheap and will satisfy all the customer’s wishes. We make or buy the required hardware, and write appropriate firmware. At this point, we give the device to customer for testing. We improve the prototype until the customer is fully satisfied with it. If the customer later decides to go into mass production with this device, we can take what has already been developed as the basis for development of a device that will comply with all relevant legislation and can be easily produced in large quantities, which is much cheaper than developing the whole device from scratch.

Tools used for development of proof-of-concept devices

To develop proof-of-concept devices, we use special procedures and tools. If possible, we use components that are freely available in small quantities. One such component is a readymade development board for certain types of microcontrollers, which enables us to build circuits faster and cheaper than if we were using individual electrical components. The situation is similar in firmware. We try to reuse readymade pieces of code (libraries), that enable us to quickly assess the functionality of a device. This type of firmware is usually for modification in a proof-of-concept device, but can’t be used in mass-produced devices. Use of the tools mentioned above and years of experience enable us to produce proof-of-concept devices at a low price.