When teams plan a new financial product, they usually start with a smartphone app. It is the obvious choice in a meeting room. It is the wrong place to start if your goal is to reach everyone.
In Rwanda, and across much of the region, a large share of people use basic handsets, share a phone, or simply do not keep mobile data on. An app cannot serve them. USSD can.
What USSD actually is
USSD (Unstructured Supplementary Service Data) is the menu system you reach when you dial a short code like *123#. It runs over the mobile network itself, not the internet. There is nothing to download, nothing to update, and no data plan required. It works the same on a ten-dollar phone as on a flagship device.
That single property, it works on any phone on any network, is why USSD remains the most inclusive channel in emerging markets.
Why it still matters
Three reasons keep USSD relevant even as smartphones spread:
- Reach. It serves the customers an app leaves out, which is often the majority.
- Reliability. Sessions are lightweight and hold up on weak networks where an app would stall.
- Trust. People already know how to dial a code. There is no install friction and no learning curve.
For onboarding, payments, balance checks, registration, and information services, USSD frequently converts better than an app simply because more people can complete the flow.
What good USSD engineering looks like
USSD is simple for the customer and unforgiving for the engineer. A few things separate a service people rely on from one they abandon:
- Short, predictable menus. Every extra step loses people. Design the happy path to the fewest possible inputs.
- Fast sessions. USSD sessions time out. The system has to respond quickly and hold state cleanly between steps.
- Secure handling. Even without an app, you are moving identity and sometimes money. Sessions need to be protected and validated.
- Graceful failure. Networks drop. A good service recovers a session or fails clearly, never silently.
We design, build, and operate USSD services to those standards, and we run them in production today. The point is not the channel for its own sake. The point is that when the rails reach everyone, more people can be served, and that is where the growth is.
Where to start
If you are launching a service that has to reach the whole market, prototype the USSD flow first, not last. Map the menu, count the steps, and test it on a basic handset on a real network. If it works there, it works everywhere.
Want to talk through a USSD flow for your product? Start a conversation.
