When a startup raises its first funding round, investors and their lawyers will review who actually owns the company’s intellectual property. If a founder wrote code before the company was incorporated, or if a contractor built a core feature without a written agreement, that IP may not legally belong to the company. Fixing the problem after a term sheet is on the table is expensive, time-consuming, and sometimes a deal-breaker.
The IP assignment agreement is the document that transfers ownership of intellectual property to your company. Without it, the default rules under US copyright and patent law leave ownership with the individual who created the work, which is almost never what founders intend when they build a product together or hire developers to build it for them.
This article explains what an IP assignment agreement covers, when you need one, who needs to sign it, and what missing or defective agreements cost you when it matters most.
1. Why the Default IP Rules Work Against Startups
Under US copyright law (17 U.S.C. § 102), the author of an original work owns the copyright the moment the work is created. For employees, the work-made-for-hire doctrine (17 U.S.C. § 101) assigns copyright to the employer automatically. But this doctrine has two conditions that create serious risk for startups.
First, the work-made-for-hire doctrine only applies automatically to employees, not independent contractors. A contractor who writes your codebase, designs your product architecture, or develops your proprietary algorithm owns that work by default under federal copyright law. Paying the invoice does not transfer the copyright. Only a written assignment agreement does.
Second, the work-made-for-hire doctrine only applies to work created within the scope of employment. A founder who wrote code nights and weekends before the company existed was not an employee of the company because the company did not yet exist. That pre-incorporation work belongs to the founder individually, not to the entity that was later formed. Without a written assignment agreement signed by the founder, the company may be building its entire product on IP it does not legally own.
Patent ownership has the same structure. Under 35 U.S.C. § 262, co-inventors each have an equal undivided interest in a jointly invented patent and can license it independently without the other inventors’ consent. A startup with multiple technical co-founders who have not executed an IP assignment agreement can find itself in a position where a departing co-founder retains the ability to license the core technology to a competitor.
2. What an IP Assignment Agreement Actually Transfers
An IP assignment agreement transfers ownership of intellectual property from the assignor (the founder, employee, or contractor) to the assignee (the company). The scope of what it transfers is the most important drafting decision in the agreement.
Current IP
The agreement should assign all existing IP related to the company’s business: source code, software, algorithms, databases, written content, design assets, trade secrets, and any patent applications or patents. For founders, this includes everything created before the company was incorporated if it is relevant to the company’s current or planned products.
Future IP
The agreement should also assign future IP created in connection with the company’s business during the term of the founder’s involvement or the contractor’s engagement. This prospective assignment prevents the same ownership gap from recurring every time something new is built. Courts have upheld prospective IP assignments in employment and contractor agreements as long as the obligation is clearly stated.
Moral Rights and Waiver
Under the Visual Artists Rights Act (17 U.S.C. § 106A), authors of certain visual works retain moral rights even after assignment. For most software and commercial work products, this is not an issue, but if your company works with visual artists or creators, the agreement should include a waiver of moral rights to the extent permitted by law.
3. Founder IP Assignment: What to Do at Incorporation
The right time to execute founder IP assignment agreements is at or immediately after incorporation. If your company is already operating without them, the risk does not disappear — it compounds as more pre-incorporation work gets incorporated into the product and more value is built on top of a potentially unassigned foundation.
Every person who contributed to the product before incorporation needs to sign an IP assignment agreement. This includes co-founders who are not active in the business, technical advisors who wrote early code, and anyone else who created anything that became part of what the company now does.
Carve-outs for Personal IP
Founders sometimes resist broad IP assignments because they have pre-existing projects, tools, or code they do not want to transfer to the company. This is a legitimate concern that good IP assignment agreements address through a carve-out schedule. The agreement assigns all company-related IP to the company and separately lists pre-existing personal IP that the founder retains. Both sides sign off on exactly what is inside and outside the assignment. This is better than a vague agreement or no agreement at all, because it creates a documented record of the scope at the time of signing.
Consideration for Founder Assignments
A contract needs consideration to be enforceable. For founder IP assignment agreements, the consideration is typically the founder’s equity in the company and any salary or compensation. The agreement should state this explicitly. An IP assignment agreement with no consideration is vulnerable to challenge, particularly from a departing founder who later wants to claim ownership of the original IP.
4. Contractor IP Assignment: The Biggest Gap Most Startups Miss
Most startups that engage contractors assume they own whatever was built. They do not, unless a written IP assignment agreement was signed before the work began. This is not a technicality. It is the default rule under federal copyright law, and it applies regardless of how much you paid or what your invoice said.
Software code does not qualify as a work made for hire for contractors under 17 U.S.C. § 101, even if you and the contractor agreed to call it that in your contract. The work-made-for-hire doctrine for independent contractors only applies to a specific, closed list of categories: contributions to collective works, parts of a motion picture, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases. Software is not on that list. Calling it a work for hire in your contract does not make it one.
The only reliable way to own code written by a contractor is an explicit copyright assignment in a written agreement signed by the contractor. Every contractor engagement should include an IP assignment clause before any work begins. This applies to offshore development firms, freelancers on platforms like Upwork, agencies, and individual developers.
What a Contractor IP Assignment Must Include
The assignment clause should transfer all IP created in connection with the engagement to the company, confirm the contractor retains no residual rights to the work product, require the contractor to sign any additional documents needed to perfect the assignment (for example, patent assignments with the USPTO), and include a representation that the contractor owns what they are assigning and that it does not infringe third-party IP. That last point matters because a contractor who uses open-source code with restrictive licensing in your product transfers a legal problem along with the code.
5. Cooperation Obligations and Survival
An IP assignment agreement is not a one-time event. The company will need ongoing cooperation from the assignor to enforce and perfect the assigned rights. Patent prosecution requires inventors to provide declarations and cooperate with the patent office. Copyright registration may require the original author’s involvement. Litigation over assigned IP requires the assignor’s testimony.
Your IP assignment agreement should include a cooperation clause requiring the assignor to execute additional documents, provide testimony, and assist with IP-related proceedings as needed, at the company’s expense. This obligation should survive the termination of the founder’s role, the employee’s employment, or the contractor’s engagement. Without a survival clause, a departing co-founder has no contractual obligation to cooperate with patent prosecution years later, even though the patent covers technology they created.
6. What Investors and Acquirers Look For
During due diligence for a funding round or acquisition, a buyer’s legal team will request copies of IP assignment agreements from every founder, key employee, and significant contractor. They are looking for three things: complete coverage (everyone who created something for the company has signed), no gaps in the chain of title (the company can demonstrate an unbroken transfer of ownership from creator to company), and no problematic carve-outs or retained rights that would limit the company’s ability to commercialize the IP.
Gaps discovered during due diligence can be fixed, but fixing them takes time and money, may require tracking down former contractors or co-founders who are no longer cooperative, and can create leverage for a price adjustment in an acquisition or conditions in a financing. The cost of getting IP assignments executed properly at the start of the engagement is a fraction of the cost of cleaning up a messy chain of title later.
Technology law practices that work specifically with startups understand what investors scrutinize in IP chain-of-title reviews. A technology lawyer who has seen how due diligence unfolds will draft IP assignment agreements that pass that scrutiny. For startup founders reviewing their overall contract infrastructure, working with an experienced contract attorney covers the broader framework of agreements that protect your business.
7. Common Mistakes That Create Unfixable Problems
Signing after the work is done. An IP assignment signed after the work was completed assigns whatever rights the contractor had at that moment, but it does not retroactively create a work-made-for-hire relationship or cure the gap in ownership between when the work was created and when the assignment was signed. A contractor who signed the assignment two years after building your core product had two years in which they could have claimed ownership, licensed the work to a third party, or created legal complications. Always sign before the work begins.
No assignment from co-founders who left early. A co-founder who left before the company raised money or signed a proper IP assignment is now a third party. If they contributed to the product, they may have retained IP rights they are not aware of. Reaching out years later to obtain an assignment is harder, and sometimes impossible if the person cannot be located or is unwilling to sign.
Relying on oral agreements or statements of intent. The Copyright Act (17 U.S.C. § 204(a)) requires a copyright assignment to be in a signed writing to be valid. An email, a Slack message, or a handshake deal does not transfer copyright ownership regardless of what was agreed.
Using templates not drafted for technology companies. Generic assignment agreements often fail to address software-specific issues: open-source license conflicts, moral rights in visual assets, data rights, and the specific cooperation obligations needed for software patent prosecution. An agreement that works for a design firm or a marketing consultant may leave critical gaps when used for a software startup.
Frequently Asked Questions
Does paying a contractor for their work give my company ownership of what they created?
No. Under US copyright law, paying a contractor does not transfer copyright ownership. Payment gives you the right to use the work product under whatever agreement you have, but ownership stays with the contractor unless a written assignment is signed. For software specifically, the work-made-for-hire exception does not apply to independent contractors, so the only way to own the code is a written assignment agreement.
When does a startup need to execute IP assignment agreements?
Immediately: at or before incorporation for founders, and before any work begins for each contractor and employee. If your company is already operating without them, getting them signed now is better than waiting. The longer you wait, the harder it becomes to track down former contributors, and the larger the gap in chain of title becomes.
Can a co-founder refuse to sign an IP assignment agreement?
Yes, technically. A co-founder cannot be forced to sign. This is why IP assignment should be addressed before the company is formed and before the founder receives equity. If a co-founder receives equity in exchange for joining the company, the IP assignment is part of the deal that justifies the equity grant. A co-founder who refuses to assign the IP they created is retaining company value they have been compensated for, which is the kind of dispute that ends companies early.
What happens to IP created by an employee who leaves?
IP created by an employee within the scope of their employment belongs to the employer under the work-made-for-hire doctrine. The departure of the employee does not affect this ownership. However, IP the employee created outside their scope of employment, or on their own time with their own tools, may not be assigned. Most technology employment agreements include IP assignment clauses that clarify this, requiring employees to assign all IP created in connection with the company’s business regardless of when or where it was created.
Does an NDA also cover IP assignment?
No. A non-disclosure agreement protects confidential information from disclosure. It does not transfer IP ownership. An NDA and an IP assignment agreement serve different legal functions and both are needed in most contractor and founder relationships. Some combined agreements address both, but they need to include explicit assignment language to do so.
Get Your IP Chain of Title Right Before It Costs You a Deal
Defective IP chain of title is one of the most common and most expensive legal problems discovered during startup due diligence. The fix is straightforward when addressed early: a properly drafted IP assignment agreement signed by each founder, employee, and contractor before they contribute to your product. Addressed late, it becomes a negotiation with people who no longer have the same interests as the company.
If you are a founder building a product, closing a funding round, or preparing for acquisition and you are not certain your IP is cleanly assigned, contact Hansen Tong at TOSLawyer.com. Our intellectual property practice works specifically with technology companies and startups on IP ownership, licensing, and the contract infrastructure that protects your most valuable assets.