Africa and the market

What two bases bring to an initiative anywhere in Africa

Companies with one foot in Mauritius and one in South Africa get described as having two offices. The useful description is what each base does for an initiative in another African country, and what the partner on the ground gets back.

In short
  • Mauritius is a platform. It offers institutions, treaty access and a legal system that reads well in English and French. It is a small market in its own right.
  • South Africa carries the engineering depth, the delivery certification and the nearest hyperscaler regions.
  • Our work in Zambia, Namibia and Botswana runs through a local partner who leads in-country. We bring proven software and delivery discipline.
  • Treaty coverage is uneven. Botswana and Namibia have tax treaties in force with Mauritius. The Zambia treaty was terminated in 2021, and in East Africa only Uganda and Rwanda are in force.
  • A partnership holds when both sides can name what they get. In-country capability first, exported afterwards.

A company registered in Ebene and delivering from Centurion gets described as having two offices. The description is accurate and it explains nothing. It does not say why anyone would arrange themselves that way, and it does not say what a business or a government in Lusaka, Windhoek or Gaborone gets from working with a company that has.

This is our answer, including the parts that do not flatter us.

What Mauritius carries

Mauritius sells institutions. The final court of appeal is the Judicial Committee of the Privy Council in London. The arbitration statute is built on the UNCITRAL model law, and the Permanent Court of Arbitration chose Port Louis for its first permanent office outside The Hague. The Mauritius Revenue Authority lists 45 double taxation agreements in force. Mauritius left the FATF grey list in October 2021 and the European Commission's list of high-risk third countries in January 2022, and is on neither today.

Those are the facts an investment committee tests when it asks who protects the capital and where a dispute would be heard. They are hard to build and easy to verify, which is what makes them worth something.

The tax rate is the weakest part of the case. The substantive reason to hold a structure in Mauritius is investment protection: fair treatment, protection against expropriation, free repatriation of returns, and access to international arbitration. For an operating company the substance requirements are part of the point. Real people, real premises and real spend are what we would have put there anyway.

There is one more thing Mauritius gives us that South Africa cannot build at home. Mauritian law is part civil law, and the country works in English and French. A Mauritian contract and a Mauritian team are legible in Abidjan, Dakar and Kinshasa in a way a South African common-law document is not. Francophone Africa is under-served by anglophone technology firms because they cannot staff French-language delivery. That is an argument, and I would rather present it as one than dress it up as a statistic.

What South Africa carries

South Africa carries the engineering depth and the delivery certification. It is where most of the team sits, where the quality gates were built and tested against regulated clients, and where the audit history lives. It also has the nearest hyperscaler cloud regions. Mauritius has certified colocation and direct fibre to South Africa, but a workload that needs an in-region hyperscaler today goes to Johannesburg or Cape Town.

For southern Africa the geography helps in a plainer way. Lusaka, Windhoek, Gaborone and Johannesburg share a time zone, and Port Louis is two hours ahead. A delivery team in Centurion works the same day as its partner in Gaborone, and can be on site in a couple of hours.

How it works in Zambia, Namibia and Botswana

Our work in these three countries follows the same pattern. A local partner leads. They hold the relationship, the in-country presence and the understanding of how things get done. We bring software that has already run in production, and the engineering and delivery discipline to adapt and deploy it.

In Zambia that means licensing a digital emergency response and safety platform to a Zambian operator. We provide the platform, the implementation and the support. The operator runs the service and owns its relationship with the people who use it. The licence sits with our Mauritian company, which is where the structure earns its keep.

In Namibia we work alongside Namibian partners on national systems: a skills marketplace that connects trainees and certified artisans with the people who need them, and regulatory monitoring work. The Namibian partner leads, and our teams build and support the platform behind it.

In Botswana we act as the digital delivery partner to a local systems integrator on a facilities, security and IoT programme. The integrator owns the physical scope and the client. We deliver the software, the integration and the data.

None of these works as an offshore contract. Each one is a named capability, delivered with someone who will still be in the country when we are not.

What each of the three bases carries Three columns side by side with arrows running both ways between them. Mauritius is the platform, carrying 45 tax treaties in force, a Privy Council appeal, a civil-law hybrid working in English and French, and the structure, treasury and intellectual property. South Africa is the delivery base, carrying engineering depth, certification and quality gates, the nearest hyperscaler regions and the audit history. The partner market carries the mandate: the local partner, the domestic market, the sovereignty requirement and the named in-country capability. None of the three is sufficient on its own. What each base carries None of the three is sufficient on its own MAURITIUS The platform 45 tax treaties in force Privy Council appeal Civil-law hybrid, EN and FR Structure, treasury, IP SOUTH AFRICA The delivery base Engineering depth Certification and quality gates Nearest hyperscaler regions Audit history PARTNER MARKET The mandate Local partner leads Domestic market and mandate Sovereignty requirement Named in-country capability Build the capability in-country first, then export the pattern through Mauritius. Johannesburg, Lusaka, Windhoek and Gaborone UTC+2. Port Louis UTC+4. One working day.
Each column carries what the other two cannot. The arrows run both ways on purpose: an arrangement that only flows outward is a sales channel.

What the partner market brings

If the arrangement only ran one way it would be a sales channel with better manners.

The partner market brings the thing neither base has: the domestic mandate. The relationships, the regulator who knows the partner, the procurement rules the partner has worked under for years, and the users who will live with the system. Increasingly it also brings a sovereignty requirement. Several African governments now write it into national strategy: national data owned, managed and protected inside national borders. Many international technology firms hear that as an obstacle. We treat it as a specification. We deploy on the client's premises, in their own cloud or in an environment we host, and we deliver in English and French as standard, so a sovereignty requirement is how we already build.

The same logic reaches further. In East Africa and the francophone west the demographic scale and the policy doors are real, and so is the need for delivery partners who can work in French. The pattern is the same everywhere: build the capability in-country first, then take it to the next market.

Where the paperwork has not caught up

The treaty map is uneven, and it is worth knowing before anyone builds a plan on it.

Mauritius has tax treaties in force with Botswana and Namibia. The Zambia treaty was terminated with effect from mid-2021, so a Mauritian structure brings less on the tax side in Zambia than it used to, and the case there rests on investment protection and contract law. In East Africa, Uganda and Rwanda are in force, Kenya is signed and awaiting ratification, and several others are under negotiation. Shared membership of SADC or COMESA settles less than people assume.

Itemising the gaps is useful. A partner who knows them in advance can plan around them.

What this means for a partner choosing who to work with

Three tests, which apply to us as much as to anyone else.

Ask where each capability physically sits, and ask the supplier to name the gap before you find it yourself. A supplier who says every base does everything is describing a brochure.

Ask what the local side gets. If the answer is jobs at some unspecified future point, the arrangement is a sales channel. If the answer is a named capability, built in-country, on a timetable somebody will be held to, it is a partnership.

Start with something small enough to fail safely. We begin with a short paid sprint of four to six weeks that puts something working in front of the people who have to live with it. If it is not working, you have spent weeks.

Our work in Zambia, Namibia and Botswana is recent and some of it is still being contracted. What I can describe with confidence is how the two bases work, what each is for, and what a version of this looks like when it benefits both ends. Early and patient beats late and certain.

Keep reading

More from Insights

Africa and the market

Getting ready for TISAX when your customer requires it

For many automotive suppliers a TISAX label is a condition of trade. What a readiness baseline found, and why the gap is usually between a control being designed and a control being switched on.

16 September 2026 · 3 min read
Data and decisions

Measuring personal growth honestly

Wellbeing products are full of impressive numbers. Most of them measure how people feel about themselves. That is worth measuring, as long as everyone is clear that it is what is being measured.

2 September 2026 · 3 min read