For those who don’t know: Anfani is a platform helping people, especially across Africa, find real opportunities: scholarships, internships, roles. We launched on Google Play earlier this year, and every week I’m reminded why we started: the messages from people who found something that changed their plans.
I’ve been a software engineer for over six years. I’ve migrated legacy systems, built enterprise workflow engines, and shipped SaaS products for clients. I thought I knew how to build software. Building Anfani taught me I knew how to build software for other people. Building it for yourself, for your own users, your own money, your own reputation, is a different education entirely.
Launching is a feature, not the finish line
There’s a fantasy that goes: you build the thing, you launch, and then it works. I’ve now launched enough things to know that launch day is about 5% of the journey, and it’s the 5% that matters least.
Our Google Play launch was exciting. Then came the real work: the first one-star review that stung more than it should have, the crash report from a device we’d never tested on, the user who couldn’t figure out how to sign up and just… left. None of that was in the launch plan, because launch plans are written by people who haven’t launched yet.
What launching actually gave us was contact with reality. Every assumption we’d argued about for weeks got settled in days, not by debate, but by data. That feature we were sure was essential? Nobody touched it. That screen we almost cut? It’s the most visited page in the app. Launching didn’t finish anything. It started the part that matters.
User feedback is the spec
On client projects, the spec comes from a stakeholder meeting. On Anfani, the spec comes from users, and users don’t write specs, they write complaints, suggestions, and occasionally very blunt reviews.
Learning to read those as product direction took practice. “The app is confusing” isn’t actionable. But five people saying “I couldn’t find the scholarships section” is a spec: the navigation is wrong. “It would be nice if…” from one person is a nice-to-have; the same request from twenty people is a roadmap.
The discipline I’ve developed: ship, listen, adjust. Small loops, constantly. We stopped trying to predict what users wanted and started watching what they did. Analytics tell you what happened; the messages tell you why. You need both, and neither replaces the other.
This is also where building in public pays for itself. When you share what you’re building as you build it, feedback finds you. People tell you what they’d want from a platform like this, and that feedback genuinely shapes what we build next. It’s free user research, if you’re humble enough to listen to it.
Consistency beats intensity
The most underrated lesson. Everyone imagines the startup journey as heroic sprints, the all-nighter before launch, the frantic pivot. In reality, Anfani has moved forward on small weekly progress: one feature shipped, one bug fixed, one user conversation, one post shared.
I used to think motivation was the fuel. It’s not. The system is the fuel. A quiet Tuesday where you fix three small bugs and reply to two users moves the product more than a dramatic weekend sprint that burns you out for the following week. Consistency compounds in a way intensity can’t, because consistency is still there in month six when the excitement has worn off.
This connects to something I learned years ago on migration projects: boring engineering done consistently beats heroic engineering done occasionally. It turns out the same is true of building a product.
What I’d tell anyone starting
If you’re building something of your own, an app, a side project, a platform, here’s the honest version:
Start before you feel ready. You’ll never feel ready, and the readiness was never the point. The point was contact with reality, and you only get that by shipping.
Listen more than you defend. Every piece of feedback is data, even the unfair ones. Especially the unfair ones, they tell you where your communication failed, not just your product.
Share the journey. Building in public felt exposing at first. Now I see it as the single best decision we made, it brought us users, feedback, collaborators, and a record of how far we’ve come on the days when progress feels invisible.
We’re still early and still improving. If you know someone hunting for opportunities, a scholarship, an internship, a role, send them our way. Anfani exists because we believe talent is everywhere, but opportunity isn’t. We’re trying to fix the second part.
And if you’ve built something of your own: what did it teach you that no course could? I’d genuinely love to hear it.
