The single most expensive sentence in many agency contracts is the one that says nothing about IP ownership. When the work goes well and the client pays on time, default IP rules don't matter. When the relationship breaks down, ambiguous IP terms turn into disputes that cost more than the engagement was worth. This guide walks through how agencies should think about IP, structure ownership in contracts, and protect their own intellectual property along the way.
In this guide:
- The default IP rules that apply when contracts are silent (and why they often surprise agencies)
- The four ownership models agencies actually use, with trade-offs of each
- How to handle pre-existing IP, third-party assets, and AI-generated content
- Portfolio rights, case study rights, and how to negotiate them
- What to do when a client refuses standard IP terms
Get the IP clauses right and most of your client relationships will never need to revisit them. Get them wrong and you'll be relitigating them in every dispute, every renewal, and every acquisition conversation.
What Counts as Intellectual Property
For agency work, IP usually includes:
- Original creative deliverables (designs, copy, video, photography, code)
- Brand assets (logos, marks, taglines)
- Strategy documents and frameworks
- Software, scripts, and custom tools
- Templates, processes, and methodologies developed in the course of work
- Source files (PSDs, Figma files, raw footage, source code)
It does not typically include the client's own materials provided to the agency, third-party assets licensed for use, or industry-standard knowledge.
The fight is usually over who owns what after delivery, who can use what after the relationship ends, and what happens to the agency's reusable methods.
Default Ownership Rules
In the United States, the default rule for most agency work is that the creator owns the IP unless there's a written agreement transferring it. There are two important exceptions:
Work made for hire: A narrow legal category that automatically vests ownership in the commissioning party. It applies in two situations: works created by employees within the scope of employment, and a specific list of nine categories of commissioned works (including contributions to collective works, audiovisual works, and a few others) when there is a written agreement.
Implied license: When IP is delivered without an explicit transfer, courts may find an implied license allowing the client to use the work for the purpose it was created. The scope of that license is often narrower than either party expected.
The practical takeaway: don't rely on defaults. Always have an explicit IP clause in writing.
The Four Ownership Models
Most agency contracts use one of four ownership models. Pick the one that matches your business.
Model 1: Full Transfer Upon Payment
The client owns all final deliverables once they're paid in full. The agency retains nothing except portfolio rights.
Best for: Brand identity work, logo design, content the client clearly needs to own outright.
Pros: Simple, easy for clients to understand, matches client expectations.
Cons: Agency can't reuse anything, even generic patterns. Source files transfer too.
Key clause language: "Upon receipt of full payment, Agency assigns all right, title, and interest in the Final Deliverables to Client."
Model 2: Transfer of Final Deliverables, Retention of Underlying IP
The client owns the final deliverables. The agency retains ownership of pre-existing materials, methodologies, frameworks, and any general-purpose tools used in the work.
Best for: Most agency work. This is the most common modern structure.
Pros: Client gets what they need; agency keeps what it built before the engagement.
Cons: Requires clear definitions of "Pre-Existing IP" and "Final Deliverables."
Key clause language: "Agency retains ownership of all Pre-Existing IP and Methodologies. Upon full payment, Agency assigns to Client ownership of the Final Deliverables, subject to Agency's continued ownership of Pre-Existing IP incorporated therein, for which Agency grants Client a perpetual, worldwide, royalty-free license to use as part of the Final Deliverables."
Model 3: Licensed Use
The agency retains full ownership of the deliverables and grants the client a license to use them. License scope is defined explicitly.
Best for: Stock content, productized templates, software products, ongoing royalty-style relationships.
Pros: Agency builds an asset base it owns. Can resell or relicense.
Cons: Most clients expect to own custom work outright. License terms must be carefully scoped.
Key clause language: "Agency grants Client a non-exclusive, perpetual, worldwide license to use the Deliverables for [defined purposes]. Client may not sublicense, resell, or modify the Deliverables without Agency's written consent."
Model 4: Joint Ownership
Both parties own the IP and either can use it freely. Usually a bad idea, occasionally appropriate for true partnerships.
Best for: Genuine co-development arrangements where both parties contribute substantially.
Pros: Both parties have full freedom to use the work.
Cons: Conflicts about modifications, future uses, and exclusivity. Hard to value or sell.
If you find yourself negotiating joint ownership, consider whether a license back to the agency would solve the same problem more cleanly.
Handling Pre-Existing IP
Pre-existing IP is anything the agency owned before the engagement: code libraries, design templates, project methodologies, internal tools, brand frameworks. This is the most commonly mishandled IP category.
The clean approach:
- Define "Pre-Existing IP" broadly in the contract.
- State explicitly that Pre-Existing IP remains the property of the agency.
- Grant the client a license to use Pre-Existing IP only as embedded in the Final Deliverables.
- Maintain an internal inventory of your reusable IP so you can prove what was pre-existing if a dispute arises.
Without this clause, an aggressive client could argue that any code, template, or framework used in their project belongs to them. With it, you can confidently reuse your own work across clients.
Third-Party Assets
Agency work often involves third-party assets: stock photography, fonts, plugins, code libraries. Each carries its own license terms.
Two responsibilities:
Licensing properly: Use only assets the agency has the right to use. Stock photo subscriptions, font licenses, and open source compliance all matter.
Disclosing in contracts: Tell the client what third-party assets are included and what licenses apply. This is especially important for assets the client will need to maintain (fonts, code dependencies, plugins).
A standard clause: "Final Deliverables may include Third-Party Assets licensed under their respective terms. Agency will provide Client with a list of such Third-Party Assets and their licenses upon delivery. Client is responsible for compliance with Third-Party Asset license terms after delivery."
AI-Generated Content
AI-generated content adds new complexity. Current US law holds that purely AI-generated work cannot be copyrighted because there is no human author. Human-edited or human-directed AI work may be copyrightable, with the protection limited to the human contributions.
Practical guidance:
- Disclose AI use in your contracts when AI tools are part of the workflow
- Clarify that AI-generated portions may not be copyrightable, even though the agency may treat them as deliverables
- Maintain records of human creative input for any AI-assisted work
- Watch for AI tool license terms that might claim ownership of outputs
A simple disclosure clause: "Agency may use AI-assisted tools in the production of Deliverables. Client acknowledges that purely AI-generated content may not be eligible for copyright protection under applicable law."
For a broader view of AI in agency workflows, see AI tools for agency productivity.
Portfolio and Case Study Rights
The most commonly forgotten clause: the agency's right to display work in portfolios and case studies.
Default behavior: if the contract is silent, the agency may have an implied right to show the work but not to disclose confidential business information.
The clean approach: explicitly grant the agency portfolio rights, with reasonable client protections.
A standard clause: "Agency may include the Final Deliverables, Client's name, and Client's logo in Agency's portfolio, case studies, marketing materials, and proposals. Agency will redact or omit any information designated by Client as confidential. Client may revoke this right with 60 days written notice for new placements."
For sensitive industries (healthcare, finance, government), expect to negotiate this clause heavily. Some clients will require:
- Approval rights for any case study before publication
- Anonymization (no client name or logo)
- Time delays before any work can be shown
- Embargoes on competitive work
Track your portfolio rights for every client. Knowing what you can show is essential to your sales process.
Protecting Agency IP
Beyond client contracts, agencies should actively protect their own IP.
Document your methodologies: Frameworks, processes, and templates that you've developed should be documented and labeled as proprietary.
Use NDAs with contractors and employees: Anyone who sees your internal IP should be under confidentiality obligations.
Trademark your brand: Your agency name, logo, and any productized service names may warrant trademark registration.
Register copyrights for important original works: Internal tools, software, and any work you license out should be registered with the US Copyright Office (or the equivalent in your jurisdiction).
Limit knowledge concentration: Don't let any single person walk out the door with your IP in their head. Document, share, and codify.
For more on protecting agency operations broadly, see our agency liability protection guide.
When Clients Push Back on IP Terms
Some clients (especially enterprise procurement teams) push for "all IP transfers to client, including pre-existing materials." This is both unreasonable and damaging to the agency.
How to push back:
Educate: Explain that pre-existing IP includes general-purpose tools your agency uses across all clients. Transferring it would prevent you from working with anyone else.
Carve outs: Offer to transfer all IP "specifically created for Client" while retaining "general methodologies, frameworks, and pre-existing tools."
License back: If a client absolutely insists on owning everything, negotiate a perpetual, worldwide, royalty-free license back to the agency for non-competitive purposes.
Walk away: Some IP terms are deal-breakers. A client who insists on owning your entire methodology is not worth the engagement.
When the Relationship Ends
IP issues come to a head most often at the end of a relationship. Build the exit into the contract.
Standard end-of-relationship IP provisions:
- Source files: Define whether source files transfer at all, and if so, when (typically only after full payment).
- Continued use: Confirm that the client may continue using delivered IP after the relationship ends.
- Return or destruction of confidential materials: Each party returns or destroys the other's confidential materials.
- Survival of IP clauses: IP ownership and license provisions survive contract termination.
- No revocation of granted IP: The agency may not claw back IP that's been transferred or licensed for past payment.
Without these provisions, every contract termination becomes an IP dispute waiting to happen.
A Clean IP Section Template
Here's a structure that works for most agencies:
- Definitions: Final Deliverables, Pre-Existing IP, Third-Party Assets, Methodologies.
- Ownership of Pre-Existing IP: Agency retains all Pre-Existing IP and Methodologies.
- Assignment of Final Deliverables: Upon full payment, Agency assigns Final Deliverables to Client, subject to embedded Pre-Existing IP licensed to Client.
- License for Pre-Existing IP: Perpetual, worldwide, royalty-free license to use Pre-Existing IP as embedded in Final Deliverables.
- Third-Party Assets: Disclosure and client responsibility for ongoing license compliance.
- AI Disclosure: Agency may use AI tools; some outputs may not be copyrightable.
- Portfolio Rights: Agency may use Final Deliverables in marketing, with client confidentiality protected.
- Survival: All IP provisions survive termination.
This template covers the situations that produce the vast majority of agency IP disputes.
Final Thoughts
IP is the area where many agencies are most vulnerable. The work has real value, the disputes get expensive, and the defaults rarely favor the agency. Spending a few hours getting your IP clauses right is one of the highest-leverage legal investments you can make.
Don't borrow IP language without understanding it. Don't sign client contracts that take more than they should. And don't deliver high-value work without an explicit, signed IP framework in place.
Ready to standardize how IP ownership and contracts flow through your agency? AgencyPro keeps your contracts, deliverables, and approval history in one place so IP terms are clear from kickoff to close. Book a demo.