The Day the Lights Went Out.

The lights went out just after lunch. At first, nobody reacted — power cuts were part of daily life in Douala. They were inconvenient, but familiar. Someone joked that the electricity would probably be back before the coffee machine cooled down. But it didn't come back. And a few minutes later, the first salesperson walked into the IT office. "I can't check inventory." Then someone from the warehouse. Then a cashier. Within half an hour, the entire company had stopped asking when the electricity would return. Instead, everyone was trying to figure out how to run the business without the application they depended on every day.

Paper notebooks suddenly became valuable again. Warehouse staff began counting products by hand. Sales representatives walked across the building asking colleagues to physically verify stock. Managers delayed purchase orders because nobody trusted the inventory numbers anymore. Customers waited longer than usual. Some stayed. Some quietly left. The blackout lasted six hours — its consequences lasted much longer.

Bantu Distribution isn't a technology company. It's a growing retail business based in Douala, employing around fifty people and serving hundreds of customers every week. Products move between suppliers, warehouses, and store shelves every day. Orders are processed, deliveries are received, invoices are generated, and inventory changes almost every minute. Technology wasn't the product Bantu Distribution sold; technology simply made the business work.

Several years earlier, the company had built its own internal inventory and order management system. Built with Flask and MySQL, it allowed every department to work from the same information: sales teams could instantly verify stock availability, warehouse employees knew exactly what needed to be prepared, and managers could monitor inventory levels without walking through the warehouse themselves. Behind the scenes, only two people maintained the entire system — one software developer and one IT manager. That was enough. Until the business started growing.

Like many SMEs, Bantu Distribution made infrastructure decisions based on practicality. The application lived on a physical server inside the office. It felt sensible — the hardware was nearby, the files were nearby, and if something happened, someone could simply walk into the server room. That physical proximity created a reassuring illusion of control: as long as the server was in the building, everyone believed the business was safe.

"The real problem had never been electricity. The real problem was allowing the business to depend on a single office server."

Over time, however, the application became far more important than anyone had anticipated. Every department relied on it, every order depended on it, every stock movement passed through it. The software became more reliable while the infrastructure supporting it became a growing business risk. There were no automated backups, no disaster recovery process, no remote access for employees working outside the office. Every power cut carried the same silent question: "What happens if this one lasts longer than usual?" Nobody wanted to find out. Eventually, they did.

The outage arrived during one of the busiest sales periods of the month. For six hours, the company reverted to processes it hadn't used for years. Warehouse teams wrote inventory updates on paper, sales representatives manually confirmed stock with colleagues instead of trusting the database, and managers postponed purchasing decisions because inventory figures could no longer be verified. Every department invented temporary workarounds, and every workaround created another opportunity for mistakes.

When power finally returned, the work had only just begun. Every handwritten transaction needed to be entered manually. Inventory discrepancies had to be reconciled. Orders had to be verified. Mistakes had to be corrected before customers noticed them. Some customers had already walked away; others had bought elsewhere. By the end of the week, Bantu Distribution estimated that nearly 800,000 CFA francs in sales had been lost — not because demand disappeared, not because employees stopped working, but because information stopped flowing. That distinction changed everything.

The following Monday, the IT team had a different conversation. Nobody proposed buying a more powerful server, installing a larger UPS, or getting another generator. Those solutions treated the symptom, not the cause. Instead, the company asked a different question: "What if our business no longer depended on the office?" That single question changed every decision that followed.

The inventory platform moved into a managed cloud environment where availability no longer depended on whether the building had electricity. The migration itself was remarkably uncomplicated: the Flask application deployed without requiring specialist DevOps knowledge, and the MySQL database became a managed service instead of another responsibility on the IT team's shoulders. Daily backups started happening automatically. Software updates became routine instead of stressful. For the first time in years, the technology team wasn't spending its mornings checking whether yesterday's backup had actually completed — they already knew it had.

The impact extended well beyond the IT department. Sales teams could securely access the application over HTTPS whether they were inside the office or visiting customers. Managers travelling between locations could verify stock levels from their laptops or phones without calling someone back at headquarters. Warehouse supervisors no longer worried that another neighborhood blackout would stop deliveries. Even billing became simpler — instead of depending on international payment methods, infrastructure could be funded locally through Orange Money in CFA francs.