Freelancer or employee in a startup: managing reclassification risk

Freelancers offer startups valuable agility. But if the relationship conceals a relationship of subordination, it may be reclassified as employment, with major employment, financial and criminal consequences. Here is how to assess, anticipate and manage the risk in practice.

1) The legal framework: reality prevails over labels

Under French law, the classification of a working relationship depends on its reality, not the contract's title. The Cour de cassation defines subordination as performing work under an employer's authority, with the power to give orders and instructions, monitor performance and sanction breaches (Cass. soc., 28 nov. 2018, n°17-22.148).

The fight against undeclared work — including concealed employment — is governed by the Labour Code (art. L.8221-5). Inspection authorities (URSSAF/DREETS) may reclassify relationships and impose reassessments based on a combination of factual indicators (DREETS – URSSAF inspections of disguised employment). At European level, the CJEU has reiterated that assessment concerns the actual working conditions, including on platforms (CJUE, 20 déc. 2017, C‑434/16, Uber).

In practice, URSSAF is intensifying inspections and recoveries from businesses, including startups (URSSAF – 2024 activity report).

2) Combined indicators: red flags vs. safer territory

Red flags (high reclassification risk)

• Imposed working hours, mandatory daily/weekly meetings as for an employee.
• Provided tools and internal accounts (badge, named company email, HR/IT access) without contractual justification.
• Hierarchical reporting and constant supervision (JIRA tickets assigned by a manager, prior approval of methods).
• De facto exclusivity (near-total availability), no other clients.
• Time-based remuneration with daily hours approval and MBO targets/bonuses like employees.
• Integration into the organisation chart (job title, managing internal teams, participation in HR routines).

Indicators of independence (reduced risk)

• Autonomy over methods and organisation (no imposed hours, no unilaterally imposed on-call duties).
• Precise scope and defined deliverables in the contract, fixed-fee or milestone-based remuneration.
• The freelancer's own tools and equipment, restricted and proportionate access at the client (need-to-know principles).
• Multiple clients, external communications in their own name (website, SIREN), subcontracting permitted.
• Limited integration into internal processes (no named internal email address, no permanent badge).

The Ministry of Labour notes that independent workers organise their work freely and bear their business's economic risk.

3) Consequences of reclassification for the startup

• Employment and payroll: back pay (overtime, paid leave), reinstated seniority, termination payments.
• URSSAF: retrospective employer/employee contributions, surcharges and penalties, possible multi-year reassessments (DREETS/URSSAF).
• Workplace accidents/occupational diseases (AT-MP): exposure to inexcusable fault claims and CPAM recovery actions.
• Criminal: possible classification as undeclared work (fine, ancillary penalties), under the Labour Code (Légifrance).
• Reputation and governance: workforce tensions, reputational risk with investors and clients.

4) Preventing risk: a 5-step method

Step 1 — Choose the right status before the assignment

If the need involves daily management, set hours and integration into team routines, prefer a fixed-term/permanent employment contract (CDD/CDI) to a freelancer. To decide according to workload, deadlines and budget, see our guide to choosing between CDD and CDI in a startup.

Step 2 — Check freelancer status and your due diligence obligations

• Check registration (SIREN/Kbis), address and activity.
• URSSAF compliance certificate (attestation de vigilance) mandatory once the total assignment exceeds €5,000 excluding VAT, for each provider (URSSAF – Compliance certificate). Renew it every 6 months.
• Collect and retain quotes and invoices to demonstrate a genuine independent service.

Step 3 — A robust services agreement

Draft a contract focused on scope and deliverables (not occupying time), with:

• Clear scope, milestones, acceptance criteria, intellectual property and appropriate assignments of rights.
• Fixed-fee remuneration (or per work package), with limited expenses and review arrangements.
• Independence clause, no subordination, no exclusivity, ability to subcontract (subject to quality/confidentiality controls).
• Access to tools strictly as necessary, security and confidentiality.
• Termination (notice, breaches), liability and insurance.

To save time and secure drafting, consult our guide to services agreements: clauses and points to watch.

Step 4 — Operational organisation without subordination

• No imposed hours; prefer milestones and deliverables to mandatory daily meetings.
• Avoid named internal emails and permanent badges; restricted and temporary access.
• The freelancer's tools and equipment by default; justify and limit any client equipment.
• No HR-style appraisals or disciplinary sanctions: use contractual mechanisms (withholding, rejection of deliverables, termination).
• Periodic invoicing against deliverables; prohibit timesheets approved day by day as for an employee.

Step 5 — Ongoing monitoring and audit

• Quarterly audit of freelance relationships (contracts, processes, IT access, team practices).
• Due diligence register (URSSAF certificates, Kbis, insurance) and preparation for URSSAF inspections (DREETS).
• Introduce legal ops to systematise these checks and evidential archiving; our guide can help organise the legal function from day one.

5) Typical startup examples

• Front-end developer “integrated” into the product team: mandatory daily meetings, sprint planning directed by the VP Eng., internal email, 9–18 working hours. High risk. Correct by switching to deliverables, freely chosen hours, own tools and a provider-side project manager.
• Freelance growth specialist paid a fixed fee
• Defined monthly scope, outcome KPIs (not guaranteed), optional weekly meetings, other clients. Moderate to low risk if autonomy is real.
• Fractional CTO 2 days/week: leads technical committees without HR management, roadmap-based objectives, assignment contract, no permanent internal tools. Manageable risk if hierarchy and discipline remain with the company.

6) What if the risk is too high?

• Switch to CDD/CDI if the assignment requires hours, close integration and hierarchical control. To define the choice and structure, see our CDD/CDI comparison and obligations for your first employee (DPAE, register, supplementary health insurance, etc.).
• Umbrella employment (portage salarial) for occasional assignments with high autonomy, retaining employee status with the umbrella company (see guidance from the Ministry of Labour).
• IT services company/agency with outcome commitments and contractual management, rather than staff augmentation through integrated time-based assignments.
• Clarify the applicable collective agreement when hiring (e.g. Syntec) to classify the role and pay correctly: guidance in our article on collective agreements for tech startups.

7) Quick checklist before signing with a freelancer

• Assignment defined by deliverables and milestones; no imposed hours.
• Services contract with independence clause, no exclusivity, controlled subcontracting permitted, assignment of rights.
• Remuneration at a fixed fee/per delivery; no employee-style bonus.
• Freelancer's tools; minimal, temporary client access.
• Due diligence : Kbis/SIREN + URSSAF certificate > €5,000 excluding VAT, renewed regularly.
• Evidence of autonomy: multiple clients, remote work, regular invoices.
• Periodic audit of team practices and IT access.