Intellectual Property Clause in an SOW: Assignment or License – Complete 2026 Guide

Why the IP Clause Is the Most Strategic Clause in an SOW

When a company commissions software development, research, design, or any other intellectual service from a freelancer or B2B service provider, it typically signs a Statement of Work (SOW). This contractual document details deliverables, timelines, and budget. Yet one clause often goes unnoticed despite conditioning 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 a dispute, funding round, or company acquisition forces a costly resolution. In France, Article L.111-1 of the Intellectual Property Code (CPI) establishes the principle that copyright is born with the creator. This principle applies equally to employees (with modifications) and to freelancers or external service providers: absent a contrary clause, the service provider remains the copyright holder of their creations.

In 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 transfer mechanism (assignment or license), geographic and temporal extent, and the fate of pre-existing works (background IP).

Assignment vs. License: Two Legally Distinct Mechanisms

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

• the nature of assigned rights (reproduction, public performance, adaptation, translation, distribution, etc.);
• geographic scope (France, European Union, worldwide);
• duration (limited to 70 years post-mortem of the author maximum, per art. L.123-1 CPI);
• purpose (commercial use, SaaS, resale, integration into a third-party product, etc.).

Omission of even one of these elements renders the assignment unenforceable regarding the unmentioned right. This legal formalism is frequently underestimated in hastily drafted SOWs.

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

Source Code and Software: A Special Legal Regime

Software is an intellectual work under 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 performance of an employment contract (art. L.113-9 CPI). Conversely, for an independent service provider, moral rights remain intact and inalienable.
• Delivery of source code is distinct from assignment of rights over that code. A client can receive an executable without ever holding the source code or adaptation rights. The IP clause must therefore distinguish: functional deliverables, source files, technical documentation, deployment scripts, databases.
• Third-party open source libraries integrated into the deliverable (React, PostgreSQL, TensorFlow…) remain subject to their own licenses (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 licenses, lest it create a warranty obligation impossible to honor.

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

Structuring the IP Clause in an SOW: Five Essential Building Blocks

A robust IP clause in a B2B SOW revolves around five distinct blocks. Overlooking them leaves blind spots that transform into disputes.

1. Definition of the Scope of Covered Deliverables

The first block precisely lists what the clause covers: source code, mockups, databases, algorithms, documentation, unit tests, automation scripts. The formula "all deliverables produced under 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, broad enough to encompass successive versions and patches.

2. Background IP Clause (Pre-Existing Works)

Every service provider brings reusable building blocks to each engagement: in-house frameworks, generic modules, proprietary libraries. These elements constitute 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 over this background IP;
• Grant the client a limited license of use over background IP insofar as necessary for exploitation of the deliverable.

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

3. Transfer Mechanism and Suspensive Conditions

In B2B practice, assignment of rights is often subordinated to full payment of the fee. This classic suspensive condition protects the service provider but must be drafted carefully: if not explicit, settled case law deems rights transferred upon delivery (Cass. 1st civ., Oct. 14, 2010, appeal no. 09-16.385).

The clause must specify:

• The transfer date (delivery, acceptance, full payment);
• Any formalities (separate assignment deed, INPI filing);
• The fate of rights in case of contract termination for fault.

The AI-powered contract generator by Certyneo offers parameterizable IP clause templates depending on deliverable type and chosen transfer model.

4. Warranties of Originality and Indemnification

The service provider must warrant that deliverables are original (per art. L.111-1 CPI), do not borrow from third-party works without authorization, and violate no patent, trade secret, or competing right. This eviction warranty must be supplemented by an indemnification obligation for the client in case of third-party claims, with a reasonable cap (often equal to the SOW amount).

5. Moral Rights and Attribution Notices

Moral rights are perpetual and inalienable under French law (art. L.121-1 CPI). The service provider may, however, contractually waive the exercise of certain prerogatives—notably the right to attribution of authorship on the deliverable. This waiver must be explicit and limited: one does not waive moral rights wholesale; 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 alters the drafting of the IP clause.

Freelancer (sole trader or individual enterprise): the creator is a natural person, copyright holder in their own right. Assignment must scrupulously comply with formalism in art. L.131-3 CPI. Moral rights are fully active. The risk of recharacterization as an employment contract (and thus application of art. L.113-9 CPI for software) exists if subordination is established.

Service provider company (SARL/SAS): the company is not an author under the CPI—its employees are. The corporate service provider must therefore contractually guarantee that it has itself obtained assignment (or license) from its employee-authors. A clause stating "the service provider warrants it holds all necessary rights to consent to this assignment" is insufficient unless backed by adapted employment contracts.

These subtleties justify having the IP clause in an SOW reviewed by a specialized legal counsel before signing. The electronic signature solution for law firms by Certyneo facilitates validation and signature of these complex contracts in streamlined workflows.

Best Practices for 2026: Operational IP Rights Management

Annex 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 licenses. This practice, recommended by ANSSI in its secure development guides, reduces the risk of license violation (notably GPL contamination) and facilitates due diligence during funding rounds or company sales.

Plan a Probative Deposit Mechanism

Depositing the work with INPI (via the Certyneo INPI hub) or with a trusted third party creates a presumption of creation date and priority. In case of dispute over authorship or originality of a deliverable, this deposit constitutes evidence opposable to third parties.

Audit and Verification Clause

For long-term missions or master service agreements, embed a clause allowing the client to have the source code audited by an independent third party—without this constituting a violation of the service provider's trade secrets—reinforces trust and prevents late disputes over deliverable compliance.

Electronic Signature and Traceability

An SOW containing a sensitive IP clause must be signed with maximum evidentiary value. Use of an advanced or qualified electronic signature compliant with eIDAS creates qualified timestamping and cryptographic fingerprinting of the document, making any subsequent alteration detectable. This traceability is determinative when the IP clause is invoked years after signature.

Applicable Legal Framework for the IP Clause in an SOW

French Intellectual Property Code (CPI)

The IP clause in an SOW falls within the framework of the French Intellectual Property Code, whose mandatory provisions cannot be waived by contract:

• Art. L.111-1 CPI: copyright is born with the creator upon work creation, without formality. This principle is cardinal: absent a clause, the service provider remains copyright holder.
• Art. L.113-9 CPI: for software created by employees in the performance of their duties, proprietary rights are automatically vested in 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 not subject to limitation. Only the exercise of certain prerogatives may be subject to limited contractual waiver.
• Art. L.131-3 CPI: any assignment of proprietary rights must mention each right assigned, its scope, its purpose, its place and duration, on pain of partial unenforceability.
• Art. L.122-6 CPI: specific software rights include reproduction, translation/adaptation, any form of distribution, and putting on the market.

General Contract Law

The SOW is a contract for work (art. 1710 French Civil Code) subject to general law of obligations. Article 1103 C.civ. reminds us that "contracts lawfully formed are binding on those who made them." The IP clause cannot derogate from public order provisions of the CPI, but it may freely arrange the conditions for transfer of proprietary rights.

eIDAS Regulation No. 910/2014 and Electronic Evidence

Electronic signature of the SOW is governed by eIDAS Regulation No. 910/2014 (art. 25: legal effect of electronic signature) and, in French law, by articles 1366 and 1367 of the French Civil Code regarding electronic documents and electronic signature. A qualified electronic signature enjoys an irrebuttable presumption of reliability and has the same evidentiary force as a handwritten signature. It guarantees document integrity and signer identity, elements essential when the IP clause is invoked in court.

Risks from Absent or Deficient Clauses

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

Usage Scenarios: The IP Clause in Real Situations

Scenario 1 — A Scale-Up SaaS Outsources Backend Development

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

Eighteen months later, during Series A fundraising, the investor's counsel discovers in due diligence that the API integrates an undeclared LGPL library, and the rights assignment is partially unenforceable due to missing legal mentions. Closing is delayed six weeks. Regularization costs (new assignment deed, SBOM audit, library replacement) total approximately €18,000, not counting valuation renegotiation risk.

Lesson: a complete IP clause and SBOM annex from SOW signature would have prevented this blockage. According to sector reports on tech M&A, IP chain defects represent 15% to 25% of causes of closing delay in transactions below €10M.

Scenario 2 — A Consulting Firm Orders Training Deliverables from a Freelancer

A consulting firm of about twenty consultants orders e-learning training support creation (videos, slides, interactive quizzes) from a freelance graphic designer via a €12,000 SOW. The IP clause provides for assignment, but the right to modify 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 of integrity remains intact, objects, deeming that modifications distort her work. A settlement agreement is concluded for an additional €4,500.

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

Scenario 3 — An Industrial SME Integrates Custom Software into Its Production Line

An 80-person industrial SME orders manufacturing execution system (MES) software from an integrator. The SOW provides for an exclusive license but does not specify whether the client can evolve the software itself or through a third party after contract maintenance ends.

Three years later, the integrator closes. The SME loses access to source code and lacks contractual rights to entrust maintenance to another service provider. Operational restoration requires partial rewrite estimated at €60,000, corresponding to production downtime of several weeks.

Lesson: for critical industrial software, the IP clause must imperatively include an escrow clause for source code (deposit with a trusted third party) and an explicit right to third-party maintenance in case of service provider failure. These clauses are now recommended by professional IT federations (Syntec Numérique) for any specific development exceeding €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 2026 IP clause remain invariant: exhaustively define covered deliverables, choose and formalize the transfer mechanism (assignment or license) respecting formalism in art. L.131-3 CPI, and anticipate background IP and third-party component fate.

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

Get started free at [certyneo.com/signup](/signup) and secure your next service contracts with the traceability they deserve.