Pre-Existing Intellectual Property Rights: Who Owns What? (2026 Updated)

If you're building a business in 2026, chances are you're not starting from a blank page.

You might be using code you wrote years ago, a logo you sketched on your iPad before the company existed, a deck built from old templates, or a process you developed at a previous job. And if you're collaborating with co-founders, contractors, agencies, or investors, the obvious question comes up fast:

Who actually owns the intellectual property (IP) you're using to build the business?

This is where pre-existing intellectual property rights (often called background IP) matter. If you don't identify and document them early, you can end up with nasty surprises later - like finding out you can't legally commercialise what you're selling, or that a key asset isn't owned by the business when you try to raise funding or sell.

Let's walk through what "pre-existing IP" is, why it matters, and how to clearly allocate ownership so your business is protected from day one.

What Counts As "Pre-Existing IP" (And Why It Matters So Much)

Pre-existing IP is any intellectual property that existed before a particular agreement, project, relationship, or company setup.

It usually shows up in situations like:

• You're incorporating a business and bringing in assets you created personally.
• A co-founder has built a prototype before the company existed.
• A contractor is using their own tools, templates, code libraries, or design systems to deliver work for you.
• You're collaborating with another business and both sides are contributing existing materials.
• You're buying a business, acquiring a product, or investing - and need to confirm what's actually owned (and transferable).

This matters because IP is often the most valuable asset in a modern business - especially if you're in software, eCommerce, creative services, content creation, product design, or SaaS.

If ownership is unclear, you can run into:

• Investor red flags during due diligence (unclear chain of title).
• Disputes with co-founders, freelancers, or agencies.
• Infringement claims if someone says you're using their work without permission.
• Operational headaches if you can't update, resell, licence, or enforce rights in key assets.

It can feel awkward to raise these issues when you're excited about launching - but sorting it out early is one of the best "future you" decisions you can make.

Common Examples Of Pre-Existing IP

Pre-existing IP can include (but isn't limited to):

• Copyright works: software code, website copy, blog posts, product descriptions, marketing materials, photos, videos, training manuals, designs.
• Trade marks and brand assets: business names, logos, slogans, packaging concepts.
• Designs: product designs, UI/UX layouts, CAD drawings.
• Confidential information: internal processes, client lists, pricing strategies, unique methods.
• Databases: customer databases, curated datasets, proprietary collections.

And importantly - "I made it" doesn't always mean "I own it" (we'll get to that).

Background IP vs Foreground IP: The Ownership Framework You Should Use

When lawyers and commercial agreements talk about "pre-existing IP", they often use two key buckets:

• Background IP (pre-existing): IP a party already owned or controlled before the project or contract.
• Foreground IP (project IP): IP created during the project (sometimes called "developed IP").

This framework is useful because it forces you to answer two practical questions:

• What is each person/business bringing into the relationship?
• What will be created during the relationship, and who will own it?

Why This Distinction Stops Disputes

Let's say you hire a developer to build features into your app. They might use:

• their own pre-written code snippets (background IP), and
• new code written specifically for your app (foreground IP).

If your agreement doesn't deal with this properly, you can end up in a messy middle ground where:

• you assume you "own the app", but
• they believe they still own substantial parts of what's inside it, or
• you can't commercialise or modify it without ongoing reliance on them.

A clear contract should define what background IP is, list it where possible, and then specify what happens to foreground IP (assignment to you, joint ownership, or a licence).

Who Owns IP By Default In The UK? (Employees, Contractors, Co-Founders)

A lot of IP disputes come down to assumptions about default ownership rules. In the UK, the default position depends heavily on the relationship.

IP Created By Employees

In many cases, IP created by an employee in the course of employment will belong to the employer (for example, under the Copyright, Designs and Patents Act 1988 for copyright works).

But "in the course of employment" can be a grey area if, for example:

• they created it outside working hours,
• they used personal equipment,
• it's not directly related to their role, or
• your contract doesn't clearly deal with IP.

That's why it's smart to deal with IP ownership clearly in an Employment Contract - including confidentiality, assignment wording, and obligations to assist with registrations.

IP Created By Contractors And Freelancers

This is where many businesses get caught out.

If you hire a contractor, freelancer, or agency, the default position is often that they own what they create unless there's a written agreement assigning it to you (or licensing it in a way that fits your business needs).

So even if you've paid in full, you might only have an implied right to use the deliverables for the original purpose - not to edit, resell, sublicence, or stop them from reusing it elsewhere.

This is why it's so important to have the right IP clauses and clearly document ownership, especially where Independent Contractors are involved.

IP Created By Co-Founders

If you're building with a co-founder, ownership can be especially confusing because people often create early-stage assets informally (before incorporation, before agreements, and before roles are properly defined).

Common examples include:

• one co-founder designs the logo and brand,
• another writes the MVP code,
• someone builds the initial pitch deck and sales collateral.

If the company doesn't receive a proper assignment of those assets, then those assets may remain owned by the individuals - which becomes a huge problem when:

• a co-founder exits,
• you take investment,
• you sell the business, or
• you try to enforce your rights against a copycat.

As a rule of thumb: if the business will rely on it, the business should have a written right to use it - ideally by owning it outright.

Common Pre-Existing IP Pitfalls (And How To Avoid Them)

Pre-existing IP problems are usually avoidable - but they tend to pop up in predictable ways. Here are some of the big ones we see.

1) "We Paid For It, So We Own It"

This is a very common assumption - and it's not always correct.

Payment doesn't automatically transfer IP ownership. You typically need an express written assignment (or at least a properly drafted licence) that states what rights transfer, when, and on what terms.

If you want the business to own the deliverables, consider putting an IP Assignment in place, particularly when the work is created externally or before incorporation.

2) Using Templates, Stock Assets, Or Platform Content Without Checking Licences

Modern businesses move fast - and it's normal to use tools like Canva templates, stock photos, UI kits, code libraries, and AI outputs.

The trap is that these tools can come with licence terms that limit:

• commercial use,
• resale rights,
• exclusive ownership claims,
• trade mark registration of generated content.

If your brand, packaging, or content strategy relies on templates, it's worth checking whether you can commercialise it and whether it can be protected. For example, questions around Canva Designs (and what you can sell) come up a lot.

3) Not Ring-Fencing Confidential Information Early

Pre-existing IP isn't always a "thing" like a logo - sometimes it's know-how, methods, or information that gives you an edge.

Before you share sensitive details with developers, agencies, manufacturers, collaborators, or potential partners, it's wise to use an NDA so you've got contractual protections around use and disclosure.

An NDA won't magically give you ownership of someone else's background IP - but it can stop your confidential information being used against you.

4) AI-Generated Inputs And Unclear Rights

AI tools are now built into a lot of business workflows - marketing copy, images, code suggestions, product names, and more.

The difficulty is that "ownership" and "exclusivity" can be complicated depending on:

• the tool's terms of service,
• whether outputs are truly original,
• whether training data creates third-party infringement risk, and
• how the output is used and adapted.

If your product or brand heavily relies on AI-generated creative outputs, it's worth understanding the commercial risk profile. This comes up a lot when businesses ask whether AI-Generated Art can be sold and protected.

How To Document Pre-Existing IP Properly In Contracts

Once you've identified what pre-existing IP exists, the next step is documenting it clearly so everyone knows where they stand.

In practice, most businesses use a mix of:

• Schedules listing background IP (where practical),
• IP ownership clauses dealing with what's created during the work,
• licences where ownership stays with one party but the other party needs usage rights, and
• assignments where IP is transferred to the business.

Background IP Schedules: Simple But Powerful

A background IP schedule doesn't need to be perfect - but it should be practical and specific.

Depending on the project, it might include:

• software libraries, modules, or repositories,
• brand assets and style guides,
• existing photos/video content libraries,
• existing training materials or SOPs,
• design files and prototypes created pre-contract.

The goal is to avoid later arguments like "that was mine before we started" versus "no, we paid for that development".

Licences: When Ownership Stays Put, But Use Is Allowed

Sometimes you don't want (or can't get) ownership of pre-existing IP - and that can be totally fine, as long as your business has the rights it needs.

A licence should be clear about:

• scope (what you can do with the IP),
• territory (UK only or worldwide),
• duration (fixed term or perpetual),
• sublicensing (can you let customers use it, or let group companies use it?),
• exclusivity (exclusive, non-exclusive, or sole),
• termination and what happens after termination.

It's also worth being careful with wording and consistency across documents - especially when you're balancing licensing and transfer concepts. The licensing/assignment distinction is a big reason businesses look closely at IP Licensing language in contracts.

Assignments: When The Business Needs To Own The IP

If the IP is central to your product or brand, it's often safest for the company to own it outright.

Assignments are commonly used for:

• logo and brand design ownership,
• software ownership (particularly MVP code and core product),
• website content and marketing collateral (where reuse restrictions would hurt you),
• product designs, CAD drawings, packaging.

Assignments need to be done properly (including timing, payment triggers, moral rights considerations for copyright works, and ensuring the party assigning actually owns what they're transferring).

Make Sure The Contract Is Actually Enforceable

Even well-intentioned IP wording can fall apart if the contract formation basics weren't handled properly (unclear acceptance, missing key terms, inconsistent versions, or informal email arrangements that don't match what you think you agreed).

If you're ever unsure about whether you've got a real agreement in place, it helps to sanity-check against the basics of Legally Binding Contracts.

Pre-Existing IP In Real Life: A Quick Checklist For Business Owners

If you want a practical approach you can action this week, here's a checklist that works well for most startups and SMEs.

Step 1: List What You're Using To Make Money

Write down the assets your business depends on, such as:

• brand name and logo,
• website copy and imagery,
• social content templates and ad creatives,
• software code (frontend, backend, APIs),
• customer databases and mailing lists,
• product designs, prototypes, packaging.

Step 2: Identify Who Created Each Asset (And When)

For each item, note:

• who created it (employee, contractor, co-founder, agency),
• when it was created (before or after the company existed),
• what agreement (if any) was in place at the time.

Step 3: Match Each Asset To The Right Legal Mechanism

• If you need full control: aim for an assignment.
• If the creator must retain ownership: get a licence that covers your real use case (including future growth).
• If the asset is sensitive: use confidentiality protections before disclosure.

Step 4: Keep A Clean "Chain Of Title" Folder

If you want to make due diligence painless (for investors, buyers, or even just your future self), keep a central folder with:

• signed assignments and licences,
• contractor agreements,
• employment contracts and IP clauses,
• brand ownership documents,
• key platform licence terms (if you're relying on third-party assets).

This small admin habit can save you weeks of stress when an opportunity comes up.

Key Takeaways

• Pre-existing IP (background IP) is anything created or owned before a project, contract, or company relationship - and it can quietly become a major business risk if it isn't documented.
• The simplest way to think about ownership is "background IP vs foreground IP": what each party brings in, and what gets created during the relationship.
• In the UK, employees often create IP that can belong to the employer, but contractors and freelancers commonly own what they create unless a contract clearly assigns or licenses it.
• If your business depends on an asset (core code, brand, designs, key content), it's usually safest for the company to own it outright via a properly drafted assignment.
• Where ownership needs to stay with the creator, a clear licence should cover scope, territory, term, sublicensing, exclusivity, and what happens on termination.
• AI tools, templates, and platform assets can come with licence restrictions, so it's worth checking commercial-use rights before you build your brand or product around them.
• Putting the right agreements in place early keeps your "chain of title" clean, helps avoid disputes, and makes investment or sale discussions far smoother.

If you'd like help identifying pre-existing IP risks in your business or getting the right documents in place, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.