Umbrella Companies: What Do They Really Cost Your Startup?

Umbrella companies promise the freedom of freelancing with the security of a permanent contract, and on paper the pitch holds up. For a company staffing a developer, though, the real invoice climbs by roughly 40% compared with a standard contractor day rate, once you count the commission and the employer contributions. I've seen enough dev engagements to know where that gap turns into a problem, and where it doesn't.

The confusion usually comes from mixing two things up: you think you're hiring a developer, and you end up paying the structure that employs them. Here's how the model actually works, what it costs you, and the cases where it's still the right call.

What does an umbrella company actually do?

An umbrella company is not a recruitment agency, and it isn't a consultancy in the usual sense. It's a legal intermediary that turns an independent contractor into an employee, without that person having to set up a company of their own.

The mechanics are spelled out in black and white by the French government: the consultant signs an employment contract (fixed-term or permanent) with the umbrella company, the umbrella invoices your business, then pays the consultant a salary after deducting contributions and its own commission. Three parties, three contracts, and a single flow of money that passes through two intermediaries before it reaches the developer's pocket.

How is the money split between the consultant, the umbrella and you?

This is where most CEOs misread what they're buying. The developer negotiates and finds the engagement alone, exactly like a standard freelancer. The umbrella company takes a commission of 5 to 15% on the invoiced revenue, handles payroll and admin, but does no sourcing and no engagement management: that work stays on your plate.

Don't confuse the salaried umbrella model with commercial brokerage either. With a broker, the intermediary is the one who won the engagement and charges a 10 to 15% commission for doing so. With an umbrella company, the consultant found the client themselves, and the umbrella simply dresses the relationship up as employment. Put differently: you're never paying for introductions, only for the administrative and social-security plumbing.

Players like ITG (€9M ring-fenced with the Caisse des Dépôts, more than 50,000 consultants served) or Ad'missions (founded in 1997, 28,000 independents served according to free-work.com) built their whole model on that plumbing. It's solid for securing payment. It is not a staffing service.

The real maths: how much more a developer costs under an umbrella

Once you know what you're buying, the question a CEO actually cares about remains: how much really leaves the bank account. On that point the numbers are unambiguous.

A consultant working through an umbrella negotiates a day rate (what you pay for one day of work) that's generally higher than a standard independent's, to make up for what gets lost along the way. Social contributions for a French sole trader cap out around 22%. For an umbrella employee they climb to roughly 45%, because they pay both the employer's and the employee's share, in exchange for unemployment insurance, income protection and training rights. Add the umbrella's commission, and the consultant nets on average 40% less than as a pure independent, for the same invoiced revenue.

That gap gets passed straight back into their day rate, almost every time. The upshot: you're paying for the contractor's social protection without getting a single direct benefit from it.

Why does the bill climb 40% above a standard day rate?

Take a senior developer who'd charge €350/day as a pure independent. Under an umbrella, to hold their take-home steady, they'll often invoice between €420 and €480/day to absorb the commission and the employer contributions. Over a 20-day month, the difference easily clears €2,000, without a single extra line of code being shipped. Here's how it compares with the other statuses you could staff a dev project with.

The full twelve-month calculation, with the contribution assumptions laid out, is in our permanent hire vs €180/day contractor comparison if you want to pick it apart line by line.

What the PEPS label protects, and what it doesn't

Paying more is justified when you're buying a genuine guarantee. The French umbrella model does offer one: the PEPS label mandates an independent audit of compliance and fee transparency, and players like ITG or ABC Portage (ISO 9001 certified, EcoVadis Silver in 2025) ring-fence several million euros with the Caisse des Dépôts to guarantee that fees get paid. If your umbrella company goes under mid-engagement, the consultant is still covered.

Does the umbrella model shield you from dodgy intermediaries?

Not everywhere, and France is right to take this seriously. The equivalent model in the UK, umbrella companies in the local sense, shows what happens when regulation is lighter: some payroll schemes miscalculated contributions, others outright defrauded HMRC. The result is a UK government crackdown that shifts tax liability for those schemes onto the client companies themselves, as Hudson Contract explains in a briefing aimed at end clients. In France, the PEPS label and the mandatory financial guarantee limit that risk, but they don't excuse you from vetting the provider before you sign.

A British electrical contractor tells it on YouTube more bluntly than I would: forced onto PAYE by an agency, he describes intermediaries who wash their hands of any dispute, supplying neither the equipment nor the cover a real employer would take on. Exactly what the French PEPS label is meant to prevent.

The real blind spot isn't where people look for it. The entry bar for becoming an umbrella employee is a level 5 qualification (two years of higher education) or three years of experience in the sector, according to the official text published on service-public.gouv.fr. That floor exists to protect a consultant retraining or in career transition, not to guarantee the seniority of a developer who's about to touch your production code. At Extra Dev, we never staff below eight years of experience minimum. The umbrella model imposes nothing comparable. The structure carries the contract, not the contractor's technical level.

When the umbrella model helps your project, and when it holds it back

Worth being upfront before going further: at Extra Dev we staff senior developers on a contractor basis, not through umbrella companies, so I have an obvious bias in this comparison. But that position is also what lets me see, engagement after engagement, where the umbrella model delivers on its promise and where it doesn't.

It still makes sense in two specific cases. First, for a consultant testing independence without yet wanting to set up a company: KIPDEV sums it up well, you need to be clearing at least €1,500 in monthly revenue for the equation to beat sole-trader status. Second, for someone exceeding the €77,000 annual revenue ceiling of sole-trader status who doesn't want to incorporate: they shift part of their activity under an umbrella to absorb the overflow, keeping the sole-trader status for the rest.

Should you use an umbrella company for a long dev engagement?

No, and this is precisely where the model becomes a drag on you. A long dev engagement (6, 9, 12 months on the same product) doesn't need the developer's employment status secured: it needs a senior profile available fast, at a predictable cost, with structured oversight. The umbrella model optimises for the consultant's peace of mind, not your time to market. On that specific criterion, a consultancy placing proven contractors stays faster and cheaper, provided you have a solid follow-up routine, which we break down in the 30-minute ritual that keeps remote contractors on track.

The 12-month maths: umbrella, contractor or permanent hire

Boil it all down to one decision. Over a year, a developer under an umbrella at an average €450/day, 18 billed days a month, comes to roughly €97,000 of spend for you. The same senior profile as a contractor through a consultancy at €180/day, at the same volume, lands around €38,800. An equivalent permanent hire, contributions included, generally sits between those two figures once recruitment costs are amortised, but with a lead time of several months that neither the umbrella nor the contractor route imposes.

"An umbrella company puts a lone consultant on solid ground. It never shortens the gap between your decision to hire and the first commit shipped."

Vincent, August 2026

For a one-off need under three months with a consultant you've already identified, the umbrella route is an honest choice: no paperwork on your side, clean invoicing, and the consultant keeps their autonomy. For a structural need, staffing a senior dev on a product that has to move fast, the maths tilts clearly towards contracting or a permanent hire. The full detail on all three options is in our 2026 developer cost comparison, with the assumptions worked through item by item.

Verdict: use an umbrella company only for a short, already-scoped engagement, never as a staffing solution for a project meant to last. The decision rule is simple: if you'll still be running that engagement in nine months, the umbrella model will cost you dearly for a guarantee you'll never use.