Marketplaces, management systems and payment platforms, mostly for companies in Ghana. Twenty-three of them so far, and I am still the one who gets called when something breaks.
I build software that outlives the developer who wrote it.
Worked with
Each one is something I designed, built or led. Open any of them for what it does, how it is put together and where it stands.
I would rather be the right answer for six things than a passable one for twenty. Anything outside this, I will tell you and point you at someone better.
Several applications sharing one API, one permission model and one source of truth. The kind of system where getting the data model wrong in month one costs you a year.
Dashboards, portals and back offices. The test is whether the person who runs the business can use it on a Monday without phoning me.
iOS and Android from one codebase in React Native and Expo. Built for the network conditions people actually have, not the ones on the spec sheet.
Corporate and marketing sites that load fast, rank, and pass an accessibility audit rather than claiming to.
Paystack, Mobile Money and bank settlement, wired so that a webhook arriving twice cannot charge a customer twice.
Live on infrastructure you own, documented well enough that the next engineer does not need me on a call.
If a client is already paying for cPanel shared hosting, the answer is PHP and MySQL and a build that runs there. Not a Kubernetes cluster they cannot afford to keep.
Several of these systems run businesses I have a stake in. That means every shortcut I might be tempted to take, I end up living with. It is a useful thing to have at the back of your mind at two in the morning.
Screens are cheap to redraw. A data model is not, once there is a year of real customer records sitting on it. So the model and the permission map get decided in week one, while changing them still costs nothing.
Every platform I build holds money as whole pesewas, moves balances inside a locked transaction, and treats the ledger as append-only. Reversing a payment writes a new row. It never quietly edits the old one.
If a role cannot see an action, the endpoint behind it still refuses that role, and there is a test proving it. Anything else is a permission system that works until someone opens the network tab.
Everything ships on infrastructure in your name, with credentials, runbooks and architecture notes written down. If you bring in someone else next year, they can pick it up without calling me.
No three months of silence followed by a reveal. If something is going to slip, you hear it the week it starts slipping.
We write down what it has to do and, more usefully, what it does not. Fixed deliverables. Nothing appears in month three that was never agreed in month one.
The data and the permissions get settled first. These are the decisions that turn expensive once there is real customer data sitting on top of them.
Delivered in stages you can open and use. You review running software, not screenshots and a status report.
Tests on the paths that carry money or records. An accessibility pass, a security pass, and the error handling checked before anyone outside sees it.
Deployed on infrastructure in your name, with the credentials, runbooks and architecture notes to match. You are never locked to me.
A couple of sentences about the problem is plenty. If it is not something I should take on, I will say so rather than quote you for it.