Design engineer or design agency: who should build your product?
The difference between a design engineer and a design agency, why it matters for a physical product, and how to tell which one your project actually needs.
The difference between a design engineer and a design agency, why it matters for a physical product, and how to tell which one your project actually needs.
If you are a founder about to build a physical product, you will quickly find two kinds of help offering to take it on, and they are not the same thing. Getting the distinction right early saves a lot of money and a lot of frustration, because the wrong choice tends to reveal itself at the most expensive moment: when the design meets the factory.
Industrial design is about how a product looks and feels: form, ergonomics, the user’s experience of the object. It is a real and valuable craft, and a beautifully resolved product usually has excellent industrial design behind it.
Design engineering is about making the product actually work and actually be manufacturable: the mechanism, the thermal behaviour, the structure, the tolerances, the choice of process, and the engineering that decides whether a design survives tooling, volume and real-world use.
A finished product needs both. The question is which one leads, and which one is brought in to support.
The trouble starts when a studio built around industrial design lists “design for manufacture” alongside its styling work and takes a product all the way to tooling. Making something look right is a different skill from making it survive a hundred thousand production cycles, and “we do DFM” on a services page is not the same as having stood on a factory floor while a tool was cut and a line ramped up.
You often only discover the gap late: the prototype looks perfect, the tool is ordered, and then parts warp, assemblies wedge, tolerances stack up, or the thing fails a compliance test. At that point the cost of the missing engineering is a recut tool, not a design revision.
A useful test is to ask where the risk in your product lives.
Most first-time hardware founders underestimate how much of the risk is in the second category, because the looks are the part you can see and the engineering is the part you cannot.
I am a design engineer, so my job is making a product work and be manufacturable, grounded in having taken consumer products through tooling and volume manufacture. When a product needs the aesthetic side, I bring in industrial designers I trust, rather than stretching past what I do best. That way the engineering that decides whether your product succeeds is the core of what you get, not a bolt-on, and you still get one joined-up process.
If you are weighing up who should take your product on, the most useful thing you can do is talk it through with someone who will be honest about which discipline your project actually needs. That is exactly the kind of conversation a short intro call is for.
Part of How to develop a physical product: a founder's guide from idea to market · all guides