An agency sells a deliverable at a fixed price, while an IT services company (known in France as an ESN) sells billable human time at a daily rate, and that difference determines who carries the risk on your project. Trying to decide between the two for a tech project? These terms come up everywhere, often used as though they were interchangeable, even though they cover very different realities in terms of business model, team management, and accountability for outcomes.
I have been working with development teams for over ten years, and I consistently see companies making the same mistakes when it comes time to choose. The problem is not a lack of options: it is a lack of clear criteria for deciding.
- 🔑 **IT services companies sell time, agencies sell a deliverable:** two incompatible logics.
- ⚠️ **Disguised employment in staff augmentation** exposes your project to involuntary turnover.
- 💡 **Cooperative ESNs and offshore teams** are changing the game in 2026.
- 🎯 **Your selection criteria must be technical,** not just about price.
1. Confusing staff augmentation and fixed-price contracts
Between an agency and an IT services company, the difference is not cosmetic: an agency sells a result at a fixed price, while an IT services company sells billable human time at a daily rate (staff augmentation). With staff augmentation, if the project falls behind schedule, the extra cost is on you. With a fixed-price contract, it is on the vendor. Everything follows from there.
The first and most widespread mistake is treating agencies and IT services companies as two words for the same thing. The business model behind each one is fundamentally different.
How does staff augmentation work at an IT services company?
An IT services company (now called ESN, for "Entreprise de Services du Numérique," in France) employs developers and places them at client sites. This is the staff augmentation model: you buy human time, billed at a daily rate. The consultant works in your offices, uses your tools, and follows your processes.
As one former consultant who spent eight years at Casino without being employed by the group explains: "He was the one who approved my time off, he was the one who gave me the laptop. My real colleagues were the Casino people, but I was not a Casino employee." This testimony, shared on the Les Compagnons du DevOps channel, perfectly illustrates the paradox of staff augmentation: the consultant belongs to a company they never actually see.
The agency model works in the opposite way. It sells a result, not time. You pay a fixed price for a defined deliverable: a website, an application, a redesign. If the agency takes longer than planned, that is their problem. If they finish faster, that is their profit.
The choice between staff augmentation and fixed-price contracts determines everything else: who carries the risk, who manages the team, who is accountable for quality.
When is staff augmentation preferable to a fixed-price contract?
Staff augmentation works when you already have an internal technical team and need temporary reinforcement. You keep control, you manage the consultant as a member of your team. Fixed-price contracts, on the other hand, work when you have no CTO, no internal technical leadership, and you want to delegate responsibility for the outcome.
The trap: choosing staff augmentation out of habit when you have no one in-house to supervise the consultant. Without technical oversight, you are paying for time with no guarantee of results.
2. Ignoring the risk of turnover and disguised employment
According to Numeum, the French digital industry trade association, the turnover rate in the French tech sector was 16% in 2024, down from the 22% peak in 2023 but still high enough to represent a structural risk: roughly one in six employees leaves their company each year. For you, the risk is concrete: the consultant who leaves takes their knowledge of your system with them.
The staff augmentation model at IT services companies creates a structural problem that many clients underestimate: involuntary turnover. A consultant placed at your company for months, sometimes years, ends up knowing your system better than anyone. The day the IT services company reassigns them to another engagement, you lose that knowledge.
Why does disguised employment threaten your project?
Disguised employment occurs when the end client fully controls the consultant's professional life: approving time off, providing equipment, giving direct orders, requesting training. On paper, it is illegal. In practice, tolerance is enormous, a situation that persists to this day, with no systematic case law to put an end to it.
This creates a dangerous dependency for your project. The consultant has no incentive to document, to transfer knowledge, or to make their work reproducible. When they leave, technical debt explodes.
Agencies absorb this risk internally. Their teams rotate between projects, but the agency remains responsible for continuity. If a developer leaves the agency, it is up to the agency to manage the transition. You do not see the difference; you receive the deliverable.
The real cost of a staff-augmented consultant is not measured by the daily rate. It is measured by what happens when they leave.
3. Assuming all IT services companies are the same
Not all IT services companies operate the same way. The most reliable distinguishing criterion is governance structure: a cooperative ESN (known as a SCOP in France), where consultants share in decisions and profits, has radically different incentives from a traditional ESN that is publicly traded or owned by a private equity fund.
Many tech professionals lump all IT services companies under the label "body shops." This term, used bluntly by several industry players, reflects a genuine frustration: companies that sell profiles without investing in skill development or caring about deliverable quality.
How do cooperative IT services companies change the equation?
Cooperative IT services companies (structured as SCOPs, for instance) offer a model where consultants are partners. They participate in decisions, receive a share of profits, and have a direct stake in client satisfaction.
This model reduces turnover and improves engagement. A consultant who is also a partner in their company will not switch assignments every six months for a bench bonus.
| Criterion | Traditional IT services | Cooperative IT services | Web agency | Offshore team |
|---|---|---|---|---|
| Dominant model | Staff augmentation (daily rate) | Staff augmentation or fixed-price | Fixed-price | Fixed-price or staff augmentation |
| Average turnover | High | Low | Medium | Variable |
| Accountability for results | Client | Shared | Agency | Vendor |
| Skill development | Low | High | Internal | Variable |
| Relative cost | High | Medium-high | Medium | Competitive |
According to Numeum, the IT services market alone was worth €34.5 billion in 2024, accounting for half of the French digital market. The problem is not the IT services model itself: it is the lack of criteria for telling the good ones from the bad.
For junior developers, IT services companies remain an excellent launchpad. Seeing different contexts, varied tech stacks, and contrasting company cultures is an accelerated education that few other structures offer. The problem arises when the consultant stays in the same place for too long, as that eight-year testimony at Casino demonstrates.
4. Overlooking the offshore alternative
Offshore teams, particularly IT services companies based in Vietnam, represent a third option often absent from the agency vs. IT services comparison, even though it can be highly relevant for projects with significant development volume. In the best cases, senior teams well-equipped with AI tools rival European teams that cost two to three times more, for comparable or superior delivery.
When you compare agencies and IT services companies, you tend to stay within a purely domestic scope. This is the fourth mistake: ignoring offshore as a credible third option. Full disclosure: I run an offshore IT services company based in Vietnam, so I have an obvious bias on this topic. That is also why I know the concrete limitations, not just the sales pitch.
Should you still hesitate about offshore in 2026?
Offshore has long suffered from a reputation for mediocre quality. That perception dates from an era when outsourcing meant sending a 200-page requirements document to a code factory in India and hoping for the best.
The reality in 2026 is radically different. Structured teams, particularly in Vietnam, combine reasonable costs with genuine technical culture. As a reference point, an offshore developer in Vietnam bills between €150 and €350 per day depending on seniority, compared to €400 to €700 for an equivalent profile at a French IT services company depending on region and experience level. The gap comes from the cost-of-living differential, not a skills gap. When you factor AI into the equation, a small, well-organized senior team can rival a European team that costs two to three times more.
I see it with my own teams: a competent developer equipped with Claude Code or Cursor delivers faster than a staff-augmented consultant coding without AI assistance. The differentiator is no longer headcount; it is the ability to use these tools intelligently.
On Reddit, an entrepreneur shared his experience after spending $47,000 over 18 months on an AI tool, only to end up with 12 users. His main mistake: outsourcing every role (developers, designers, writers) with zero technical oversight. One comment summed up the problem: "You outsourced literally every role, so what did you do besides last minute marketing?" This story illustrates a point I stand behind: writing code is not enough; you need to understand the requirement, structure the product, and deliver properly.
Offshore is not a shortcut to pay less. It is a strategic option when the team on the other end knows how to take responsibility for the outcome. On that point, the best offshore teams work exactly like a good agency: they sell a deliverable, not time. I covered the concrete advantages of an offshore IT services company in a dedicated article if you want to dig deeper into this model.
5. Choosing between agency and IT services company without clear technical criteria
The deciding factor is not the daily rate, the size of the company, or geographic proximity. It is the vendor's ability to take technical responsibility for the outcome, and to answer three questions clearly before you sign anything.
The last mistake is the most costly: choosing your vendor based on price, geographic proximity, or a LinkedIn recommendation, without a technical evaluation framework.
How do you concretely evaluate a tech vendor?
Ask three questions before you sign. First question: who bears the responsibility if the project goes off the rails? With staff augmentation, it is you. With a fixed-price contract, it is the vendor. If no one can answer clearly, walk away.
Second question: what is the team's skill development policy? A vendor that does not invest in training its developers will send you profiles who code like it is five years ago. In 2026, a developer who does not use AI in their daily workflow falls further behind every month. I have detailed how these tools are genuinely transforming productivity on ai-first.fr.
Third question: what happens if a key team member leaves the project? Good organizations have a plan: documentation, pair programming, structured handover. Bad ones leave you with a Git repo and a "good luck."
The daily rate is an indicator, never a decision criterion. A consultant at €600 per day who delivers in three months costs less than a consultant at €350 per day who takes eight months. The question is not how much you pay per day, but how much you pay for the result.
The right vendor is neither the agency nor the IT services company by default. It is the one that takes technical responsibility for your project.
Frequently Asked Questions
What is the difference between a SSII and an ESN?
There is no operational difference. ESN (Entreprise de Services du Numérique) is the new name for SSII (Sociétés de Services en Ingénierie Informatique), adopted in 2013 by the French trade association Syntec Numérique (now Numeum). The rebrand aimed to modernize the sector's image, but the business model remains identical: placing consultants in staff augmentation roles or delivering fixed-price projects.
Can a web agency do staff augmentation like an IT services company?
Some agencies do offer staff augmentation, but it is not their core model. An agency's DNA is the fixed-price contract: you pay for a defined deliverable, not for billable hours. If an agency offers you exclusively staff augmentation, it is functioning as an IT services company in all but name.
How can you tell if a staff-augmented consultant is in a disguised employment situation?
Check who actually controls the consultant's professional life. If you (the end client) are the one approving their time off, providing their equipment, setting their schedule, and giving them direct orders, the criteria for disguised employment are likely met. The risk of reclassification by a labor tribunal is real, even if tolerance remains widespread in the sector.
What is an offshore IT services company and how does it differ from a traditional one?
An offshore IT services company (also called an offshore ESN or ODC, for Offshore Development Center) applies the same principle as a domestic IT services company (consultant placement or project delivery) but from a country with lower labor costs, such as Vietnam, Madagascar, or Romania. The key difference is structural: without a client on-site to supervise consultants day to day, the best offshore IT services companies often operate on a fixed-price basis rather than pure staff augmentation, which brings them closer to the agency model. Vietnam, for example, has more than 50 CMMI-certified software engineering centers of excellence, reflecting a genuine level of industrial maturity, provided you choose the right organization rather than the cheapest on the market.
Is offshore compatible with GDPR for a European project?
GDPR does not prohibit offshore, but it does require safeguards for the processing of personal data. A serious offshore vendor implements standard contractual clauses, restricts access to production data, and can work on anonymized development environments. Vietnam, for instance, has had a cybersecurity law in force since January 1, 2019, and many teams there are accustomed to European compliance requirements.
Should you choose a large vendor or a small firm?
Size is not a reliable criterion. A large IT services company might assign you an unsupervised junior, while a small firm of five senior developers can deliver a solid product. The deciding factor remains the vendor's ability to take responsibility for the outcome, not the headcount on their sales brochure.
Vidéos YouTube
- Why do I call IT services companies "meat dealers"? · Les Compagnons du DevOps
- Découvrez notre agence CODiLOG de Nanterre · CODiLOG
- Comment on travaille au sein d'une ESN ? · AS International Group
- Interview SSII production · PCM Productions
