When we set out to build Anzisha, a business feasibility platform for Tanzanian entrepreneurs, we thought the hardest part would be the AI scoring engine. We were wrong. The hardest part was everything else: localization, payment integration, trust building, and the dozens of small design decisions that determine whether a platform gets used or abandoned.
Here's what we learned. These lessons apply to anyone building digital products for the East African market.
Lesson 1: Bilingual Is Not Translation
Anzisha supports both Swahili and English. Our initial approach was straightforward: build in English, translate to Swahili. This was a mistake. Swahili-first users don't just need translated labels. They need different mental models, different examples, and different navigation patterns.
For example, the concept of a "feasibility score" translates directly to Swahili, but the concept doesn't land the same way. Tanzanian entrepreneurs we tested with wanted to understand "will this work?", not "what is the feasibility score?" The distinction seems subtle, but it changes how you present the output, what data you emphasize, and even the visual hierarchy of the results page.
Key Insight
True bilingual design means designing two experiences, not translating one. Test with Swahili-first users from the beginning, not after the English version is "done."
Lesson 2: Mobile Money Is the Payment Rail
We integrated M-Pesa and Tigo Pesa as primary payment methods. Credit card support was an afterthought, and the data validated this decision. Over 90% of our test transactions came through mobile money. More importantly, the conversion rate for mobile money was significantly higher than card payments. Users trusted it more and the friction was lower.
The technical integration with M-Pesa's API has its challenges: callback reliability, transaction status polling, and handling the various edge cases of mobile money (network timeouts, insufficient balance, SIM swap scenarios). But these are solvable engineering problems. The bigger insight is strategic: if your pricing model doesn't work at mobile-money-friendly price points (round numbers, TZS-denominated), you'll struggle with conversion regardless of your UI.
Lesson 3: AI Must Be Grounded in Local Data
Anzisha's feasibility scoring engine uses AI to evaluate business plans. Early in development, we found that general-purpose AI models had significant blind spots when it came to the Tanzanian market. They would flag businesses as high-risk that were actually well-suited to the local context, or overrate ideas that didn't account for local infrastructure constraints.
Our solution was to ground the AI with local data: actual business registration statistics from BRELA, sector-specific data from the Tanzania Investment Centre, pricing data from local markets, and regulatory requirements specific to different business categories. The AI layer provides the scale; the local data provides the accuracy.
Lesson 4: Trust Is Designed, Not Assumed
Tanzanian users are understandably cautious about entering business information into digital platforms. Data privacy concerns, experiences with unreliable platforms, and general skepticism about "too good to be true" digital services all contribute to a trust deficit that doesn't exist in more mature digital markets.
We addressed this through several design decisions:
-
Progressive disclosure: Users can explore the platform and see sample outputs before creating an account or paying anything.
-
Transparent methodology: We show users exactly how their feasibility score is calculated. No black box.
-
Local branding: Swahili naming, Tanzanian imagery, and content that reflects the local business environment, not generic stock photos of Silicon Valley offices.
-
Offline capability: Key outputs can be downloaded as PDFs for sharing in environments where connectivity is intermittent.
Lesson 5: BRELA Integration Is a Superpower
One of Anzisha's most valued features is its integration with BRELA registration guidance. For Tanzanian entrepreneurs, the business registration process is often the first major hurdle. By providing step-by-step guidance specific to their business type, including required documents, fees, and expected timelines, we turned a friction point into a value proposition.
This feature wasn't in our original spec. It emerged from user research. Founders kept asking "okay, my business is feasible, now what?" The answer, for most, was "register with BRELA." So we built the bridge.
What We'd Do Differently
If we were starting Anzisha from scratch today, we'd invest more in community features earlier. The business idea marketplace, where entrepreneurs can browse and evaluate business opportunities, is shaping up to be one of the platform's most engaging features based on early testing. We built it as a secondary feature, but test users treat it as a primary one. The lesson: East African entrepreneurs are hungry for peer learning and idea exchange, not just tools.
We'd also invest more heavily in WhatsApp integration from day one. Many of our test users found Anzisha through WhatsApp groups and prefer to interact with digital services through messaging rather than traditional web interfaces. Meeting users where they are, not where you think they should be, is the fundamental product lesson we keep relearning.
Avril Capital builds digital platforms for the East African market. If you have a platform idea you'd like to explore, let's talk.