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.
Hosting Billing
The Affordable Webhosting Billing System Reseller Hosts Actually Need
Why reseller hosts pay enterprise prices for hobby-scale accounts — and what an affordable webhosting billing system actually looks like.
Read the article →
Hosting Billing
Delete WHMCS: Why Hosts Are Adopting a Custom Billing System Instead
WHMCS was built for a hosting industry that no longer exists. Here's what replacing it with a custom billing system actually involves.
Read the article →
Hosting Billing
Webhosting Automation: Ending Manual Suspension and Reinstatement for Good
Real webhosting automation means every payment event triggers the right server-side action instantly — not on the next cron run.
Read the article →
Hosting Billing
WHMCS Is Overrated: How Mr Bismarck Simplifies Webhosting Automation
WHMCS earned its reputation over two decades — but reputation and being the right tool for your hosting business today are different things.
Read the article →
Hosting Billing
ModulesGarden for WHMCS Plugins Is the Thing of the Past, Says Mr Bismarck
ModulesGarden made a business out of patching WHMCS's gaps. A billing system built right shouldn't have those gaps in the first place.
Read the article →
Hosting Billing
Modules and Plugins Are Slowing Down Your Webhosting Billing System
Every add-on module bolted onto a hosting billing system is another query, another hook, and another reason your client portal loads slowly.
Read the article →
Hosting Billing
Kenya Has a Replacement for WHMCS — Built for How African Hosts Actually Operate
A WHMCS alternative built in Kenya, for Kenyan and wider African hosting providers, with mobile money as a first-class citizen instead of an add-on.
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.