Five things we build. Each one proven by a system running now.
ISP & network operations
Optical monitoring, billing and payments usually live in three separate platforms that were never built to talk to each other. A connection can be down for hours before anyone technical knows, because the only signal is a customer complaint.
Payments & mobile money
M-Pesa integration is often the part that gets rushed — paybill and till behave differently, bank webhooks arrive asynchronously, and reconciling a payment to the right account by hand doesn't scale past a handful of transactions a day.
Ecommerce & growth
Most stores in this market launch on a template with no measurement attached. Traffic arrives, sales happen, and months later nobody can say which channel actually produced them — by which point the data is simply gone.
Identity & attendance
Card-based attendance has one structural weakness: a card only proves the card was present, not the person. It can be handed to someone else, and most systems have no way to know.
Platform engineering
Systems that handle money and network infrastructure can't be deployed the way a personal project is. A missed migration backup or an unscanned image is how an outage becomes a data-loss incident.