A Client Wants To Own All The IP In Your Work - What Should You Check Before Agreeing?

A client sends you a contract, but there’s a catch - they want to own all the intellectual property in the work you create.

That may be completely reasonable for the final deliverables they are paying for. The issue is that some IP clauses are drafted broadly enough to cover more than just the finished work. If your business uses existing templates, systems, code, frameworks or processes to create the deliverable, those materials could also fall within the wording unless they are clearly excluded.

For example, a client may reasonably expect to own a custom report, campaign asset or piece of software created specifically for their business. That does not necessarily mean the supplier should also give up ownership of the templates, frameworks or reusable tools used to create it.

The key is to work out what the client should own, what your business needs to keep, and whether the contract makes that distinction clear.

What Does It Mean To Give A Client The IP?

Intellectual property can include copyright, patents, trademarks and trade secrets, and the rules for ownership and transfer are not identical across each category.

For many agency, design, content and software projects, copyright is likely to be one of the main rights involved.

Paying someone to create something does not automatically mean the client owns the copyright in it.

For copyright purposes, ownership can depend on who created the work and whether it qualifies as a work made for hire.

A work made for hire can arise where an employee creates copyrightable work within the scope of their employment. It can also apply to certain specially commissioned works, but only where the work falls within one of the statutory categories and the parties have a signed written agreement stating that it will be treated as a work made for hire. 

For copyright that does not qualify as work made for hire, ownership may instead need to be transferred through an assignment.

An assignment is used to transfer ownership of intellectual property rights, although the exact requirements can depend on the type of IP involved. A license allows someone to use IP without necessarily becoming its owner.

For example, a developer might build a custom platform for a client using a framework they have developed across many different projects. The client might receive ownership of certain elements created specifically for them, while the developer keeps ownership of the underlying framework and gives the client the license rights needed to use it.

For copyright specifically, a transfer of ownership generally needs to be in writing and signed by the copyright owner or their authorized agent. 

If the IP wording appears inside a broader client agreement, a Business Contract Review can help clarify what the clause actually requires before you sign.

What Exactly Is The Client Asking To Own?

Before deciding whether an IP clause is reasonable, look closely at what it actually covers.

There can be a big difference between a clause saying the client owns the final deliverables created specifically for the project and one saying the client owns all intellectual property created, developed, used or incorporated in connection with the services.

The second version can go much further.

Imagine a marketing agency creates a campaign for a client. The final copy and creative assets may have been developed specifically for that business, but the agency could have created them using an existing reporting framework, briefing process, template library or internal methodology.

Those underlying materials might never be delivered to the client as separate assets. However, if the ownership wording is broad enough, questions can still arise about whether they have been swept into the transfer.

The same issue can arise where a developer uses an existing code library, a consultant adapts their standard framework or a designer relies on templates or systems they use across multiple projects.

This is why it is worth checking how terms such as Intellectual Property, Work Product, Deliverables or Developed IP are actually defined in the contract.

This is also where background IP becomes important.

What Is Background IP?

In commercial agreements, background IP is commonly used to describe intellectual property a business already owns or develops independently of the particular client project.

That might include software libraries, templates, frameworks, internal systems, processes, methodologies or standard materials.

Take a consulting business that has spent years developing its own assessment framework.

A client hires the consultant to review its operations and prepare a customized report. The report itself may contain findings and recommendations created specifically for that client, but the framework used to produce it could be something the consultant relies on across dozens of engagements.

If the contract broadly assigns everything used or developed in connection with the services, the consultant needs to check whether that wording could also reach the underlying framework.

That is a very different commercial outcome from giving the client rights to the bespoke report they commissioned.

Can The Client Own The Deliverable While You Keep Your Background IP?

Yes. Depending on the project, the contract can separate the client-specific work from the tools and materials the supplier already owns.

For example, a client might receive ownership of a custom design, report or software component created specifically for the engagement, while the supplier keeps ownership of its existing systems, templates or reusable code.

Sometimes those two layers are connected.

A software developer might build a custom platform using libraries or components they rely on across many different projects. The client still needs to be able to operate and maintain the finished platform, but that does not necessarily mean they need ownership of every underlying component.

The agreement can instead deal separately with those rights - for example, transferring ownership of specified client-specific material while licensing the background IP that remains embedded in the final product.

That way, the client can get the practical rights it needs without the supplier giving up assets it uses across the rest of its business.

What About Reusing Your Work?

This is where a broad ownership clause can create problems beyond the current project.

Say a developer has built a library of generic components that they reuse across different clients. While working on one project, they use some of those existing components and also develop another generic function that could be useful later.

The client may have a legitimate reason to own the custom software built specifically for them. But if the contract says the client owns everything created or used during the engagement, the developer needs to check whether that wording also captures components they would normally continue using elsewhere.

The same issue can arise with an agency's reporting framework, a consultant's methodology or a designer's templates.

This does not mean a supplier should be free to reuse a client's confidential information, trade secrets or bespoke work for someone else. Those are separate issues.

The question here is whether the agreement clearly separates client-specific IP from the underlying tools, systems and materials the supplier needs to keep using in its own business.

The goal is not necessarily to prevent the client from owning its bespoke work. It is to make sure that ownership does not unintentionally extend to the assets your business needs to keep serving other customers.

Does The Client Actually Need To Own Everything?

Sometimes ownership is exactly what the commercial deal requires.

A client commissioning bespoke software for its core product, for example, may want ownership of the custom code developed specifically for it.

In other cases, what the client actually needs is the freedom to use, modify, commercialize or have another supplier work on the finished deliverable.

Those objectives are not necessarily the same as owning every piece of IP used to create it.

That is why it can be useful to work backwards from what the client needs. The appropriate arrangement might be an assignment, a license or a combination - for example, client ownership of bespoke deliverables with a license to the supplier's background IP.

Do You Actually Have The Right To Transfer It?

Before promising to transfer IP to a client, check that your business actually has the rights it is promising to give them.

A finished deliverable might contain licensed images, software components, plugins or other third-party materials. Your business may have permission to use those assets without owning them, which can limit what rights you can pass on to the client.

The same applies if freelancers or subcontractors helped create the work. In the US, paying an independent contractor does not necessarily give your business ownership of the copyright they create, and contractor work does not automatically qualify as work made for hire. 

So if you are promising certain rights downstream to your client, make sure your agreements upstream give your business the rights needed to make that promise.

For a closer look at this issue, see our guide to independent contractor IP ownership.

When Does Ownership Transfer?

Even if both sides agree that certain IP will eventually belong to the client, the agreement should still deal with when that transfer happens.

Ownership might transfer when the work is created, when it is delivered, when the project is completed or only after the client has paid in full.

That timing can matter for suppliers.

For example, if an assignment takes effect as soon as the work is created but the client later fails to pay the final invoice, the supplier may already have transferred the relevant rights before receiving the full agreed price.

Another agreement might instead make the transfer effective only once payment has been received.

The right structure depends on the project and the parties' commercial deal. What matters is understanding the trigger rather than assuming ownership will transfer at the point you expect.

What Should You Check Before Signing?

Before agreeing to a client's IP clause, ask:

• What am I actually transferring? Is it limited to the bespoke deliverables, or does the definition extend further?
• What existing IP am I bringing into the project? Check whether your templates, software, frameworks, systems and processes are carved out.
• Will I need to use any of this again? Make sure the agreement does not unintentionally stop you from reusing your own underlying materials.
• Do I actually own the rights I am promising? Check contractors and third-party components.
• When does ownership transfer? In particular, check how the assignment interacts with delivery and payment.

An IP provision might take up only a few paragraphs of a client contract, but it can determine who owns some of the most valuable assets your business creates.

The Bottom Line

A client asking to own the IP created specifically for their project is not unusual, and in many cases there may be good commercial reasons for it.

The issue is making sure the clause does not go further than either side intended.

The bespoke work created for the client, your existing business assets and the tools you use to produce that work are not necessarily the same thing. A clear agreement should explain what is being transferred, what stays with you and what rights each party has to use anything that sits between the two.

If a client has sent you an agreement containing a broad ownership clause, a Business Contract Review can help you understand what you would actually be agreeing to before you sign. You can reach us at (888) 449-8437 or team@sprintlaw.com for a free, no-obligations chat.