The Question Nobody Asks in Time
A founder hires a freelance engineer for the enclosure, a contract developer for the firmware, and a designer for the industrial design. Everyone is paid in full and on time. Two years later an acquirer's counsel asks for the assignment agreements and there are none. The invoices say "design services rendered" and nothing about who owns the result.
This is the most common defect found in small hardware companies during diligence, and it gets harder to fix over time, because the leverage disappeared the moment the final invoice was paid.
The Default: Payment Is Not Transfer
US law does not give the payer ownership by default. Two separate regimes apply, and both work against a client with no written agreement.
Copyright. Source code, CAD files, drawings, schematics, and renderings are copyrighted works, and the author owns the copyright from the moment of creation. The work-made-for-hire doctrine is far narrower than most people believe: it applies automatically only to employees within the scope of employment, and for contractors only to nine enumerated categories that generally exclude software, engineering drawings, and mechanical designs. A contract saying deliverables "shall be works made for hire" and stopping there can leave copyright with the contractor.
Patents. Ownership starts with the inventor. If your contractor conceived any part of a claimed invention, that contractor is a co-inventor and co-owner until they sign an assignment; paying for the work does not move the right. A court may find you have an implied license, which lets you build the product but leaves you unable to grant an exclusive license, sue an infringer alone, or give an acquirer clean title.
Employees run on different rules, described in whether an employer owns an employee's invention, and hiring a firm rather than an individual is covered in who owns the IP when a company develops your product.
The Wording That Actually Works
Belt and braces, in this order:
- A present-tense assignment. The contractor "hereby assigns" all right, title, and interest, not "agrees to assign." The difference is not stylistic: a promise to assign later must be enforced later, possibly against someone who has become uncooperative, while a present assignment transfers rights on signature. US courts have voided ownership claims over exactly this distinction.
- A work-for-hire clause as a backstop, with the assignment covering anything the doctrine does not reach.
- A further-assurances covenant. The contractor agrees to sign whatever the USPTO later requires, plus a power of attorney letting you sign if they become unreachable.
- Warranties of originality and non-infringement, a waiver of moral rights, and an indemnity if the budget supports negotiating one.
Define the Deliverables as Files, Not as Outcomes
Owning the intellectual property is worthless without the artifacts. A contract promising "the enclosure design" that delivers a PDF and a STEP file has technically been performed, and you are now dependent on that contractor for every future change because you have no parametric model with its feature tree.
List deliverables explicitly: native CAD with full feature history and the software version used, assembly files, dimensioned drawings, firmware source plus build configuration and toolchain version, schematic and PCB layout source files rather than only Gerbers, the bill of materials with manufacturer part numbers, and test fixture designs. Specify that files must open and rebuild without errors. Benchmark bids against typical CAD design service costs before accepting a low quote that excludes source files.
The Borrowed-Component Trap
Every experienced contractor arrives with a toolkit: parametric libraries, firmware modules, motor control routines, a proven power supply block. Reuse is why they are fast and affordable. But they cannot assign what they intend to reuse for the next client, so a clause assigning everything is either being breached quietly or about to create a conflict.
Handle it honestly. Define background IP as anything the contractor owned before the engagement or develops independently of it, require it listed in a schedule, let them keep it, and take a perpetual, worldwide, irrevocable, royalty-free, sublicensable license to use, modify, and distribute it within your product. Anything unlisted is deemed assigned.
Open-source components need the same treatment: a written list of every external library, its license, and where it appears. A copyleft license buried in firmware can obligate you to publish your source code. When manufacturing partners also receive your files, the protective structure differs again, as discussed in why an NDA is not enough for overseas manufacturing.
Already Worked Without a Clause? Fix It Now
Do not wait; leverage is highest while the contractor still wants future work from you. Send a short confirmatory assignment covering all past deliverables, effective back to the start of the engagement. Most contractors sign without objection, because they assumed you owned the work anyway. Collect source files at the same time and verify they open. Where a contractor made a genuine inventive contribution, name them as an inventor and take an assignment of their ownership interest; both acts are required. Record it with the USPTO.
Going forward, hold the final payment tranche until source files are delivered and the assignment is signed, and put confidentiality in place before the first technical conversation, as covered in NDAs for inventors.
Why It Detonates at the Worst Possible Moment
Nobody discovers a missing assignment on a quiet Tuesday. It surfaces during a fundraise, an acquisition, or an infringement suit, with a chain-of-title review running against a deadline. At that point the contractor holds the leverage and knows it, and the price of a signature can be five figures. It is item one on any serious investor diligence checklist, and who handles it by default is one of the tradeoffs in a design firm versus a freelance engineer.
Own What You Paid For
Projects House delivers full assignment of rights and complete native source files as standard, so the chain of title is clean before anyone asks to see it. Tell us about your product and any contractor work already done through the contact form.