The short answer
A new hardware device takes about 12 to 24 months to go from concept to mass production. Three months is enough for a feasibility study and a proof of concept prototype. Three months cannot cover design for manufacturing (DFM), design validation (DVT), production validation (PVT), and certification for a device that starts from a blank page.
Founders come to hardware studios with one request: build my device in three months. Some vendors say yes. If you hear that yes, ask which stages the quote leaves out, because the stages a fast quote skips are the ones that turn a single working unit into thousands of identical, certified, sellable ones.

What can you build in 3 months?
Three months buys you a proven concept or a rebranded product. The table shows each realistic outcome and what you hold at the end.
| What you ask for | Realistic in 3 months? | What you hold at the end |
|---|---|---|
| An existing white label device with your logo | Yes. Production can start in 2 to 4 months | A product the manufacturer controls. You cannot change the functions, the design, or the firmware. |
| A feasibility study with a proof of concept | Yes. 2 to 3 months. | Product specification, component selection, early industrial design, a cost estimate, and a “works like” prototype built on development kits. |
| An engineering prototype with custom electronics | No. 5 to 6 months after the feasibility study. | 10 to 30 finished, working units for investors and demo users. |
| A custom device ready for mass production | No. 12 to 24 months. | A validated design, production tooling, certifications, and a factory that builds every unit to the same standard. |
A prototype proves that your idea works once. An engineer assembles it by hand, 3D prints the enclosure, and wires in off the shelf modules. That unit can look finished in a photo and still fail every test a real product must pass. Nobody has dropped it, heated it, frozen it, measured its radio emissions, or built it on a production line.
Two offers that leave you with a product you cannot scale
Garage teams. A small team or a solo engineer can build a prototype in three months that looks finished. The problems appear at the manufacturing phase. A garage team works without a contract manufacturer, tooling, test jigs, a supply chain plan, or a certification path, so nobody designs the unit for a production line. You receive a hand soldered, 3D printed device, and scaling it is close to impossible without design changes. A factory cannot build that unit 5,000 times at a price your customers will pay.
Development that costs too little. A connected product costs tens of thousands of dollars for feasibility and early prototypes and reaches six figures through EVT, DVT, PVT, and tooling. A quote far below that range leaves stages out. Ask the vendor to show you where DFM, tooling, compliance testing, and the pilot run sit in the price. If those lines are missing, you will pay for them later, and the bill will be far higher than a full team would have charged from the start. You fund the cheap design first. After it fails at the factory, you fund the redesign for manufacturing, the new tooling, and a repeat of every test. The 1:10:100 rule sets the price: a fix that takes 1 hour at the design stage takes over 100 hours after the first batch.
Both offers end the same way. You own a device that works on a desk and cannot go into production, and you fund a second round of development to redesign it for manufacturing.

Simpler products move faster, and phases can overlap or combine to fit your goals.
The full range across our projects is 12 to 24 months. Products that reuse a proven compute platform land at the short end.
We shorten the schedule inside each stage. Hardware, firmware, and mechanical engineering run in parallel, and our in house prototyping lab turns design changes into physical parts fast. We keep every validation gate, because each gate protects your production run. You can read the full process on our hardware product development page and in our guide to EVT, DVT, and PVT.
Why DFM, DVT, and PVT do not fit into 3 months
Each validation stage answers a different question, and each answer comes from physical units that someone has to build, ship, and test.
- Engineering prototypes ask: does the product work as specified? Engineers design the electronics, the mechanics, and the firmware, then build 10 to 30 working units in house and test them. A second iteration follows when the first units miss the specification.
- EVT asks: can a factory build this design? The team selects a contract manufacturer, reworks the design for manufacturing (DFM), orders the first production tooling, and builds 50 to 100 units. Those units go through early compliance testing, beta testing, and field trials.
- DVT and PVT ask: can the factory build it the same way every time? The team finalizes the BOM and the supply chain, refines the tooling, and optimizes assembly and testing. DVT produces 500 to 1,000 production grade units for certification (FCC, UL) and launch. PVT is a 10,000 unit production run.
Three facts about physical products keep these stages from shrinking:
- Parts have lead times. Someone has to fabricate the circuit boards, order the components, and cut the tooling before any test can start. Software teams ship a release every week. In hardware, one design change often costs months.
- Tests run in real time. On a smart padlock project we programmed a CNC machine at the factory to press the buttons and pull the shackle without a pause until the first failure appeared. Then we adjusted the design. A durability test like that takes as long as it takes.
- Freight takes time. A sea shipment from China to a US port takes about four weeks. That is a third of a three month schedule.

Certification adds its own queue. Most products for sale in the United States must pass EMC and EMI testing, and a lab can only test units that match what the factory will build. Our guide to FCC certification covers that step.
Skipping validation moves every fix to the most expensive stage. Our CEO Alex Gudilko describes the 1:10:100 rule in Forbes: an issue takes 1 hour to correct at the design stage, 10 hours once a prototype exists, and over 100 hours after the factory produces the first batch. The same ratio applies to cost.
Red flags in a 3 month hardware development offer
A three month promise for a custom, production ready device should make you slow down. Some vendors underestimate the work. Others know the schedule is false and count on you to keep paying once your money is committed. Your loss looks the same in both cases, so check every proposal for these signs.
- The quote names no stages. You see one line called “development” with no EVT, DVT, or PVT and no exit criteria for any of them.
- Nobody mentions manufacturing. The proposal has no DFM, no tooling, no contract manufacturer, and no pilot run.
- The deliverable and the pitch disagree. The contract says “prototype” while the sales call says “ready for production.”
- The price arrives before any research. A vendor gives you a fixed price for the whole product without a feasibility study or a written specification.
- The schedule has no second iteration. Real projects plan for a second round of samples when the first round fails a test.
- Nobody asks about volume. A partner who plans for production asks how many units you want in the first batch and what the device should cost to build.
- The portfolio stops at renders and prototypes. Ask for a product the vendor took through PVT, and ask to speak with that client.
An honest three month proposal exists. It names its deliverable as a feasibility study or a proof of concept, lists what the price excludes, and tells you how many months and dollars stand between that prototype and your first production run.
How to plan your budget and timeline
Pick the route to market that matches your deadline first. Your deadline decides how much of the product you can own.
Our article on four strategies for building a hardware product compares these routes in detail.
Once you choose custom development, five habits protect your money:
- Start with a feasibility study. In 2 to 3 months you learn how the product looks, how it works, and what it costs to build. You spend a small share of the budget before you commit the rest.
- Budget by stage. A connected product costs tens of thousands of dollars for feasibility and early prototypes and reaches six figures through EVT, DVT, PVT, and tooling. Release tooling money only after the design passes validation.
- Plan your fundraising around the real schedule. Tell investors 12 to 24 months. A launch date built on a three month promise will cost you their trust when it slips.
- Know your production numbers early. Most contract manufacturers prefer to see at least $1,000,000 in bill of materials for a production order.
- Put certification and DFM in the plan from the first day. Teams that treat them as a final step pay for the same design work twice.

Ask every vendor on your shortlist the same four questions:
- Which stages does your quote cover?
- What do I hold in my hands at the end of each stage?
- Which products have you taken to mass production?
- What happens to the schedule and the price if a sample fails a test?
Frequently asked questions
Can you build a hardware device in 3 months?
You can build a proof of concept prototype or launch a white label product in 3 months. A custom device ready for mass production takes 12 to 24 months, because engineering validation, design for manufacturing, tooling, certification, and a pilot production run each need their own time.
How long does hardware product development take?
Hardware product development takes 12 to 24 months from concept to mass production. At AJProTech the phases run 2 to 3 months for the feasibility study, 5 to 6 months for engineering prototypes, 4 to 5 months for EVT, and 4 to 6 months for DVT and PVT.
What are the stages of hardware product development?
The stages are feasibility study, engineering prototypes, engineering validation (EVT), design validation (DVT), production validation (PVT), and mass production. Each stage ends with a gate: a set of tests the product must pass before the next stage starts.
What is the difference between a prototype and a production ready product?
A prototype shows that the idea works in a few hand built units. A production ready product has passed functional, environmental, and compliance tests, uses tooling a factory can run at volume, and comes off a validated production line with a known yield.
Why does a 3 month hardware promise put my money at risk?
A three month schedule for a custom device leaves no room for DFM, DVT, PVT, or certification. You pay for a prototype that no factory can build at volume, and then you pay again to redesign it for manufacturing.
How much does hardware product development cost?
A connected product costs tens of thousands of dollars for feasibility and early prototypes and reaches six figures through EVT, DVT, PVT, and tooling. After a feasibility study AJProTech gives a fixed estimate against a list of deliverables.
What is the fastest honest way to launch a hardware product?
White label is the fastest route, with production starting in about 1 to 3 months, and you give up control of the design. For a product you own, start with a 2 to 3 month feasibility study and plan the full schedule from its results.


