Markets
Africa is not one market, and a system that pretends it is will break at the first border. We design for the differences between markets from the start — so that growth into the next one is configuration, not reconstruction.
Connected markets
Fourteen markets we design for — and the connections between them. No market is the centre; the system is designed to work across them.
Working in another African market? Most of what we design transfers; tell us where and we will say what changes.
Designed with regional differences in mind
These are the inputs to every architecture we draw. They are held as configuration inside the system — which is what makes the second market possible without a second system.
Mobile money, cards, bank transfer, cash on delivery — and the mix shifts from market to market. The checkout, the reconciliation and the refund flow are designed for the methods customers actually use.
English, French, Arabic, Portuguese, Swahili and the languages customers message in. Interfaces, automated replies and documents hold language as configuration, not as a rebuild.
Several currencies, sometimes within one business. Pricing, invoicing and reporting keep the currency on every record and consolidate to one set of numbers.
Invoice formats, tax rules, data protection and sector regulation differ by country. The system holds them as rules per market, applied automatically.
Address conventions, delivery zones, last-mile partners and cross-border corridors vary. Delivery promises are computed from real rules for each market, not typed by hand.
Data costs, network quality and the phones in customers' hands shape every interface. Pages are light, apps work offline where they must, and messaging is a first-class channel.
How customers discover, compare, negotiate and pay differs — trust is built differently in each market. Acquisition and conversion flows are designed against that behaviour, not a global template.
A business in two markets needs one system with two configurations, one set of numbers and no duplicated staff. The architecture is designed for the second market before the first goes live.
Regions
Broad patterns, not statistics — the things we check first when a business tells us where it operates. Every engagement then starts with the specifics of its own market.
Nigeria · Ghana · Côte d'Ivoire · Senegal
Kenya · Tanzania · Uganda · Rwanda · Ethiopia
South Africa · Zambia
Egypt · Morocco
Cameroon
Dedicated market pages
We publish a dedicated page for a market only where we have genuine, current operating insight and commercial activity — never a thin page for search engines. As engagements complete in each market, its page follows.
Cross-border growth
When a business we work with enters a second country, the system already knows how. This is what it holds per market:
One conversation about where the business is, where it is going, and what the system has to hold to get there.
Start a Project
