About Me

Hi, I'm Kwaku. I'm a software engineer in Accra, and I build the systems that small businesses and regulated teams run on: the backend and its database, the web app the staff use every day, and the hosting and pipeline that keep it all running. I take one client at a time and stay from the first conversation to the day it goes live.

If you run a business on spreadsheets, WhatsApp threads and someone's memory, and you have reached the point where that costs you money or sleep, I am probably the person you are looking for.

What I build

Most of my work is an operations system for one business: the records it has to keep, the rules it has to enforce, and the screens its people use all day. Right now that is an inventory and compliance system for a licensed medicine shop, where every sale, batch and expiry date has to be accounted for and nothing can be quietly edited after the fact.

The same shape fits a clinic, a distributor, a savings group, a school office. Different rules, same need: one place where the truth lives, that the right people can change and everyone else can trust.

Why security is built in, not bolted on

By day I build identity and access management at the Central Securities Depository, Ghana's securities registry: who can log in, what each role may do, and how every change is traced. I hold the ISACA CISA Associate designation and Microsoft's SC-900, and from September 2026 I am reading for an MSc in Digital Forensics and Cybersecurity at GIMPA.

That background shows up in the work in practical ways. Who can do what is decided in the data model, not in a checkbox on a screen. Every action that matters leaves a record that cannot be rewritten. Logins are rate-limited, sessions expire, and the API is tested against the OWASP guidance before anyone calls it done. My final-year project, a student information system for more than 3,000 users, was built this way too, with two-factor login, role-based access and an audit log, and it is the reason I still work this way.

How the work goes

1. A conversation. You tell me what the business does and where it hurts. No forms, no fee.
2. A written scope. What ships first, by when, for how much. Small and fixed, so we both know what done means.
3. Weekly, running software. The repository is in your name from day one, and every week you see the real thing working, not a slide.
4. Live, on infrastructure you own. With monitoring, backups and a runbook another engineer could pick up. Then a support arrangement if you want one.

Before software

I studied psychology first, at the University of Ghana, before a second degree in computer science at Valley View University. It still shapes the two questions I ask most about any system: how will people actually use this, and what happens when they misuse it? I also hold the Ghana Stock Exchange securities certification, which means I can read a financial institution's rulebook without a translator, and I spent time in enterprise IT before writing software for a living, managing Active Directory and group policy for a savings and loans company and supporting Hyper-V and Microsoft Sentinel for an ICT firm.

Talk to me

Have a look at some projects, then tell me what you are building. I reply within two working days, and if I am not the right person for it I will say so and suggest who might be.