Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.
Maya runs a growing skincare brand. She hires a designer to create new packaging, a developer to build her online store, and a marketing agency to produce product photos and ad copy.
A few months later, she asks for the editable design files and website source files so her team can make updates. The designer says those files were never included. The developer says the underlying code library belongs to them. The agency wants to showcase the campaign publicly, even though Maya hasn't launched the products yet.
This is exactly where IP ownership clauses in business contracts matter. They help decide who owns the work, who can use it, who can edit it, and what happens to materials that existed before the project started.
The good news is that this doesn't have to be complicated. You just need the contract to say the things that people often assume are obvious.
What Is An IP Ownership Clause?
An IP ownership clause is the part of your contract that says who owns intellectual property created, supplied or used during the relationship.
In a business contract, IP can include:
- logos, brand names, taglines and packaging designs
- website designs, software code, databases and app features
- photos, videos, copy, graphics, music and marketing assets
- product designs, inventions, technical documents and processes
- trade secrets, know-how, source files, templates and internal systems
For many businesses, the finished deliverable is only part of the story. You may also need the editable source files, admin access, account credentials, design systems, development files, raw footage or rights to modify the work later.
A good clause usually deals with three buckets:
- New IP: work created specifically for your business under the contract.
- Pre-existing IP: tools, templates, code, methods or materials a contractor already had before working with you.
- Third-party IP: stock images, fonts, plugins, open source code or licensed content that someone else owns.
If your contract doesn't separate these clearly, you can end up paying for a project but not getting the rights you need to use it confidently.
Do You Automatically Own Work You Pay A Contractor To Create?
No, you don't automatically own all IP just because you paid a contractor, agency or developer to create it.
Under the Copyright Act, copyright generally belongs to the person who creates the original work, unless an exception applies or there's a written transfer. That means a freelance designer may own the copyright in a logo design, a photographer may own the copyright in photos, and a developer may own copyright in parts of the code they wrote, unless your contract says otherwise.
The phrase work made for hire is often misunderstood. For employees, copyright in work created within the scope of employment is usually owned by the employer. For independent contractors, work made for hire only applies if:
- there's a written agreement saying the work is a work made for hire; and
- the work fits into one of the specific categories under the Copyright Act.
Many common business projects, including custom software, websites, logos and marketing materials, don't always fit neatly into those categories. That's why a contractor agreement or work for hire agreement should usually include a clear IP assignment as well as any work made for hire wording.
An assignment means the contractor transfers their rights to your business. Copyright assignments need to be in writing and signed by the owner of the rights. For inventions and patentable work, the inventor usually owns the invention at first, so you also want a written invention assignment. For trademarks, ownership is tied closely to business use and goodwill, and assignments should transfer the associated goodwill too.
Payment still matters. Some contracts say IP transfers when the work is created. Others say it transfers only once you've paid in full. Both approaches can be workable, but they create different leverage if there's a dispute about invoices or quality.
What Should Your Clause Say About Deliverables And Source Files?
Your clause should say exactly what the contractor must give you, what rights transfer to your business, and when that transfer happens.
For creative, tech and marketing projects, be specific about deliverables in the statement of work. A vague phrase like all project materials may not be enough if you later need editable files or backend access.
You may want the contract to cover:
- final files in the formats you need
- editable source files, such as design files, layered artwork or code repositories
- raw footage, unedited images or working documents
- domain names, hosting access and admin credentials
- documentation, build instructions and handover notes
- test environments, staging sites and databases
- social media, ad platform or analytics account access
If source files are valuable to your business, don't leave them to assumption. Some agencies price projects on the basis that you receive final outputs only, and source files cost extra. That's not necessarily unfair, but it should be clear before the work starts.
Example: Website Build
Say you hire a developer to build a custom booking platform for your fitness studio. You receive a working website, but your contract doesn't mention the code repository, plugins, design system or deployment process.
Six months later, you want another developer to add features. Without source code access and a license to use any underlying developer tools, the handover may be slow, expensive or impossible.
A better contract would state that your business owns the custom code and project-specific deliverables, receives access to the repository, and has a license to use any pre-existing modules that are needed for the platform to keep running.
Can A Contractor Keep Pre-Existing Materials And Tools?
Yes, a contractor can usually keep ownership of their pre-existing materials and tools, but your business should receive the rights it needs to use the final work.
This is a normal part of many projects. A developer may use their own code libraries. A marketing agency may use its internal templates and campaign frameworks. A consultant may use its existing methodology. You usually don't need to own all of that background material.
What you do need is a clear license. The license should say whether your business can use, copy, modify, maintain and sublicense the pre-existing materials as part of the deliverables.
For key business assets, you may want the license to be:
- perpetual: it doesn't expire after the project ends
- irrevocable: it can't be withdrawn if you're complying with the contract
- worldwide: you can use it across markets
- royalty-free: you don't owe ongoing fees beyond the agreed price
- transferable or sublicensable: you can allow your group companies, buyers, service providers or future developers to use it where needed
Third-party materials need separate attention in contract drafting. If your project includes stock photos, fonts, plugins, commercial code or open source software, your contract should require the contractor to identify those items and confirm the license terms.
Open source software can be especially sensitive for software businesses. Some licenses are very permissive. Others may require notices, source code disclosure or specific license terms for derivative works. If your product will be sold, funded or acquired, open source review can become a serious diligence item.
Can An Agency Use Your Project In Its Portfolio?
It depends on what your contract says, and you can set boundaries around timing, confidentiality and how your brand is presented.
Agencies, designers and developers often want portfolio rights because your project helps them market their services. That can be fine, especially once the project is public. But there are times when portfolio use can cause problems for your business.
For example, you may not want an agency to:
- publish screenshots before your product launch
- share confidential product strategy, sales numbers or customer information
- imply that you endorse the agency
- use your trademarks in paid ads without approval
- show work that includes unreleased designs or trade secrets
A practical portfolio clause might allow the agency to show non-confidential examples of the completed work after public launch, provided it gets your written approval first and doesn't suggest sponsorship or endorsement.
This also connects to trademark law. Under the Lanham Act, trademarks help identify the source of goods or services and protect against consumer confusion. If another business uses your name or logo in a way that makes people think you endorse them, partner with them or approved their marketing, that can create risk.
For confidential material, your contract should also include a confidentiality clause. Trade secrets can be protected under the federal Defend Trade Secrets Act, but only if you take reasonable measures to keep the information secret. A clear contract, limited access and careful handling of sensitive files all help.
How Do IP Clauses Work For Employees And Founders?
Employees and founders need IP clauses too, even though the rules can be different from contractor projects.
For employees, copyright created within the scope of employment is generally owned by the employer under the work made for hire rule. But you still shouldn't rely on that alone. An employment agreement or inventions agreement can help cover inventions, patent rights, confidential information, moral rights consents where allowed, and work created using your systems or resources.
State law can limit how far invention assignment clauses can go, especially for work created on an employee's own time without using company resources and unrelated to your business. The exact position depends on your state, so get tailored advice before using a broad employee invention clause.
Founder IP is another common gap. If you built your product, brand or first prototype before forming your company, the company may not automatically own those assets without a written assignment. Investors, buyers and major customers often expect the company to own or control the IP it depends on.
To clean this up, you may need founder IP assignments covering things like:
- software code and technical documents
- brand names, logos and domain names
- product designs, content and databases
- business plans, customer lists and confidential know-how
- inventions and patentable improvements
If you plan to register a trademark with the USPTO, make sure the applicant is the correct owner. If your company is using the brand in commerce, filing in an individual's name by mistake can create avoidable cleanup work later. For copyright, registration with the Copyright Office isn't required for copyright to exist, but registration can be needed before suing for infringement of a US work and can affect available remedies if done on time.
Documents And Wording To Get Right
The right document depends on who you're hiring and what they're creating, but the aim is the same: make ownership and usage rights clear before the work starts.
Common documents include:
- Independent contractor agreement: useful when an individual freelancer is creating designs, code, copy, photos or other work for your business.
- Master services agreement and statement of work: useful for agencies, developers and ongoing service providers where each project has its own scope and deliverables.
- Software development agreement: useful for apps, platforms, integrations, APIs, source code and technical handover.
- Employment agreement or inventions agreement: useful for employees creating IP as part of their role.
- Founder IP assignment: useful when founders created business assets before or around company formation.
- NDA or confidentiality agreement: useful before sharing sensitive plans, customer lists, code, formulas or commercial information.
When reviewing the wording, look for these points:
- Does the contract define the deliverables clearly?
- Does it say whether IP is assigned to your business or only licensed?
- Does the transfer happen on creation, delivery or full payment?
- Are source files, credentials and admin access included?
- Are pre-existing materials carved out and licensed back to you?
- Are third-party materials identified, with license terms disclosed?
- Can the contractor use your name, logo or project in a portfolio?
- Does confidentiality continue after the project ends?
- Does the contractor promise not to infringe someone else's IP?
- Is there a practical handover process when the contract ends?
Templates can be a helpful starting point, but IP clauses often need tailoring and contract review. A clause that works for a one-off photo shoot may not be right for custom software, a new brand identity or a product design that could be patented.
Frequently Asked Questions
Does Paying An Invoice Transfer Copyright?
No. Payment alone usually doesn't transfer copyright. You generally need a written assignment signed by the copyright owner, or a valid work made for hire arrangement.
Can I Change A Logo Or Design After I Receive It?
Only if your contract gives you the right to modify it. If you only received a narrow license, changing the work may go beyond what you were allowed to do.
Who Owns A Business Name Or Brand?
Trademark rights generally come from using the mark in commerce for your goods or services, but registration through the USPTO can strengthen protection. Logo artwork may involve separate copyright rights, so your designer contract still matters.
What If My Contract Says Nothing About IP?
You may still have some implied rights to use what you paid for, but those rights can be uncertain and limited. It's usually better to put a clear written assignment or license in place.
Key Takeaways
- Paying a contractor doesn't automatically mean your business owns the IP they create.
- For contractor work, use clear assignment wording, not just work made for hire language.
- Spell out deliverables, source files, admin access and handover requirements before the project starts.
- Contractors can keep pre-existing tools, but your business needs a strong enough license to use the final work.
- Portfolio rights, confidentiality and trademark use should be controlled in the contract.
- Employees, founders and contractors all need tailored IP wording so the business owns or controls its key assets.
If you'd like help with your contractor agreements, software development terms, founder IP assignments or portfolio and confidentiality wording, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.







