A South African MSP evaluating M365 backup vendors typically starts on a marketing landing page priced in US dollars. The headline number is clean — "$3 per seat per month" or similar. The actual bill on the SA MSP's books at the end of the month is something else, and the difference is rarely on the landing page.
This piece works through where the difference comes from, what global vendors typically charge, what SA-resident vendors typically charge, and the policy and operational implications that fall out of the comparison. The numbers cited are publicly-listed marketing prices for representative tiers — actual contract prices vary with volume, term length, and negotiation.
The currency-conversion gotcha
A USD-denominated SaaS price applied to a SA MSP carries three line-item adjustments before the bill lands. First, the USD/ZAR exchange rate at billing time. The R/USD rate has spent the last twelve months in a band roughly between R17 and R20 per dollar — a 17% intra-year volatility window. Second, 15% South African VAT. Third, sometimes an FX spread or international payment fee charged by the payment gateway, typically 1-3%.
A "$3.00 per seat per month" headline at R18.50/USD becomes R55.50 net, R63.83 with VAT, and approximately R65 once payment-gateway fees clear. At R20/USD the same headline becomes R69. The difference between a budgeted R55.50 and an actual R69 across a thousand seats is R13,500 per month — meaningful for an MSP operating on tight per-seat margins.
What global vendors typically charge
Public marketing pages for the major global M365 backup vendors put per-seat per-month pricing in roughly this range: AvePoint Cloud Backup at $4-8 per seat depending on tier; Veeam Backup for Microsoft 365 at $2-4 per seat depending on perpetual versus subscription model; Datto SaaS Protection at $3-5 per seat; Keepit at $4-6 per seat; Druva Inside at $5-9 per seat. These are list prices; actual MSP-channel pricing is typically discounted by 15-30% with volume commitments.
At a representative midpoint of $5.50 per seat per month, an SA MSP's actual cost translates to roughly R125 per seat once VAT and exchange volatility are factored in. The same vendor's landing page never quotes that number.
A 17% currency-volatility band over twelve months means an MSP's per-seat backup cost can swing from R110 to R130 per seat between two billing cycles, on the same number of seats. SA-resident pricing in ZAR removes the swing.
What SA-resident vendors typically charge
SA-resident M365 backup vendors quote in ZAR with VAT included or VAT-clearly-separated. Public pricing across the visible SA-resident market puts entry tiers around R45-65 per seat per month and full-platform tiers up to R180-200 per seat per month, depending on add-on bundle. The pricing is fixed in rands — no exchange-rate exposure for the MSP, no FX-spread fees.
For a MSP buying a comparable feature set across the two paths — global vendor at $5.50/seat versus SA-resident at R85/seat — the SA-resident path saves roughly 30-35% per seat at current exchange rates, plus the volatility hedge. At scale this is the difference between a sustainable per-seat margin and a thin one.
Affordability as a competitive lever
Affordability is not a marketing adjective; it is a structural property of how the vendor is priced. SA-resident vendors that ship in rands and bill in rands have lower per-seat all-in cost for SA tenants by construction, not by discount. The lever is durable — it does not depend on the SA-resident vendor's pricing strategy, only on its currency of denomination.
For an MSP doing the calculation, the question is rarely "is the cheaper option good enough" — it is "where is the headline price actually coming from." A USD-denominated vendor selling into SA is paying for global infrastructure, USD-denominated salaries, and a global support footprint that the SA MSP's tenants do not benefit from. The premium funds capabilities the SA tenant does not consume.
Data-residency obligations that change the calculus
POPIA Section 72 governs cross-border transfer of personal information (Republic of South Africa, 2013). The provision is permissive but conditional — transfer is allowed where the recipient is bound by adequate safeguards equivalent to POPIA. In practice, SA tenants increasingly require backup data residency within South Africa specifically to simplify the Section 72 analysis.
Global vendors typically offer SA data residency as a configuration option, sometimes at a price premium. SA-resident vendors offer it as default. The comparison matters at the regulator-review stage of an incident: a tenant whose backup data is in a SA-resident vendor's SA data centre has a tighter, simpler Section 72 story than one whose backup is in a global vendor's EU data centre under a Section 72 transfer agreement.
POPIA implications
POPIA Section 19 frames "appropriate, reasonable technical and organisational measures" — a phrase that includes affordability when an MSP is balancing measures against budget (Republic of South Africa, 2013). Section 72 frames cross-border transfer. Both sections lean toward SA-resident solutions for SA tenants holding personal information, particularly in regulated sectors.
The Information Regulator has not specified that SA tenants must use SA-resident backup, and the law permits cross-border transfer with appropriate safeguards. The point is that the simpler regulator story is the one that does not need a Section 72 cross-border transfer agreement.
References
Republic of South Africa (2013) Protection of Personal Information Act, No. 4 of 2013. Government Gazette of the Republic of South Africa.
IBM (2025) Cost of a Data Breach Report 2025. IBM Security. Available at: https://www.ibm.com/reports/data-breach (Accessed: 8 May 2026).