Key takeaways
- An NDA governs who may see and use your information. It does not decide who owns the design, the files or any invention made during the project.
- Ownership is set by the development agreement, and US patent rights are assigned by a written instrument. Read that clause more carefully than the NDA.
- Protection is staged: what you document before contact, what you disclose during vetting, what the contract says, and what reaches the factory at handoff.
- A development firm’s business depends on clients trusting it with ideas. Verify that through its documents and references, and have a qualified attorney review anything deal-specific.
This guide describes how idea protection typically works when you hire a hardware development company. It is general information, not legal advice, and it does not create an attorney-client relationship. Ask a qualified attorney about your jurisdiction and your agreement.
You protect an idea with a development partner by putting the right document in place at each stage: a confidentiality agreement before you share details, a development contract that states who owns what the project produces, and patent filing decisions coordinated with a patent attorney before anything becomes public.
No single document does all of that. Most founders put their energy into the NDA and skim the agreement that actually decides ownership. This guide maps protection to each stage of a project, explains what each document typically does and does not do, and points to where each mechanism is covered in depth.
What you are actually protecting, and from whom
“My idea” usually means three different things, and each is handled differently.
The idea, the design, and the files are three different things
| What it is | Example | What typically governs it |
|---|---|---|
| The concept | A pet feeder that weighs each portion | Confidentiality, and a patent only once it is described in enabling detail |
| The design | The mechanism, circuit and enclosure that make it work | The development agreement’s ownership terms, and any patent filing |
| The files | CAD, schematics, firmware source, BOM, drawings | The deliverables and ownership clauses of the agreement |
A bare concept is the hardest to protect and usually the least valuable on its own. US patent law asks for a description that enables someone skilled in the field to make and use the invention, so a concept without that detail is not yet something a filing can secure. The design and the files are where most of the value sits once development starts, and they are created during the engagement. That makes the contract covering the engagement more important than any document you sign before it.
The realistic risks usually come from four places:
- Accidental public disclosure by you, such as a crowdfunding page or a trade show demo, which can cost patent rights.
- Unclear ownership of what the partner produced, discovered only when you try to change suppliers.
- Undocumented subcontractors who saw the design without a written obligation.
- Factory-side copying after production files leave your control.
Where protection comes from at each stage
The work splits across four stages, and a different document carries it at each one.
Before you contact anyone
- Write it down and date it. A dated description, sketches and the problem it solves create a record of what you brought to the project, which matters later when separating your background IP from what was created together.
- Keep it off public channels. A post, a pitch video or a pre-order page can be a public disclosure. The disclosure rules are covered in patent vs prototype.
- Decide filing timing with an attorney, before any public step rather than after it.
During vetting and first conversations
- Share in layers. Explain the problem and the market first, then the approach, and hold the specific mechanism until a confidentiality agreement is signed.
- Ask how the firm handles client information, who on its side will see it, and whether it uses outside contractors. These belong on your list of questions to ask before hiring a hardware development company.
- Check the firm’s track record before handing over detail. Our guide on how to vet a hardware development company covers references, deliverables and contract terms.
Inside the development agreement
This is where ownership, file delivery and confidentiality during the work are settled. It is the subject of its own section below, because it is the term that matters most.
At manufacturing handoff
Production files leave your direct control at this stage. Tooling ownership, factory confidentiality terms and the exact files the factory receives should all be settled in writing before anything moves. Tooling is covered in who owns the tooling.
What an NDA does, and what it does not do
A non-disclosure agreement is a contract. It typically defines what counts as confidential information, how the receiving party may use it, how long the obligation lasts, and what happens when the relationship ends. It gives you a contractual claim if those terms are broken. It does not make misuse impossible.
What an NDA typically does not do:
- It does not transfer ownership. A standard NDA says nothing about who owns the design or files the partner later creates.
- It does not cover what is already public. Information already disclosed, already known to the other party, or developed independently is usually excluded.
- It does not enforce itself. Pursuing a breach costs time and money, and depends on proving what was disclosed and when. That is why a dated record matters.
- It does not replace a patent. An NDA binds the people who signed it. A granted patent applies to everyone.
Some established firms and investors will not sign a one-way NDA at first contact, often because they review many similar ideas. That is frequently a practical policy rather than a warning sign. Share only the problem at that stage, and ask what confidentiality terms the firm puts in its development agreement.
An NDA decides who may use your information. It does not decide who owns what gets built with it.
Ownership is the term that matters most, and it is not the NDA
The development agreement decides who owns the design, the files and any inventions that come out of the project. Three points surprise most founders:
- Patent rights are assigned in writing. Under 35 U.S.C. 261, patents and patent applications are assignable by an instrument in writing. Without a written assignment, rights in an invention generally start with the people who invented it, so an agreement that is silent on inventions leaves the question open.
- Engineers can become co-inventors. Under 35 U.S.C. 116, joint inventors can apply together even if they did not work together physically or make the same type or amount of contribution. An engineer who contributes to the conception of a claimed feature may be a joint inventor, which is why assignment terms need to cover inventions made during the work, not only the files.
- “Work for hire” is a copyright term with limits. Under 17 U.S.C. 101, a commissioned work counts as made for hire only if it falls into one of nine listed categories and both parties sign a written agreement saying so. It is not a patent concept, and engineering deliverables often fall outside those categories, which is why agreements commonly pair it with an express assignment. Ask your attorney how your agreement handles both.
Two more terms decide what you can actually do with the results:
| Term | What it typically covers | The question to ask |
|---|---|---|
| Background IP | What each party brings in: your concept, or the partner’s existing tools, libraries and reference designs | Do I get a license to any of the partner’s background IP that ends up inside my product? |
| Foreground IP | What is created during the project | Who owns it, and does the assignment cover inventions as well as files? |
| Deliverables | Which files are handed over, in which formats, and when | Are native CAD, schematics and firmware source in scope, or only exports? |
At Inventornest, source files are not automatically included in every engagement. Their delivery depends on the agreed scope. Factory file provision is also distinct from the client’s entitlement to source-file delivery, which is governed by the agreement. The general lesson applies to any partner: check the deliverables list in the contract, not the sales conversation.
The type of partner matters here too. With an ODM, the design is often the partner’s existing product carrying your brand, a very different ownership position from a commissioned design, as explained in OEM vs ODM. How payment and scope are structured shapes these terms as well; see product development engagement models.
Where patents fit, and where they do not
A patent is the only tool in this list that can apply beyond the people you have signed agreements with. It also costs money, takes time, and covers only what the application describes. Two guides already cover timing in depth:
- Patent vs prototype explains why feasibility comes first and why you file once the invention is definite and before any public disclosure.
- What a provisional patent application is explains what it secures, the 12-month clock, and why thin filings fail.
Not every idea suits a patent. Some products are better served by keeping the know-how confidential. Under the federal definition in 18 U.S.C. 1839, information is a trade secret only if it has value from not being generally known and its owner has taken reasonable measures to keep it secret. Confidentiality agreements and controlled file access are part of those measures, which is one more reason to document who has seen what.
The practical point is coordination. Technical development and filing decisions need coordination with the client’s patent attorney, because a filing made before the design settles can end up describing a product you never build.
Who else will see your design?
A hardware project usually involves more organizations than the firm you signed with: PCB fabricators, assembly houses, machinists, test labs and, eventually, a factory. Each one sees part of your design. Three questions are worth settling in writing:
- Who does the work? Ask which disciplines the firm handles itself and which it sends out.
- What binds the others? Every party that sees confidential files should be under a written confidentiality obligation, and ownership of anything they create should flow back through the chain.
- Who coordinates? Someone should own the relationship with each vendor, so files go out on a need-to-know basis.
At Inventornest, we handle product design and development in-house. We retain responsibility for engineering coordination and design clarification when production is handled by our manufacturing partners. External laboratory certification and specialist patent-attorney services remain separate professional activities. Ask any partner the same question and get the answer in writing; undocumented handoffs are among the red flags in a product development partner. For the factory relationship itself, see working with overseas suppliers.
A practical sequence for a first-time inventor
- Document the idea in a dated description with sketches and the problem it solves.
- Talk to a patent attorney about timing before any public step. For a physical product, technical feasibility usually comes first; see product feasibility analysis.
- Shortlist partners and share only the problem at first contact.
- Sign a confidentiality agreement before sharing the mechanism, and keep a log of what you disclosed, to whom, and when.
- Read the development agreement for assignment, background IP, deliverables, subcontractors, and what happens if the project stops. Have an attorney review it.
- Approve scope in writing. Clients do not need to arrive with a complete engineering specification, but before full development begins the client should approve the requirements, deliverables, exclusions, payment milestones and acceptance criteria.
- Settle factory terms before handoff: tooling ownership, confidentiality, and which files the factory receives.
- Stay private until your filing position is set.
When to bring in a qualified attorney
Use an attorney for the decisions that are hard to reverse or depend on your jurisdiction:
- Before any public disclosure, to set patent filing timing.
- Before signing the development agreement, to review assignment, background IP and deliverables.
- Before production starts overseas, to adapt confidentiality and tooling terms to the factory’s country.
- When you suspect misuse, before you respond to the other party.
Bring your dated idea record, your disclosure log, every signed confidentiality agreement, and the draft development agreement. An attorney can only assess what you can show.
Frequently asked questions
Do I need an NDA before talking to a product development company?
Not for a first conversation about the problem and the market. Sign a confidentiality agreement before you share the specific mechanism, drawings or files. Many development firms are used to signing mutual NDAs at that stage.
Does signing an NDA mean I own the design?
No. An NDA covers confidentiality. Ownership of the design, files and inventions is set by the development agreement, and in the US patent rights are assigned by a written instrument.
What if a development firm refuses to sign my NDA?
Some firms decline one-way NDAs at first contact because they see many similar ideas. Share only the problem at that stage, and ask what confidentiality terms the firm includes in its development agreement.
Can an engineer at the firm become a co-inventor on my patent?
It is possible. Joint inventorship depends on contribution to the conception of what is claimed, not on who paid for the work. Assignment terms in the agreement need to cover inventions made during the project.
Should I file a patent before hiring a development firm?
It depends on your invention and your disclosure plans. A filing only covers what you can describe at that point, so discuss timing with a patent attorney first. Patent vs prototype explains the trade-off.
Will I get the CAD files and firmware source at the end?
Only if the agreement includes them. File delivery varies by firm and by scope, so check the deliverables list for native formats before you sign.
Where Inventornest fits
We are a hardware development team, not a law firm, and we do not give legal advice. What we do is the engineering work that has to line up with your protection decisions: turning an idea into a defined design, documenting it well enough to support a filing, and keeping track of who sees what.
- Patent coordination. We provide patent services through expert patent attorneys engaged according to the product and relevant jurisdiction. This is not a blanket recommendation to delay filing: the attorney should assess timing, public-disclosure risks and intended markets first.
- Written scope. Deliverables, exclusions and file delivery are set in the agreement, because source files are not automatically included in every engagement.
- Coordination through production. We handle product design and development in-house and retain responsibility for engineering coordination and design clarification when production is handled by our manufacturing partners.
Inventornest has built 200+ products over 12+ years building hardware, across 30+ industries. To see how we take a product from idea to production, start with our OEM services.
Last reviewed October 2026. This article is general information and not legal advice. Laws differ by country and change over time; confirm anything specific to your situation with a qualified attorney.
