Why We Price Enterprise AI in Rand, Not Dollars

Most enterprise software sold in South Africa is priced in US dollars. The invoice may arrive in rand, but the number is pegged to a dollar figure and re-converted every cycle. That arrangement looks neutral and is not: it silently moves currency risk from the vendor — who could hedge it — onto the customer, who usually cannot. Pricing in rand reverses that. This is why we do it.

The hidden question in every USD invoice: who carries the FX risk?

When software is priced in dollars, the South African buyer absorbs every movement in the ZAR/USD exchange rate. A budget signed in January can be 10–15% more expensive by June without a single line item changing, purely on currency. Rand-denominated pricing moves that exposure to the vendor, who is far better placed to manage it. The buyer gets a number they can put in a budget and trust for the year.

This matters most for the people who approve software, not the people who use it. A CFO cannot forecast a cost that floats with the currency. An unpredictable line item is a reason to delay or decline adoption — which is why FX-indexed pricing quietly suppresses enterprise software adoption across the continent.

A 5% rand move is a margin event

For a business buying USD-priced tooling, every adverse 5% move in the rand is an unbudgeted increase that lands straight on the operating line. Over a year of normal currency volatility, that can swing a software budget by double digits. The vendor experiences none of this; the customer experiences all of it. Calling the price "global" does not make the risk disappear — it just assigns it to whoever is weakest at managing it.

Rand pricing is not a discount — it is a risk transfer

It is worth being precise: pricing in rand does not necessarily make software cheaper in absolute terms. What it does is remove variance. The customer trades the possibility of a favourable currency swing for the certainty of a fixed cost. For enterprise procurement, certainty is worth more than the lottery ticket — budgets are annual, and a predictable cost is one you can actually approve.

Why this fits the rest of our architecture

Rand pricing is one expression of a broader thesis: software built for South African conditions should remove South African frictions rather than import foreign ones. The same logic drives in-region hosting in AWS af-south-1 (covered in the residency explainer) and POPIA-native compliance (in the POPIA deep-dive). Currency, residency, and compliance are the three frictions foreign SaaS imposes by default; addressing all three is the point of building locally.

How our pricing works

Our subscriptions are quoted and billed in rand, from a fixed monthly figure, with no dollar peg and no FX surcharge. The full tier breakdown — and the founding-customer programme — is on the pricing page. The strategic frame behind the whole platform is in the pillar essay.