You've decided to build a team in Morocco. Then comes the question every executive asks us next: should you create your own subsidiary, go through a vendor, or combine both? There is no universally right answer — there is a right model for your situation. Here is how to decide.

The three possible models

1. The wholly-owned subsidiary

You create your own Moroccan legal entity, hire your employees, lease your offices. The team is yours: your culture, your processes, your tools.

  • Pros: full control, protected intellectual property, costs under control over time, asset value (an established team has balance-sheet value).
  • Cons: a more demanding setup — local law, accounting, payroll, compliance — and a commitment that should be thought of in years.

This is the model we deployed for Ippon Technologies: an IT subsidiary operational in under six months, with a 100% local team aligned with headquarters' standards.

2. The vendor (classic outsourcing)

You contract with a Moroccan company that staffs your projects. You pay an invoice, not salaries.

  • Pros: fast start, no structure to create, simple reversibility.
  • Cons: the vendor's margin eats into the savings, staff turnover you don't control, know-how that stays with the vendor, contractual dependency.

It's the right choice to test a market, absorb a workload peak, or outsource a standardized function.

3. Build-operate-transfer (BOT)

A local partner builds the team for you — recruitment, offices, administration — operates it for an agreed period, then transfers it to you along with the legal structure.

  • Pros: a vendor's speed at the start, ownership of the subsidiary at the end. The startup risk is carried by the partner.
  • Cons: requires a transfer agreement properly negotiated from day one — which is where most BOTs fail.

The four criteria that drive the decision

Time horizon. Less than two years or a one-off need: vendor. Three years or more with a growing team: subsidiary or BOT. The economics tip quickly — for a stable team, a subsidiary's costs are structurally lower than vendor billing.

Target size. Up to 5 people, a subsidiary's overhead weighs proportionally heavy. Beyond 10, it amortizes, and every additional hire strengthens the advantage. Our clients targeting 20 people or more almost always go for a subsidiary or a BOT.

How critical the know-how is. If the team touches your core business — your product, your code, your customer data — owning the team is not optional. You don't durably outsource what differentiates you.

Your ability to operate locally. A subsidiary requires a reliable local relay: legal, accounting, HR. This is precisely what separates a project that moves forward from one that bogs down. Without that relay, BOT is the way through.

What we see on the ground

Two lessons come up on every engagement in Morocco.

First, the savings are real in all three models — up to 40% lower operating costs on support functions, and 35% lower payroll costs in the first year for a tech startup set up in Tangier's offshore zone. The model doesn't change the size of the savings; it changes who captures them over time.

Second, the decisive factor is never the legal structure: it's the quality of the initial recruitment. The first three people you hire set the bar for everyone who follows. That is the one point where you should never delegate your vigilance, whatever the model.

How to decide in practice

Ask the questions in this order: what horizon, what target size, how critical, what local relay. If your answers point in different directions, BOT is often the rational compromise — provided the transfer is negotiated from day one.

At Connectis Partners, we have operated all three models — subsidiary creation, structured outsourcing, and team transfers. If you're hesitating between two options for your project, tell us about your situation: we'll tell you frankly which one applies, and which one doesn't.