A Nigerian SME signs up for a US SaaS tool because it is the well-known option. Twelve months in, they have paid four times what they expected. Here is where the money goes.
The sticker price lie
The line on the website says $29/month. That is not what you will pay. Here is what you will actually pay.
1. The currency tax
You are paying in dollars. Your revenue is in naira. Every time the FX rate moves against the naira (which it does, repeatedly), your "$29 a month" becomes a different number in your local currency. Over a year of currency volatility, the effective cost can be 30-50% higher than you budgeted.
This is not theoretical. Any Nigerian business that signed up for a US SaaS at one FX rate and renewed a year later at another knows the feeling.
2. The customisation tax
The product was built for US or EU customers. The fields are wrong for your business. The currency formats are wrong. The address formats are wrong. The reporting templates assume a tax regime you do not operate in.
So you customise. You pay a consultant to glue it together. You write internal documentation explaining which fields to ignore. You train every new hire on "what we actually use this tool for, versus what it says it does." That is an ongoing cost, paid in staff hours every month.
3. The integration tax
The tool does not connect to your local bank's API. It does not handle NIN or BVN. It cannot pull from the Nigerian tax portal. It has no idea what NDPR is.
So you build glue code. You hire someone to maintain the glue. The glue breaks when the vendor updates their API. The glue breaks when your bank updates theirs. You pay for the integration work twice — once to build, then forever to maintain.
4. The support tax
When something breaks at 4pm on a Tuesday in Lagos, the vendor's support team is asleep in San Francisco. You file a ticket. You wait 14 hours. The first response is a copy-paste asking for screenshots. The actual resolution takes three days.
During those three days, your business is degraded. You are paying staff to work around the broken tool. The "support included" in your subscription does not include speed of response that matters for your operating reality.
5. The roadmap tax
You file a feature request. The vendor's response is polite. They will consider it. The feature ships in 14 months, if at all, because their priority is the US customers who pay them 50x what you do.
So you live without it. Or you build it externally. Either way, you are paying the cost of having no say in your own tools' direction.
Adding it up
The honest total cost of running a foreign SaaS in a Nigerian business is rarely 1x the sticker price. In our experience, depending on the tool, it is 3x to 6x once you include all of the above.
Most businesses never do this accounting. They see the $29 and they sign up. They never compute what the year-end cost actually was.
The sticker price of foreign software in Africa is what you start paying. The real cost is what you keep paying after the sticker stops being interesting.
The case for locally-built software
Locally-built software, priced in naira, designed for Nigerian business reality, supported in Nigerian time zones, integrated with Nigerian banks and identity systems — does not have most of these taxes.
That is the argument. Not that local software is always better. Not that local software is always cheaper at the sticker level. The argument is that the total cost of ownership for a local tool is usually a fraction of the total cost of a foreign tool that does not quite fit.
What "fit" means
It means the field labels match how you actually talk about your business. It means the payment flows match how Nigerians actually pay. It means the verification flows know what a NIN is. It means the support team picks up the phone before your day is over. It means the FX risk lives on the vendor's books, not yours.
None of these are exotic features. They are the baseline that local software starts from and that foreign software has to retrofit, badly, if at all.
The honest counter-argument
Some categories of software are genuinely better as foreign products. Developer tools. Some highly specialised analytics. Where the market is global, the foreign tool may win on quality even after the taxes above.
But the long list of "business operations" software — invoicing, payroll, CRM, property management, hospitality, fleet tracking, identity — is where local builders should win, and where foreign tools are still the default mostly because of inertia and marketing budgets.
Inertia is a cost too. Add it to the list.
What we do about it
We build software that is born here, priced here, and operated here. Our customers do not pay an FX risk premium. They do not file tickets into a void. They do not customise around the tool's blind spots; the tool already has the things they need.
This is not a charity exercise. It is a calculation. The total-cost-of-ownership math favours local software for African businesses, almost every time. We think more African operators should run the numbers themselves.