We have a product concept. How long will it take to build our prototype?

June 30 , 2025

sofeast

A business has a product concept and an initial BOM (Bill Of Materials) and now needs to create a prototype to raise funding. Backers will want to see a working and relatively good-looking prototype first before parting with their cash.*

Building a prototype once all the design work is done and if components can be ordered is one thing, maybe just a couple of weeks, including testing. But is that the situation here?

 

How do we get to the prototype stage?

Getting a tangible work-like and looks-like prototype usually involves many steps:

  • Understanding the product requirements and asking questions to clarify points, etc.
  • Planning for 1 design iteration and setting a test plan for the prototypes
  • Doing some sourcing work
  • Doing some engineering design
  • 3D printing some parts, and maybe applying surface treatment (e.g. paint)
  • Making a few prototype PCB assemblies if it’s a work-like prototype
  • Receiving the various parts from outside vendors, checking if they are OK, and getting new ones to replace any they messed up
  • Building prototype(s), usually with a bit of trial & error
  • Testing the prototypes and, maybe, making corrections if needed
  • Packaging and sending the prototypes

As mentioned in this blog post we wrote earlier:

We often tell our clients this.

Remember, the Dyson vacuum cleaner we know today went through 5,000 prototypes before its version 1.0 was approved for manufacturing.

For a relatively unique and complex product, it is pretty common for the development to take 3 months or more of intense work. Sometimes it is 9 to 12 months. And sometimes many years, for the most challenging products.

This means that there is probably no fast route to a fairly advanced prototype.

 

Might a proof-of-concept prototype be enough?

One point to consider is that you may not require a work-like and looks-like prototype to illustrate well enough to backers how the product will work. Building a proof-of-concept prototype that looks rougher than a looks-like prototype and only has, say, 1 or 2 of the key functions, may be adequate. Getting to this stage will be a lot less work and lower cost.

Making a proof-of-concept prototype is a double-edged sword, as it will also address whether some large assumptions are being made and if there are known technical difficulties that could derail the project.

 

Conclusion

A list of parts (basically, a very initial BOM) probably isn’t enough for you to produce quite an advanced prototype. There is still a lot of work to be done. However, if backers providing funding need to see tangible evidence of the product and how it works, an earlier proof-of-concept prototype might be more suitable at this point.

P.S.

You may also like:

*Based on a real Sofeast reader’s question.

Stay connected with us

Join our newsletter for insights, updates, and industry news, or learn more about what we do.

Fill up the form

Single Blog Form