The challenge
Three dessert branches in Nairobi — South C, Parklands, and Kilimani. Each one was a different WhatsApp group. Stock was tracked in a shared Google Sheet that was always wrong by Friday. At the end of every day, someone had to manually cross-reference M-Pesa statements with orders. Deliveries were coordinated by phone. By the time the owner had a clear picture of revenue, the day was over.
The problem wasn't the business — it was growing fast. The problem was the tools. Three locations with three separate operating realities, connected only by a single exhausted operations manager.
How they use Maamul
One dashboard for all three branches
Every sale from every branch flows into the same dashboard in real time. The owner can see Parklands vs Kilimani vs South C revenue, orders, and stock — side by side — from a phone or laptop. No end-of-day calls. No spreadsheet consolidation.
M-Pesa reconciled automatically
Every M-Pesa payment is automatically matched to the order it was collected for. When a customer pays for a delivery at Kilimani, that payment logs against the order, the till, and the daily total — instantly. There is no manual reconciliation step. The books are always current.
Kitchen display per branch
Each kitchen has its own display. Orders from walk-ins, delivery apps, and WhatsApp all appear on the same screen. The kitchen team sees only their orders. No paper tickets. No lost orders. No cold food.
Stock moves with the sales
Every ingredient used is tracked. When stock at South C drops below the reorder threshold, the system flags it. The owner can transfer stock from Parklands without a phone call — the transfer is logged, approved, and the inventory updates on both sides.
“The biggest change wasn't the software — it was getting a full night's sleep. Before Maamul, every evening ended with 45 minutes of reconciliation. Now that 45 minutes is zero.”
Multi-branch Dessert Kitchen · South C · Parklands · Kilimani, Nairobi