40 systems-design lessons
Filter by discipline, or browse all. Each article links through to the live Zuma module — or the Mr Bismarck webhosting billing platform — it's drawn from.
Payments
Accepting Money From Anyone, On Any Rail
A payments layer that doesn't care whether the customer pays by mobile money, card, or bank transfer.
Read the article →
Payments
One Wallet, Six Rails: Reconciling Mobile Money at Scale
Why a single ledger — not six separate integrations — is what keeps a multi-currency wallet honest.
Read the article →
Fintech
Pricing Credit on Behaviour, Not Paperwork
Designing loan risk models on wallet transaction history instead of collateral documents.
Read the article →
Payments
Paying Creative Talent Without Losing 30% to Transfer Fees
Escrow-based freelance payouts designed around low-fee local rails.
Read the article →
Payments
Booking a Flight With the Money You Already Have
Ticketing checkout that accepts wallet balances, not just international cards.
Read the article →
Payments
Tickets That Can't Be Forged, Money That Reaches the Organiser
Cryptographic ticketing tied directly to settlement, cutting out resale fraud.
Read the article →
Payments
Making Emergency Giving Traceable, Without Making It Slow
Donation flows that satisfy accountability without adding friction at the worst moment.
Read the article →Get to know how I work
Hosting providers, MSPs, data centres, and platform or marketplace businesses — anywhere billing, automation, payments or e-commerce logic needs to hold together at scale. Most of my clients are in East and Southern Africa, but the systems I build travel.
A short discovery call, a written scope covering the specific systems involved (billing, payments, automation, or e-commerce), then build in phases with checkpoints — so you see working software early, not just a plan.
Both. I run implementation and ongoing monitoring/support packages, particularly for data-centre and hosting-automation engagements — sized by server count, from small providers to enterprise data centres.
Remotely, primarily. Most engagements are scoped and delivered without needing to be on-site, though I'm based in Nairobi and can meet in person for clients in the region if that's useful for discovery or handover.
I built my own hosting billing platform, Imara Cloud, specifically because off-the-shelf billing tools don't close the gap between what's invoiced and what's actually provisioned. I can also work inside a client's existing stack when migration isn't practical.
Yes — M-Pesa, MTN MoMo, Airtel Money, Tigo Pesa, HaloPesa, Stripe and card rails, reconciled into a single ledger rather than left as six disconnected integrations. This is the same architecture behind Zuma's multi-currency wallet.
Yes. The ERP pattern behind Zuma — billing, inventory, logistics and support tied into one system of record — applies well beyond hosting, and I've used it for education, tourism and non-profit platforms too.
It starts with mapping which incident types are safe to automate versus which always need a human sign-off — the same L1/L2/L3 governance model behind AIOP. From there it's integration work against your existing panel (cPanel/WHM, DirectAdmin, Proxmox) and monitoring stack, not a rip-and-replace.
It depends on scope — a billing-automation fix is priced differently from a full multi-vertical ERP build. I scope and quote after the discovery call rather than off a fixed rate card, since the right structure (fixed-price phase vs. ongoing retainer) depends on what's being built.
Access to whatever systems are in scope (panel, billing platform, payment provider dashboards) and one point of contact who can make product decisions during the discovery phase. I'll flag anything else specific once the scope is clear.
Didn't find your question?
Send me a message directly — I read and respond to every enquiry myself.