Who Owns Work Created by a Contractor in the US?

A startup can pay a designer for a logo, a developer for source code, a writer for website copy or a consultant for a strategy deck and still not automatically own the underlying intellectual property. The common mistakes are assuming payment equals ownership, relying on a brief invoice, or using the phrase "work made for hire" without checking whether it actually works under US copyright law.

Contractor intellectual property ownership matters when you launch a product, pitch investors, apply for trademark registration, sell the business or stop working with a freelancer. A clean written agreement can decide whether you own contractor deliverables outright, have only a limited license to use them, or need to go back and negotiate an IP assignment after the work is already valuable.

\n

Contractor IP Ownership Checklist for US Businesses

\n

The safest position is to treat contractor-created work as something your business must expressly acquire in writing, not something it automatically owns because it paid the invoice.

For startups and small businesses, the ownership question usually comes up at practical moments: a new brand identity is ready to launch, a contractor has built the first version of an app, a marketing agency has delivered ad creative, or a consultant has created templates your team wants to reuse. Before you put that work at the center of your business, check the documents that sit behind it.

A strong contractor IP file usually includes:

• A written services agreement: This should identify the contractor, the business, the scope of work, payment terms and who owns the deliverables.
• An IP assignment clause: The agreement should transfer the relevant copyright, patent rights, design rights, trade secret rights and other IP rights in the deliverables to your business, where legally possible.
• Work made for hire wording where appropriate: This can help for certain copyright works, but it should not be the only ownership mechanism.
• A license for background materials: If the contractor uses pre-existing code, templates, stock assets, frameworks, processes or tools, your business needs clear permission to use them as part of the final work.
• Confidentiality obligations: Contractors often see product roadmaps, customer lists, source code, data and pricing. The agreement should restrict how that information is used and disclosed.
• Warranties about originality and third-party materials: The contractor should promise that the work does not knowingly copy someone else's protected work and that any third-party assets are disclosed and properly licensed.
• Delivery requirements: For software, this may include source code, build instructions, documentation, credentials and repositories. For creative work, it may include editable design files and final output files.
• Post-termination obligations: The agreement should say what happens when the project ends, including return of confidential information, deletion of copies and cooperation with IP filings if needed.

Payment terms should work with the IP terms. Some contracts say ownership transfers only once the contractor is paid in full. Others assign ownership as work is created, while giving the contractor a right to suspend work or claim unpaid fees if invoices are not paid. The right structure depends on your bargaining position, the project risk and how business-critical the deliverables are.

Do not rely only on a proposal, statement of work, chat thread or invoice unless it contains clear ownership language. A line item that says "website design" or "app development" usually describes what the contractor will do, not who owns the IP when the work is complete.

\n

What US Law Says About Contractor-Created Work

\n

Under the US default rules, an independent contractor usually owns the copyright in original work they create unless a valid written assignment or a qualifying work made for hire arrangement says otherwise.

The Copyright Act protects original works of authorship fixed in a tangible medium. For business purposes, that can include website copy, photographs, illustrations, videos, music, software code, UI graphics, training materials, pitch decks and product documentation. Copyright ownership starts with the author. For an employee creating work within the scope of employment, the employer is generally treated as the author under the work made for hire doctrine. For an independent contractor, the default rule is very different.

If your company hires an outside designer to create a logo, the designer may own the copyright in the artwork unless the agreement transfers it. If a freelance developer writes custom code for your platform, the developer may own copyright in the code unless there is a signed assignment or a valid work made for hire arrangement. Your business may have an implied license to use the work for the purpose everyone expected, but an implied license is often narrower, harder to prove and less useful than ownership.

Other IP rights have their own rules:

• Trademarks: US trademark rights generally arise from use of a mark in commerce and are governed federally by the Lanham Act, with registration handled by the USPTO. A contractor may create the visual logo, but your business may be the one building trademark rights through use of the brand. Copyright in the artwork and trademark rights in the brand are separate issues.
• Patents: Patent rights generally start with the individual inventor. If a contractor invents a technical solution, your company may need a written assignment of patent rights and cooperation with filings.
• Trade secrets: The Defend Trade Secrets Act and state trade secret laws can protect valuable confidential business information if the business takes reasonable measures to keep it secret. Contractor agreements are part of those measures.
• Contract rights: General contract principles, and for certain transactions the Uniform Commercial Code, can affect payment, acceptance and remedies. They do not automatically transfer all IP in creative or technical deliverables unless the contract says so.

State law can affect contract interpretation, employment status, invention assignment obligations and confidentiality restrictions. The federal baseline is still a useful starting point, but the exact result may depend on the contract wording, the type of work, the parties' conduct and the law that applies to the agreement.

A common founder example shows the risk. A startup pays a freelancer to design a character mascot for its app. The brand takes off, merchandise opportunities appear and investors ask for proof that the company owns the character art. If the only document is an invoice marked "paid," the company may need to negotiate an assignment later, often at a higher price and with less leverage.

\n

Why Work Made for Hire Often Is Not Enough

\n

Calling contractor work a "work made for hire" does not automatically make your business the owner, because the Copyright Act allows that treatment for contractors only in limited circumstances.

For employees, work made for hire can be broad. For independent contractors, two things generally need to be true. First, there must be a written agreement stating that the work is a work made for hire. Second, the work must fall within one of the specific categories recognized by the Copyright Act for specially ordered or commissioned works. Many everyday startup deliverables do not fit neatly into those categories.

That means a work made for hire contractor clause may help for some commissioned works, but it is risky to rely on it alone. A software build, brand package, product design, marketing funnel, website content set or consulting framework might not qualify depending on the facts. If the work does not qualify, the contractor may still own the copyright unless there is a separate assignment.

A better drafting approach is often to use both concepts:

• State that eligible deliverables are works made for hire to the maximum extent allowed by law.
• Include a present assignment of all right, title and interest in the deliverables to the business.
• Require the contractor to sign further documents if needed for Copyright Office, USPTO or other filings.
• Clarify when ownership transfers, especially if payment milestones are tied to delivery.
• Reserve the contractor's ownership of clearly identified pre-existing materials, while granting the business a license to use them as embedded in the deliverables.

The assignment language should be active and clear. Wording such as "Contractor hereby assigns" is usually stronger than a vague promise that the company "will own" the work. A promise to assign in the future can create arguments if the contractor later refuses to sign documents or if the work becomes valuable before the paperwork is cleaned up.

For copyright, a transfer of ownership generally must be in writing and signed by the owner or the owner's authorized agent. For patent rights, written assignments are also commonly used, and recordation may be relevant to later transactions. For trademark-related work, your agreement should separate ownership of the creative files from ownership and use of the brand itself.

There are also rights that may not be fully captured by a simple ownership sentence. A contractor may have moral rights in limited categories of visual art under the Visual Artists Rights Act. A contractor may use open source code that brings license obligations. A photographer may use a stock image license that cannot be transferred. A consultant may bring pre-existing playbooks and only license them for a particular project. These issues do not mean the project cannot proceed, but they need to be visible before your business depends on the work.

Founders often discover the work made for hire problem during due diligence. An investor or buyer asks for contractor agreements covering the first product build, original logo, customer onboarding materials and core content. If those agreements only say "work made for hire" and the deliverables do not qualify, the buyer may require confirmatory assignments before closing or may treat the issue as a risk to valuation.

\n

How to Own Contractor Deliverables in Practice

\n

Your business is much more likely to own contractor deliverables if the contract clearly defines the work, assigns IP rights, deals with background materials and keeps confidentiality obligations separate from ownership.

Start with the deliverables. A contract that says a contractor will provide "marketing help" is too vague if you need to own ad copy, landing page copy, campaign concepts, source files, account structures and analytics templates. A contract that says a developer will "build the platform" may leave uncertainty about source code, APIs, documentation, testing scripts, database schema, infrastructure configuration and deployment materials.

For creative and technical projects, define deliverables in a statement of work and then make the IP clause apply to those deliverables. Your definition can include drafts, iterations, final files and supporting materials created specifically for your business. If you only receive flat files or screenshots, you may not have what you need to update or commercialize the work later.

Next, separate newly created work from pre-existing materials. Contractors often use their own tools, libraries, templates, design systems, know-how, snippets or methods. It is usually unrealistic to demand ownership of everything in the contractor's toolkit. Instead, the agreement can say:

• Your business owns the new deliverables created specifically for the project.
• The contractor keeps ownership of identified pre-existing materials.
• The contractor grants your business a broad, perpetual license to use any embedded pre-existing materials as part of the deliverables.
• The contractor must disclose third-party materials and confirm the license terms that apply.
• The contractor cannot include materials that would prevent your intended commercial use.

This distinction is especially important for software. Your app may include custom code, open source components, third-party APIs, cloud services, contractor-owned libraries and configuration scripts. Owning the custom code does not mean you own every component in the stack. You need enough rights to run, modify, maintain, commercialize and transfer the product if the company raises funding or is transferred in a business sale.

Confidentiality should sit beside IP assignment, not replace it. A non-disclosure obligation can stop the contractor from sharing your confidential information, but it does not necessarily transfer ownership of the contractor's work product. Similarly, an IP assignment can transfer ownership of deliverables, but it does not automatically protect your customer data, business strategy or trade secrets unless confidentiality and security obligations are included.

For trade secrets, the Defend Trade Secrets Act focuses on information that derives independent economic value from not being generally known and is subject to reasonable secrecy measures. In contractor relationships, reasonable measures can include written confidentiality terms, access controls, limited repository permissions, secure credential practices and return or deletion obligations at the end of the project.

For branding projects, distinguish copyright from trademark. The designer's file ownership is not the same as your right to use a brand name in the market. Before investing heavily in a name, many businesses search for potential conflicts and consider applying to register the mark with the USPTO. Registration is a separate process, and a clean design assignment does not guarantee the brand is available as a trademark.

For written content, videos, course materials and marketing assets, confirm whether the contractor may reuse the work in their portfolio, resell templates or repurpose concepts for other clients. Some businesses are comfortable with limited portfolio use after launch. Others need stricter limits because the materials reveal strategy, product positioning or customer information.

For consultants, decide whether the output is meant to be owned or merely used. A management consultant may deliver a framework that draws on years of prior work. The business may need a license to use the recommendations internally, not ownership of the consultant's underlying methodology. A product consultant, on the other hand, may create naming systems, product requirements or workflows that should be assigned to the company.

Practical next steps for a founder hiring a contractor include:

1. Collect the documents before work starts: Put the services agreement, statement of work, confidentiality terms and IP terms in one signed package.
2. Use project-specific language: Generic ownership wording may not capture source files, code repositories, inventions, data, credentials or editable assets.
3. Ask about third-party materials: Require disclosure of stock assets, open source code, AI-generated content inputs, fonts, plugins and templates.
4. Confirm who can sign: If the contractor operates through a company, make sure the contracting party has the rights from the individuals doing the work.
5. Get assignments from key contributors where needed: Subcontractors and collaborators can create ownership gaps if their rights are not passed through in subcontractor agreements.
6. Store evidence carefully: Keep signed agreements, statements of work, payment records, delivery records and final files in a diligence folder.

If work has already started, do not assume it is too late. A confirmatory IP assignment agreement can often clean up ownership after the fact, provided the contractor is willing to sign and the scope is clear. The commercial conversation may be easier if the relationship is still positive and invoices are current.

If a contractor refuses to assign IP, focus on what your business actually needs. In some cases, a broad exclusive license may be workable. In others, especially core software, branding, investor-facing assets or product content, lack of ownership may be a material business risk. The right answer depends on whether you need to modify the work, prevent reuse, sublicense it, transfer it in a sale or enforce rights against third parties.

\n

FAQs

\n

Does My Business Own Contractor Work If We Paid for It?

Payment alone usually does not transfer copyright or other IP ownership from an independent contractor to your business. It may support an argument that you have permission to use the work for the expected project, but that is not the same as owning it.

A written assignment is the cleaner position. It should identify the deliverables, transfer the relevant rights and explain what happens to background materials and third-party content.

\n

Is Contractor Work Automatically Work Made for Hire?

No. Contractor work is not automatically work made for hire under US copyright law. For an independent contractor, there generally needs to be a signed written agreement and the work must fall within a limited statutory category.

Because many startup deliverables do not clearly fit those categories, work made for hire wording is often paired with a separate IP assignment.

\n

Can We Get an IP Assignment After the Contractor Finishes?

Yes, a later assignment can often transfer rights after the work is complete, but it may be harder to negotiate once the contractor has leverage or the work has become central to the business.

The assignment should be specific about the project, deliverables, dates, rights transferred and any retained materials. If the work is already part of a product, fundraising process or sale, timing can matter.

\n

What If the Contractor Used Open Source Code or Stock Images?

Your business may not own those third-party materials, even if it owns the custom deliverables. You need to know the license terms and whether they allow your intended commercial use, modification, distribution and transfer.

The contractor agreement should require disclosure of third-party materials and prohibit use of materials that would create unexpected restrictions for your business.

\n

Who Owns a Logo Created by a Freelance Designer?

The designer may own copyright in the artwork unless the contract assigns it to your business. Your business may separately build trademark rights in the brand through use in commerce, and may seek USPTO registration if the mark is available and registrable.

A good logo agreement deals with both the creative files and the intended brand use, including editable files, portfolio permissions and third-party fonts or assets.

\n

Key Takeaways

\n

• Independent contractors usually own the copyright in original work they create unless a valid written assignment or qualifying work made for hire arrangement changes that result.
• Work made for hire is limited for contractors, so businesses commonly use both work made for hire wording and a separate IP assignment.
• Owning contractor deliverables requires more than paying an invoice. The agreement should cover source files, code, drafts, inventions, third-party materials and background tools.
• Copyright, trademark, patent and trade secret rights follow different rules, so the right wording depends on the type of work being created.
• Clean contractor IP paperwork can reduce friction during fundraising, product launches, trademark filings, business sales and disputes over reuse.
• State law, contract terms and the facts of the working relationship can affect the outcome, so high-value or business-critical projects should be reviewed before work begins.

If your business is hiring a contractor for software, branding, content, product design or consulting work, our team can help with your contractor agreement, IP assignment language, confidentiality terms and deliverables schedule. You can reach our team on (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they are provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.