How do French companies outsource software development in 2026?
French companies outsource software development mainly to add senior engineering capacity faster than the Paris and Lyon markets can supply it, and increasingly to reach AI, data and cloud specialisms that are scarce everywhere. The structural choice is between a nearshore team in Southern or Eastern Europe with same-hours collaboration, and an offshore team in India with deeper senior supply and a lower cost per engineer.
What distinguishes France from its neighbours is not the commercial logic — it is the legal framing. French law polices the boundary between buying a service and lending labour more strictly than most European jurisdictions, employee representative bodies have real consultation rights, and the research tax credit imposes specific conditions on subcontracted development. Getting those three right at the contracting stage costs a fortnight. Getting them wrong costs considerably more.
Nearshore or offshore: which model suits a French buyer?
| Model | Overlap with Paris | Relative cost per senior engineer | Senior supply depth | Best suited to |
|---|---|---|---|---|
| Hire in France | Full | Highest | Limited and highly competitive | Architecture ownership and long-term domain knowledge |
| Nearshore Europe (Portugal, Spain, Poland, Romania) | Same hours or ±1 hour | Moderate | Moderate | Exploratory product work with moving requirements |
| Offshore India | Roughly four to five usable hours | Lowest | Deepest, particularly in AI and platform engineering | Sustained delivery and teams expected to grow |
| French ESN / régie | Full | High | Depends on bench availability | Short-term gap filling within an existing process |
Most French buyers who scale successfully end up with a hybrid: architecture and product ownership in France, delivery capacity offshore, and a deliberately small number of interfaces between the two. Our guide to choosing a software outsourcing partner in Europe sets out how to run that selection without a six-month procurement cycle.
What is prêt de main-d'œuvre risk, and why does it matter here?
French law prohibits the for-profit lending of labour outside authorised temporary work arrangements, and treats marchandage — supplying workers in a way that deprives them of legal or collective protections — as an offence. The practical implication for outsourcing is precise: a contract that simply supplies bodies who are then directed day-to-day by your own managers, priced by the hour with no defined deliverable, looks structurally like labour lending rather than a service.
The remedy is contractual, not cosmetic. Buy a defined service or outcome. Let the vendor retain hierarchical authority over its own personnel, including performance management and task allocation. Give the vendor its own team lead who receives your priorities rather than having your managers assign work individually. Keep the statement of work specific about deliverables and acceptance rather than about hours and headcount. French counsel will recognise this framing immediately; the mistake is importing an Anglo-Saxon staff-augmentation contract unchanged.
Do we have to consult the CSE?
Where a comité social et économique exists, it has information and consultation rights over decisions affecting the organisation, management and general running of the company, including changes to work organisation. Outsourcing that adds capacity to an existing team is a materially lighter conversation than outsourcing that reduces or displaces internal roles — but the sequencing matters either way, because consultation is meant to precede the decision, not ratify it.
The pattern that works is straightforward: brief the CSE on the capacity problem before the vendor selection concludes, be explicit about what happens to existing roles, and document the consultation. The equivalent German debate, which follows similar logic, is covered in our piece on works councils and outsourcing in Germany.
What does the CNIL expect when data leaves France?
The GDPR applies directly and the CNIL supervises it. A development vendor that touches personal data is a processor and needs an Article 28 agreement covering instructions, sub-processors, security measures, breach notification and deletion at the end of the engagement. Where the vendor sits outside the EEA in a country without an adequacy decision — India included — transfers require standard contractual clauses supported by a transfer impact assessment.
Sensitive sectors go further. Public bodies and operators handling sensitive data increasingly expect qualified, sovereign hosting for the data itself, even when development work is performed elsewhere. That distinction is the one to hold onto: where your data is hosted and who may access it are separate questions from where your engineers sit. Our guide to EU-hosted LLMs and data residency works through the same separation for AI workloads.
In practice, the strongest control is architectural. Keep production personal data out of development environments, use pseudonymised or synthetic datasets, restrict production access to a named, auditable few, and log it. That posture survives regulatory scrutiny far better than a contractual clause alone.
Does outsourced development still qualify for the research tax credit?
This is the question French finance directors ask first, and the answer requires care. The crédit d'impôt recherche can cover research work entrusted to third parties, but eligibility depends on the subcontractor holding the required approval and on the work itself meeting the definition of research — genuine technical uncertainty resolved by systematic investigation, not routine development. Rules on approved subcontractors and on the treatment of work performed outside the EEA have been tightened in recent years.
Two practical consequences follow. First, do not assume an offshore vendor's invoices are creditable; confirm the position with your tax adviser before you build the saving into a business case. Second, structure the work so that the genuinely novel research stays where it is creditable, and the routine build — which was never eligible anyway — goes wherever it is most efficient. That split is usually good engineering practice regardless of the tax treatment.
How should a French company run its first engagement?
- Define a service with deliverables and acceptance criteria, not a headcount with an hourly rate.
- Confirm the vendor's team lead directs its own people, and write that into the contract.
- Brief the CSE before the decision is final, and keep a record.
- Have the DPO approve the transfer mechanism and the data-minimisation design before the pilot starts.
- Run a paid four-to-six-week pilot on real backlog, and judge accepted output rather than presentation quality.
- Keep source code in your own repositories from day one and make documentation an explicit deliverable.
ILMTEC's senior engineering teams are structured as managed delivery teams working European hours, which is the shape that fits French contracting requirements most cleanly.
Which work do French companies hand over first?
The engagements that succeed start where verification is easy and domain knowledge is shallow, then deepen. Backend services against an agreed API contract, frontend build-out from settled designs, QA and test automation, and cloud platform work are the usual first tranche. Data and AI engineering follow once the team has absorbed enough of the business context to be trusted with it.
What stays in France, in almost every arrangement that lasts, is architectural authority, product ownership and the customer relationship. That division is worth stating explicitly in the statement of work, because it also reinforces the service framing that French contracting requires: your architects set direction and acceptance criteria, and the vendor delivers against them using its own management chain.
On working language, be deliberate rather than assumptive. English as the language of code, tickets and technical documentation is normal in French engineering organisations, but obligations regarding French-language documents provided to employees are a genuine consideration in French workplaces. Decide early which artefacts are internal engineering documents and which are documents your own staff are required to work from, and take advice where the line is unclear.
What usually goes wrong
The recurring French failure mode is a contract borrowed from another jurisdiction: hourly régie pricing, direct task assignment by internal managers, and no defined deliverable. It works until someone examines it. The second failure mode is assuming tax credit eligibility travels with the work. The third is the universal one — under-investing in onboarding and then blaming the vendor for a slow first month.
