A contractor agreement for a French tech startup sets the scope of work, IP assignment, payment terms and termination rules for an independent freelancer or consultant, with the goal of avoiding a URSSAF reclassification claim and locking down ownership of the code, design or model the contractor builds. A startup running a rotating bench of freelance developers carries a sharper risk profile than a SaaS company with one long-term contractor: more handoffs, more IP transfers, more hours that start looking like full-time work.
- A contractor agreement for a French startup must state scope, IP transfer and independence markers to survive a 2026 URSSAF audit.
- Missing IP assignment clauses are the most common defect in founder-drafted freelance contracts.
- Generic templates skip the cession de droits clause French copyright law requires, leaving code ownership with the freelancer.
- Lina drafts a fixed-fee contractor agreement with senior lawyer sign-off, typically delivered within 36 hours.
Why this matters
French labor law presumes independence for a registered freelancer under Article L.8221-6 of the Labor Code, but that presumption flips the moment URSSAF finds a lien de subordination: fixed hours, one exclusive client, tools and badge access supplied by the company. Reclassification turns the "contractor" into a retroactive employee, with back pay and social charges assessed from day one. One reclassification finding during a funding round's due diligence can cost more than every contractor invoice combined, and it stalls the round.
Why contractor agreements matter for French tech startups
A generic US-style independent contractor template doesn't hold up in France: it skips the cession de droits clause, ignores the URSSAF independence test, and rarely accounts for GDPR when a freelancer touches production data. A startup building an MVP with freelance developers, or scaling an AI product with contract engineers, needs a freelance contract for tech startups that treats IP transfer as the default clause, not an afterthought.
VCs check contractor status and IP chain of title during Series A due diligence in 2026. A defective contractor agreement turns into a closing condition on the term sheet, not a footnote in the data room.
1. Confirm the contractor is genuinely independent, not disguised employment
- Check the contractor invoices under their own SIRET, EURL or SASU, not through your payroll.
- Confirm they serve other clients, not just your startup exclusively.
- Let them choose their own hours and tools; no fixed 9-to-5 badge access.
- Skip the company email address and org-chart title.
- Document these facts in the contract's preamble, not just verbally.
“If a contractor works exclusive hours under your daily instructions, URSSAF calls that an employee, no matter what the contract says.”
2. Scope the deliverable, not the hours
- Write scope as a deliverable, "build and deploy the payments API," not a time block, "40 hours a week."
- Set milestones tied to acceptance criteria, not attendance.
- Cap revision rounds per deliverable, two rounds is a reasonable default, to block scope creep.
- Keep one-off project work and any ongoing retainer in separate agreements.
3. Assign the IP explicitly, because French copyright law does not do it automatically
French intellectual property law grants authorship rights to the individual creator by default, even when paid, and a services contract alone does not transfer copyright. Founders need a standalone cession clause naming the works, scope of use, territory and duration.
- Name every deliverable class covered by the transfer: code, documentation, designs, trained models.
- State the assignment is exclusive and worldwide, not limited to France.
- Cover future improvements the contractor makes to the code, not just the first delivery.
- Waive moral rights attribution where the law permits it, particularly on internal tools.
- Tie the transfer date to payment, not to contract signature.
Founders drafting this clause alone often copy language from a generic template that never mentions cession de droits. The deliverable gets built, the invoice gets paid, and the code stays the freelancer's copyright on paper. Lina fixes the clause list before the freelancer starts, with a fixed fee agreed within one hour and senior lawyer sign-off on the final draft.
4. Add a data processing clause when the contractor touches personal data
- List which personal data categories the contractor can access: users, employees, prospects.
- Define retention and deletion timelines after the contract ends.
- Require the contractor to flag any sub-subcontractor before onboarding.
- Set breach-notification timelines that match your own DPA with customers.
- Reference the legal basis under which the contractor processes the data.
Founder-stage contracts often default to a generic confidentiality clause and skip this layer entirely. A GDPR subprocessing agreement for tech providers closes that gap for any contractor who touches production data.
5. Set payment terms that match the contractor's real status
- Require an invoice with a SIRET number, not a payslip.
- Set net payment terms, 30 days is standard, in line with France's commercial payment rules.
- State the contractor bears their own social charges and VAT status.
- Pay per deliverable or milestone, not by the hour.
- Add statutory late-payment interest to protect both sides.
6. Add confidentiality and non-solicitation, sized to the actual risk
- Cover both directions: the contractor protects your data, you protect their rate and methods.
- Set a non-solicitation period, 12 to 24 months is standard for early-stage teams, on staff and clients the contractor meets on the project.
- Skip a broad non-compete on a true independent contractor; French courts strike these down more readily than on employees.
- Carve out the contractor's pre-existing IP and any open-source components they bring in.
7. Set termination and liability terms before the relationship starts
- Define a notice period for termination without cause, 15 to 30 days is common.
- Cap liability to a multiple of fees paid, not unlimited exposure.
- List for-cause termination triggers: missed milestones, IP disputes, breach of confidentiality.
- State what happens to unfinished work product and access credentials on exit.
The same termination logic that governs a commercial contract termination agreement applies here: a clean exit clause protects the startup as much as the ongoing scope clause does.
8. Sign, store and reuse the template
- Get e-signature from both parties with the contractor's SIRET or company registration attached.
- Store the signed contract and IP assignment in your data room ahead of any funding round.
- Tag the contract to the specific deliverable or project it covers, for audit trail.
- Build one reusable base template so IP and independence clauses don't get diluted contractor to contractor.
Compare your options for a French startup contractor agreement
| Option | Best for | Key limitation |
|---|---|---|
| DIY or free template | Pre-seed founders testing one freelancer | No cession de droits clause, no France-specific independence language |
| Generic online contract generator | Recurring low-risk gigs, small design tweaks | Boilerplate GDPR clause, weak on French reclassification risk |
| General business lawyer, hourly | One-off, complex contractor deal | Hourly billing, slower turnaround, may lack startup or tech specialization |
| Lina fixed-fee contractor agreement | Startups onboarding freelance developers or designers ahead of a funding round | Requires sharing deliverable scope upfront to fix the fee |
Verdict: a free template is fine for a one-off logo tweak; a startup onboarding a freelance engineer ahead of a priced round needs the IP and independence clauses locked, and that's where a fixed-fee contractor agreement from Lina earns its cost. Buy the specialist draft once IP and funding are both in play; DIY only when the stakes are genuinely low.
Common mistakes French tech startups make
- Treating a full-time freelance developer like an employee, fixed hours, company laptop, a "team" role on Slack, then reacting with surprise to a URSSAF reclassification notice.
- Reusing a US-style independent contractor template that never mentions cession de droits, leaving code copyright with the freelancer.
- Skipping the GDPR processing clause when a contractor gets production database access for a bug fix.
- Signing contractor deals in English only with no French governing-law clause, then discovering a French court applies mandatory French provisions regardless.
- Letting a contractor invoice without a SIRET number, a gap that by itself can flag a URSSAF audit.
Get your contractor agreement fixed-fee
Scope, price and delivery date agreed within one hour.
FAQ
What's the best way to draft a contractor agreement for a French tech startup in 2026?
Start with scope, IP assignment and independence markers, then add GDPR and termination clauses if the contractor touches customer data. A fixed-fee specialist draft closes the gaps a generic template leaves open, particularly the cession de droits clause French law requires.
Is a French freelance contractor treated as an employee under French law?
Not by default. A registered freelancer is presumed independent under Article L.8221-6 of the Labor Code, but URSSAF can reclassify the relationship if it finds fixed hours, exclusivity or company-supplied tools.
Do I need a written IP assignment clause for freelance developers in France?
Yes. French copyright law grants authorship rights to the individual by default even when paid, so a services contract alone does not transfer ownership of the code or design.
How much notice does a startup need to give to end a contractor agreement in France?
There's no fixed statutory minimum for a commercial contractor relationship, but 15 to 30 days notice for termination without cause is standard practice in 2026 tech contracts.
Can a non-compete clause bind an independent contractor in France?
Broad non-competes on true independent contractors are struck down more readily by French courts than clauses on employees. A narrower non-solicitation clause on staff and clients holds up better.
Does GDPR apply to freelance contractors who access customer data?
Yes. Any contractor processing personal data as a subprocessor needs a data processing clause covering retention, deletion and breach notification, matching your own commitments to customers.
How fast can Lina turn around a contractor agreement?
Lina responds within 30 minutes, gives a fixed-price quote within one hour, and typical delivery runs around 36 hours, with senior lawyer sign-off on the final draft.
What happens if URSSAF reclassifies a contractor as an employee?
The relationship is treated as employment retroactively, meaning back pay, social charges and penalties from the actual start date of the work, not the reclassification date.
One last thing
Founders rarely think about the exit clause when the IP transfer clause is what actually matters. If the cession de droits is tied to contract signature instead of final payment, and the last invoice never gets paid, the contractor can argue the transfer never completed and the code stays theirs on paper. Tie the IP assignment to payment, every time, not to the date both parties signed.
