For twenty years, the nearshore equation fit on one line: a good engineer, a shared language, a one-hour time difference, a lower cost. You were buying capacity. More people, for less, not too far away.

AI breaks that line. When part of the code, the tests and the documentation is produced with an assistant, the question is no longer how many people you can line up. It is what each of them can do with those tools.

What the first index of its kind says

In July 2026, the firm Ataraxis published the Global Outsourcing AI Readiness Index 2026. It compares 25 outsourcing destinations on how ready they are for AI. Morocco ranks 19th out of 25, with an overall score of 43.35 out of 100, and 2nd in the Middle East and North Africa region, behind Egypt. India leads with 84.55 points.

The breakdown says more than the rank. According to the figures reported by Hespress, Morocco scores:

  • 48 for AI adoption by the population;
  • 46 for its education and training system;
  • 41 for the AI skills of its workforce;
  • 39 for deployment inside companies.

In other words: Moroccans use AI, schools are starting to teach it, but companies have barely built it into the way they produce. The weak point is not access to the tools. It is industrialising them.

The index should be read for what it is: a snapshot relative to 25 countries, not a forecast. A lower-ranked country can still be the right choice for you because of language, proximity or specialisation. But the message is clear, and it applies everywhere: the nearshore advantage is moving from cost to capability.

Why this is your problem, not Morocco's

The instinct is to read this ranking as a public-policy issue. It is one. But for an executive building or running a team in Casablanca, Rabat or Tangier, the consequences are immediate.

Headcount is losing its value

A team of ten developers who have not changed the way they work in three years delivers roughly what it always did. A smaller team that has built assistants into its development, review and testing workflow can deliver as much with fewer people. The day rate becomes a misleading metric if it says nothing about what gets shipped.

Entry-level work is disappearing

Nearshore has long run on a pyramid: many junior profiles on repetitive tasks, a few seniors to supervise. Those repetitive tasks are exactly what AI absorbs first. A team built on that model has a structural problem, not a cost problem.

Risk is moving

A team that uses AI without a framework raises new questions: which data goes into which tools, who reviews generated code, who is accountable for it. Since 2 August 2026, the transparency obligations of the EU AI Act apply, for instance telling users that they are interacting with a chatbot. If your nearshore team builds such systems for your European clients, the compliance is yours.

What we would do in your place

1. Hire on practice, not on claims

Everyone "masters AI" on a CV. The only test that matters is practical: a real case, an assistant open, and one hour to see how the candidate breaks the problem down, checks what the tool suggests and rejects what is wrong. Judgment matters more than speed.

2. Train the existing team, with rules

Morocco's lowest score in the index is about companies, not people. That is good news: closing the gap is in your hands. In practice:

  • tools chosen and paid for by the company, not personal accounts;
  • a written rule on which data can be submitted and which never is;
  • systematic human review of anything that goes to production;
  • dedicated time every month to share what works.

3. Rebuild the pyramid

Fewer execution roles, more people able to understand a business domain, design and review. Juniors remain essential, or you will have no seniors in five years. But you train them on work that creates value, in pairs, not on what an assistant already does.

4. Measure what is delivered, not time spent

If your contract or dashboard only talks about man-days, you are paying for AI without seeing the benefit. Manage by deliverables, lead times and quality. It takes more effort to set up, and it is the only way to know whether the team is improving.

5. Aim for work where people stay at the centre

The Hespress analysis of the index puts it well: Morocco's challenge is to move towards software development, data, engineering, cybersecurity, finance and complex process management. These are also the areas where a stable team that knows your business creates the most value. That is where your team belongs.

Morocco has the right fundamentals, not yet the right reflex

Nothing in this ranking questions what makes Morocco strong: language, proximity, solid engineering schools, an ecosystem that is maturing. What it shows is that these strengths are no longer enough on their own.

At Ippon, it took less than six months to build the team in Morocco. What makes the difference afterwards is not hiring speed. It is what the team learns to do every quarter, and the role it is given in decisions.

The nearshore model that wins the next five years will not be the cheapest. It will be the one where the client company has invested in its team's capability as much as in its size.

---

Building a team in Morocco, or looking to evolve the one you have? Write to us: we will look with you at where the value lies and how to structure it.

Sources: Ataraxis, Global Outsourcing AI Readiness Index 2026, as reported by Hespress (16 and 21 July 2026); EU AI Act, Article 50.