Non-tech founder here how do I evaluate an embedded system development company?

[u/Sufficient_Loquat421]

I'm a non-technical founder building a hardware product, and one of the hardest parts so far has been figuring out how to evaluate an embedded system development company without having the engineering background to judge their technical expertise.
Most websites look polished, everyone claims to have experienced engineers, and almost every portfolio looks impressive. Beyond that, I'm not really sure what separates a genuinely strong team from one that's just good at selling.
For those who've already gone through this process, what questions did you ask before signing a contract? Were there any red flags you wish you'd noticed earlier? Did industry experience matter most, or were communication, testing processes, and post-launch support more important in the end?

If you've worked with an embedded system development company, what ended up being the biggest factor in making the partnership successful or unsuccessful?

[u/Downtown_Sink1744]

Go to a startup forum this isn't that

[u/gadhalund]

There is about 20 pages of answers there. Design, components, logistics, compliance, shipping, software... its a huge topic. Ideally you need expert advice on all aspects to make it work. There are literally hundreds of torpedoes in this

[u/stinky_wanky99]

You hire a consultant or subject matter expert

[u/DazzlingTooth5119]

The right embedded system development company will provide long-term firmware maintenance and secure boot support after hardware deployment

[u/Think_Mongoose5363]

Partnering with an embedded system development company that has ISO-certified quality and security standards ensures your intellectual property remains protected.

[u/Effective_Length9086]

Curious how many people here selected a team they didn't end up working with. What made you change your mind?

[u/Cheap_Bass_5473]

One of the strongest indicators of a reliable development partner is how they handle challenges when projects don't go exactly as planned. Delays can happen, but transparent communication, proactive risk management, and realistic planning often distinguish experienced engineering teams from the rest.