A Nairobi developer building a WhatsApp automation tool for local SMEs finished the Meta verification process in four days.
The next step was selecting a Business Solution Provider. There are hundreds. The cheapest credible option was $49 per month. That is before Meta's per-message fee, before the BSP markup, before a single message was sent.
He chose the one with the most English-language documentation and the shortest thread about African deployments.
The category is mandatory. The market serving it is thin.
Meta does not offer direct WhatsApp Business API access. Every business using the API goes through a BSP. No exceptions.
The BSP charges in two layers. The first is a platform fee - $49 to over $500 per month, regardless of message volume. The second is a per-message markup, typically 15 to 20 percent on top of Meta's base rate.
The established providers - WATI, 360dialog, Respond.io - priced for MENA and Indian market assumptions. Their lowest tiers start at $49, $47, and $79 per month respectively. Per-message markup adds 15 to 20 percent on top of that. The total cost to an African SME runs 2x to 5x Meta's published rate.
Total cost at sign-up is rarely disclosed before the first invoice. The businesses discovering this after the invoice have not made a research error. The information is structured to be found late.
In May 2026, a Brazilian founder described the BSP market in a single post. WhatsApp for business was an expensive BSP and a bot that answered "I did not understand". The dashboard had not changed since 2014. His company, Arara HQ, spent six months rebuilding the full stack from scratch. New API layer. New conversation interface. New pricing built from Brazilian SME revenue assumptions. The post drew 138 likes. For most who responded, the description was familiar.
Africa has not produced the equivalent.
The conditions for doing so are more acute. Nigeria's marketing rate - $0.052 per message - sits among the highest globally outside Europe. The revenue context in which that rate lands is African ARPU, not European ARPU. A BSP priced for Indian market assumptions and deployed in Lagos is not a localisation gap. It is a structural mismatch between the pricing layer and the market it serves.
Seventy-eight percent of Sub-Saharan African SMEs run their sales through WhatsApp. DuceCRM, CRM Africa, Sukhiba, and Ghala are each building automation and CRM products on top of that channel. The unit economics of WhatsApp-native African software are partly set by the BSP layer beneath them. A BSP built for African conditions lowers the floor for every product in the ecosystem.
The market case is structural, not speculative. The BSP is mandatory infrastructure for the largest messaging channel on the continent. Existing providers either skip Africa entirely or treat it as a MENA afterthought. The window for an Africa-first BSP to become the default infrastructure layer is open.
What building it requires is not primarily an engineering problem. It is a pricing model problem. A cost structure that begins at African SME revenue levels, not MENA enterprise tolerances. Transparent per-message rates from signup. Documentation built for the developer ecosystem actually working in this market.
The Nairobi developer chose the BSP with the shortest thread about African deployments. He did not make a bad choice.
There was no better one.
