About
I've been building things since 2011. Not managing things. Not planning things. Actually building them — writing the code, debugging the hardware, shipping the feature, watching real users use it. Fifteen years in, that hasn't gotten old. If anything, it's gotten more interesting.
This is not a resume. It's a story of what I've actually built and why I'm not done yet.
The Journey
It started with Android. In 2011, when the ecosystem was still young and a decent mobile app felt like magic, I was writing apps and figuring out how to make things work on devices that had barely any RAM and a fragmented OS. That time taught me something I still rely on: when the platform is immature, your fundamentals have to be solid.
From mobile, I moved into fintech — and fintech changed everything. At Mahindra Comviva, I worked on Zoto, which became Nigeria's leading payments super-app. Millions of users sending money, paying bills, accessing financial services from their phones. The scale was real, the stakes were real, and the complexity of building in a regulated, multi-currency, high-transaction-volume environment taught me what engineering actually means when it has to work.
That same period produced DBXP — a digital banking platform that went live across 15+ countries. Not a prototype. Not a pilot. A platform in production, handling real money, in markets with different regulations, different currencies, and different user behaviors. Building for that kind of breadth forces you to design systems that are genuinely flexible rather than just theoretically clean.
Then came logistics. I joined Raaho, a logistics tech startup, and took on a different kind of challenge — leading cross-functional engineering teams, architecting a backend of 50+ microservices, and building in a domain where the physical and digital worlds collide in ways that keep you humble. Trucks move. Drivers go offline. GPS drifts. Systems that work perfectly in staging break in interesting ways when a driver is in a dead zone on a highway at 2am.
Along the way, I built a complete closed-loop NFC Tap & Pay prepaid payment system — alone. Hardware integration, backend API, transaction engine, merchant dashboard. The whole thing. That project taught me more about end-to-end systems thinking than anything else I've done. When you're the only person who can fix something, you learn every layer of it.
Most recently, I've been deep in AI agents. Chhotu Bot — a Telegram assistant powered by OpenAI — now handles GitHub PR summaries, CleverTap analytics reports, and DigitalOcean cron monitoring for my team. What used to be 90 minutes of daily dashboard-checking is now three commands in a chat window. I built it because I was tired of being the glue between my own tools. I kept building it because it actually worked.
What Drives Me
I build because I genuinely cannot stop thinking about what's broken and how it could be better. Not in an abstract, whiteboard-session way — in a "why is this dashboard still open when I could automate this" way. The thing that gets me out of bed is the gap between how things work and how they could work, and the fact that I know how to close it.
I'm most alive when the problem is hard, the domain is real, and I have the freedom to go from idea to production without asking permission at every step.
What's Next
I'm not going anywhere in a hurry. I'm heads-down at Raaho, building real systems that move real trucks across real roads — and that work is genuinely interesting.
But I also know where things are going. AI is changing what's possible at the infrastructure and product level faster than most companies can adapt. I've been building into that shift deliberately — not because I need to, but because I want to be at the frontier of it when the right thing comes along.
When that moment arrives, it'll be an AI-first company where intelligent systems are the actual product, not a roadmap item. The kind of place where 15 years across fintech, logistics, and distributed systems is an asset — because the problems are genuinely hard and the domain is real.
Let's Connect
If you're building something in that space, I'm always up for a good conversation about hard problems.