Intellectual Property Clause in a SOW: Assignment or Licence in 2026

Why the IP clause is the most strategic clause in a SOW

When a company commissions software development, a study, a design or any other intellectual service from a freelancer or B2B service provider, it generally signs a Statement of Work (SOW). This contractual document details the deliverables, timelines and budget. Yet, one clause often goes unnoticed even though it determines the entire economic value of the transaction: the intellectual property clause (IP clause).

Without precise drafting of this clause, the answer to the question "who owns the delivered source code?" can remain legally ambiguous for years — until the day a dispute, a fundraising round or a company sale forces an expensive resolution. In France, article L.111-1 of the Intellectual Property Code (CPI) establishes the principle that copyright is created on the head of the creator. This principle applies to both employees (with adjustments) and freelancers or external service providers: in the absence of a contrary clause, it is the service provider who remains the holder of rights over their creations.

Within the framework of a well-structured SOW, the IP clause is not limited to a single line stating "rights are assigned to the client". It must specify the exact scope of deliverables, the mode of transfer (assignment or licence), the geographical and temporal extent, as well as the fate of pre-existing works (background IP).

Assignment vs Licence: two legally distinct mechanisms

Assignment of patrimonial rights (art. L.131-3 CPI) permanently transfers to the assignee the ownership of rights in the deliverable. The service provider loses all control over the future exploitation of the work. To be valid, the assignment must explicitly mention:

• the nature of rights assigned (reproduction, performance, adaptation, translation, distribution, etc.);
• the geographical extent (France, European Union, worldwide);
• the duration (limited to 70 years post-mortem of the author at most, according to art. L.123-1 CPI);
• the destination (commercial use, SaaS, resale, integration into a third-party product, etc.).

The omission of even one of these elements makes the assignment unenforceable with respect to the right not mentioned. This legal formality is frequently underestimated in hastily drafted SOWs.

Licence is less drastic: the service provider retains intellectual property ownership but grants the client a defined right of use. The licence may be exclusive or non-exclusive, revocable or irrevocable, free or paid. In a B2B software development context, an exclusive irrevocable licence with no duration limitation can produce effects practically equivalent to an assignment, whilst allowing the service provider to retain their moral rights.

Source code and software: a particular legal regime

Software is an intellectual work within the meaning of the CPI (art. L.112-2, 13°), but it benefits from a derogatory regime on several points:

• Moral rights are considerably weakened for software created in execution of an employment contract (art. L.113-9 CPI). Conversely, for an independent service provider, moral rights remain full and inalienable.
• The delivery of source code is distinct from the assignment of rights over that code. A client may receive an executable without ever holding the source code, nor adaptation rights. The IP clause must therefore distinguish: functional deliverable, source files, technical documentation, deployment scripts, databases.
• Third-party open source libraries integrated into the deliverable (React, PostgreSQL, TensorFlow…) remain subject to their own licences (MIT, Apache 2.0, GPL). An IP clause cannot transfer rights that the service provider does not hold. The clause must therefore include a list of third-party components and their licences, otherwise it creates a warranty obligation that is impossible to fulfil.

To secure these operations, recourse to qualified electronic signature guarantees the integrity and certain date of the signed SOW, elements that are decisive in case of judicial dispute.

Structuring the IP clause of a SOW: the essential building blocks

A robust IP clause in a B2B SOW is articulated around five distinct blocks. To forget them is to leave blind spots that transform into litigation.

1. Definition of the scope of deliverables covered

The first block precisely lists what the clause covers: source code, mockups, databases, algorithms, documentation, unit tests, automation scripts. The phrase "all deliverables produced in the context of this SOW" is insufficient: it does not cover derivative works created after final delivery or iterative improvements to an initial deliverable.

Provide a contractual definition of the term "Deliverable" at the head of the SOW, sufficiently broad to encompass successive versions and bug fixes.

2. Background IP clause (pre-existing works)

Every service provider brings reusable components to each mission: in-house frameworks, generic modules, proprietary libraries. These elements constitute the background IP or pre-existing IP. The clause must clearly:

• Identify the background IP that the service provider brings;
• Confirm that the client acquires no rights to this background IP;
• Grant the client a limited right of use of the background IP to the extent necessary for the exploitation of the deliverable.

Without this block, a service provider could theoretically claim the destruction of the delivered product because it integrates a module over which they retain ownership — and for which no assignment has been granted.

3. Transfer mechanism and suspensive conditions

In B2B practice, the assignment of rights is often conditional upon full payment of the price. This classic suspensive condition protects the service provider but must be drafted carefully: if not explicit, consistent case law considers that rights are transferred upon delivery (Cass. 1st civ., 14 October 2010, appeal no. 09-16.385).

The clause must specify:

• The date of transfer (delivery, acceptance, full payment);
• Any formalities (separate assignment deed, INPI registration);
• The fate of rights in the event of contract termination for default.

The AI-powered contract generator from Certyneo proposes parameterisable IP clause models according to the type of deliverable and the transfer model chosen.

4. Warranties of originality and indemnification

The service provider must warrant that the deliverables are original (within the meaning of art. L.111-1 CPI), do not borrow from third-party works without authorisation, and do not infringe any patent, trade secret or competing right. This warranty of non-infringement must be supplemented by an obligation to indemnify the client in the event of third-party claims, with a reasonable cap (often equal to the amount of the SOW).

5. Moral rights and author attribution

Moral rights are perpetual and inalienable under French law (art. L.121-1 CPI). The service provider may nonetheless contractually waive the exercise of certain prerogatives — notably the right to attribution of their name on the deliverable. This waiver must be explicit and limited: one does not waive moral rights in bulk; one contractually restricts their exercise case by case.

Freelancer vs service provider company: impact on the IP clause

The legal nature of the service provider materially modifies the drafting of the IP clause.

Freelancer (micro-entrepreneur or sole trader): the creator is a natural person, holder of copyright rights in a personal capacity. The assignment must scrupulously comply with the formalities of art. L.131-3 CPI. Moral rights are fully active. The risk of reclassification as an employment contract (and thus application of art. L.113-9 CPI for software) exists if subordination is established.

Service provider in LLC/SAS: the company is not an author within the meaning of the CPI — its employees are. The service provider company must therefore contractually warrant that it has itself obtained the assignment (or licence) from its employee authors. A clause such as "the service provider warrants that it holds all necessary rights to consent to the present assignment" is insufficient unless relayed by adapted employment contracts.

These subtleties justify that the IP clause of a SOW be reviewed by a specialist lawyer before signature. Certyneo's electronic signature solution for law firms facilitates the validation and signature of these complex contracts in a streamlined circuit.

Best practices in 2026 for operational management of IP rights

Append the list of third-party components

Every software development SOW should integrate a Software Bill of Materials (SBOM) annex, listing all open source components used, their versions and their licences. This practice, recommended by ANSSI in its secure development guides, reduces the risk of licence violation (particularly GPL contamination) and facilitates due diligence during fundraising rounds or company sales.

Provide for a mechanism of probative deposit

Deposit of the work with INPI (via Certyneo's INPI hub) or with a trusted third party creates a presumption of creation date and priority. In the event of a dispute over the authorship or originality of a deliverable, such deposit constitutes evidence enforceable against third parties.

Audit and verification clause

For long-duration missions or framework contracts, integrate a clause allowing the client to have the source code audited by an independent third party — without this constituting a breach of the service provider's trade secrets — strengthens trust and prevents late disputes over deliverable compliance.

Electronic signature and traceability

A SOW containing a sensitive IP clause must be signed with maximum evidential value. The use of an advanced or qualified electronic signature compliant with eIDAS creates qualified timestamping and a cryptographic fingerprint of the document, making any subsequent alteration detectable. This traceability is decisive when the IP clause is invoked years after signature.

Legal framework applicable to the IP clause in a SOW

Intellectual Property Code (CPI)

The IP clause of a SOW falls within the framework of the French Intellectual Property Code, whose mandatory provisions cannot be set aside by contract:

• Art. L.111-1 CPI: copyright is created on the head of the creator upon creation of the work, without formality. This principle is cardinal: in the absence of a clause, the service provider remains the holder.
• Art. L.113-9 CPI: for software created by employees in the exercise of their duties, patrimonial rights are assigned by operation of law to the employer. This regime does not apply to independent service providers.
• Art. L.121-1 CPI: moral rights (attribution, integrity, disclosure) are perpetual, inalienable and imprescriptible. Only the exercise of certain prerogatives may be the subject of a limited contractual waiver.
• Art. L.131-3 CPI: any assignment of patrimonial rights must mention each right assigned, its extent, its destination, its place and its duration, on pain of partial unenforceability.
• Art. L.122-6 CPI: specific rights for software include reproduction, translation/adaptation, any form of distribution and putting on the market.

Common law of contracts

The SOW is a contract for work (art. 1710 of the Civil Code) subject to the common law of obligations. Art. 1103 C.civ. recalls that "contracts validly entered into have the force of law for those who made them". The IP clause cannot derogate from the mandatory provisions of the CPI, but it may freely arrange the conditions of transfer of patrimonial rights.

eIDAS Regulation No. 910/2014 and electronic evidence

The electronic signature of the SOW is governed by eIDAS Regulation No. 910/2014 (art. 25: legal effect of electronic signature) and, under French law, by articles 1366 and 1367 of the Civil Code relating to electronic writing and electronic signature. A qualified electronic signature benefits from an irrebuttable presumption of reliability and has the same evidential force as a handwritten signature. It guarantees the integrity of the document and the identity of the signatory, elements that are essential when the IP clause is invoked in court.

Risks if clause is absent or deficient

• Risk of blocked exploitation: the client cannot legally exploit the deliverable without the author's permission.
• Risk of third parties claiming rights: an employee of the service provider may claim rights if internal contracts are deficient.
• Risk in due diligence: upon fundraising or M&A, the absence of a clear IP clause on software assets may result in a discount, conditional earn-out or abandonment of the transaction.
• Risk of open source licence violation: the undeclared integration of components under GPL licence can contaminate the entire delivered software (copyleft effect), obliging disclosure of source code in open source.

Use scenarios: the IP clause in real situations

Scenario 1 — A SaaS scale-up outsources its backend development

A French scale-up specialising in vehicle fleet management employs around ten developers and outsources the development of its billing API to an independent service provider (SASU). The SOW provides for an assignment "of all rights in the deliverables" but mentions neither geographical extent nor duration, and does not list the integrated open source components.

Eighteen months later, during a Series A fundraising round, the investor's lawyer realises in due diligence that the API integrates an undeclared LGPL-licenced library, and that the rights assignment is partially unenforceable for lack of legal mentions. The closing is delayed by six weeks. The costs of regularisation (new assignment deed, SBOM audit, library replacement) amount to approximately EUR 18,000, without counting the risk of valuation renegotiation.

Lesson: a complete IP clause and SBOM annex from the SOW signature onwards would have avoided this blockage. According to sector reports on tech M&A, IP chain defects account for between 15% and 25% of causes of closing delay in transactions below EUR 10 million.

Scenario 2 — A consulting firm commissions training deliverables from a freelancer

A consulting firm specialising in digital transformation with around twenty consultants commissions a freelance graphic designer to create e-learning training materials (videos, slides, interactive quizzes) via a SOW for EUR 12,000. The IP clause provides for an assignment, but the right to modify the materials (adaptation for other clients) is not explicitly mentioned.

Six months after delivery, the firm wishes to resell these adapted materials to a banking sector client. The freelancer, whose moral right to the integrity of the work remains intact, objects, arguing that the modifications distort their work. A settlement agreement is concluded for an additional EUR 4,500.

Lesson: the absence of a clause waiving the exercise of the right of integrity and an explicit right to commercial adaptation generated an unforeseen cost of 37% of the initial SOW amount. Precise drafting of the scope of assignment (including the right to adaptation and commercialisation to third parties) is non-negotiable for deliverables with strong reuse potential.

Scenario 3 — An industrial SME integrates bespoke software into its production line

An industrial SME with 80 employees commissions an integrator to develop production line supervision software (MES). The SOW provides for an exclusive licence of use but does not clarify whether the client may itself or through a third party evolve the software after the maintenance contract ends.

Three years later, the integrator ceases operations. The SME finds itself without access to the source code and without a contractual right to entrust its maintenance to another service provider. Operational restoration requires partial rewriting estimated at EUR 60,000, corresponding to production downtime of several weeks.

Lesson: for business-critical software, the IP clause must imperatively include an escrow clause for source code (deposit with a trusted third party) and an explicit right to maintenance by a third party in the event of service provider failure. These clauses are now recommended by professional IT federations (Syntec Numérique) for any specific development above EUR 20,000.

Conclusion

The intellectual property clause is the strategic heart of any SOW involving digital deliverables. It determines who truly owns the created value: without precise drafting, the client exploits without clear title, and the service provider faces future claims. The three pillars of a solid IP clause in 2026 remain constant: exhaustively define the deliverables covered, choose and formalise the transfer mechanism (assignment or licence) in compliance with the formalities of art. L.131-3 CPI, and anticipate the fate of background IP and third-party components.

Signed with an eIDAS-compliant electronic signature solution, the SOW becomes a document with maximum evidential value, enforceable in all circumstances. Certyneo allows you to sign, timestamp and archive your SOWs in minutes, with a validation circuit parameterisable for your legal and procurement teams.

Start free on [certyneo.com/signup](/signup) and secure your next service provision contracts with the traceability they deserve.