One continent, three very different buying markets
'Africa' is not a procurement region. It's three, at least. A workforce split across Lagos, Nairobi, and Johannesburg is a workforce split across three currencies, three connectivity realities, three funding mechanisms, and three different talent markets. Treat them as one line in a vendor spreadsheet and you'll buy a tool that shines in one city and quietly fails in the other two.
Quickly, because it shapes everything downstream. Lagos is the currency-risk market, where the naira's swings can rewrite a contract's economics between signing and the first renewal. Nairobi, the self-styled Silicon Savannah, is the connectivity market, where delivery over metered data on a mid-range Android is the constraint that decides everything. Johannesburg is the compliance market, where SETA levies and B-BBEE scorecards mean the same spend can be worth far more or far less depending on how it's structured. A vendor tuned for one of these is not automatically fit for the other two.
The money is real and it's growing fast. South Africa alone accounts for something close to a third of the continent's e-learning spend, Nigeria is the next-largest single market, and corporate learning is the slice pulling ahead of the rest. That growth dragged in a crowd: continental names like ALX and Andela, local specialists like Utiva, Gomycode, Moringa School, and Decagon, all pitching the same enterprises. Telling the ones that deliver from the ones that only present well is the whole job of this guide.
Related reading: Nigeria's 3-Million Tech Talent Gap in 2026: A B2B Vendor Playbook for Lagos · South Africa's Enterprise AI Upskilling Reset in 2026: An L&D Leader's Playbook · Nairobi's Silicon Savannah in 2026: How Enterprises Are Hiring and Building AI Teams.
The currency question comes first
Before pedagogy, before the content library, before the demo, ask how the vendor prices and in what currency. This has killed more African training contracts than weak content ever did. A dollar-denominated deal with rigid terms looks fine on signing day and turns punishing the moment the naira or the cedi moves against you. Nigeria taught this the hard way: vendors who quoted in dollars through 2024 watched accounts walk to local players who never carried the mismatch.
Nail these down in the contract, not on the kickoff call:
- Currency of the quote, and whether it's held fixed for the full term or floats.
- Local-entity invoicing, which matters for tax and forex controls in all three markets and whose absence can strand a payment for weeks.
- How renewals reprice. A vendor who quietly resets to the spot rate at renewal is a vendor you're already replacing.
- In South Africa, whether the spend qualifies for a SETA offset and feeds your B-BBEE scorecard. That line moves the real cost more than any discount the sales team offers.
Get that local-entity invoicing point in writing early. A vendor billing from Delaware or Dubai into a Lagos subsidiary can leave your finance team fighting forex controls every quarter, while a competitor with a Nigerian or South African invoicing entity gets paid on time and keeps the relationship warm. That friction is invisible in the demo and very visible by month three.
None of this is glamorous. All of it decides whether the contract still makes sense in month nine.
Delivery: build for the phone that's actually in the room
Africa crossed 500 million smartphone users years ago, and most enterprise learners do their training on a mid-range Android over metered data. Delivery is not a footnote in the RFP. It's a pass-fail gate, and it's where the cleverest-looking platforms fall over.
Here's the failure that taught me to test delivery before anything else. A client rolled out a well-reviewed platform to a field cohort and watched the dashboard stall at 40 percent completion for a month. The team read it as disengagement and nearly pulled the plug. The truth only surfaced when someone reconciled a sample of handsets against the vendor's reported numbers: the learners had finished. The platform fired its 'completed' event only on a final cloud sync, and that sync never went through on a capped data bundle. The training worked. The reporting lied. Trust that dashboard and you cancel a programme that's doing its job, or on a different build you renew against completion figures that were never real.
Put these in the RFP as hard requirements, not nice-to-haves:
| Requirement | Why it matters | How to test it |
|---|---|---|
| Low module weight (MB) | Learners pay for their own data | Ask for the average; if they don't know it, they never measured |
| Real offline mode | Connections drop mid-module constantly | Test on a Tecno or Infinix, not the demo iPhone |
| Reliable progress sync | Lost progress kills engagement fast | Kill the connection mid-module, reopen, check the state |
| Honest completion reporting | Dashboards drive your renewal decision | Reconcile a sample of devices against the vendor's reported numbers |
| Localisation | Swahili, isiZulu, Nigerian English land differently | Ask what is properly localised versus auto-translated |
Localisation is where the gap between a demo and a deployment shows up. 'We support 40 languages' usually means machine translation with the idioms left in. Swahili in a Nairobi call centre, isiZulu on a Durban factory floor, and Nigerian English in a Lagos bank are not interchangeable, and learners can tell within a screen or two whether a person who speaks their language built the content or a translation API sprayed it on afterwards. Ask which languages are properly localised, by whom, and when a native speaker last reviewed them.
Content vs. outcomes: the pivot every buyer should make
The vendors still opening with '4,000 courses' on slide one are selling last decade's product. A course count is an input. Your CFO is buying an output. The most useful move in your evaluation is to stop scoring library size and start scoring whether a vendor can tie their training to a number you already track.
Ask one question and watch the shortlist thin: show me a client who looks like us, and the operational metric that moved after your programme. A real vendor answers with a name and a figure. A slideware vendor answers with testimonials about 'engagement' and 'empowerment'. One of those is evidence. The other is wall art.
This is also the quickest way to separate a partner from a reseller. A partner has sat with a client's operations data and can point to the line that moved: average handling time, first-call resolution, loan-processing turnaround, defect rate. A reseller has a catalogue and a login. Both will happily quote you 4,000 courses. Only one can tell you which three of those courses a comparable client actually finished, and what changed on the floor afterwards.
Insist on a paid pilot with a baseline
Never sign the enterprise licence first. Run a paid pilot. Sixty to ninety days, one department, one number agreed before anyone logs in. The discipline is the same whether you're running it in Ikeja, Westlands, or Sandton:
- Pick one team of 25 to 40 that already reports a weekly metric.
- Baseline that metric for four weeks before any training starts.
- Hold a control group of comparable staff who train later.
- Measure at 30, 60, and 90 days, and expect real behaviour change around week eight, not week two.
- Convert the trained-versus-control gap into money. That number is your rollout case.
The step buyers skip most is the baseline, and skipping it is fatal. Without four weeks of before-numbers and a control group, you can't separate training's effect from seasonality, a new manager, or a team simply trying harder because it knows it's being watched. That's how organisations renew a programme on a feeling. The baseline and the control are cheap. The wrong annual licence is not.
A vendor who backs their product takes those terms without flinching. A vendor who pushes hard to skip the pilot and sign the annual licence is telling you they don't trust their own outcomes. Believe them.
A scoring sheet you can actually use
Boil the whole thing into a weighted sheet so procurement and L&D argue about the same numbers instead of talking past each other. My rough weighting for a 2026 African enterprise buy:
- Outcome evidence (a real client, a real moved metric): 30%
- Delivery fit for mobile and low bandwidth: 20%
- Commercial terms and currency safety: 20%
- Localisation and regional presence across your actual sites: 15%
- Pilot willingness and measurement rigour: 15%
Notice what isn't on the list: content library size. If you want it as a tiebreaker, fine, but it shouldn't score a single point against outcome evidence. And weight that last line heavier than it looks, because a vendor's willingness to be measured is the best single predictor you have of whether they'll deliver.
Buy for the workforce you actually have, on the Tecno and Infinix handsets they actually carry, in a currency the naira or the cedi can't ambush at renewal, against a number you agreed before signing. Do that and the crowded African upskilling market gets a lot easier to read. Skip it, and you'll be back running this same procurement a year from now, wondering why the last vendor never stuck.