You paid the invoice in full. The developer delivered the code, the designer handed over the logo files, and the freelancer sent the final cut of your product video. So you own all of it — right?
Not necessarily. Under U.S. law, the person who creates intellectual property owns it by default, even if you paid them to create it. Without a signed, written transfer, that contractor still holds the copyright to the code on your servers, the patent rights to the invention in your prototype, and the leverage to complicate your next funding round or acquisition.
This is one of the most expensive paperwork gaps a young company can carry. The fix is simple, cheap, and best done before work starts: a written IP assignment from every developer, designer, and freelancer who touches your product.
The Default Rule: The Creator Owns It, Not the Payer
Payment is not a transfer. Ownership starts with the human creator and moves only by a signed writing.
That principle plays out differently across each type of intellectual property:
Copyright: code, designs, copy, photos, video
Copyright vests in the author the moment an original work is fixed in a tangible form — when code is saved, copy is written down, or a design is exported. For employees creating work within the scope of employment, the employer is treated as the author under the work-made-for-hire rule.
For independent contractors, the opposite is true. The contractor is the author and owner unless ownership is transferred in writing. Your invoice proves you paid for the work. It does not prove you own the copyright.
What this covers for a typical startup: application source code, website templates, UI/UX mockups, logos and brand illustrations, marketing copy, blog posts, product photography, training videos, and documentation.
Patents: inventions and technical improvements
Patent rights initially vest in the human inventor — the person who conceived the invention — not the company that funded the work. An employer or client has no automatic claim without an express assignment.
This matters when a contractor improves your algorithm, designs a novel mechanical feature, or solves a technical problem in a patentable way during the engagement. Without an assignment, the inventor can file, license, or withhold the invention even though your money paid for the lab time.
Trademarks: names, logos, slogans
Trademark rights come from using a mark in commerce to identify your goods or services, not from drawing the logo. But copyright and trademark overlap on brand assets: your designer owns the copyright in the logo artwork until they assign it, while you build trademark rights by using that logo with customers.
If the copyright assignment is missing, you can end up in the awkward position of owning trademark goodwill in a logo whose underlying artwork you do not fully control.
Trade secrets: formulas, customer lists, processes
Trade secret protection depends on reasonable secrecy measures, including written confidentiality obligations. A contractor without a confidentiality agreement is under no automatic duty to keep your roadmap, pricing model, or customer data private.
Why "Work for Hire" Language Alone Will Not Save You
Many contractor templates say the work is "work made for hire" and stop there. That clause, standing alone, usually fails for contractors — especially for software.
Under Section 101 of the Copyright Act, a contractor's work qualifies as work made for hire only if three conditions are all met:
- The work was specially ordered or commissioned.
- Both parties sign a written agreement stating the work is made for hire.
- The work falls into one of nine narrow statutory categories: a contribution to a collective work, part of a motion picture or audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas.
Most startup deliverables do not fit. Custom software code, for example, is generally not in any of those nine categories. A website, a mobile app, or a backend API labeled "work for hire" without more is still owned by the contractor who wrote it.
The fix is a belt-and-suspenders clause: state that the work is made for hire to the extent the law allows, and then add a present-tense backup assignment — "to the extent any work is not deemed work made for hire, Contractor hereby assigns all right, title, and interest to the Company." That second sentence does the real work.
What a Solid Contractor IP Assignment Needs
You do not need a 40-page agreement for every small engagement. You do need these seven elements in writing, signed before work begins:
1. Present-tense assignment, not a promise to assign
Wording decides who holds title. "Contractor agrees to assign" is a promise to transfer rights in the future. "Contractor hereby assigns" is a present transfer of rights, including rights in future work created under the agreement.
Federal courts have repeatedly treated the first as an obligation and the second as an actual conveyance — and investors' counsel will flag the difference in diligence. Use "hereby assigns" and add an obligation to sign any further documents needed to perfect the transfer, such as patent assignments or copyright transfer records.
2. A broad definition of covered work
Define "Work Product" to cover everything the contractor creates, conceives, reduces to practice, or delivers in connection with the engagement: code, documentation, designs, inventions, data, models, prompts and outputs where applicable, and all intellectual property rights in each — copyrights, patent rights, trademark rights, trade secrets, and moral rights to the extent waivable.
Tie coverage to the scope of the engagement, not just to final deliverables. Drafts, prototypes, notebooks, and discarded approaches should be included.
3. Pre-existing IP carve-out with a license back
Contractors often bring their own libraries, templates, or tools. Ask for a short list of pre-existing materials excluded from the assignment, and require a perpetual, royalty-free license to use anything from that list that ends up embedded in your deliverables. Without that license, a contractor's reusable component can become a hold-up right inside your product.
4. Waiver of moral rights and attribution claims
In the U.S., moral rights are narrow, but foreign contractors may hold broader attribution and integrity rights under local law. Include a waiver to the extent permitted by applicable law, plus consent to use the work without attribution and to make modifications.
5. Confidentiality and non-disclosure
Prohibit the contractor from disclosing your confidential information and from using it for anyone else's benefit. Define confidential information broadly, set a survival period of several years (with trade secrets protected indefinitely), and require return or deletion of materials at the end of the engagement.
6. Further assurances and power of attorney
Require the contractor to sign patent applications, copyright registrations, oaths, and transfer documents on request, at your expense. Add a limited power of attorney allowing you to sign on their behalf if they become unavailable or uncooperative — a clause that pays for itself when a former contractor has moved on and a patent filing has a deadline.
7. Representations about originality and third-party rights
Have the contractor represent that the work is original, does not infringe third-party rights, does not violate any prior agreement (such as a non-compete or a university IP policy), and does not incorporate restrictive open-source code without your written approval. Pair it with an obligation to disclose any third-party components before incorporating them.
Three Gaps That Surprise Even Careful Founders
Founders' own pre-incorporation work
The contractor rule applies to you, too. Code, designs, or inventions created before the company was formed belong to the individual founders until each founder signs a written assignment transferring that work to the company. Every funding diligence checklist asks for these founder assignments. Get them signed at incorporation, not the week before a term sheet.
Open-source contamination
A contractor who copies restrictive licensed code into your proprietary codebase can impose license obligations on your whole product — including requirements to disclose source code. Your agreement should require prior written approval before incorporating any third-party or open-source code, require a bill of materials listing every dependency and its license, and represent that no copyleft code was included without disclosure.
Track that inventory the same way you track expenses: as a standing schedule to the agreement, updated with each milestone.
AI-assisted output and foreign contractors
Generative-AI tools add a new wrinkle: purely machine-generated output may lack copyright protection at all, and tool terms may grant the tool provider broad rights in inputs. Require contractors to disclose material AI-tool use, to avoid feeding your confidential code or data into tools that retain training rights without approval, and to stand behind the originality representation for AI-assisted deliverables.
For contractors outside the U.S., local law may restrict assignment of future inventions, require additional compensation for patent assignments, or preserve unwaivable moral rights. Have local counsel review the template for each country where you regularly hire, rather than assuming a U.S. form travels intact.
What Investors and Acquirers Actually Check
When an investor or acquirer reviews your company, intellectual property diligence almost always asks the same questions:
- Can you produce a signed invention-assignment agreement for every founder, employee, advisor, and contractor who contributed to the product?
- Is there an unbroken, recorded chain of title from each inventor to the company for every patent application?
- Are copyright registrations (if any) in the company's name, with written transfers from non-employee authors?
- Did any contributor develop IP before joining, at a university, or under another employer's agreement that could claim it?
- Are confidentiality agreements in place covering everyone with access to trade secrets?
- Is third-party and open-source code inventoried with compatible licenses?
A single missing contractor assignment rarely kills a deal outright, but it costs time and leverage. The typical cure is a frantic search for a former freelancer to sign a confirmatory assignment — sometimes years later, after a falling-out, a move abroad, or a competing claim. Verbal assurances and old email threads do not satisfy the written-assignment requirement, and every missing signature becomes a negotiating discount.
Keep an IP file from day one: each contributor's signed agreement, the scope of work, payment records showing consideration, and a list of deliverables. Diligence goes quickly when the file is complete; it stalls for weeks when it is not.
A Practical Playbook: From Template to Clean IP File
Before any work starts
Use one standard contractor agreement for every engagement, with the IP assignment and confidentiality terms built in — not as an optional exhibit. Require signature before repository access, design-file sharing, or the kickoff call. Oral start dates with paperwork "to follow" are how gaps are born.
Classify the worker correctly as well. Misclassifying an employee as a contractor creates tax and benefits exposure that no IP clause fixes. If the person works full-time on your roadmap, under your direction, with your equipment, get employment counsel involved.
At each milestone
Collect the deliverables, the dependency and third-party-code list, and confirmation that no new pre-existing materials were embedded without approval. File invoices alongside the agreement they were paid under. Your accounting records are part of your IP proof: they show who was paid, for what scope, and when — which is why contractor payments should be booked to the project or vendor they belong to, not lumped into generic expense lines.
If you track finances in Beancount.io, tag contractor postings by vendor and project so each payment maps to its statement of work. The docs show how to structure accounts and tags for project-level tracking, and the Fava dashboard makes it easy to pull a per-contractor payment history when diligence asks for it.
When you find a gap
Do not rewrite history. Use a short confirmatory assignment that references the original engagement dates, describes the work product, assigns it retroactively with present-tense language, and recites the consideration already paid. Get it signed promptly, while the relationship is still cooperative. For founders, sign pre-incorporation assignments even if everyone "already agreed" — memories fade, cap tables change, and diligence requires paper.
Record patent assignments with the patent office and keep copies of copyright transfer records. Calendar renewal and maintenance deadlines so registered rights do not lapse for administrative reasons.
Simplify Your Financial Management
Getting IP ownership right is ultimately a records discipline — signed agreements, scoped payments, and a complete paper trail from contributor to company. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data, so contractor costs, project budgets, and diligence-ready histories stay version-controlled and auditable. Get started for free and keep every dollar of product investment traceable to the work it paid for.