Skip to content

Point of view · 7 min read

Nearshore in Casablanca: the SAP service centre without the distance.

Outsourcing the run and enhancements of your SAP is nothing new. What has changed is how clear-sighted leadership teams have become about what distance really costs: in time difference, in language, in loss of context, in meetings that never replace a presence. Our conviction: a service centre should be judged by the distance it makes disappear, not only by the rate it displays.

Signed by the experts of our Casablanca service centre · a stance, lessons from experience and recommendations

The reasoning that drives companies to outsource SAP application maintenance is sound. Skills are scarce and expensive, activity peaks are unpredictable, and an IT department prefers to devote its teams to what differentiates the company rather than to fixing Monday morning’s interfaces. The reasoning that drives them to choose the most distant provider, however, is far less sound. It rests on a single variable, the hourly rate, and ignores all the others. Yet it is the others that make the quality of a service, and often its real cost.

What distance really costs.

We have seen enough disappointing run contracts to recognise the symptoms. They look alike, whatever the geography.

  • The time difference turns every question into a lost day. An anomaly reported in the morning is picked up in the evening, understood the next day, fixed the day after. Business teams learn to work around rather than report.
  • Language and context. A ticket written in French by a Moroccan accountant, translated into English for a distant centre, comes back with an answer that is technically correct and functionally beside the point. Business vocabulary, local practices, regulatory obligations do not survive translation.
  • Team turnover. In large offshore centres, the consultant who knew your configuration is replaced without your being told. The knowledge of your system leaves with them, and the learning curve starts again at your expense.
  • The absence of presence. Some subjects — the design workshop for an enhancement, taking charge of a major incident, the relationship with a business department — cannot be settled by video conference. When nobody can catch a plane in the morning to be there in the afternoon, they are settled badly.

None of these costs appears on the rate card. All of them appear in the operating account, in the form of delays, workarounds and impossible reversibility.

Why Casablanca.

The choice of locating the group’s SAP service centre in Casablanca is not a choice of convenience. It answers the pitfalls of distance point by point.

The time zone. Casablanca runs on Paris time, give or take an hour depending on the season. Teams work the same hours as your users, in Casablanca as in Paris, Dakar or Abidjan. A question asked in the morning gets an answer in the morning.

The languages. Our consultants work in French, Arabic and English. The accountant’s ticket is read in their own language by someone who knows their chart of accounts. An international group’s documentation is understood without translation. Documents in Arabic, in Document AI flows as in exchanges with government bodies, are no longer a blind spot.

The air hub. Casablanca has direct flights to the major European cities and to most capitals of French-speaking Africa. A consultant can be in your offices the same day. A design workshop is held in person, not as a mosaic of faces.

The group standard. This is the point that distinguishes a service centre from a subcontractor. The Casablanca centre applies the same methods, the same tools and the same quality requirements as KOORTIS in Paris-La Défense and AGILICIS in Dakar. The engagement lead is the same from scoping to production. Those who scope are those who deliver, and those who deliver are those who maintain.

A good service centre is not recognised by its hourly rate, but by the number of times you forget it is somewhere else.

Three engagement models, one principle.

There is no good model in itself; there is a model suited to your situation, and a principle that runs through all of them: accountability must rest with named people, and reversibility must be contractual.

The dedicated team

Consultants assigned to your account, who know your landscape, your key users and your ticket history. It is the model for complex or constantly evolving systems, where context is worth more than flexibility. It is managed as an extension of your team, with your rituals, your tools and your governance.

On-demand capacity

A minimal base of knowledge of your system, and skills mobilised as needed: a closing peak, a deployment wave, a regulatory change. It is the model for stable landscapes that want to stay agile without carrying a permanent team. Its condition for success: a core that does not change, so that the capacity mobilised does not arrive with a blank slate.

The fixed-price contract with service levels

A defined scope, response and resolution commitments by criticality, a known price. It is the model that reassures finance departments, and it is legitimate, on one condition: that the service levels cover what matters to the business — resolution, not a mere acknowledgement of receipt — and that they are measured transparently, with the same figures on both sides of the table.

In all three cases, we refuse two things: the silent rotation of consultants, and a contract without an operational reversibility clause. The knowledge of your system belongs to you. It must be documented, transferable, and transferred if you so decide.

Security and confidentiality: the question to ask first.

Entrusting your SAP to a service centre means entrusting access to your financial, commercial and sometimes personal data. The question of security is not dealt with in an appendix to the contract; it is dealt with before signing. A few requirements we consider non-negotiable, and which we apply to ourselves.

  • Named, traced, revocable access, with the principle of least privilege: each consultant accesses what their task requires, and rights are reviewed at every change of engagement.
  • Environment separation and control over what moves: production data does not travel to workstations, and test copies are anonymised.
  • Compliance with the law applicable to each of your entities, Moroccan, European or that of each African country where you operate, particularly with regard to personal data, and contractual clarity on where processing takes place.
  • Contractual confidentiality, from the first conversation, even without an engagement to follow. What you share with us stays between us.

These requirements are not brakes on efficiency. They are what allows a leadership team to sleep soundly having entrusted its core management system to a team it does not see every day. And one hour from Paris, it can see that team more often than it thinks.

What to remember

The real cost of a service centre shows in delays, workarounds and loss of context, not only in the hourly rate.

Casablanca

Same time zone as Paris, French, Arabic and English, direct flights to Europe and French-speaking Africa, and the quality standard of the KOORTIS · AGILICIS · INTENOV group.

The models

Dedicated team, on-demand capacity or fixed-price contract with service levels: the right model depends on your landscape. The principle does not change: named accountability, contractual reversibility.

Security

Named and traced access, separated environments, applicable law respected entity by entity, confidentiality from the first conversation. To be settled before signing.

To go further: our nearshore service centre offering, the presentation of the group and its common standard, and our point of view on SAP 2027 seen from Morocco, where the service centre takes over from the programme.

Your SAP run

What if the distance disappeared?

Thirty minutes with a manager from the Casablanca service centre, one hour from Paris, to look at your landscape, your service expectations and the engagement model that would suit you. Allions nos forces (let’s join forces).

Let’s talk