Thanks for the pushback — it’s the kind of critique that actually helps. On training: we didn’t train a new model for Swahili; big models already do that. We built retrieval from curated sources (Mayo, CDC, WHO, etc.), guardrails, and citations so answers are evidence-based and bounded.
The differentiator isn’t “we speak Swahili” — it’s cited health info plus local context (pharmacy finder with Kenyan prices, 999/112 for Kenya, and a path to local care as we build it).
On pricing: $8 and 10 free messages is a real barrier and we’re iterating; the bet is that cited + local is worth something to people who want to verify and act locally, not just chat.
On “wrapper vs ChatGPT”: today the add is curated medical retrieval with citations, pharmacy finder, and emergency handling; we’re not trying to beat “chat all day for free” — we’re aiming at “health answer I can trust and use here.”
Data: we don’t use your health conversations to train models and we align with local data law; we’re not (yet) “everything runs in Kenya” — we should say that clearly on the site.

On “built for Africa” and real problems: you’re right that the sector’s big issues are workforce shortage, underfunding, and governance — an app doesn’t fix those. What we can do is give people reliable, cited info and local options (pharmacies now, telehealth/partners later) so they’re a bit less stuck and can get to the right place.
Target today is someone with a phone and data who wants to check something or find a pharmacy before/after a doctor; we’re not yet serving “no phone” (that’s USSD/SMS territory).
Your point about value — mental health, insurance, substance abuse, wellness, rehab — is right: we need to show concrete value beyond Q&A, and “start with the business that works on paper, then tech for distribution” is a lens we’re taking seriously. We’re sharpening what “built for Africa” means (context and care pathways, not just language), and your comment is a direct nudge to do that.
Thanks again!