IP Assignment Agreements: Issues For SaaS Companies

What Is an IP Assignment Agreement?

An IP assignment agreement is a contract that transfers ownership of intellectual property (IP) from one person or entity to another. For SaaS (Software as a Service) companies, these agreements are critical to ensure the business truly owns the software, trademarks, branding, and other creative assets that drive its value.

Without clear IP assignment agreements, founders, employees, contractors, or third parties might retain rights to code, logos, or technology. This can create serious risks if you want to raise capital, sell your company, or prevent others from using your IP.

In the United States, federal law governs many aspects of IP, such as patents, copyrights, and trademarks. However, state contract law often determines how assignment agreements are interpreted and enforced. This means both federal and state rules can impact your IP assignment strategy.

• Patents: Assignments must be in writing and should be recorded with the USPTO to be effective against third parties.
• Copyrights: Assignments must be in writing and signed by the assignor. Recording with the US Copyright Office is recommended for added protection.
• Trademarks: Assignments must include the goodwill of the business. Recording with the USPTO is recommended for public notice and priority.

For SaaS companies, IP assignment agreements typically cover software code, product names, logos, domain names, databases, and any other creative assets or inventions that are central to the business.

It is important to note that the default legal position in the US is that the creator of an IP asset owns it unless there is a written agreement stating otherwise. This is why a handshake or verbal promise is not enough to transfer IP rights.

Why Are IP Assignment Agreements Critical for SaaS Companies?

SaaS companies rely on their technology, codebase, and branding as their core value proposition. If you do not have clear ownership of your software, trademarks, or other IP, you risk:

• Disputes with founders, employees, or contractors over who owns the code, branding, or technology
• Problems when seeking investment, securing loans, or selling the business
• Difficulty enforcing your rights against competitors or copycats
• Potential loss of key assets if someone leaves the company or is terminated
• Challenges if a third party claims ownership or prior rights

Investors and acquirers will almost always review your IP assignment agreements during due diligence. If there are gaps or missing assignments, it can delay or derail deals, or reduce your company valuation.

Consider these common scenarios where SaaS companies need IP assignments:

• Founders: When several founders start a SaaS company, each may contribute existing code, technology, or branding. A written assignment ensures the company owns these assets, not the individual founders.
• Employees: Employees who develop software, create documentation, or design branding may own the IP by default unless there is a written assignment. This is especially true for work created outside normal job duties.
• Contractors and Freelancers: Contractors do not automatically assign IP to your company. You must have a written agreement that clearly transfers ownership of all deliverables.
• Acquisitions: If your company acquires another business, a product, or technology, you need assignment agreements to transfer all relevant IP rights.

For example, if a SaaS company hires a developer as a contractor to build a new feature, and the contract does not address IP assignment, the contractor may legally own the code. This can become a major problem if the contractor later refuses to transfer the rights, or demands additional compensation.

Key Issues and Common Mistakes in IP Assignment Agreements

Not all IP assignment agreements are created equal. SaaS companies should pay close attention to these issues and avoid common mistakes:

• Scope of Assignment: The agreement should cover all relevant IP, including software, source code, documentation, trademarks, domain names, databases, and any related assets. Be specific and attach schedules or lists if needed.
• Timing: Make sure the assignment is effective immediately, unless there is a clear reason to delay. Avoid language that makes the assignment conditional or ambiguous.
• Prior Works: If the assignor created IP before joining the company, the agreement should explicitly cover these prior works. This is common for founders contributing existing code or technology.
• Moral Rights: In some cases, creators retain "moral rights" that allow them to object to certain uses of their work. Include a waiver of moral rights if possible, especially for creative works like graphics or documentation.
• Further Assurances: The assignor should promise to assist with future filings, enforcement, or paperwork needed to perfect the assignment.
• Governing Law: Specify which state law applies to the agreement and where disputes will be resolved. This is especially important if you have remote employees or contractors in different states.
• Consideration: Make sure there is clear value exchanged for the assignment, such as salary, equity, or a specific payment. Lack of consideration can make the agreement unenforceable in some states.

Common mistakes include:

• Using vague or future-tense language like "will assign" instead of "hereby assigns," which can make the assignment ineffective.
• Failing to cover all types of IP, such as forgetting to include domain names or databases.
• Not addressing IP created before the person joined the company.
• Not obtaining signatures from all parties.
• Relying on templates that do not comply with state-specific requirements.

For SaaS companies, it is especially important to ensure that all software code, libraries, and related documentation are covered by the assignment. If you use open source code, check that your assignment does not conflict with open source licenses or obligations.

Some states, such as California, restrict the ability of employers to claim ownership of inventions created entirely on an employee's own time without using company resources. Always review state-specific rules before finalizing your agreement.

How to Structure IP Assignment Agreements for SaaS Companies

Effective IP assignment agreements for SaaS companies should include the following elements:

1. Clear Identification of Parties: Name the assignor (the person or entity transferring IP) and the assignee (the company receiving IP).
2. Description of Assigned IP: Be specific about what is being transferred. Attach schedules or exhibits listing software, trademarks, databases, or other assets if needed.
3. Assignment Language: Use clear, present-tense language such as "hereby assigns" to avoid ambiguity.
4. Consideration: State what the assignor is receiving in exchange (salary, equity, or other compensation).
5. Further Assurances: Require the assignor to assist with future filings, enforcement actions, or paperwork.
6. Governing Law and Jurisdiction: Specify which state law applies and where disputes will be resolved.
7. Signatures: Both parties should sign and date the agreement.
8. Warranties: The assignor should warrant that they have the right to assign the IP and that it does not infringe on anyone else's rights.
9. Moral Rights Waiver: Where applicable, include a waiver of moral rights to prevent future disputes over how the work is used or modified.

For employees and contractors, consider including IP assignment language in your employment agreements or contractor agreements. For founders, a separate assignment agreement is often used when the company is formed, especially if founders are contributing existing code or branding.

It is also good practice to keep a checklist of all IP assets and make sure each one is covered by an assignment agreement. This can include:

• Source code and software libraries
• Product names, logos, and trademarks
• Domain names and website content
• Databases and data sets
• Designs, graphics, and documentation
• Business processes or inventions

Example: A SaaS company is building a customer relationship management (CRM) platform. The founders contribute an early prototype, a contractor designs the logo, and an employee builds a new analytics feature. Each of these contributions should be covered by a written IP assignment agreement to ensure the company owns the entire platform and branding.

Federal and State Law Caveats for IP Assignments

Federal law sets the baseline for patents, copyrights, and trademarks, but state contract law often determines how assignment agreements are enforced. Here are some important caveats to consider:

• Patents: The US Patent and Trademark Office (USPTO) requires assignments to be in writing and recommends recording them. If you do not record the assignment, a later purchaser may take priority. See USPTO trademark basics for details.
• Copyrights: The US Copyright Office requires a written, signed assignment. Recording is optional but can provide extra protection against third-party claims. See US Copyright Office circulars for more information.
• Trademarks: Assignments must include the associated goodwill. State trademark laws may impose additional requirements, such as specific language or filing procedures. Check your state's trademark office for details.

Some states, such as California, have laws that limit an employer's ability to claim inventions developed entirely on an employee's own time without company resources. For example, under California Labor Code Section 2870, an employer cannot require an employee to assign inventions developed entirely on their own time without using company equipment, supplies, or trade secrets, unless the invention relates to the employer's business or anticipated research.

Other states, such as Illinois or Massachusetts, have similar statutes. If you have remote employees or contractors in different states, you may need to tailor your agreements to comply with each state's rules.

Some states also require that employees be given notice of assignment provisions in writing, and may require a separate signature or acknowledgment. Failing to comply with these requirements can make your assignment unenforceable.

For more on protecting your business's IP, see our guide to Intellectual Property.

Checklist: Best Practices for SaaS IP Assignment Agreements

• Identify all founders, employees, contractors, and third parties who have contributed IP to your business.
• Prepare a written IP assignment agreement for each contributor, covering all relevant IP assets.
• Use clear, present-tense assignment language ("hereby assigns").
• List all assets being assigned, including code, branding, domains, and data.
• Include a waiver of moral rights, if applicable.
• Specify governing law and jurisdiction, considering where your contributors are located.
• Ensure there is valid consideration (salary, equity, or payment).
• Obtain signatures from all parties and keep signed copies on file.
• Record assignments with the USPTO or US Copyright Office where appropriate.
• Review state-specific rules for employee and contractor assignments.

Regularly review your IP assignment agreements as your business grows, especially if you expand into new states or bring on new contributors.

FAQs

What happens if I do not have an IP assignment agreement?

If you do not have a signed IP assignment agreement, the person who created the software, logo, or other IP may retain ownership. This can cause problems if they leave the company, join a competitor, or dispute your right to use or sell the IP. It can also make it harder to raise investment or sell your business. In some cases, you may have to negotiate a new assignment, which can be costly and time-consuming.

Can I assign IP created before I joined the company?

Yes, but the agreement must clearly state that it covers prior works. This is common when founders contribute existing code or technology. Be specific about what is being assigned and ensure that the assignor has the right to transfer it. If the IP was created with another employer or partner, there may be restrictions or third-party rights to consider.

Do I need to record my IP assignment with the USPTO or Copyright Office?

Recording is not always required, but it is recommended. Recording an assignment with the USPTO or US Copyright Office provides public notice and can protect you against later claims by third parties. For patents and trademarks, recording is especially important. For copyrights, it is optional but helpful, especially if you plan to enforce your rights in court.

Are there special rules for assigning IP from employees or contractors?

Yes. Employees may be required to assign IP created within the scope of their employment, but state laws can affect this. For example, California and some other states limit the employer's rights over inventions developed on the employee's own time. Contractors do not automatically assign IP unless it is in the contract. Always include clear assignment language in your agreements with both employees and contractors, and check for any state-specific requirements.

Can I use a template IP assignment agreement?

Templates can be a starting point, but they may not address your specific business needs or state law requirements. It is wise to have your agreements reviewed by a qualified attorney, especially if your company operates in multiple states or handles sensitive technology. Relying solely on a generic template can lead to gaps or unenforceable provisions.

Key Takeaways

• IP assignment agreements are essential for SaaS companies to secure ownership of software, trademarks, and other key assets.
• Federal law sets the baseline, but state contract law and specific industry rules can affect how assignments work and are enforced.
• Be specific about what is being assigned, when the assignment takes effect, and what consideration is provided.
• Include assignment language in employment, contractor, and founder agreements as needed, and tailor for state-specific rules.
• Recording assignments with the USPTO or Copyright Office is recommended for extra protection.
• Review both federal and state rules, and seek legal advice if you have questions about your situation.
• Common mistakes include vague language, missing assets, lack of signatures, and ignoring state law requirements.

If you need help drafting or reviewing IP assignment agreements for your SaaS company, contact our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they are delivered by licensed lawyers at trusted US law firms through the Sprintlaw platform.