MM Muhindo Mubaraka
Consultancy

Bringing me in

I take on a small number of engagements at a time, and I would rather tell you early that I am the wrong fit than take work I cannot finish properly.

What I take on

Enterprise system design

Architecting and building multi-platform information systems — web, Android, iOS, USSD/SMS — that run reliably at national scale and offline-first in the field.

Databases & data governance

Schema design, query optimisation, migration, backup and recovery across MySQL, PostgreSQL and MongoDB, with data governance built in.

Infrastructure & security

Linux server administration, Docker, Nginx, cloud deployment, and cybersecurity best practice — SSL/TLS, RBAC, encryption and secure APIs.

ICT strategy & delivery

Digital transformation strategy, IT policy, vendor and stakeholder management, and end-to-end project delivery from requirements to rollout.

Integration & interoperability

Payment gateways, GIS/GPS, biometrics, barcode/QR and USSD/SMS — integrating systems so government and private data move together.

Training & capacity building

Hands-on staff training and user enablement across districts, plus technical documentation and ongoing support that makes systems stick.

How an engagement runs

A conversation, at no cost

You tell me what you are trying to solve. I tell you honestly whether it needs the system you think it needs, and whether I am the right person to build it.

Requirements, with the people who will use it

Time with the actual users — field officers, clerks, inspectors — not only the managers commissioning the work. This is the step most failed systems skipped.

A written scope and a fixed price

What is included, what is not, what it costs and when it lands. Anything outside it is a change we agree on in writing, not a surprise on the invoice.

Build, in the open

You see working software early and often, so a wrong assumption costs a week rather than a project.

Handover and training

Documentation, and your staff trained until they can run it without me. Support afterwards is a choice you make, not a dependency I engineer.

Whether we are a fit

Good fit

  • A system real people depend on daily, not a brochure site
  • Government, NGO or private operations at national scale
  • Field data collection where the network cannot be relied on
  • Replacing paper, spreadsheets or a system nobody maintains
  • You want your own team able to run it afterwards

Probably not me

  • A logo, a brand identity or purely visual design work
  • Something needed in full next week
  • Work with no access to the people who will use it
  • Rescuing a codebase with nobody left who understands it
That is the whole story. The next step is yours. Hire Me Start Learning