Jacob Mziya

The Social Cash Transfer Programme MIS

Malawi's Social Cash Transfer Programme puts money directly into the hands of the country's most vulnerable families. I work on the national information system behind it — the platform that registers households, manages payments, and keeps the programme honest. When this system fails, real families miss real money. That fact sits with me on every line of code, and it has taught me more about building carefully than any textbook ever did.

Civil Registration Systems

Before that, I worked on the systems that record births, deaths, and identity — the quiet infrastructure of being counted. A birth certificate seems like a small thing until you meet someone who doesn't have one. This work showed me that the most important software is often the least glamorous: foundational records that everything else in a country quietly depends on.

The Blantyre Prevention Strategy

In public health, information arrives scattered — across clinics, partners, and paper. I helped build the systems that gathered it into something decision-makers could actually use for HIV prevention planning in Blantyre. It taught me that data doesn't change anything by itself. What changes things is putting the right information in front of the right person at the moment they have to decide.

MonityIO

MonityIO is my consulting practice — where I help growing organizations build their digital foundations: cloud infrastructure, workspaces, websites, and workflows that hold together as they scale. It's also where I'm learning what it means to build a business rather than just software. Customers, value, trust. A different kind of system entirely, and in many ways a harder one.

Systems and infrastructure

Underneath all of it runs the unglamorous work I keep coming back to: data migrations, deployment pipelines, monitoring, and lately an AI-augmented workflow I'm building for my own consulting and engineering practice. This is the craft layer — the part of the work that never makes it into a portfolio, but decides whether everything above it survives.

A business is a system for creating value, and most of them fail at the definition, not the execution. I think a lot about what customers actually need versus what founders want to build, and about why small organizations outgrow their tools before they notice. Building MonityIO has made me humble about this — it's one thing to advise on systems, another to live inside one you built yourself.

The same software transforms one organization and dies in another, and the difference is never the code. It's the people, the incentives, the institution around it. So I think about engineering less as writing programs and more as designing the whole system — including the humans. Leadership, it turns out, is a systems problem too: the best leaders build things that work when they leave the room.

I've learned more from things that broke than from things that worked. Failure is feedback arriving faster than you wanted it. Curiosity is the only reliable engine I've found — it outlasts discipline, outlasts motivation, and it compounds. The trick is staying a beginner at something, always. The moment I feel like an expert everywhere is the moment I've stopped growing.

Fatherhood is the most honest feedback loop I know. Children don't listen to what you say; they run on what you do, repeatedly, over years. A marriage is the same — a small system of two people, held together less by grand gestures than by defaults and daily patterns. Raising children has convinced me that families are where people are made, and that no system I build at work matters more than this one.

AI is changing what one curious person can build, and I think about it daily — both as a tool I use and as a force reshaping the work I do. But I hold onto this: tools change every eighteen months; the judgment to know which problem is worth solving does not. The future belongs to people who understand systems deeply enough to know where the new tools actually fit.