What Is an IP Carve-out Agreement?

If you are signing a services agreement, sale agreement, licence, investment document or collaboration deal, one clause can quietly reshape who owns valuable intellectual property. That clause is often an IP carve-out. Founders commonly make three mistakes here: they assume all pre-existing IP is automatically protected, they rely on a verbal assurance that "your stuff stays yours", or they sign broad assignment wording without checking what has been excluded. The result can be expensive confusion over software code, branding, product designs, templates, data sets or know-how you built before the deal started.

An IP carve-out agreement, or an IP carve-out clause within a broader contract, is designed to separate out certain intellectual property from what is being transferred, licensed or shared. That matters before you sign a contract, before you invest in branding, and before you rely on the other side's standard terms. This guide explains what an IP carve-out agreement means, where it shows up in Australian business deals, what to check before signing, and the mistakes that often catch startups and SMEs.

Overview

An IP carve-out agreement identifies intellectual property that is excluded from a broader transfer, assignment, licence or access arrangement. Its job is to stop a general ownership clause from accidentally sweeping up pre-existing materials, founder know-how, third party tools or other assets that were never meant to change hands.

For Australian businesses, the practical question is not just whether there is a carve-out, but whether it clearly says what is excluded, who can keep using it, and what rights the other side still gets.

• Define the excluded IP precisely, including pre-existing materials, background IP and third party components.
• Check whether the contract assigns ownership, grants a licence, or only permits limited use.
• Confirm what happens to improvements, customisations, new materials and derivative works.
• Make sure confidential information, know-how, source files and technical documentation are addressed separately where needed.
• Look for warranties and indemnities about ownership, infringement risk and authority to grant rights.
• Check whether the carve-out lines up with employee, contractor and supplier IP arrangements.
• Confirm post-termination rights, access, return obligations and any ongoing licence fees or restrictions.

What What Is an IP Carve-out Agreement Means For Australian Businesses

An IP carve-out agreement means certain intellectual property is deliberately kept out of the main deal. In plain English, it says, "this contract covers some rights, but not these specific assets".

You will often see IP carve-outs in agreements where one party is otherwise receiving broad rights. That could include a business sale, software development contract, distribution agreement, white label arrangement, technology licence, franchise-style operational agreement, manufacturing contract, agency arrangement or investment documents. The carve-out stops the receiving party from claiming ownership or unrestricted use of IP that sits outside the intended commercial arrangement.

What counts as intellectual property here?

In business contracts, intellectual property usually includes more than registered rights. It can cover trade marks, copyright, designs, patents, domain names, software, databases, content, drawings, formulas, product specifications, training materials, processes and confidential know-how.

That broad meaning is exactly why carve-outs matter. If the main clause says all IP created, supplied or used in connection with the services belongs to the customer, that wording may be wide enough to capture pre-existing templates, reusable code libraries, internal tools or brand assets unless they are specifically excluded.

Where founders usually come across IP carve-outs

Startups and SMEs tend to run into IP carve-outs at founder moments such as these:

• before you sign a developer agreement and the developer wants to keep ownership of its coding framework or reusable modules
• before you accept the provider's standard terms for software implementation, where the provider keeps background IP but gives you a limited licence to use the deliverables
• before you sell part of a business and want to keep family-owned branding, methods or technology outside the sale
• before you enter a joint venture and each side needs to ringfence the IP they bring to the project
• before you commission creative work and the agency wants to retain ownership of production tools, working files or template assets
• before you buy assets from another business and need to know whether the sale includes only specific IP or all associated know-how and materials

Why the carve-out matters commercially

The main risk is a mismatch between what the parties think they are buying and what the legal drafting actually says. One side may believe it is purchasing a finished product outright. The other may think it is only granting access to a custom layer built on top of its own existing systems.

That gap can become a real business problem quickly. It affects whether you can switch suppliers, update software, reuse content, manufacture products through another provider, expand into new markets or raise investment without ownership questions hanging over your key assets.

In Australia, contract wording usually does the heavy lifting here. Copyright ownership, licences and assignments are strongly shaped by the contract itself. Trade marks, designs and patents may also need formal assignment steps or registration updates, but the first question is still what the agreement says has been excluded or transferred.

Carve-out versus licence, assignment and reservation of rights

A carve-out is not automatically the same as a licence. A contract might say certain background IP is excluded from transfer, but also grant the other party a non-exclusive licence to use that background IP as part of the deal. That is common in software and services arrangements.

A carve-out is also different from a full assignment. An assignment transfers ownership. A carve-out does the opposite, it identifies what ownership is not moving across.

You may also see a reservation of rights clause. That clause usually says each party keeps all rights not expressly granted. It can help, but it is not always enough on its own. If the contract also contains broad assignment language, a vague reservation may not save you from a dispute. Specific exclusions are usually safer.

Legal Issues To Check Before You Sign

Before you sign, the safest approach is to map the actual assets involved and match them against the contract wording. If you cannot point to a list of what is excluded, licensed, assigned and newly created, the drafting may be too loose.

1. Is the excluded IP clearly identified?

The best carve-outs are specific. They refer to background IP, pre-existing materials and named assets, then define them clearly in a schedule or annexure.

Descriptions such as "our existing IP" or "supplier tools" can be too vague if the relationship later breaks down. A stronger approach is to identify categories and examples, such as:

• existing software libraries and source code owned before the contract date
• brand assets, logos, trade marks and style guides not created for the customer
• templates, forms, workflows and standard operating materials used across multiple clients
• manufacturing processes, formulas or technical know-how developed independently of the project
• third party software, stock images, open source components and licensed content

2. What rights does the other side still get?

An asset can be carved out from ownership transfer but still be licensed for use. That is often commercially sensible, but the licence terms need to be checked carefully.

Look at:

• whether the licence is exclusive or non-exclusive
• whether it is perpetual or tied to the contract term
• whether it can be sublicensed to affiliates, contractors or end users
• whether it is limited to a territory, field of use or product line
• whether the licence survives termination for ongoing operation or support

This is where founders often get caught. They preserve ownership of core IP, but grant such a broad licence that the commercial result is almost the same as giving it away.

3. Who owns improvements and customisations?

Many disputes sit in the grey area between old IP and new work. If a supplier uses its pre-existing platform to build a custom feature for your business, who owns that feature? If your team improves the supplier's process during a project, can the supplier reuse those changes elsewhere?

The agreement should separate:

• background IP, which existed before the deal
• project-specific deliverables, which are created for the deal
• improvements or derivative works, which build on existing IP
• feedback and suggestions, which one party may want a right to use broadly

There is no single right answer. The commercial position depends on bargaining power and the nature of the project. What matters is making the line clear before you sign.

4. Are third party rights dealt with properly?

Some IP cannot be freely assigned because it is licensed in from someone else. That includes open source software, stock content, software subscriptions, fonts, datasets or white labelled materials.

If the agreement promises ownership or unrestricted use of those components, you may end up with a promise that cannot actually be delivered. The contract should identify any third party materials and spell out the limits on your rights.

Where open source is involved, extra care is needed. Different licences create different obligations around attribution, distribution and source code disclosure. That issue is highly fact-specific, so it is worth legal review if software is central to the deal.

5. Do the warranties and indemnities match the carve-out?

Broad IP warranties can undermine the practical value of a carve-out. For example, a party may exclude ownership transfer of a software module, but still give a broad warranty that all materials supplied are owned outright and do not infringe any third party rights.

Check whether the contract says:

• the party owns or controls the rights it is licensing or assigning
• the IP infringes no third party rights
• the party has authority to grant the agreed use rights
• an indemnity applies if a third party makes an infringement claim

If those promises are too broad, they may expose you to risk that should have sat with the other party, or vice versa.

6. Does it line up with your internal IP chain of title?

A carve-out is only useful if you actually own what you are trying to exclude. Before you rely on a carve-out, check whether your employees, contractors, founders and suppliers have properly assigned relevant IP to the business.

This matters a lot in startups. A founder might say the company is retaining ownership of source code or branding, but the underlying work may still legally sit with an individual founder, freelance designer or developer if the paperwork was never cleaned up.

7. What happens when the contract ends?

Termination clauses often decide the real-world value of an IP deal. If access ends immediately, can you keep using the product? If the supplier's background IP remains embedded in your operations, can you maintain continuity?

Check for post-termination arrangements such as:

• ongoing licence rights needed to use deliverables already paid for
• access to source materials, export files or documentation
• transition assistance to move to another supplier
• return or deletion of confidential information
• limits on continued use of names, brands and marketing materials

Common Mistakes With What Is an IP Carve-out Agreement

The most common mistake is treating an IP carve-out as boilerplate. A few broad words can decide whether your business keeps control of core assets or loses leverage at the worst possible time.

Mistake 1: Assuming pre-existing IP is automatically protected

Founders often believe anything created before the contract date stays with them as a matter of common sense. Sometimes that is commercially intended, but broad assignment wording can still create a fight.

If the agreement says all IP used in connection with the services or all materials supplied under the agreement belong to the customer, a court will start with the words on the page. Do not rely on assumptions where a simple schedule of excluded IP could remove doubt.

Mistake 2: Failing to separate background IP from project deliverables

This happens in software, design and consulting deals all the time. A provider reuses its own tools and methods to create a customised outcome, but the contract does not distinguish the reusable engine from the bespoke output.

The result is friction later. The customer thinks it bought the whole system. The supplier thinks it only sold the custom layer. Good drafting and contract review separate those categories from the start.

Mistake 3: Using undefined terms like "materials" or "works"

Undefined catch-all terms can sweep too far. If "deliverables" include all materials developed or provided in relation to the services, that could include internal working files, templates, scripts, code snippets or process documents that were never priced for transfer.

Definitions should match the commercial deal. If only final approved assets are being assigned, say that. If working files are excluded, say that too.

Mistake 4: Forgetting moral rights and consents

Copyright ownership is not the whole story. Individual creators may also have moral rights in certain works, such as rights of attribution and integrity. In some projects, especially branding, content and design work, the agreement may need moral rights consents from individuals who created the material.

This does not replace IP ownership clauses, but it can be part of making the intended use workable.

Mistake 5: Overlooking confidential information and know-how

Some of the most valuable business assets are not registered rights at all. Processes, formulas, customer insights, pricing logic and internal methods may be protected mainly through confidentiality.

An IP carve-out should not be viewed in isolation. If the real value sits in know-how, your confidentiality obligations, access controls and post-termination restrictions may matter just as much as the ownership wording.

Mistake 6: Accepting standard terms without checking the IP stack

Many suppliers use standard contracts that are written to preserve their platform, methods and reusables. Many customers use procurement templates written to capture everything produced under the engagement. Neither approach is necessarily wrong, but each can be a poor fit for the actual transaction.

Before you accept the provider's standard terms, compare the IP wording against what you are paying for, what you need to keep, and what you may need to use after the relationship ends.

Mistake 7: Not matching the carve-out to a sale, investment or exit plan

Before you spend money on setup, growth or due diligence, think ahead to who will review your contracts later. Buyers and investors usually want confidence that the business owns or securely controls the IP it depends on.

If key rights sit under messy carve-outs, undocumented licences or founder-owned assets, that can slow down a transaction or reduce deal confidence. Clear allocation of IP rights helps now and later.

FAQs

Is an IP carve-out agreement a standalone contract or just a clause?

It can be either. Often it is a clause within a larger agreement, but in some transactions the parties use a separate deed or side agreement to identify excluded intellectual property more precisely.

Does an IP carve-out mean the other party gets no rights at all?

No. A carve-out usually means ownership is not transferred, but the other party may still receive a licence to use the excluded IP for limited purposes. You need to read the licence wording as well as the carve-out.

Do I need to list every item of excluded IP?

Not always, but the clearer the better. For high-value assets, named lists or schedules are safer than vague descriptions. A combination of defined categories and specific examples is common.

Can a customer own custom work while the supplier keeps its pre-existing tools?

Yes. That is a common structure. The customer may own project-specific deliverables, while the supplier retains background IP and grants a licence to the extent needed for the deliverables to function.

What if the contract is silent on improvements?

If improvements are commercially important, silence is risky. The parties should address who owns modifications, derivative works and enhancements before they sign, especially in software, product development and technical services deals.

Key Takeaways

• An IP carve-out agreement excludes specified intellectual property from a broader transfer, assignment or use arrangement.
• The core issue is clarity, you need to know what is excluded, what is licensed, what is assigned and who owns new work or improvements.
• Broad contract wording can accidentally capture pre-existing software, templates, branding, know-how or third party materials unless these are carved out properly.
• Australian businesses should check ownership wording, licence scope, warranties, third party rights, confidentiality obligations and post-termination use rights before signing.
• The carve-out should also match your internal IP ownership records with founders, employees, contractors and suppliers.
• Well-drafted IP carve-outs reduce disputes, protect bargaining power and make later investment, sale or supplier transition easier.

If you want help with contract drafting, IP ownership clauses, licence terms, and supplier or customer negotiations, you can reach us on 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.