A working prototype is an important milestone. The idea is taking shape, the technology is producing results and you can show others what you have in mind. The excitement is justified. It also tends to raise a new question: when can we start selling?
My answer depends on what has already been demonstrated. For a product you can sell, you want to know that it meets the relevant requirements, withstands its intended use and can be manufactured consistently. Customers also need to be able to install and use it without the developer standing next to them.
These final steps contain work that is easy to overlook at the start. Much of it determines what the customer actually receives.
Use product-specific acceptance criteria; a successful demo covers only part of this.
Test for the environment the product will face
A successful demonstration tells you that something works at that moment. You also want to investigate how the product behaves during transport, daily use and the conditions it was designed for.
The tests required depend on the application. Vibration may be relevant to a device mounted on a machine. For a wearable, mechanical stress and exposure to moisture may matter. The test plan should reflect the usage requirements and the risks you have identified.
One method that can help is HALT, Highly Accelerated Life Testing. Products are exposed to increasing stresses, such as temperature and vibration, to uncover weaknesses. HALT alone does not establish an exact number of years of service life. Its main value is helping you understand where the design is vulnerable, so you can make targeted improvements and test further.
Address conformity during development
Certification is often treated as something to sort out at the end. That can cause delays if a test reveals that the design needs to change. Investigate the applicable requirements early, along with the design choices that affect them.
For products that require CE marking, the manufacturer must carry out the applicable conformity assessment, prepare technical documentation and draw up the EU declaration of conformity. The required assessment and any involvement of an external body depend on the product and the applicable rules. CE is therefore not a general quality label that you simply order from a laboratory.
A test laboratory can help you determine the relevant tests and when to perform them. Make sure the version you ultimately deliver matches what was assessed and documented. Take changes to components, the enclosure or the design seriously from that perspective too.
Set up production and quality control together
A good prototype may have received a great deal of individual attention from an engineer. In production, you want an agreed method to deliver good results consistently. This requires clear assembly instructions, suitable tools and defined checkpoints.
Think early about how you will test each product. Can you reliably program the firmware? Can you check that the sensors and communication work? Which deviations require rejection, and which measurements do you want to retain? If the design needs test access points for this, include them during development.
A pilot run lets you investigate whether the process works in practice. Look at faults, rework and differences between units. A reference product helps establish the intended build. Test results and agreed procedures help you achieve that same build in subsequent batches.

Test stations are part of the production process: agree what each unit must pass and which results to retain.
Let someone try the installation independently
The first experience begins when a customer opens the packaging. Is it clear what is inside? Do they know what to do first? Does the user understand when the device is ready and what an error message means?
This deserves attention in business products too. The person installing the device is not always the person who was involved in development. A logical installation process and a useful manual reduce the need for explanations and lower the risk of misuse.
Test the entire initial experience with someone who does not know the product. Let them unpack it, install it and complete their first task. Take the moments when you feel the need to intervene seriously. They show where the product, documentation or guidance could improve.
Packaging and delivery are part of the product
Packaging protects the product in transit and helps users understand what they are receiving. For a consumer product, the presentation also shapes expectations of quality. Plan this work and its costs early enough.
The same applies to the supply chain. You need to know where components come from, how they are sourced and what lead times and dependencies are involved. A chosen battery or chip may later become difficult to obtain. Discuss with suppliers how you will handle changes and shortages.
Clear agreements are especially valuable when manufacturing takes place at a distance. Define which checks will be carried out and how deviations will be handled. Also investigate sourcing and working conditions in the supply chain in a way that fits your product, suppliers and responsibilities. A low quotation tells you little about those factors.
Decide how you will support the product after delivery
Responsibilities for a connected device continue after the sale. Consider help with installation problems, returns, software maintenance and handling vulnerabilities. Decide who will do this work and how feedback from the field will reach the development team.
You can therefore best assess readiness for sale through evidence from testing, production and use. Have the important risks been investigated? Can the manufacturer deliver the agreed quality? Can the user get started independently? With that foundation in place, the decision to enter the market becomes one you can justify.
Discuss your next step
Our manufacturing service covers the move from pilot to repeatable production. Read about functional production testing and CE certification support.
In this hardware development series
- Hardware development costs: what should you budget?
- Hardware development stages: PoC, EVT, DVT and PVT
- How to test a hardware idea before investing heavily
- Hardware design: size, battery life, performance and cost