Clay Tech

"clay-works make things real"

translated from clazytech.com

Startups Should Weigh Their Own Strengths Before Involving a Factory

In practice, it depends on the case. Let’s consider a few typical examples.

<Company A’s case> Company A is a startup that just launched, and the founders are not engineers with manufacturing experience. Most of the team members are external resources such as contractors, and let’s say the company has managed to get a working principle prototype running with part-time help. Fundraising has only reached the minimum seed funding needed for development, with no prospect yet of raising funds for manufacturing.

In this case, bringing a manufacturing factory on board seems premature. One reason is that Company A’s strengths haven’t yet been established. If the founders were researchers trying to turn their research results into a business, what matters for differentiation isn’t the research results themselves but the hardware or service that correctly implements them. Unless they get to the point of designing it themselves and getting it to work at a product-equivalent level, that strength won’t be fully realized. If they’ve secured development funding, they would do better to spend the next six months to a year growing the team and repeating prototyping to mature the technology, then make their move once further funding comes in.

<Company B’s case> Company B has already built up several years of business and revenue with software products, and let’s say it has now decided to commit to a service that also uses hardware. The team has run some proof-of-concept testing using a combination of off-the-shelf components, and now wants to turn this into a product by translating it into dedicated hardware.

In this case, bringing a manufacturing factory on board at this point seems like the right move. First, this company hasn’t built up hardware know-how, and it doesn’t seem desirable for it to start now. It’s wiser, and more competitive, for them to pursue a strategy weighted toward software, which is their strength. Also, the fact that they ran proof-of-concept testing using a combination of off-the-shelf parts means the hardware itself isn’t very unique. Given that, it seems feasible to bring in a manufacturing factory and use its design resources and partners to quickly turn the product around through horizontal deployment of general-purpose technology.

<Company C’s case> Suppose this is a startup that has raised sufficient funding, with a rock-solid staff for pushing forward both development and manufacturing — people who came from major development companies alongside people with experience running manufacturing factories. Even so, they remain fabless. The prototype has gone through repeated rebuilds over two years and, at a glance, has reached a quality level not far from a mass-production unit.

In this case, I’d recommend first putting together manufacturing specifications internally, then starting conversations with multiple manufacturing factories at the same time. There is considerable variation in what factories require. That depends on the factory’s own technical capability and management ability. So if you leave the judgment calls about design changes too much up to the manufacturing factory, you risk the self-defeating situation of being forced into modifications that undermine the original design intent. If this is something your team can manage and judge in-house, it’s better to firm things up internally as far as possible before going into negotiations with the manufacturing factory — this lets you demand a higher-quality output. That said, it’s natural for a factory to say “what can’t be done can’t be done,” so you should approach several of them.


Originally published in Japanese at https://clazytech.com/2021/08/543/. Translated with LLM assistance and reviewed before publication.