1 – The real problem: your offshore contract is a blank check on your IP
The majority of IT outsourcing contracts signed by French SMEs contain no enforceable intellectual property assignment clause before a Malagasy court. This is not a minor detail. It is a ticking time bomb.
1.1: The freelancer assigns you nothing by default
Under both Malagasy and French law, the author of source code holds the economic rights. Unless there is an explicit contrary clause. A freelancer in Antananarivo who codes your application for six months remains the owner of what they produce if your contract does not include a complete, irrevocable and worldwide assignment of economic rights.
Most freelance régie contracts I see mention a "licence of use". That is not an assignment. You have the right to use the code. Not to resell it, modify it freely, or protect it against a third party who might use it.
Concrete result: a French SaaS publisher discovered that their Malagasy freelancer had deployed 60% of the same codebase for a direct competitor. The contract provided for a non-exclusive licence. Legally, the freelancer was within their rights.
As we detailed in our analysis on la propriété intellectuelle en offshore, without a proper assignment clause, you are financing an asset that does not belong to you.
1.2: The traditional ESN pools your developers — and therefore your IP risks
The offshore ESN solves the assignment problem. In theory. The contract is signed with a legal entity that employs the developer. The IP assignment flows through the employment contract between the ESN and the employee, then through the commercial contract between the ESN and you.
The problem: most offshore ESNs in Madagascar operate on a pooling model. The same developer works on two, three, sometimes four projects simultaneously. They handle your functional specifications in the morning and those of your competitor in the afternoon.
Your confidentiality clause is technically valid. But operationally unenforceable. How do you prove that an architectural pattern, a business logic or a pricing algorithm leaked from one project to another when the same mind works on both?
Pooling is the ESN's business model. It is also its Achilles heel when it comes to IP protection. You sign a watertight contract with a structure whose internal workings are a sieve.
1.3: The real risk is not theft — it is contamination
Founders think about code theft. The dramatic scenario where a developer copies your repo and sells it. That scenario exists but it is rare. The real risk is more insidious: contamination.
A developer working on multiple projects reuses patterns. Snippets. Architectural approaches. They do not do it out of malice — they do it for efficiency. And in a pooled ESN, nobody monitors that.
Contamination creates an unmanageable legal grey area. You cannot prove that your scoring logic was copied. You can only observe that your competitor released a strikingly similar feature six months later.
This problem disappears structurally with a one-collaborator-dedicated-to-one-client model. Not through the contractual clause — but through operational organisation. At Taram, each collaborator works exclusively for a single client. Contamination is not possible because there is no second project.
2 – Product velocity: the contractual structure dictates your ability to ship
IP protection is only one side of the problem. The other side, which nobody addresses in ESN vs freelance comparisons, is the direct impact of the contractual structure on your delivery speed.
2.1: The freelancer makes you dependent on an individual
A high-performing freelancer in Madagascar ships fast. Often faster than an ESN team, because there is no management layer between them and your need. That is appealing.
Until the day they fall ill. Until they accept a better-paid assignment. Until they simply disappear — which happens more often than is acknowledged in the Malagasy freelance ecosystem.
Your product velocity is then at zero. Not reduced. At zero. Because nobody else knows your codebase. Nobody can pick up the current sprint. You restart from a three-week onboarding at minimum.
turnover en offshore à Madagascar is a topic most vendors avoid. In freelance régie, turnover is not even a risk — it is a statistical certainty. A freelancer has no obligation of continuity beyond their current assignment.
Direct consequence: your product roadmap depends on the loyalty of an individual whom nothing binds to you.
2.2: The pooled ESN kills your velocity through context-switching
The ESN solves the individual dependency problem. If a developer leaves, the ESN replaces them. That is the promise. In practice, the replacement takes four to eight weeks. But the real problem lies elsewhere.
A developer pooled across three projects loses between 20 and 40% of their productive capacity to context-switching. Studies demonstrate it. Field experience confirms it. Every time they switch from your project to another, they lose the thread. It takes them 15 to 30 minutes to reconnect to your business context, your architecture, your code conventions.
Over a five-day week, a developer pooled across three projects delivers the equivalent of 2.5 useful days. You pay a daily rate calculated on five days. Your real velocity is halved without anything in your reporting showing it.
This mechanism is documented. It is measurable. And yet no offshore ESN mentions it in their commercial proposals. Because pooling is their margin.
2.3: The dedicated model — the only one that aligns contractual structure and velocity
The solution is neither the freelancer nor the pooled ESN. It is a dedicated collaborator, employed by a structure that handles infrastructure, management and continuity — but assigned exclusively to your project.
At Taram, the collaborator is recruited to measure, validated with the client, integrated into their tools — Slack, Teams, CRM, Git — and managed by a European management team based in Maurice. They work on a Ryzen 7 workstation with fibre and 5G backup. They have a single client.
This model does three things that neither the freelancer nor the ESN do simultaneously. It secures your IP through an employment contract with an integrated assignment clause, operational exclusivity and full traceability. It guarantees your velocity through full-time work with no context-switching. And it ensures your continuity through structured management that anticipates turnover instead of suffering it.
For the price of one French employee, Taram deploys 3 dedicated collaborators. Not 3 fractions of pooled time. 3 people who work only for you. As our guide sur les clauses SLA en offshore shows, it is this exclusivity that makes performance commitments credible.
3 – The contractual clauses nobody negotiates — and that make all the difference
Choosing the right structure (freelancer, ESN, dedicated collaborator) is not enough. What truly protects your IP and your velocity are specific clauses that 90% of offshore contracts do not contain.
3.1: IP assignment clause — worldwide, irrevocable, across all media
An assignment clause that states "the client owns the deliverables" is worthless before a court. Under Francophone copyright law — the law that applies in Madagascar — the assignment must be explicit, limitative and detailed: which rights (reproduction, adaptation, distribution), on which media (digital, physical, future), for which duration (the legal term of copyright), over which territory (worldwide).
Add an assignment clause covering rights to preparatory works: mockups, architectures, data schemas, technical documentation. The final code is only the visible part. The detailed functional specifications, the architecture diagrams — that is where your competitive advantage resides.
Finally, require an originality warranty clause. The contractor or employee warrants that the code produced contains no components from other projects, except duly identified open source. That is your protection against the contamination described above.
If your current contract does not contain these three elements, you are operating without a safety net. Full stop.
3.2: Reversibility clause — your code must be able to leave with you within 48 hours
Reversibility is the ultimate test of your independence from your offshore provider. If you cannot recover your entire codebase, documentation and environments within 48 hours, you are captive.
With a freelancer, reversibility depends on their goodwill. If they host the repo on their personal GitHub account, if they use their own staging servers, you are at their mercy on the day of separation.
With an ESN, reversibility is contractually provided for but often accompanied by delays of 30 to 90 days and "transition" fees. That is a disguised retention lever.
The Taram model resolves this problem at the source: the collaborator works in your tools, on your repos, with your access credentials. There is nothing to transfer because everything is already with you. Reversibility is instantaneous by design, not by contractual clause. That is a fundamental difference we detail in our overall approach to l'externalisation offshore pour PME.
3.3: Non-compete and non-solicitation clause — the real barrier
Your freelancer or the ESN's employee knows your technical stack, your product roadmap, your weaknesses, your competitive advantages. What happens when they go to work for a competitor? Or when they start their own company in the same market?
In freelance régie, a non-compete clause is legally fragile. The freelancer is independent. Preventing them from working in their area of expertise amounts to preventing them from earning a living. Malagasy courts, like French ones, are reluctant to enforce it.
In an ESN, the non-compete clause is in the employment contract between the ESN and the employee. Not between you and the employee. If the ESN does not enforce it — and it has no interest in doing so once the commercial contract ends — you have no recourse.
At Taram, the non-compete clause is doubled: in the collaborator's employment contract and in the commercial contract with the client. The European management based in Maurice ensures its enforcement. And the non-solicitation protects against the poaching of the collaborator by the client themselves or by a competitor — a frequent scenario that structures without gouvernance structurée do not know how to handle.
Which contractual structure truly protects your IP and your velocity in offshore Madagascar?
The freelancer exposes you on IP and makes you dependent on an individual. The pooled ESN signs fine contracts but organises contamination and halves your velocity. Both structures have one thing in common: they optimise their own business model, not your protection.
The only structure that aligns IP protection, product velocity and operational continuity is the dedicated collaborator within a contractual framework designed for exclusivity. One employee, one client, complete assignment clauses, native reversibility and management that enforces commitments.
Every week you spend with a poorly structured offshore contract, you are building a software asset on sand. And when the sand shifts — it will shift — you will recover nothing.
