Eight teams, one demo day: the Bamenda Community Challenge

We ran the Bamenda Community Challenge starting June 9th. This is the fifth year we have done it, and it does not get any less satisfying to watch.

I am a co-organiser, not the lead, so my job was the unglamorous part that actually makes an event like this run. Workshops, logistics, sitting with teams and pushing their thinking. Alouzeh Brandon leads the whole thing and has for all five years. Tuesday through Thursday were workshops and design meetups, Friday was a bootcamp day, and Saturday every team stood up and demoed what they built in front of judges.

What we actually asked teams to build

The brief was simple. Build something as a startup, as founders, solving a real Cameroonian problem. Not a class project, not a toy. Something you would actually try to run as a business the day after the event ends. Eight teams took that brief, mostly building software, and spent the week turning a problem they knew personally into something working.

The workshops covered the parts most young builders never get taught here: how to pitch so a room understands your idea in two minutes, how to think about product and UX instead of just shipping features, and technical support when a team got stuck on the build itself. Demo day was judged, with a prize and follow-up support for the team that came out on top, so there was something real on the line beyond a certificate.

The team I could not stop thinking about

Out of eight teams, one stuck with me: Wé, a mobile app for shop and store owners to manage their inventory.

Inventory management is not a new idea, there are a hundred apps that do it. What got me was how deliberately simple theirs was. They were not building for developers or for people comfortable with software. They were building for a shop owner in Bamenda who has never used anything more complicated than WhatsApp, and who needs to know what is in stock without reading a manual first. That is a genuinely hard design problem, harder than the inventory logic underneath it, and they clearly understood that before they wrote a line of code.

I have spent enough of my career watching smart technical decisions get undone by a UI nobody outside the room can actually use. Watching a team of founders get that right, on their first real product, in the space of a week, was the best part of the whole event for me.

Why this is the story I wanted to tell

I write a lot about the harder side of building software from here, the power cuts, the payments, the clients who make you prove yourself twice. All of that is true and I am not walking any of it back. But it is not the whole picture, and events like this are the other half.

Eight teams showed up with real problems and left with real products, judged by people who took them seriously. Nobody in that room needed convincing that Bamenda has founders worth backing. We already knew that going in. The Bamenda Community Challenge is not trying to prove a point to anyone outside. It is just building the thing, again, for the fifth year running, and I get to help.

If you want to see what the event looks like or where it goes next, it lives at bamendacommunitychallenge.com.