Prototype to manufacturing: industrializing electronics

Prototype to manufacturing: a regime change, not a phase

Taking an electronic product from prototype to manufacturing means walking through five normalized milestones, Engineering Validation Test (EVT), Design Validation Test (DVT), Production Validation Test (PVT), CE/FCC certification and Mass Production (MP), each one sealed by a contractual deliverable and a First Article Inspection (FAI) checkpoint. At AESTECHNO, based in Montpellier, we design PCBs that are EMC pre-compliant and aligned on IPC-A-610 Class 3 from the very first iteration, with no later adaptation phase.

The gap between a working prototype and a shippable product is where most schedules slip. A board that runs on the bench still has to survive environmental and ESD testing, pass the accredited EMC lab and be assembled repeatably by an EMS partner. This guide walks through each gate, its typical duration, the drivers of the budget and the mistakes we observe most often.

Contents

• Overview: the 5 industrialization steps
• Step 1: Proof of Concept (POC)
• Step 2: Functional prototype
• Step 3: Pre-series (DVT/PVT)
• Step 4: CE/FCC certification
• Step 5: Mass production
• Realistic schedule
• Budget drivers
• DFM: anticipate from prototype
• 5 fatal mistakes to avoid
• How long does industrialization take?
• Bottom line
• FAQ

Overview: the 5 industrialization steps

Industrializing an electronic product is the structured five-step process (POC, prototype, pre-series DVT/PVT, certification, mass production) that turns a validated idea into a manufacturable product, aligned with IPC-A-610 Class 3 and IPC-6012 Class 3 acceptance criteria. Each step has its own objectives, deliverables and gate criteria. Skipping a step or underestimating it always pushes problems downstream, where corrections cost more in time, money and reputation.

Each gate answers a different question. The POC asks whether the idea can work at all, the prototype whether the complete product meets its specification, pre-series whether it can be built repeatably, certification whether it may legally be sold, and mass production whether it can be delivered at the target cost and yield.

The five steps we will detail below:

1. Proof of Concept (POC): validate the technical feasibility
2. Functional prototype: develop the complete product
3. Pre-series (DVT/PVT): validate manufacturability and reliability
4. Certification: secure the regulatory approvals
5. Mass Production: launch series manufacturing

Every step has a cost and a duration. Compressing them too aggressively is paid for in quality, in delays, or in later cost overruns.

Step 1: Proof of Concept (POC)

A Proof of Concept validates that an idea is technically achievable before committing to full development. The POC answers a single question: can it work? It is not a product, it is a fast and inexpensive experiment that lifts the major technical uncertainties before any heavy investment.

In practice, the POC is where the team tests the critical components, checks that the sensors, connectivity and algorithms behave as expected, and lists the technical risks that will drive the rest of the project. Its output is not hardware to keep but material for a go/no-go decision. A POC typically lasts 2 to 8 weeks, and its findings feed directly into the specification of the functional prototype.

POC objectives

• Validate the fundamental technical principles
• Test the critical components (sensors, connectivity, algorithms)
• Identify the major technical risks
• Provide tangible material for the go/no-go decision

What a POC is NOT

• A finished or even fully working product
• A design optimized for production
• A baseline for certification
• A commercial demo unit

Typical form of a POC

An electronic POC often takes the form of a vendor evaluation board, an assembly of off-the-shelf modules, or a quick PCB without optimization. The code is functional but not industrial. What matters is execution speed and tight cost control.

Typical duration: 2 to 8 weeks

Common mistake at this step

Confusing POC with prototype. A POC that "works" does not mean the final product will work: lab conditions never reflect the real environment. We have observed clients pitch their POC to investors as a near-finished product, creating unrealistic expectations on schedule and cost. Contrary to that intuition, the gap between POC and certifiable product is usually 6 to 9 months of solid engineering.

Step 2: Functional prototype

The functional prototype is the first complete version of the product, integrating every feature in a form factor close to the final design. It is the baseline on which design, ergonomics and performance are validated before the industrialization investment, and it usually goes through two to three iterations to converge.

Where the POC proves a principle, the prototype proves the product: final component selection, complete PCB routing, functional firmware and mechanical integration with the enclosure come together for the first time. Every feature in the specification is tested under realistic conditions, and the certification tests start to be prepared. Plan 3 to 6 months for this phase, because each iteration surfaces firmware bugs, thermal issues or routing tweaks that the next version must correct.

Prototype objectives

• Integrate all the features defined in the specification
• Validate the hardware and software architecture
• Test performance under realistic conditions
• Refine industrial design and ergonomics
• Prepare the certification tests

Activities in this phase

Prototype development mobilizes the full electronic-engineering toolkit:

• Schematic design: complete architecture, final component selection
• PCB routing: design optimized for performance (high-speed, EMC, thermal). For the basics of how a printed circuit board works, see our PCB design methodology
• Firmware development: functional code, drivers, communication stacks
• Mechanical integration: coordination with the enclosure, thermal constraints
• Functional tests: validation of every feature in the specification

Number of iterations

Few projects succeed in a single prototype iteration. Plan on 2 to 3 versions before reaching a stabilized design. Each iteration brings its share of corrections: firmware bugs, thermal issues, routing tweaks, changes triggered by the first user feedback.

Typical duration: 3 to 6 months for 2 to 3 iterations.

Common mistake at this step

Postponing Design for Manufacturing (DFM) until later. A design that runs correctly on prototype but is impossible or expensive to mass-produce will force a late redesign. In our practice, we systematically integrate the manufacturing constraints from the very first prototype version. A complete specification must mention production constraints from day one.

Step 3: Pre-series (DVT/PVT)

The pre-series is the structured industrial validation phase, split into Engineering Validation Test (EVT), Design Validation Test (DVT) and Production Validation Test (PVT), that confirms manufacturing repeatability, quality stability and environmental robustness before the Mass Production (MP) investment. According to IPC, the IPC-A-610 Class 3 acceptance criteria apply to high-reliability products at the end of this phase, and IPC-7711/7721 governs the rework procedures.

In practice, pre-series is the first time the product is built by the EMS partner rather than by the design team. DVT exercises the design under environmental, ESD and RF immunity stress, while PVT runs a pilot lot, typically 50 to 200 units, to measure yield, cycle time and the automated test procedures. Plan 2 to 4 months for the whole phase.

Pre-series objectives

• Validate the manufacturing process with the EMS (electronic manufacturing services partner)
• Verify production repeatability
• Run the reliability tests (temperature, humidity, vibration, aging)
• Finalize the production test procedures
• Build a stock of units for certification testing

DVT: Design Validation Test

DVT validates that the design meets specifications across all operating conditions. The protocols rely on standards published by the IEC:

• Environmental tests: thermal cycling -40 °C to +85 °C (industrial range) or -20 °C to +70 °C (consumer range), humidity 85 percent at +85 °C (IEC 60068-2-78), mechanical shock (IEC 60068-2-27), vibration up to 50 Grms for one hour per axis
• ESD tests per IEC 61000-4-2: plus or minus 8 kV contact, plus or minus 15 kV air discharge
• Radiated RF immunity per IEC 61000-4-3: 3 V/m in the 80 to 1000 MHz band, 10 V/m for industrial
• Accelerated aging tests (HALT/HASS): thermal stress beyond plus or minus 20 °C around the operating range to expose design margins
• Endurance: continuous operation over several weeks, typically 500 to 1000 hours

PVT: Production Validation Test

PVT validates that production is under control:

• Pilot lot manufacturing, typically 50 to 200 units
• Yield measurement
• Validation of cycle times and unit cost
• Operator training
• Validation of automated test procedures

Typical duration: 2 to 4 months

Common mistake at this step

Skipping pre-series to "save time". Issues that hide at this stage will surface during mass production with much larger consequences: customer returns, product recalls, brand damage. Despite the short-term schedule pressure, pre-series is an investment, not an avoidable expense. Contrary to that pressure, our methodology keeps PVT non-negotiable on every CE/FCC project.

Step 4: CE/FCC certification

Certification confirms regulatory compliance and authorizes market placement. For an electronic product sold in Europe, this means the CE marking and, for radio-enabled products, RED Directive 2014/53/EU compliance. Despite a common assumption, certification is not a paperwork formality, it is a measurement campaign that sanctions the design quality.

The certification campaign combines in-house EMC and radio pre-tests, corrections where needed, official testing in an ISO/IEC 17025 accredited lab, and a technical file with the schematic, BOM, test reports and risk analysis. For IoT products, ETSI EN 303 645 adds cybersecurity requirements in line with the Cyber Resilience Act. Plan 6 to 12 weeks, and start in parallel with pre-series so that the samples tested are representative of final production.

When to launch certification?

Certification must be planned in parallel with pre-series, not after. The certification tests need samples representative of final production. Any design change after certification can trigger a full retest, which is why we freeze the AVL and the firmware build at the start of the lab campaign.

Certification activities

• In-house or non-accredited EMC and radio pre-tests, targeting EN 55011 Class B limits (40 dBuV/m at 3 m between 30 and 230 MHz, 47 dBuV/m between 230 and 1000 MHz)
• Corrections after pre-tests if needed: ferrite beads 100 ohm at 100 MHz, stackup tweak, shielding
• Official testing in an ISO/IEC 17025 accredited lab
• Technical file: schematic, BOM, test reports, risk analysis per EN 62368-1
• Drafting the EU Declaration of Conformity
• For IoT products: ETSI EN 303 645 (strong authentication, no default credentials, signed updates) per the Cyber Resilience Act, EU Regulation 2024/2847
• Affixing the CE marking

For international markets (USA via FCC Part 15 Subpart B/C, Canada ISED RSS-Gen, Japan MIC), additional certifications are required.

Typical duration: 6 to 12 weeks

Common mistake at this step

Treating certification as administrative paperwork. Lab failures are common on poorly designed products. A failure means hardware modifications, fresh prototypes, weeks of delay and a new lab booking. The design must integrate EMC and radio constraints from day one, which is why we recommend building EMC pre-compliance into the schematic review, not the lab booking.

Step 5: Mass production

Mass Production (MP) is the launch of commercial-scale manufacturing with a frozen Approved Vendor List (AVL), a First Article Inspection (FAI) signed off by the Electronic Manufacturing Services (EMS) partner and target yields above 95 percent. The product is certified, the manufacturing process is validated and the supply chain is in place. This is when the product starts generating revenue, and also when earlier mistakes become very expensive.

Mass production is also the phase where the relationship with the EMS becomes the main lever on quality, cost and lead time. Before the first lot, production documentation, tooling, supply chain, EMS contract and quality procedures must all be locked, and second sources identified for the critical components so that a shortage does not stall the line.

Series launch preparation

Before the first production lot, several elements must be locked:

• Production documentation: final BOM, Gerber files, assembly procedures
• Tooling: stencils, test fixtures, injection moulds for custom enclosures
• Supply chain: secured component sourcing, identified second sources
• EMS contract: manufacturing terms, MOQ, lead times, warranties
• Quality procedures: acceptance criteria, traceability, non-conformance management

EMS (Electronic Manufacturing Services) selection

The EMS choice has a direct impact on quality, cost and lead time. Per Lacroix, Eolane and Asteelflash in Europe, and per Flex, Jabil and Foxconn for international large-volume programs, the selection criteria converge on four axes:

• Technical capability: mastered technologies (SMT, BGA, press-fit, RF, microwave)
• Volume fit: matching your needs, small versus large series
• Location: Europe for responsiveness, Asia for cost in volume
• Certifications: ISO 9001, ISO 13485 (medical), IATF 16949 (automotive), IEC 61340-5-1 and ESD S20.20 for ESD line protection
• Services: component sourcing, testing, logistics

Production cost structure

Unit cost in series production breaks down into:

• Components: typically 40 to 60 percent
• Bare PCB: 5 to 15 percent
• Assembly: 15 to 25 percent
• Test: 5 to 10 percent
• Enclosure and mechanics: variable depending on complexity

Unit cost goes down with volume due to component-purchase scale and tooling amortization.

Common mistake at this step

Underestimating supply-chain issues. Component shortages can stall production for months. Plan validated alternates (second source) and keep safety stock for critical references.

Our shortage playbook: field feedback

At AESTECHNO, we have helped multiple clients secure their move into series despite shortages on key components. When a pin-compatible drop-in replacement exists, we qualify it quickly; when a re-qualified second source is feasible, we validate it; and when no alternative exists, we redesign the board to bypass the shortage. Our decision grid: 12 to 24 month availability, certification impact, redesign cost versus wait cost.

Realistic schedule: from POC to mass production

A realistic schedule is the time-line that aligns POC, prototype iterations, pre-series, certification and series launch on a single critical path, with explicit float for unplanned events.

The critical path runs through the prototype iterations and the pre-series, while certification is prepared in parallel with DVT so that it does not add months at the end. Most of the uncertainty sits in two places: the number of prototype iterations needed to converge, and the EMC and supply-chain risks that can force an unplanned respin. A realistic plan therefore states its assumptions and keeps a margin of 20 to 30 percent for the unexpected, rather than presenting a single optimistic date.

Here is a baseline for a medium-complexity IoT product:

Realistic total duration: 10 to 15 months from POC kickoff to first series shipments.

This schedule assumes a project without major surprises. Add 20 to 30 percent margin for the unexpected: technical issues, extra iterations, supplier delays. Despite optimistic Gantt charts, the EMC and supply chain risks are the two biggest schedule killers we observe.

Drivers that move the global budget

The total budget of an industrialization project depends heavily on product complexity: RF, high-speed or thermal constraints, the number of prototype iterations, the certification scope and the reliability requirements all move it up or down. Rather than a single figure, the useful question is which cost lines will dominate for your product.

The development budget runs from POC kickoff to series launch and splits into five lines, from the POC to the tooling. Production costs per unit come on top, scaled to ordered volumes. Each of these lines is shaped by decisions taken early, during specification and prototype design, which is why the budget deserves a review at every gate rather than a single estimate at kickoff. Below are the main cost lines to anticipate.

Development cost lines

• POC: limited investment to validate technical feasibility
• Prototype: the largest line, including design, iterations and bring-up
• Pre-series: industrial validation, reliability tests, process qualification
• Certification: variable depending on target markets, CE only versus international
• Tooling: moulds, test fixtures, stencils, amortized over production volume

Factors that push the budget up

• Technical complexity: RF, high-speed, thermal constraints
• Number of prototype iterations needed
• Certification scope: CE only versus multi-market
• Reliability requirements: extended environmental testing, IEC 61508 functional safety
• Specific tooling: custom enclosure, complex fixtures

The development budget runs from POC to series launch. Production costs (per-unit manufacturing) are added later, scaled to ordered volumes. Contrary to a common framing, the cost line that breaks projects is rarely the engineering itself, it is the unbudgeted respin triggered by an EMC failure or a late DFM finding.

Design for Manufacturing: anticipate from prototype

Design for Manufacturing (DFM) is the body of design practices that simplify manufacturing and reduce production cost. DFM works hand in hand with Design for Assembly (DFA) and Design for Test (DFT) to cover the entire industrialization chain. Per Altium, Cadence and Siemens (Mentor), DFM rule-checkers integrated into EDA suites detect 70 to 90 percent of fabrication issues before Gerber export. Integrating these three dimensions from prototype avoids late redesigns.

In practice, DFM covers concrete choices: standard and available component packages, a PCB designed for efficient panelization, accessible test points, readable markings and tolerances that stay within the production equipment capability. Having the Gerber files reviewed by the PCB fabricator or EMS partner before each prototype run closes the loop.

Essential DFM rules

• Standard components: prefer common packages (0402, 0603, QFN, standard BGA)
• Available components: check stock and lead time before freezing the BOM
• Panelization: design the PCB for efficient panelization, V-cut plus tabs
• Testability: plan accessible test points for production test
• Markings: readable component references for inspection
• Tolerances: stay within the production equipment capability

DFM analysis

Before each prototype run, get your Gerber files reviewed by your PCB fabricator or EMS partner. They will flag potential issues: insufficient spacing, misplaced vias, problematic copper zones. According to IAPD (International Association of Plastics Distribution), DFM analysis must also include mechanical and material constraints for technical enclosures.

In our practice, our methodology systematically validates the critical DFM rules: copper isolation greater than or equal to 100 microns on inner layers, annular ring greater than or equal to 150 microns on 300 micron vias, BGA pad spacing greater than or equal to 200 microns, trace width for 1 A continuous greater than or equal to 0.4 mm in 35 micron copper, controlled impedance 50 ohms plus or minus 10 percent on RF lines.

5 fatal mistakes to avoid

The five most expensive industrialization mistakes we observe regularly are skipping steps, underestimating firmware, ignoring certification until the last minute, neglecting the supply chain and under-budgeting the project. All five share the same root cause: a problem that could have been caught cheaply early in the project is discovered late, when the fix costs far more.

Issues that escape detection cost ten times more to fix in production than in prototype, and a product that fails certification can require a complete redesign. Firmware usually takes longer than planned, an unavailable critical component can stall the whole project, and an unrealistic budget forces compromises on quality. Each mistake is detailed below, with the way to avoid it.

1. Skipping steps

Going straight from POC to mass production, or skipping pre-series. Issues that escape detection cost ten times more to fix in production than in prototype.

2. Underestimating firmware

Firmware development usually takes longer than planned. A working hardware with unstable firmware is not a sellable product.

3. Ignoring certification until the last minute

Regulatory constraints must be integrated from day one of the design. A product that fails in certification can require a complete redesign.

4. Neglecting the supply chain

An unavailable critical component can stall the whole project. Validate availability and plan alternates from the design phase.

5. Under-budgeting the project

An unrealistic budget leads to compromises on quality or to project abandonment. Plan a 20 to 30 percent margin for the unexpected.

How long does it take to industrialize an electronic product?

From POC kickoff to first series shipments, plan on 10 to 15 months for a medium-complexity IoT product, 4 to 6 months for a simple product (basic sensor without RF), and 18 to 24 months for a complex product (advanced RF, class IIa medical certification under IEC 60601-1 and IEC 62304, or automotive under ISO 26262). In our practice, the duration depends more on the number of PCB iterations forced by EMC respins than on the development volume itself.

The dominant variable is therefore design quality upstream. A complete specification, DFM rules applied from the first prototype and EMC pre-compliance built into the schematic review reduce the number of iterations, while each EMC respin adds new prototypes, a new lab booking and weeks of delay. Add a 20 to 30 percent margin for the unexpected.

Bottom line: industrialization is anticipation

Industrializing an electronic product does not mean adding a production phase to a working prototype, it means designing from the very first line of schematic with series production in mind. The five steps (POC, prototype, DVT/PVT, certification, MP) are not formalities, they are gates where reliability (tests -40 °C to +85 °C, ESD plus or minus 8 kV per IEC 61000-4-2), regulatory compliance (EN 55011, ETSI EN 303 645, FCC Part 15, IEC 61508 for functional safety) and unit economics (series yields above 95 percent, unit cost held within plus or minus 10 percent) are decided.

At AESTECHNO, our signature fits in one sentence: product design IS production design. We design EMC pre-compliant PCBs, aligned on IPC-2221 and IPC-A-610 Class 2 or 3, and ready for high-volume manufacturing as soon as routing is complete. Contrary to the "prototype then adapt" approach, this method removes one expensive iteration and secures the certification crossing.

Key points to remember:

• Five normalized gates, EVT/DVT/PVT plus certification plus MP, every one with measurable pass criteria.
• High-speed pre-compliance run in-house on Tektronix TekExpress before the ISO/IEC 17025 accredited lab.
• DFM, DFA and DFT integrated from schematic capture, never patched at industrialization.
• BOM longevity (anti-NRND) with A/B alternates locked at schematic capture, ESD S20.20 protection at the EMS.
• Field-feedback loop after every PVT lot, IPC-7711/7721 rework standards, IPC-A-610 Class 3 acceptance.

Related articles

• Electronic design services methodology, the AESTECHNO 6-step methodology with EVT/DVT/PVT milestones.
• Electronic product specification guide, how to write a specification that survives industrialization.
• CE/RED certification for IoT products, the regulatory process and lead times.
• Electromagnetic compatibility (EMC), pre-compliance approach and lab strategy.
• Design for Manufacturing (DFM), cost-cutting playbook for series production.
• Electronic component shortages, BOM strategy and second-source planning.
• High-speed PCB design, signal integrity and TekExpress pre-compliance.

FAQ: industrialization questions we hear most

How many prototype iterations should I plan for before series?

Plan on 2 to 3 prototype iterations for a medium-complexity product. Simple products may converge in one iteration; complex products (RF, high-speed, thermal constraints) may take 4 or more. Each iteration corrects issues surfaced by the previous round of testing.

Can the steps be parallelized to go faster?

Some activities can be parallelized: firmware development can advance during PCB fabrication, and certification can start during pre-series. However, the foundational steps (POC, prototype, validation) must stay sequential. Excessive parallelization creates rework risk that wipes out the time saved.

From which volume should I move into series production?

There is no absolute threshold. Below 100 units, production stays mostly artisanal (small-batch prototyping). Between 100 and 1000 units, you enter the gray zone where industrialization starts paying off. Above 1000 units, full industrialization (tooling, automated test, EMS partnership) becomes essential.

Should I produce in France or in Asia?

Both options have merits. France or Europe: responsiveness, proximity, ease of communication, small to medium volumes. Asia: lower cost in volume, massive production capacity. For a first product, we recommend starting in Europe to master the process, then transferring to Asia once the product is stable and volumes are significant.

Who should manage the EMS relationship?

The electronic design company can manage the industrial transfer and the first lots, but ultimately, the manufacturer (you) should own the EMS relationship. The design firm stays available for technical support and product evolutions.

How do I handle product evolutions after launch?

Any post-certification change can require a regulatory re-evaluation. Group changes into major versions rather than modifying continuously. Document each change and assess its impact on compliance, especially for EMC and radio.