The Short Answer: The Contract Decides — Not Assumptions

One of the most sensitive questions inventors raise in a first meeting is about IP ownership in product development: if an engineering firm develops my product, who ends up owning the results? The short answer is that everything is determined by the written agreement — not by assumptions, industry folklore, or verbal understandings. In client-funded product development it is standard practice for the client to receive full ownership of the deliverables created for them, but the exact wording is what governs in practice. At Projects House we put ownership in writing before work begins, precisely so there's no ambiguity at the moment the product is ready for production. One caveat before we dive in: we're an engineering firm, not a law firm — treat this as an educational map of the issues, and have your actual agreements reviewed by an attorney.

An Idea vs a Protectable Work Product

It's important to separate two very different things. An idea, by itself, is not a legal asset; you can't register ownership of a thought, and two people can conceive the same solution in the same week. What can be owned and protected is the concrete expression: CAD models and drawings, electrical schematics, PCB layouts, firmware source code, a working prototype — and an invention on which a patent application can be filed. So when people talk about "owning the idea," what's actually at stake is ownership of the engineering work product and the know-how created around it. Under US law, one detail matters more than most people realize: by default, IP created by an independent contractor is not automatically owned by the paying client — a written assignment is what transfers it. That's exactly why the contract language matters.

What a Good Development Agreement Covers

  • Assignment of ownership in the deliverables to the client, typically conditioned on full payment of the agreed fees.
  • Background IP: know-how, software libraries, or design modules the firm owned before the project stay with the firm — and you receive a license to use them within your product. Make sure that license is broad enough to survive manufacturing anywhere.
  • Source file delivery: not just PDFs — parametric CAD files, Gerber files, the bill of materials, and source code. Without them, your "ownership" is theoretical, and switching vendors later becomes hostage negotiation.
  • Mutual confidentiality with a clear scope and duration.
  • Portfolio rights: whether and how the firm may show the project after launch.
  • Infringement responsibility: who bears the risk if the design infringes a third party's rights.

These questions belong on the table when you're choosing a partner in the first place — our guides on choosing a product design firm and design firm vs freelance engineer include the contract questions worth asking before you sign.

What an NDA Does — and Doesn't Do

A non-disclosure agreement is an important tool, but it transfers no ownership. It restricts use and disclosure, nothing more. Many inventors sign a generic NDA and feel protected while the development contract itself contains no ownership clause at all. The right sequence: an NDA before the first detailed conversation, then a development agreement that settles ownership, delivery, and payment. Watch the term, too — an NDA that expires after a year doesn't protect a product that launches later. Our article on NDAs for inventors covers when they help and when they're theater.

Special Cases Worth Knowing

Some circumstances change the picture. If your invention arose from work you did for an employer — especially in your employer's field, or using its resources — the employer may have rights in it; check your employment agreement before investing. If co-founders are involved, settle ownership, contribution, and exit mechanics in a founders' agreement before development starts. If government grant money funds the work, the award terms may attach conditions to the resulting IP. And if you manufacture overseas, your manufacturing agreement must clearly separate the purchase of production services from any license to your design files — otherwise the factory may treat your tooling and design as shared assets.

How to Protect Yourself, Step by Step

The recommended sequence is simple and inexpensive. First, signed paperwork before full disclosure. Second, a provisional patent application if there's patentable novelty, to lock a priority date. Third, tidy records of creation dates, versions, and who contributed what. Fourth, a development contract that mandates full source-file delivery at the end. Do these four things and IP ownership stops being a fog and becomes a set of measurable clauses. The broader journey is mapped in our idea to product hub and the patents and intellectual property hub.

If you're about to engage a development partner and want the engineering and commercial side of the relationship structured cleanly — deliverables, source files, milestones — reach out to Projects House through our contact form and we'll walk through your project together.