There's a particular kind of pressure that comes with building something real.
Not the performative pressure of Twitter threads and "week 1 update" posts — but the quiet, persistent weight of knowing that actual people are depending on what you're making. Their orders, their livelihoods, their time.
That's the pressure I've been living inside while building Maha.
Why I'm writing this
I've been heads-down for months. Coding, shipping, debugging at 2am, rewriting things I thought were done. And somewhere in that blur, I stopped talking about it.
This blog is me correcting that. Not for the audience — for the discipline. Writing forces clarity. If I can't explain what I'm building and why, I don't understand it well enough yet.
What building in Lagos actually looks like
It means your product has to work on a 4G connection in Surulere — and yes, we have 5G now, but not everyone is on it. It means your payment flow has to handle failed transactions gracefully because the network dropped mid-checkout. It means your delivery logic has to account for the fact that street addresses don't always exist the way Google Maps thinks they do.
Every constraint is a design decision. Every workaround is a feature.
The thing nobody talks about
The loneliness of it. Not the romantic, founder-in-a-hoodie loneliness — the actual kind. Where you're not sure if what you're building matters, and you don't have a co-founder to ask, and the only feedback you have is a handful of users who are too polite to tell you what's broken.
You ship anyway. Because the alternative is not shipping, and that's worse.
I'll be writing here about building Maha, about software, about what it means to build for Africa from inside Africa. No frameworks for success. Just what I'm seeing.