← Back to blog
November 19, 2026·15 min read·Engineering

How Many Units Should You Build During EVT, DVT, and PVT? Hardware Manufacturing Quantities and Timelines Explained

Compare EVT, DVT, and PVT build quantities, timelines, tooling lead times, and production strategies for low-volume and high-volume hardware products.

Serge Kadjo
Serge Kadjo
hardware manufacturingNPI planningbuild quantitiestooling
How Many Units Should You Build During EVT, DVT, and PVT? Hardware Manufacturing Quantities and Timelines Explained

Introduction: How Many Prototypes Do You Actually Need?

One of the most common questions when planning hardware development is:

How many units should we manufacture during EVT, DVT, and PVT?

The answer depends on much more than the size of the company or the eventual production order.

A startup developing 200 specialized industrial controllers per year does not need the same validation program as a consumer electronics company planning to manufacture 200,000 devices.

Their manufacturing economics, tooling strategies, reliability requirements, and production processes are fundamentally different.

Yet both companies must answer the same essential questions:

  • Does the engineering design work?

  • Does the complete product meet its requirements?

  • Can manufacturing reproduce it consistently?

  • Is the product ready for commercial production?

The challenge is deciding how many units are needed to generate credible answers without wasting engineering resources.

This guide explains typical build quantities and timelines, how they differ between low-volume and high-volume manufacturing, and how engineering teams can develop realistic production schedules.

1. There Is No Universal EVT, DVT, or PVT Build Quantity

Hardware manufacturers use substantially different build sizes.

For example, Formlabs describes EVT builds of approximately 20–50 units, DVT builds commonly around 50–200 units, and PVT builds that can involve 500 or more units.

Instrumental describes a considerably larger high-volume consumer hardware process, with EVT builds of 100–1,000 units, DVT builds of 300–2,000, and PVT builds of 1,000–20,000.

Contract manufacturers serving smaller production programs may conduct pilot runs with only a few dozen units.

These differences are not necessarily contradictions.

They reflect different products, manufacturing strategies, and qualification requirements.

A high-volume smartphone program may need thousands of units to evaluate yield, tooling variation, cosmetic defects, and production throughput.

A specialized robotics company building 100 systems annually might learn more from 25 carefully instrumented devices than from an unnecessarily expensive 1,000-unit pilot.

The correct build quantity is the number of units required to produce sufficient engineering and manufacturing evidence.

It is not simply a percentage of the expected annual sales volume.

2. Low-Volume vs. High-Volume Hardware Manufacturing

Before estimating quantities, define the intended production model.

Low-volume hardware

For planning purposes, consider low-volume production as approximately 10–1,000 finished units annually.

Examples include:

  • Specialized industrial controllers.

  • Laboratory instruments.

  • Research robotics.

  • Custom automation systems.

  • Small-batch IoT devices.

  • Early commercial hardware startups.

These products may use CNC machining, sheet metal fabrication, additive manufacturing, standard extrusions, off-the-shelf components, or flexible assembly operations.

The manufacturing strategy usually prioritizes flexibility and reduced capital expenditure over achieving the lowest possible per-unit cost.

High-volume hardware

For comparison, consider high-volume production as 50,000 or more units annually, potentially reaching millions.

Examples include:

  • Consumer electronics.

  • Smart home devices.

  • Wireless accessories.

  • Wearables.

  • Connected sensors.

  • High-volume electronic appliances.

High-volume production often justifies significant investments in tooling, dedicated fixtures, automated testing, supplier qualification, and process optimization.

These are illustrative business categories, not industry-wide definitions. Many products fall between them.

3. Typical Build Quantities by Stage

The table below combines published manufacturing examples with practical planning ranges.

These ranges are illustrative starting points—not standardized requirements or statistically sufficient sample sizes. They must be adjusted to the actual test plan.

StageLow-volume hardwareHigh-volume hardware
EVT5–30 units50–1,000 units
DVT10–75 units300–2,000 units
PVT10–100 units1,000–20,000 units
MPSmall recurring production lotsThousands to millions over the production lifecycle

Why are the quantities so different?

High-volume hardware programs must evaluate manufacturing variation across many components, tools, suppliers, operators, and potentially multiple production lines.

They may also need substantial numbers of units for reliability characterization, destructive testing, field evaluations, and supplier process qualification.

Low-volume programs may use more flexible manufacturing processes and fewer tools or production stations.

However, low volume does not automatically mean low risk.

A medical device, industrial safety controller, or aerospace component may require more rigorous validation than a much higher-volume consumer product.

The complexity and consequences of failure matter more than volume alone.

4. EVT Quantities: Build Enough to Validate the Engineering Architecture

EVT is primarily an engineering learning phase.

The objective is to evaluate the chosen architecture, compare critical design options, and uncover functional problems before committing to expensive production investments.

Example: A low-volume industrial controller

Suppose a team plans to manufacture 250 controllers annually.

During EVT, the team wants to compare two wireless antenna configurations.

A possible test plan includes:

ActivityUnits
Configuration A: functional evaluation4
Configuration B: functional evaluation4
Thermal and environmental evaluation2
Debugging and teardown2
Total EVT build12

This is an illustrative allocation. Some nondestructive tests could reuse units, while destructive or configuration-specific tests could require additional samples.

The team might choose to build 12 prototypes rather than 100 because the engineering questions are narrowly defined.

Example: A high-volume consumer device

Consider a company designing a wireless consumer product expected to reach 200,000 units annually.

Its EVT program might involve:

  • Multiple antenna designs.

  • Several mechanical configurations.

  • Different battery suppliers.

  • Multiple PCB revisions.

  • Thermal and charging experiments.

  • Functional and firmware stress tests.

A build involving hundreds of engineering units may be justified.

However, the quantity should still be derived from the engineering test matrix rather than selected solely because the company expects high sales volume.

EVT timeline

A small, well-defined EVT build may take several weeks from released fabrication data to completed initial testing.

Complex programs may take several months because engineers must revise hardware, repeat PCB assembly, and investigate failures.

A critical distinction is the difference between build lead time and stage duration.

A PCB assembly supplier might deliver boards in two weeks, but completing EVT could take considerably longer if the engineering team needs multiple design revisions.

5. DVT Quantities: Size the Build Around the Qualification Plan

DVT usually requires more units than EVT because the complete product must undergo detailed qualification.

The build must support the planned functional, environmental, safety, and reliability testing.

Some tests permanently damage devices.

Others occupy test samples for days or weeks.

Build the DVT quantity from the test matrix

Consider a simplified DVT plan for an industrial wireless device.

Test allocationUnits
Functional and system verification10
Temperature and humidity qualification8
Mechanical shock and durability6
EMC and regulatory testing6
Long-duration reliability testing10
Engineering investigation and spares5
Total45

In this example, the engineering team budgets 45 units because the test program requires them.

The actual allocation should account for destructive testing, test sequencing, retest needs, and the ability to reuse samples.

It should also distinguish qualification samples from units intended for demonstration, customer evaluation, or marketing.

Why DVT can become expensive

Production-intent parts are often more costly than early prototypes when tooling costs are included.

For example:

  • An injection-molded enclosure may require a new tool.

  • A custom gasket may need a controlled material and fabrication process.

  • A PCB assembly must use approved components.

  • Cosmetic surfaces may require tooling refinement.

  • Product testing may involve external laboratories.

A design change discovered after hard tooling has been manufactured can create delays and additional tooling expenses.

Therefore, DVT build quantities should be sufficient to validate the design without unnecessarily increasing exposure to late-stage changes.

6. PVT Quantities: Validate the Manufacturing Process, Not Just the Product

PVT is different because the central objective is manufacturing repeatability.

Building 20 devices may be sufficient to expose basic assembly problems in a low-volume operation.

It may be inadequate for demonstrating expected production performance across a high-volume manufacturing line.

Low-volume example

Consider an industrial equipment manufacturer planning to produce 250 units annually in batches of 25–50.

A pilot involving 30–50 units may demonstrate:

  • Operator readiness.

  • Assembly sequence repeatability.

  • Fixture functionality.

  • Test coverage.

  • Material handling.

  • Production documentation accuracy.

The required quantity depends on the number of operators, stations, process risks, and acceptance criteria.

High-volume example

A consumer hardware company planning a first commercial order of 50,000 units might conduct a pilot of several thousand units.

That pilot can help evaluate:

  • Sustained line throughput.

  • Functional yield trends.

  • Process variation.

  • Cosmetic defects.

  • Test equipment stability.

  • Supplier replenishment.

  • Packaging and logistics performance.

A large build does not automatically guarantee statistically meaningful results. Sampling methods, process stability, defect rates, and the number of production variables must also be considered.

Should PVT equal a percentage of the first production order?

Some manufacturers use planning rules such as 5%, 10%, or another proportion of the first production order.

These rules can be convenient for early budgeting, but they are not universal engineering requirements.

A 5% pilot for a 600-unit order contains 30 units.

The same percentage applied to a 100,000-unit order requires 5,000 units.

Neither automatically proves that the proposed pilot is technically appropriate.

Instead, teams should determine what the pilot needs to demonstrate and how many units are required to evaluate those conditions.

7. How Long Do EVT, DVT, and PVT Take?

Time is often harder to forecast than build quantity.

The actual program depends on engineering iteration, supplier lead times, tooling development, laboratory availability, and manufacturing readiness.

The following table provides illustrative early planning assumptions for moderately complex electronics-based products.

StageLow-volume planning rangeHigh-volume planning range
EVT4–12 weeks8–24 weeks
DVT6–16 weeks8–16 weeks
PVT2–8 weeks4–12 weeks
Production ramp2–8+ weeks4–16+ weeks

These estimates are not measured industry averages, guarantees, or minimum required durations.

For comparison, Formlabs presents an example lifecycle of roughly three to six months for EVT, three months for DVT, and one month for PVT.

Different manufacturers publish shorter schedules for simpler products.

The variation is substantial, which is why a planning range should always be connected to an actual work breakdown and supplier schedule.

Can the stages overlap?

Some activities can overlap.

A team might begin designing production test fixtures during EVT, start tooling procurement before all DVT testing finishes, or prepare manufacturing documentation while reliability testing is still underway.

However, overlapping activities creates financial exposure if an earlier design fails.

A project schedule should clearly distinguish tasks that can run in parallel from decisions that require completed validation evidence.

8. The Five Biggest Drivers of Hardware Development Timelines

1. PCB fabrication and assembly

Every significant PCB revision introduces fabrication, assembly, shipping, bring-up, and testing work.

Firmware-only corrections may be comparatively fast.

A schematic or PCB-layout change can affect multiple components and trigger substantial additional validation.

2. Mechanical tooling

Tooling for injection molding, stamping, die casting, and other manufacturing methods can become a critical-path activity.

Early samples may require repeated adjustments to correct warpage, sink, tolerances, and cosmetic defects.

A production tool being delivered does not mean it has been qualified.

3. Long-lead components

Specialized ICs, sensors, displays, motors, batteries, connectors, and custom materials can delay a build even when the engineering design is otherwise ready.

Approved alternates and early supplier engagement can reduce some of this risk.

4. Reliability and certification testing

Some qualification tests require long operating durations, environmental exposures, or scheduled laboratory time.

If testing fails, engineers must investigate the root cause, implement changes, and determine the appropriate retest scope.

5. Engineering change cycles

Hardware schedules are particularly sensitive to repeated design loops.

A single late change may affect the enclosure, PCB, firmware, supplier tooling, work instructions, and compliance evidence.

The true impact is not just the time needed to update a CAD model or schematic. It is the time required to reestablish confidence in the changed product.

9. Example Production Plan: 250 Units vs. 200,000 Units per Year

Consider two hypothetical hardware programs.

ParameterIndustrial controllerConsumer wireless device
Annual volume250 units200,000 units
EVT build12 units200 units
DVT build45 units800 units
PVT build40 units3,000 units
Manufacturing strategyFlexible assembly, CNC and sheet metalDedicated tooling and production line
Main financial concernEngineering cost per unitTooling investment and scaled unit cost
Main production concernTechnician consistency and component supplyThroughput, cosmetic quality and yield

These are illustrative engineering plans, not actual program results.

Industrial controller strategy

The low-volume manufacturer may prioritize:

  • Reusable manufacturing fixtures.

  • Modular product architecture.

  • Commercially available components.

  • Flexible fabrication processes.

  • Low tooling investment.

  • Detailed technician instructions.

Production can be economically viable even with relatively high labor content if the product's sales price supports it.

Consumer electronics strategy

The high-volume manufacturer may prioritize:

  • Automated assembly operations.

  • Reduced assembly time.

  • High-cavitation molding or other scalable fabrication methods.

  • Automated end-of-line testing.

  • Supplier capacity qualification.

  • Scrap and defect reduction.

  • Optimized material and labor costs.

Investment in manufacturing automation becomes more attractive when the expected volume justifies its fixed cost.

10. How to Calculate the Right Build Quantity

A useful engineering approach is to size each build from the evidence needed.

Step 1: List the configurations

Identify the product versions, component alternatives, materials, or manufacturing processes requiring validation.

Do not assume results from one configuration automatically transfer to another.

Step 2: List every test

Include functional, reliability, environmental, safety, regulatory, manufacturing, and field-validation activities as applicable.

Step 3: Identify destructive and non-destructive tests

A product used for destructive impact testing may be unsuitable for subsequent electrical qualification.

Other units may be reused if the test sequence permits it.

Step 4: Account for statistical confidence

Some reliability or quality claims require formal sample-size calculations.

For example, under an idealized independent, identical pass/fail model, observing zero failures in 59 trials provides approximately 95% one-sided confidence that the probability of passing a single trial is at least 95%.

That calculation does not automatically establish lifetime reliability. Actual reliability qualification must account for operating time, stress, failure mechanisms, and the specified confidence objective.

Step 5: Reserve investigation units

Failures often require destructive teardown, component replacement, or detailed failure analysis.

A build plan with no investigation samples is vulnerable to delays.

Step 6: Add a justified contingency

Reserve additional units based on expected engineering risk, supplier capability, and the cost of repeating a build.

Avoid adding large arbitrary buffers without understanding their purpose.

A practical build-sizing principle

Required build quantity = Qualification samples + Configuration-specific samples + Investigation samples + Justified contingency

Where samples can be reused, count them appropriately rather than simply adding every test allocation.

The final quantity should be supported by the validation plan.

11. Building a Realistic Hardware Schedule

A useful schedule should be built backward from the intended production release while explicitly tracking dependencies.

For every critical activity, document:

  • Required input.

  • Responsible owner.

  • Supplier or internal resource.

  • Expected lead time.

  • Acceptance criteria.

  • Dependencies.

  • Alternative plan if the activity fails.

The schedule should also reserve time for engineering iteration rather than assuming every test passes on the first attempt.

It is important to distinguish the following milestones:

Design release: The engineering configuration has been authorized for the next build.

Parts available: Suppliers have delivered acceptable materials.

Build complete: The planned devices have been assembled.

Qualification complete: Testing and failure analysis are finished.

Gate approved: The responsible stakeholders have accepted the evidence.

These milestones are not interchangeable.

A completed build is not necessarily a completed validation stage.

Conclusion: Optimize for Evidence, Not Prototype Count

The goal of EVT, DVT, and PVT is not to manufacture as many prototypes as possible.

It is to reduce technical and manufacturing uncertainty before significant commercial commitments are made.

Low-volume manufacturers can often achieve this with carefully selected, instrumented builds and flexible manufacturing methods.

High-volume manufacturers usually require larger builds to qualify production processes, evaluate yield, and support manufacturing ramp-up.

Regardless of volume, the same principle applies:

Build the number of units required to make a confident engineering decision—then use the resulting evidence to plan the next stage.


Frequently Asked Questions

How many units should a startup build during EVT?

A small startup may use a handful to a few dozen integrated engineering units. The correct number depends on the configurations and tests being evaluated.

Is a 100-unit PVT build sufficient?

It may be for some low-volume programs, but not for every product or manufacturing line. The pilot must support the required process validation and confidence objectives.

Why does high-volume DVT require more units?

Large programs may need more samples for reliability testing, tooling qualification, product configurations, and evaluation of manufacturing variation.

Can a manufacturer skip PVT when production volume is low?

The team may simplify its validation process, but it still needs objective evidence that its manufacturing method consistently produces conforming products.

Are faster manufacturing processes always better?

No. Shorter fabrication lead times are valuable only when the resulting parts and processes support the product's engineering and validation requirements.

Further Reading

In this series

Stop bad hardware changes before they ship.

30-day pilot on one active product. Fixed $8k. Live on your own BOM in week one.