Journey
Chapters, not a résumé
It starts with a teenager in Lagos who wanted to build robots and didn't own a laptop. It ends, for now, with payment rails carrying money for millions of people across a continent. Told the way it actually happened.
High school, Lagos
Humble beginnings
I wanted to build robots. I was in high school in Lagos, I didn't own a laptop, and I had no idea how the real world worked, which turned out to be an advantage, because nobody had told me yet what I couldn't do. Then one day my computer studies teacher started explaining HTML, and the idea landed with a force I can still feel. You could write words into a machine, and the machine would build what you described. It wasn't robotics. It was closer.
First contact
Discovering innovation
I went home and started digging, and the discovery was waiting in my own house. My brother was already doing this exact thing. Web development, real pages, real code. The mystery suddenly had a name and a person attached to it. I still had no laptop, so I learned the only way available to me. W3Schools on a phone screen, syntax memorized, everything rehearsed in my head until the rare moments a real keyboard appeared. People ask where I learned to work within constraints. That was the school.
Kwara State
Tasting freedom
Kwara State Polytechnic gave me three things at once. Admission, distance from everything familiar, and, at last, a laptop of my own. I had moved my whole life from Lagos, and I was determined to make the freedom count. So I doubled the load. Enrolled at HiiT for the Oracle Certified Java Associate alongside my regular coursework, and passed. Those years set the rhythm I still work by. Lectures by day, code by night, and no gap between wanting to know something and starting to learn it.
Bincom
Learning in production
My first real job. At Bincom in Lagos, programming stopped being something I practiced and became something people depended on. Tutorials never mention the parts that actually form you. Code reviews that sting and teach in the same sentence, clients whose deadlines don't care how you feel, the first time something you wrote broke for a real user, and the first time you fixed it. I arrived thinking I knew how to code. I left knowing how to work.
ConstantSee
Software for the worst moment
ConstantSee was a GPS-enabled emergency notification and response app. One tap alerted your pre-built response network, with a marketplace of emergency vendors nearby. I worked with the team to lay the foundation of the location system, integrating the backend of the GPS tracking engine and building out the mobile interface for customers in Ionic and Cordova. It was the first time my code carried real urgency. Nobody opens an emergency app casually. It works instantly, or it fails someone completely. Years before I touched money, ConstantSee taught me the shape of software people reach for at the worst moment of their day, and the standard that kind of trust demands.
Optisoft
The oldest promise
Optisoft handed me a new definition of the word promise. As a software engineer on an insurtech team, I helped build the software behind policies nobody thinks about until the day they need them, claims, underwriting, the fine print most people never read until it matters. A premium is a quiet bet that a promise will be honored later, and the code we shipped was the machinery that decided whether it would be. Insurance turned out to be the oldest financial product built entirely on trust extended in advance, paid for today, redeemed only in someone's worst month. It was a strange rehearsal for the industry I would spend the next decade in. Payments ask the same question insurance always has, will the system keep its word when it is actually tested.
Intelligent Innovations
Intelligent moves
Intelligent Innovations built software for other companies, so every few months handed me a new industry. A learning platform for millions of students. A way for ordinary people to own a slice of real estate. Then came the project that changed my trajectory for good, architecting a savings platform for Vetiva Capital Management, one of Nigeria's largest investment firms. I watched a real balance move because of code I had written. Funded. Grew. Withdrew. Nothing about the syntax was different from anything I'd shipped before, but the weight was. This was someone's actual retirement, not a demo account. Money entered my codebase that year, and it never left.
SeamFix
Finding the seams
SeamFix taught me the disciplines consumer work rarely does. Onboarding businesses instead of users, redesigning merchant flows, managing fleets of devices in the field. It was unglamorous the way plumbing is unglamorous, invisible until it fails, unforgivable when it does. Somewhere in that year my ambition quietly changed shape. I stopped wanting to build impressive systems and started wanting to build dependable ones.
Cutstruct
Laying foundations
At Cutstruct I got the assignment every engineer should get once. A blank repository and an industry waiting. I pioneered the server-side logic for LiveVend, a project-management platform for Africa's construction sector, and learned what founding systems demand. There is no prior art to hide behind. Every decision is load-bearing. You aren't just writing code. You're pouring the foundation everyone after you will build on. A fitting thing to learn from the construction business.
Blusalt
Salting
Blusalt handed me two educations at once. The first was building embedded finance into a product nobody expected to carry money. I led the engineering of a multitenant SaaS platform that businesses across African markets relied on for bulk SMS and campaign services, then watched the real work become the financial layer underneath it, utility payments and Blupayment-integrated cross-border transactions, running through infrastructure that was originally built to send messages. Identity verification and anti-money-laundering screening came with the territory, the price of operating legally across a dozen regulated markets, not the product itself. The second education came from the engineers who reported to me, my first real team, and the discovery that a team is a distributed system too, with its own throughput, its own failure modes, and its own single points of failure. One of which, I learned, was me. I've been debugging that system ever since.
Softpass
The company I closed
Between jobs leading other people's systems, I bet on myself. Fresh from building compliance infrastructure at Blusalt, I founded Softpass. Customer KYC, AML screening, and anti-money-laundering checks as a service. Compliance as infrastructure any company could plug into. The thesis was right, and I still believe it. But a product needs more than a correct thesis, and after a year of building it and selling it, I made the hardest call of my career. I wound Softpass down. Deliberately, cleanly, with nothing left in an unknown state, which is exactly how I'd want any system of mine to fail. It taught me what no salary ever could. What it costs to own every decision, why distribution beats elegance, and how it feels to switch off something you built from nothing. Every compliance system I've touched since carries its fingerprints.
Chipper Cash
Chippin' away
Then the stakes went continental. At Chipper Cash I lead a product engineering squad moving millions of dollars every month for users across Africa, virtual cards, investments, merchant APIs, the full spectrum of modern money. I still write the code that matters most. I architected the on-ramp and off-ramp services connecting our stablecoin rails to the Stellar Anchor Network, converting crypto to fiat and back across markets. But somewhere in the last few years the real craft changed shape. The engineers around me stopped being people whose pull requests I reviewed and started being a squad I was responsible for. The thing I'm proudest of building recently wasn't a service. It was a recovery framework that gives a struggling engineer an honest path back instead of a quiet write-up. I shape the architecture with our most senior engineers, then get out of the way of the implementation. That is the whole job, holding a high bar without becoming the bottleneck.
What's next
The next decade
The financial infrastructure of the next billion users is still being written. The rails, the ledgers, the invisible systems modern money will run on. I intend to help write it. And I intend to write it down as I go, so the engineers coming after us, the ones learning on their phones, waiting for their first laptop, start further ahead than I did.
Every chapter here began with someone deciding to bet on something uncertain. The next one hasn't been written yet.
Will you be part of it?