What five years of running programs taught me
Five years and more than 5,000 founders later, I have finally admitted that the programs we are known for are the least important thing we do.
Magothe Innocent · Anko wa Startups9 September 2026 · 4 min readFive years and more than 5,000 founders later, I have finally admitted that the programs we are known for are the least important thing we do.
That is a strange thing to say out loud. We built our name on those programs. X number of weeks, a sharp curriculum, good mentors, a demo day people still talk about. When I started in 2020, I thought the formula was simple. Teach founders the right things and more of them will make it.
Then I started paying attention to what happens after the programs end.
A cohort finishes on a high. Everyone scatters back to their lives. And three months later, when we check in, half the momentum we built together is gone. The founders still climbing are rarely the ones who were sharpest in the room. Something else decides who makes it, and it took me years to see what.
Here is what five years have taught me.
Teaching is the easy 20 percent
The content was never the bottleneck. Almost everything we teach you can find in a book or on YouTube for free. What you cannot download is a reason to keep showing up after the excitement wears off. The founders who keep going are the ones with a place to return to, and people to return to, week after week. That is the whole reason we stopped being a programs company and built Hackhouse Africa . Founders already have plenty of events. What most of them are missing is somewhere to belong on an ordinary Tuesday.
You cannot teach hunger
I used to bet on the sharp ones, the confident ones, the ones who pitch well. Five years in, the pattern is much plainer than that. The founders who make it show up when nothing is happening. No demo day, no deadline, no one watching. Just them, still working the same boring problem. We can teach the missing skills easily enough. What we cannot put into anyone is the will to keep going when it stops being fun. So we look for the people who already have it, and we get behind them.
Community is the curriculum that sticks
Founders come for the sessions and stay for each other. The chance introduction that turns into a co-founder. The late-night voice note from someone one step ahead who has already solved the thing you are stuck on. The person across the table who survived the exact month that is breaking you right now. Years later, people barely remember a single slide. They remember who sat next to them. So we flipped it. The people are the point now, and the content is the thing that gets them through the door.
Back the person, because the company will change
Almost every founder we back ends up building something different from what they first showed us. The idea moves, the market pushes back, the plan bends. The one thing that stays the same is the person. So we hold their first idea loosely and pay attention to the human instead. How fast do they learn. How do they handle being wrong. Do they come back after a bad week. Back someone who learns quicker than their problems grow and you will be right more often than not.
We were measuring the wrong things
For years we counted the easy things. How many applied. How many seats we filled. How many turned up to demo day. It all looked good in a report and told us almost nothing that mattered. The number that counts is the hard one to see: who is still standing twelve and twenty-four months later, still serving customers, still in it. The day we started caring about year two instead of week twelve, everything about how we work changed.
Five years in
So here is where this leaves me. There is no shortcut you can teach that beats a founder showing up, around the right people, for long enough. It is slow. It does not make a good poster. It is also the only thing I have watched work, over and over.
That is the whole job now: give people a room, put the right people in it, and give them a reason to keep coming back long after the applause dies down. Everything else we build sits in service of that.
If you run a program, or you are thinking about starting one, do not pour everything into the twelve weeks. Build for the day after they end. That is where it is won.