
As a founder, you've probably shipped something technically sound that barely moved. Not because the product was broken or lacked skill. But because something upstream was off — something in how you framed the problem, who you believed was worth solving it for, and what you assumed the user actually needed. That upstream thing is something we rarely speak about - a belief gap. The most adopted products in Africa — and the ones that eventually get funded — aren't always the most elegant. They're built by founders who have interrogated their own assumptions about the user before writing a single line of code. In this session, we'll get into the parts of product-building that don't show up in roadmaps or pitch decks: how your internal model of the user shapes what you build, and how to close the gap between what you think people need and what they'll actually pay for. You'll leave with a sharper lens for building things that fit — and a clearer read on where your assumptions might be costing you.