Legal counsel for hardware and deep tech

Hardware and deep-tech founders face a legal landscape that doesn't look like SaaS: longer development cycles, capital-intensive prototyping, manufacturing contracts that lock in commitments years out, and IP that can be reverse-engineered the moment a product ships. The legal posture has to be set up earlier and tighter than in a typical software startup.

Prior-employer IP claims are the first risk

Most hardware founders are building on knowledge they accumulated at a prior employer. Their employment agreement almost certainly contains invention-assignment, non-compete, or trailing-IP clauses that can sweep in side work — even work done on personal time, with personal tools, in an unrelated area. The defense is documentary: dated notebooks, separate code repos, clear records that the project was conceived and built outside of work resources. If there's any ambiguity, getting a written carve-out from the employer before the project gains value is dramatically cheaper than litigating it after.

Patent vs trade secret is a strategy decision

Patent the inventions that are visible in the shipped product — anything a competitor could reverse-engineer and copy. Patent costs ($15K+ per filing) buy 20 years of legal exclusivity. Trade-secret the inventions that stay inside the company — processes, formulas, internal tooling, optimizations the customer never sees. Trade secrets have no time limit but require active protection: NDAs, segmented access, exit interviews, and IT controls. Most successful hardware companies use both.

Manufacturing contracts are where the leverage shifts

The first MSA a contract manufacturer hands you favors them in every important clause: tooling ownership, IP from "improvements," capacity commitments, change-order procedures, quality acceptance, defect liability, exclusivity. The cost of negotiating these clauses up front is much lower than the cost of trying to switch CMs mid-production. Specifically, watch for tooling ownership (your tooling should be yours, not the CM's collateral), exclusivity (often broader than founders expect), capacity commitments (the CM's commitment to you, not just yours to them), and IP rights to improvements (the CM should not own modifications to your designs).

Trade-secret protection requires architecture, not just paperwork

NDAs protect against intentional misappropriation by parties who care about US legal enforcement. They do not protect against bad actors in jurisdictions with weak IP enforcement, nor against accidental disclosure by parties operating in good faith. Practical protections complement the NDA: segmenting the BOM across suppliers, watermarking drawings, gated access to the most sensitive specifications, and keeping the highest-value IP inside the founding team for as long as possible.

Component-level supply contracts matter more than founders expect

Sole-source components are operational risk. Long-lead components are operational and financial risk — large deposits, hard-to-cancel POs, allocation problems during shortages. Component-level supply contracts (volume commitments, allocation guarantees, last-time-buy provisions) become as important as the CM agreement once production scales. Many hardware startups underestimate this until a supply disruption forces a re-spin of the product.

Product liability arrives the moment you ship

The first time a customer is harmed by your product (or claims they were), the legal exposure runs through every contract you have — supply, manufacturing, distribution, customer terms — and through your insurance coverage and corporate structure. The work to limit product-liability exposure is mostly done before shipping: appropriate warnings and documentation, appropriate insurance, appropriate corporate structure (separating product-facing entities from holding entities), and the right indemnification provisions in each contract layer.