IP assignment in outsourcing contracts: what you can give away and what you cannot

What the client actually needs

Start from the buyer’s real requirement, because it is narrower than their template. An enterprise client needs three things from an IP clause. It needs to use the deliverable for its business without asking permission. It needs to modify it, or have someone else modify it, including a supplier that is not you. And it needs enough certainty to satisfy its own auditors and, in a funding or sale process, its own diligence.

None of those requirements need ownership of your component library. A broad, perpetual, transferable licence over the background materials delivers all three. Once you frame the conversation that way, the negotiation is about drafting rather than about principle, and drafting conversations close.

Deliverables versus Pre-Existing Materials

The whole clause turns on two defined terms. Get the definitions right and the operative wording almost writes itself.

• Deliverables — the code, configuration, documentation and other materials created specifically for this client under a statement of work. Specific to the client, created under this engagement.
• Pre-Existing Materials — anything you owned or developed before the engagement, anything you develop outside it, and anything generic you develop during it: frameworks, libraries, utilities, patterns, deployment tooling, internal know-how and the general skills of your people.

The third category is the one templates miss. If you write a generic date-handling utility while building the client’s invoicing module, is it a deliverable? Under the buyer’s template it probably is. Define Pre-Existing Materials to include materials of general application developed during the engagement, and the problem disappears without anyone arguing about it.

Assignment on payment

Templates say assignment happens “upon creation”. That means the client owns the work before it has paid for it, and if the relationship ends badly your leverage is a debt claim rather than an asset.

“Upon payment in full of the fees relating to the relevant Deliverable” is the version to ask for. It is not aggressive — a client that intends to pay loses nothing — and procurement teams generally accept it. Pair it with an interim licence: until assignment takes effect, the client has a licence to use the deliverable for the purposes of the project. Without that, a client who has paid ninety per cent of an invoice technically cannot deploy, which is not a conversation anybody wants.

The licence back, and what it has to cover

The licence over your Pre-Existing Materials is where deals stall, usually because the first draft is too narrow. Make it perpetual, irrevocable, worldwide, non-exclusive, royalty-free, and — this is the one people forget — sublicensable to the client’s affiliates and assignable with the business. Include the right to modify and to have third parties modify on the client’s behalf.

That last right is what a careful buyer is really testing. They want to know that if they replace you, the next supplier can work on the system. A licence that permits use but not modification by a third party is a lock-in clause, and buyers who spot it will escalate.

Open source in the deliverables

Almost every deliverable contains third-party open-source components, and almost every enterprise template contains a warranty that the deliverables do not infringe third-party rights and were not encumbered by open-source licences. Both cannot be true at once.

The workable position: you warrant that open-source components are used in compliance with their licences, and that no component subject to a copyleft licence has been incorporated in a way that would require the client to disclose its own source code. Attach a list of components and licences, and commit to keeping it current. Buyers accept this because it is what their own engineering teams expect, and because a blanket “no open source” warranty from a software supplier is not credible.

Moral rights and the EU wrinkle

In most EU jurisdictions an author’s moral rights — attribution and integrity of the work — cannot be assigned, and in several they cannot be waived either. An English-law template will contain a moral-rights waiver that simply does not operate in Germany, Poland or France.

This rarely causes a commercial problem, but it does cause a drafting problem: a clause that purports to do something impossible casts doubt on the clause around it. The practical version is a covenant not to assert moral rights to the extent permitted by applicable law, rather than a waiver. It achieves the same commercial outcome and does not require anyone to pretend.

The same point applies to your own people. Where the authors are employees, most EU systems vest economic rights in the employer by operation of law or by standard employment terms. Where the authors are B2B contractors — which in CEE software houses is often most of the team — nothing vests automatically, and the assignment has to be in the contractor agreement.

Aligning with your subcontractor agreements

This is the failure that actually costs money. Your client MSA assigns all deliverables to the client. Your contractor agreement says nothing about IP, or says it in one sentence copied from a template. You have promised something you do not own, and you will not discover it until a diligence process or a dispute.

Work the chain backwards. Whatever the client MSA obliges you to assign, the contractor agreement must assign to you, in at least the same scope, at least as early, and on terms at least as durable. Add the licence too: if you grant the client a licence over pre-existing materials that a contractor brought with them, you need the right to grant it.

Poland is the jurisdiction that punishes shortcuts here. Polish copyright law requires an assignment to specify the fields of exploitation — the pola eksploatacji — and an assignment that does not enumerate them is ineffective as to the fields it omits. A one-line “Contractor assigns all rights” clause is not enough. Estonian and English law are more forgiving, but if any part of your team contracts under Polish law, the enumeration has to be there.

What to concede

Not everything is worth fighting. Concede exclusivity over the deliverable itself — you should not be reselling the client’s bespoke module anyway. Concede a broad warranty that you have the right to assign what you are assigning, because you should. Concede assistance with registrations and formalities at the client’s cost. And concede the client’s right to use your name as a reference only if you actually want the reference; it is a small thing to trade for something larger.