Who actually sells software in France

Six kinds of organisation can sit between a foreign B2B product and a French customer. They get lumped together as “partners”, and they are not interchangeable: they do different work, earn money in different ways, and a yes from each one proves something different about your product. Which you approach first decides what you learn.

Written by Matteo Henriques, who runs Evolren.Published 11 August 2026.

Start with the words French firms use

The umbrella term for a services firm is ESN, for entreprise de services du numérique; the older word, SSII, still appears on some sites. Numeum, the French digital industry association, organises its own membership around the same vocabulary: ESN, éditeurs de logiciels, platforms and technology consultancies.

An intégrateur is a role rather than a separate species, and plenty of ESNs describe themselves that way for one client and not for another. A revendeur resells, a grossiste distributes, and an apporteur d’affaires introduces for a fee and does nothing else. That last term is worth knowing before you propose a partner programme to someone offering you an introduction.

The practical consequence is immediate: search for intégrateur alongside the vertical you sell into rather than for the English term, because the French word is what these firms use about themselves.

What a yes from each one proves

Read the fourth column before the second. It is easy to pick a category for what it could do for you, and then find that its enthusiasm meant something narrower than you assumed.

The six organisation types that can sit between a foreign B2B software product and a French customer, compared on capability, commercial incentive, what their interest actually demonstrates, and a mismatch worth checking for. Evolren's framework, reasoned from how these roles are structured rather than drawn from a survey.
Role	What it can actually do	How it makes money	What a yes from them proves	A mismatch to check for
Reseller (revendeur, VAR)	Resell licences and hold the commercial relationship, with light implementation or none.	Margin on the licence, sometimes a recurring share. Breadth of catalogue matters more than depth in any one product.	That your pricing leaves room for somebody else, and that the product can be sold without you in the room.	Signing transactional resellers for a sale that needs a consultative conversation, then reading the silence as lack of interest.
System integrator (intégrateur)	Design and deliver the project your product sits inside, next to components from four other vendors.	Billable days. The software licence is often the smaller half of the deal.	That your product fits a project shape their clients are already buying and budgeting for.	A product that removes billable days sits awkwardly with the model, however much the engineers like it.
Managed service provider (infogéreur, MSP or MSSP)	Operate it for the customer month after month, inside a managed contract.	A recurring fee per seat, device or site. Predictability is the thing they are actually selling.	That the product survives being run by someone who did not build it, and that its licensing can be resold monthly.	Licensing that cannot be resold monthly, or that cannot be operated across several clients at once, can rule you out whatever they think of the product.
Consulting or implementation partner	Shape the specification before a purchase is decided, and implement afterwards.	Advisory and implementation days. Frequently no licence margin at all.	That the problem you address is one their clients are currently paying to think about.	Warm meetings that do not convert, because they influence the shortlist and do not hold the budget.
Referral partner (apporteur d'affaires)	Introduce you, then step out of the deal.	A one-off fee or a small share of the first contract.	Less than any other category: that somebody likes you enough to spend a little of their own credibility.	Counting it as channel coverage. It is coverage of nothing until an introduction turns into a deal.
Distributor (grossiste, distributeur à valeur ajoutée)	Carry credit, contracting and logistics for a network of resellers you would otherwise manage one by one.	A slice of every transaction, in exchange for absorbing administration and payment risk.	That someone experienced believes there is repeatable reseller demand. It does not prove the demand.	Signing a distributor with no resellers behind it and expecting it to recruit them. Distribution serves a channel more readily than it creates one.

The third column is the one to argue with internally. A category tends to behave the way its revenue model rewards, and programme design does not override that. If your product shortens an integration from forty days to five, an integrator going quiet may not be obstruction. It may be arithmetic.

Whether a particular firm behaves like its category is a different question, and one that public sources cannot answer.

Examples of sector-specific requirements to check

Some French requirements decide whether a partner can put you in front of its clients at all. They apply to particular products, data or projects rather than to the French market in general, so treat these as examples of the kind of thing to establish early rather than as a general property of selling here.

Public bodies and sensitive data. The French State’s “cloud au centre” doctrine, as published by the interministerial digital directorate, sets conditions for cloud offers used where data of particular sensitivity is handled, including SecNumCloud qualification or a recognised equivalent. If your target partners serve the public sector, ask about hosting in the first conversation rather than the fifth.
Health data. HDS certification, administered by the Agence du Numérique en Santé, applies to hosting personal health data on behalf of a third party, where that data was collected in the course of prevention, diagnosis, care or medico-social follow-up. It turns on the role played rather than on the sector: a healthcare organisation running its own system is not covered by it. Whether it reaches you, your hosting provider or neither depends on who holds the data and in what capacity, which is worth establishing before a partner with healthcare clients asks.

Which category to approach first

There is a test that settles this faster than a strategy session. For each of the six, write one sentence in this form and try to fill in the number:

“A firm of this kind earns roughly ___ more per year because it works with us, and it earns it by ___.”

Where you cannot fill in either blank, that category is a hope rather than a channel, and approaching it is likely to produce polite meetings and little information. Where you can fill in both, you have a category worth testing and a specific claim to test: whether a firm of that kind agrees with your arithmetic.

Which of the six actually stands between you and a French buyer also varies by sector, and the table above is a structure to reason from rather than a description of every market. Establishing it for one product is the first thing a validation mission has to do.

If you want to know which of these six is worth approaching for your product before you build a partner programme around a guess, say what you sell and how it reaches a buyer today. We reply within two working days.

Discuss which French organisations fit your product

Sources

Each entry is the page the claim was read on, with the date it was checked. Where a source states its own date, it is given too. Rules and thresholds change; if you are about to act on one, open the link.

Le syndicat patronal des professionnels du numérique en France
Numeum · checked 11 August 2026
Cloud au centre : la doctrine de l'État
Direction interministérielle du numérique · checked 11 August 2026
Certification Hébergeur de données de santé (HDS)
Agence du Numérique en Santé · checked 11 August 2026